Viewing 6 reply threads
  • Author
    Posts
    • #11279
      nlbailey
      Participant

      I took over management of a site that has Piklist setup for a CPT. I discovered that another CPT that appears to be handled by another plugin is not working properly though. I can view all the entries that the plugins CPT has but when I try to add a new one I get:

      PHP Fatal error: Uncaught Error: Cannot use object of type redrokk_metabox_class as array in /home/public_html/wp-content/plugins/piklist/includes/class-piklist.php:2351
      Stack trace:
      #0 [internal function]: Piklist::sort_by_args_order(Array, false)
      #1 /home/public_html/wp-content/plugins/piklist/includes/class-piklist-meta.php(413): uasort(Array, Array)
      #2 /home/public_html/wp-includes/class-wp-hook.php(292): Piklist_Meta::sort_meta_boxes(”)
      #3 /home/public_html/wp-includes/class-wp-hook.php(316): WP_Hook->apply_filters(NULL, Array)
      #4 /home/public_html/wp-includes/plugin.php(484): WP_Hook->do_action(Array)
      #5 /home/public_html/wp-admin/admin-header.php(147): do_action(‘admin_head’)
      #6 /home/public_html/wp-admin/edit-form-advanced.php(425): require_once(‘/home/discov96/…’)
      #7 /home/public_html/wp-admin/post-new.php(75): require(‘/home/discov96/…’)
      #8 {main}
      thrown in /home/public_html/wp-content/plugins/piklist/includes/class-piklist.php on line 2351

      There is a conflict between the two but I don’t really know where to start. Is there a way to disable Piklist from interacting with this post type in the admin? It works fine on the frontend but the conflict doesn’t allow new items to be added. Any thoughts are appreciated.

    • #11280
      Steve
      Keymaster

      @nlbailey– Welcome to the Piklist community.

      Searching for redrokk_metabox_class I come up with files like this: https://gist.github.com/michael-cannon/9359973. I’m not sure this is registering CPT’s, might just be metaboxes.

      Can download the codebase to your local and search for redrokk_metabox_class to identify the plugin or files and what they are doing?

    • #11281
      nlbailey
      Participant

      Yeah, it appears to be the plugin Testimonials Widget.

      Testimonials Widget

      You are correct the redrokk_metabox_class does appear to be creating meta boxes.

    • #11282
      nlbailey
      Participant

      I am assuming that Piklist doesn’t like the meta boxes that the plugin is using. Is there any way to disable Piklist from processing that CPT?

    • #11283
      Steve
      Keymaster

      I can’t reproduce. The Testimonial Widget saves new testimonials for me.

      Please try this:

      1) Disable all other plugins except these two and see if that fixes the issue. If so, start reactivating them one by one until you find the conflicting one.
      2) Switch to one of the default themes and see if that fixes the issue. If so, you will need to look into the theme.
      3) What version of WordPress are you running?
      4) What version of Piklist are you running?
      5) What version of the Testimonials Widget are you running?

      • #11284
        nlbailey
        Participant

        So I have been able to replicate the issue in a test environment.

        1)It looks like the key is Advanced Custom Field which is also being used on the site. If you have Piklist, the testimony plugin and ACF installed and activated then try to add a testimony you will see the error. As a note, I don’t have ACF setup with the Testimony CPT at all so it’s not doing anything specifically with that CPT.
        2) This happens with the default theme on my test site
        3) Test site had 5.5.5 installed, updated to 5.7.2 and still can replicate
        4) Piklist version 1.0.11
        5) Testimonial Plugin version 4.0.1

    • #11285
      nlbailey
      Participant

      I added a temporary check in class-piklist-meta.php for post type to bypass the sort. This allows the page to load for now.

    • #11286
      Steve
      Keymaster

      @nlbailey– Glad you were able to get around the issue. We’re still investigating. I’ll let you know what we find.

Viewing 6 reply threads
  • You must be logged in to reply to this topic.