Yea, the UI has almost always been horrible, and a lot of it was due with it being designed with HTML4.01, but with APL v0.3, HTML5 had just released. Designs during that time weren’t the best, and usually took extensive workarounds. However, things are different now days, and WordPress has also continued to improve, especially with the community and its guidelines/documentation.
That being said, there is a new version (v0.4 Early Beta) that focused on UI and backend data structure. It’s still familiar, but the UI and UX is drastically improved. It is still in early beta, but I’ve been using it in production testing, and have a few more things I want to iron out.
You mentioned Divi, and I’ve commonly work with it with others. However, I see plenty of limitations where APL could improve or fill in. I’ve also been working on a project to extend and possibly support APL. Designs will also eventually become interchangeable. I am curious what other would think, but have held off on making any kind of announcements. At least until community support reaches a stable point
—————————–
In regards to the issue…
I do have the WP Function already added, but it good news to see you were able to quickly & easily navigate to the code…but I also took extra steps to make it well documented. It’s possible Divi found a workaround. My worry is if it is intentional by WordPress.
Simply for reference, the code…
$encoding = mb_internal_encoding();
$return_str = strip_shortcodes( mb_substr(
strip_tags( $this->_post->post_content ),
0,
$atts_value['length'],
$encoding
));
Adding code to integrate 3rd party is something I prefer not to do with APL being a public release. I do think adding custom filters to some of the internal shortcodes would help significantly, and it’s something I’ve slowly been doing as I work on the code.
I think I would mark this issue as “Add custom filters to Internal Shortcode(s) [post_excerpt]”
-
This reply was modified 7 years, 5 months ago by
EkoJR. Reason: Fixing code section