The Toolset Community Forum is closed, for technical support questions, please head on to our Toolset Professional Support (for paid clients), with any pre-sale or admin question please contact us here.
This support ticket is created 6 years, 7 months ago. There's a good chance that you are reading advice that it now obsolete.
This is the community support forum for Types plugin, which is part of Toolset. Toolset is a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients and people who registered for Types community support can post in it.
Thank you for reaching out to us. I can see that you are using older version of Toolset plugins (Types, Views, Access, Cred, Map, etc ). Please update ALL Toolset plugins to it latest official release. Or you can download it from your account: https://toolset.com/account/downloads/
- If issue still persists, please try to check it by deactivating all third-party plugins (except Toolset) and switching back to the Default Theme (e.g. Twenty Sixteen theme) to see for any possible conflicts with any of the plugins or themes.
I've updated all WP-Types plugins to the latest version, deactivated all non-WP-Types plugins, and switched to Twenty Seventeen, and the issue remains.
I set the permalink structure to /%category%/%postname% and the issue remains.
This is .htaccess:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule .* - [E=noabort:1]
RewriteRule .* - [E=noconntimeout:1]
</IfModule>
I have checked your site and see the error messages when tried to update any Custom post:
Notice: unserialize(): Error at offset 1042 of 2202 bytes in /var/www/vhosts/1/141766/webspace/httpdocs/wp-content/plugins/types/application/models/helper/condition/views/views_exist.php on line 28
You need to go through the database and correct the character counts for the affected URLs.
As mentioned in the summary of above ticket: It is best not to modify serialized data in the database manually. If you must do this, ensure that all serialized strings containing URLs were converted properly. If the number of characters in a migrated URL string do not match the number of characters in the original URL string, serialization errors may occur.
