June 21, 2015 at 6:15 pmParticipant
I became aware of Aesop reading an article from N. Weller and there were references, of course, to using it with Divi but when I tried to click the “Add Components” button from inside the Divi page builder (in a text module) it does not open the Aesop interface (although it works fine inside the standard WP page editor). Is this an issue with the Aesop “Add Component” button or should I be asking Elegant Themes this question. Regardless, very innovative work. I’d just like to be able to use it inside Divi. Thank you.June 22, 2015 at 2:51 pm
We are not too familiar with the Divi page builder, but it would seem that the Divi page builder shows on the front end of the site, correct? There haven’t been any issues with other themes causing this type of clash in the post editor as Aesop Story Engine was built to work in the standard WP post editor. However, we do have a front-end editing plugin called Lasso that allows Aesop to be used on the front-end of the site. If you use Aesop in the post editor and Divi for whatever else in its page builder form, you may be golden.
Let me know if that clarifies things.June 22, 2015 at 3:33 pmParticipant
Thank you for responding. Actually, the Divi Page Builder is an alternative visual page building tool that is activated as an alternative to the standard WordPress editor within the page or post editing area on the back end. It consists of various sections, rows and modules that are used to construct the page. One of the modules is a text module that makes use of a similar version of the wordpress text input area and that is where your “add component” button does show up – same as if I were editing text in the WordPress editor. The only difference is that, within the Divi instance of the text editor the button doesn’t activate anything whereas in the standard WordPress editor, the button works fine. I’m afraid that I don’t know anything deeper, technically, as to how the two text editors are different, however they look exactly the same and have all of the same functions and buttons except the Divi text editor opens up in a separate window. I’ll look at lasso and I can also just use the Aesop functions inside the standard editor but it would be helpful at some point to learn if there is something that is keeping it from working. Thank you. JohnJune 24, 2015 at 2:11 pm
Thanks for the clarification as those were many of the things I had in mind that Divi was up to. Aesop could be pulled into Divi, but that would be on their part, as most themes generally use the post editor, which is where ASE can be accessed. Maybe they would be willing to incorporate ASE. Let me know if you need anything else.October 17, 2015 at 10:32 amParticipant
I am using Divi, and I have installed ASE. I am getting a bit limited use of ASE in my posts though as I am not very good at crafting CSS from the ground up. I wish there was a CSS file that contained some basics that we could use.
It would have to use CSS classes that is guaranteed not to interfere with anything else out there, and that goes well together with my wish that all plugin producers got their own “handle” or CSS class. So e.g. all CSS produced by ASE could actually start with .ase 🙂
Is there a CSS document out there that has a basic, working set that will work with just about any template? Preferrably a well commented one…October 17, 2015 at 4:16 pm
You can check out all of source code here: https://github.com/bearded-avenger/aesop-core (where we have laid out all of our classes) and how to work with ASE in our quick start guide here: https://aesopstoryengine.com/quick-start-guide.
If your theme does not natively support Aesop Story Engine, add the code snippet below to your child theme’s functions.php file, or add using Code Snippets plugin to enable Extended Style Support. This will load one CSS file for any of the items that you include in the snippet below:
add_theme_support(“aesop-component-styles”, array(“parallax”, “image”, “quote”, “gallery”, “content”, “video”, “audio”, “collection”, “chapter”, “document”, “character”, “map”, “timeline” ) );