Warning: First Parameter must be an object or the name of an existing class. Suggestions?

[stotman]

Hi team,
I have three issues this morning, but they may be related. I do not know if I changed something or it is an issue with the update.

Issue 1:
I am receiving this warning over my pages.
Warning: First parameter must either be an object or the name of an existing class in /home/auminist/public_html/wp-content/themes/pro/framework/functions/global/helpers.php on line 137

Issue 2:
It is not pulling the content which existed before but now says “There is nothing to show right now.” Could this have something to do with using custom post types? I haven’t made any changes to them and they were working previously. Also, it is working on one of the custom post types, but not the others.

Issue 3:
When I go into the cornerstone editor, I am getting this warning.

Warning: Creating default object from empty value in /home/auminist/public_html/wp-content/themes/pro/cornerstone/includes/classes/content/class-content-preview-frame.php on line 80

All my plugins and themes are up-to-date. I also tried to disable all the plugins but I was still having issues with the cornerstone editor even after doing that.

WordPress Version 4.8.3
Pro Version: 1.2.4
Child-Theme

[stotman]

Update:
Solution (I think). So the problem was that I enabled “removed “category/”” option in the Yoast SEO plugin. While this is what I wanted to happen, it is not playing nice with Pro. Alternatively, I was able to remove it using a redirect and it worked fine. I don’t know if this is the best practice or anything but it is working. I’m open to other suggestions.

[lely]

Hi There,

Those are just warning and it should not interfere with how the builder works. Please check wp-config.php file on the root folder of you installation and make sure that the following line is set to false.

define('WP_DEBUG', false);

Then try disabling removed category from YOAST and then check again. If issue persists, please share site URL, credentials and page with issue on a secure note.

[stotman]

Right, the bulider issue was something separate that occurred because of a custom post type issue. I’m new to cpt and I had created some unnecessary php files that were causing a conflict. I may not be completely out of the woods yet but for now it’s working. Steep learning curve with php.

[lely]

Glad you have what was causing the issue!

If you have further question, please do open a new thread.