Skip Navigation

[Resolved] Types plugin displays errors

This support ticket is created 6 years, 9 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
- - 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00
- - - - - - -

Supporter timezone: Asia/Ho_Chi_Minh (GMT+07:00)

Tagged: 

This topic contains 3 replies, has 2 voices.

Last updated by Pat 6 years, 9 months ago.

Assisted by: Beda.

Author
Posts
#614636

Pat

Hello,

I just updated Types and other toolset plugins and I'm getting those errors :
upplied for foreach() in /home/mysite/wp-content/plugins/types/vendor/toolset/types/embedded/includes/custom-taxonomies.php on line 63

Warning: Invalid argument supplied for foreach() in /home/mysite/wp-content/plugins/types/vendor/toolset/types/embedded/includes/custom-types.php on line 377

Warning: Invalid argument supplied for foreach() in /home/mysite/wp-content/plugins/types/vendor/toolset/types/embedded/includes/custom-types.php on line 377

Warning: Invalid argument supplied for foreach() in /home/mysite/wp-content/plugins/types/vendor/toolset/types/embedded/includes/custom-types.php on line 377

Warning: Invalid argument supplied for foreach() in /home/mysite/wp-content/plugins/types/vendor/toolset/types/embedded/includes/custom-types.php on line 377

Warning: Invalid argument supplied for foreach() in /home/mysite/wp-content/plugins/types/vendor/toolset/types/embedded/includes/custom-types.php on line 377

Warning: Invalid argument supplied for foreach() in /home/mysite/wp-content/plugins/types/vendor/toolset/types/embedded/includes/custom-types.php on line 377

Warning: Invalid argument supplied for foreach() in /home/mysite/wp-content/plugins/types/vendor/toolset/types/embedded/includes/custom-taxonomies.php on line 76

Warning: Illegal string offset 'category' in /home/mysite/wp-content/plugins/types/vendor/toolset/types/wpcf.php on line 404

Warning: Illegal string offset 'post_tag' in /home/mysite/wp-content/plugins/types/vendor/toolset/types/wpcf.php on line 404

Warning: Cannot modify header information - headers already sent by (output started at /home/mysite/wp-content/plugins/types/vendor/toolset/types/embedded/includes/custom-taxonomies.php:63) in /home/mysite/wp-admin/includes/misc.php on line 1114

Can you tell me what I need to do in order to retrieve a normal situation?
Regards
Pat

#614813

The last Toolset Types update was released December 7th, 2017.

We had no reports of PHP failure like this since then.

Toolset CRED was updated recently although that just fixed some issues that were not related to support forum reported bugs.

I also tried to replicate such an issue but when I update or install all the Plugins and Theme you do, I do not see any error.

If you do not have explicit steps to replicate this, I think the best for us would be a copy of your site.
I can then determine what happened on this specific install.

Even better would be if you have a backup of before the issue happened, so I could actually observe what happens during the update.

And that would also be the only current solution for you, if you want to retrieve a normal situation, as I currently cannot replicate this issue, hence I do not know what exactly happens.

It seems according the error that the plugin cannot get any post type or taxonomy at all from your database.
This would mean not even the native post types and taxonomies are received.

Then the code fails. This is usually impossible, that is why I need to analyze this locally.
Do you see your post and taxonomies types in the Toolset backend?

Can you also send me a Duplicator package?
https://toolset.com/faq/provide-supporters-copy-site/

#614879

I have tried all the way back to Types 1.8, which is where we (with Types 1.9.1) started to introduce the code that is creating the issue on your site.
We had a problem with that update in-between (1.9) and 1.9.1 holds a code that urns just once, so to ensure a smooth update.
And that part of the code is the problem here, it does not receive the expected data.

But as tested on the duplicator, it seems to have been around much earlier, as even with 1.8.x I see those warnings.

I cannot spot why the data is wrong a t this point.
The code seems to receive a serialized array, which should not be the case, as PHP cannot read that, on top, the array is trunked off in the middle, not closed.

This is unexpected and not replicable so far.
I suspect, the issue is much older, and it's source nests in the past versions all the way down to 1.8 and earlier.

Here is a solution I found:

- disable all plugins and the theme, use Twenty Seventeen instead
- Enable the latest Types. The errors will happen.
- Navigate to this exact URL:
wp-admin/admin.php?page=wpcf-ctt
- You should be able to click on edit, for each taxonomy (only the native ones)
- just save them, nothing else.

Now, for me, the issue is solved.
After re-saving the array of Taxonomy (the inbuilt) by simply pressing "save" in each respective Taxonomy Edit screen, it's solved.

Can you confirm this on a test site as well?

#614988

Pat

Hi Beda,

Perfect. Everything works fine now.
Many thanks for your support.
Regards
Pat