Error: add define(“APL_ALLOW_PHP”, true); even when present

Disregard that last, this was a bug.

JUST recently Fixed [php_function] Undefined Constant with an update I’m about to push (APL 0.3.5). I thought it was the last update I had added it.

I decided to push an early update mainly because of the File Structure & Class/Object changes that I prefer to do before 0.4 (which has a database update). In your case, it is a good thing I’m pushing an early update.

Keep a look out for an update for the next few hours, and hope to hear positive results 🙂

I may have to run this through a few tests, and like you say, removing $this->_post is only temporary.

Currently doing some much needed organizing and cleaning after the recent code push. So it may be a little while. However, I do suspect these…

1. [post_meta] is being passed to another ‘internal’shortcode – This is likely NOT the issue, but “internal shortcodes” was designed to be encapsulated, and only work within the Internal Shortcodes Class. However, I designed everything to be loaded before the [php_function].
2. The WP_Post has nothing to reference to in that instance while in another function/shortcode that also uses $wp_query. Which is still odd considering there should still be a valid $post. I’ll need to confirm this theory first.
3. Removing $this->_post prevents the defaults, and fixes the issue, but is still being stored in APL_Internal_Shortcodes::_replace(). This is rather interesting, but falls under #2. However, in one of the 0.3.X versions, I did remove WP_Post from being passed, but quickly added it back in to prevent issues with other sites.
4. It is an issue with the WP Review Plugin code when getting the meta data; which seems like a function rather than a value to reference to, but I still want to confirm this scenario ( personally haven’t had much need for meta data…yet ). Please note: I might not be able to help if it is a Premium Plugin/Feature.

Hope this helps some, but I at least wanted to add my thoughts on it for later if needed. I’ll need some time until I can reproduce this, and it may even end up on the GitHub Ticket list.

• This reply was modified 8 years, 11 months ago by EkoJR. Reason: Converted Markdown to HTML

You’re absolutely right too! I have a draft written on how to use it, but still have yet to posted it on the Wiki, and I probably should sooner rather than later; considering I even forgot mentioning passing the $post, and the error it throws.

I suppose my delay on the Wiki is mainly due to the amount of work that has been going on in the backend of APL, and the amount of changes that could take place. Plus, I have been trying to force myself to be more user-friendly on explaining, but with APL being somewhat of a Web Design tool. It makes it a little bit harder to explain through an additional layer.

I’ve also been thinking about re-coding the php_function, or alt, to make the $post an optional variable.