• Resolved Gabor Lippert

    (@lunule)


    Hi,

    I started a support topic on the ACF Extended plugin’s WP support forum, regarding errors in the debug.log file such as

    Error "Warning: Attempt to read property "ID" on null in [plugins_dir]\acf-extended\includes\module-post.php on line 39"

    I just received a message from the plugin author, saying “I took a look at the Profile Builder plugin, and it looks like it doesn’t correctly set a?$post_id?when using WP metaboxes, leading to this error in ACFE.”

    Not sure if this is still an issue or already fixed, but I thought it’s worth letting you know about it.

    The referenced ACF Extended topic can be seen here:
    https://www.ads-software.com/support/topic/error-warning-attempt-to-read-property-id-on-null/

Viewing 5 replies - 1 through 5 (of 5 total)
  • Hello,

    ACF Extended developer here ?? I just wanna add some context as it might look cryptic right off the bat.

    Small note: this issue is not a compatibility issue with ACF Extended only, as it may happen with any plugin.

    The problem comes from the code in \profile-builder\assets\lib\wck-api\wordpress-creation-kit.php:1543

    function wck_settings_page_add_meta_boxes() {
        global $post;
        do_action( 'add_meta_boxes', $this->hookname, $post );
    }

    In this function the WordPress hook add_meta_boxes is manually triggered. As we can see in the hook documentation, this action should provide the $post object as second argument.

    In your code you try to provide it with global $post. But since this code is executed on your plugin’s admin page: /wp-admin/admin.php?page=user-email-customizer, there is no $post to retrieve/provide.

    As a consequence null is passed as second argument. The problem became visible in my plugin as I add_action('add_meta_boxes' ...) and check the $post argument to add different metaboxes.

    But this problem may arise with any plugin that use add_action('add_meta_boxes', 'my_add_meta_boxes', 10, 2) (which is pretty standard) and by visiting your Email Customizer settings page.

    I hope it’s now more clear.

    Have a nice day!

    Regards.

    Plugin Author Georgian Cocora

    (@raster02)

    Hello @lunule, @hwk-fr,

    Thank you for the details. I’ll see what we can do in order to prvent this error.

    Regards.

    Plugin Author Georgian Cocora

    (@raster02)

    Hello @lunule, @hwk-fr,

    The issue should now be fixed with the latest update of the plugin.

    Let me know if you still encounter issues.

    Regards.

    Hello!

    Nice! I just tested with the previous version of my plugin, and I confirm the error is fixed with the latest version.

    Side note: The “Email Customizer” admin page is now empty. I don’t know if it’s intended or not, just saying.

    Regards.

    Thread Starter Gabor Lippert

    (@lunule)

    Hey Georgian,

    ?? Huge thanks for the update.

    And I can confirm Konrad’s report: the Settings > Email Customizer tab is completely empty now (both the User Emails and the Administrator Emails tabs). ??

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Conflict with ACF Extended’ is closed to new replies.