[Gelöst] Memcached prevents field group title from saving

[Author]

Artikel

[sarahP]

When I add a field group title for a custom repeatable Post Field Group I created with Types, it does not save. This happens whether I add the field group title when I am first adding a repeatable group item or if I go back later and edit the item. I add the title, click update, and when the post edit screen refreshes, the title is once again blank as shown in the screenshot.

After some troubleshooting, I found the cause appears to be having Memcached turned on. I have this enabled via my host's (SiteGround) plugin, SG Optimizer. When I disable Memcached via the plugin settings, the field group titles save.

Is there any way to fix this? I would like to have Memcached enabled AND to be able to save field group titles too. Thanks!

[Minesh]

Hello. Thank you for contacting the Toolset support.

Well - just wanted to double check is it really related the memcached or plugin SG Optimizer?

What if you try to deactivate SG Optimizer plugin or all non-Toolset plugins?

[sarahP]

Hi Minesh,
I am pretty sure it is related to memcached which is set by my host and controlled via the SG Optimizer plugin.

I started troubleshooting by disabling plugins. When I deactivated the SG Optimizer plugin, the field group titles saved.
Next, I reactivated SG Optimizer and disabled the options within the plugin one by one to find out what form of caching was causing the problem. Only disabling memcached restored the ability to save field group titles.

I can also disable memcached directly from cPanel. When I do this, the field group titles save. So, the problem appears to not be with the plugin but with memcached itself.

-Sarah

[Minesh]

Well - can I have problem URL where I can see the repeating field group as well as access details.

*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin and FTP) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.

I would additionally need your permission to de- and re-activate Plugins and the Theme, and to change configurations on the site. This is also a reason the backup is really important. If you agree to this, please use the form fields I have enabled below to provide temporary access details (wp-admin and FTP).

I have set the next reply to private which means only you and I have access to it.

[Minesh]

Thank you for sharing access details.

I'm able to see the issue and reported same to our next level support for further debugging. Please hold on for further updates.

[Minesh]

I've got the news that we have develop version available which contains the fix for this issue.

Is that OK with you if I try to upload the develop Types plugin version on your test site to check if that help to fix the issue?

[sarahP]

That's great to hear! Yes, you may do what you need on the test site.

[Minesh]

I've uploaded the Develop Types version on your test site and I can see that the issue is fixed.
(Once you test it, remove this version and switch to stable Types version.)

Please note that official fix will be shared with near future release of Types. We do not recommend to use Develop version with production sites, so please always keep in mind to use the stable Toolset plugin version available on your accounts download page.

[sarahP]

Thanks, Minesh! I see that the problem is solved with the Types developer version you uploaded to my test site (I will go ahead and delete this site). I look forward to seeing the fix pushed out in a near future release for use on my live site. Kudos to your developers for finding and fixing this issue! 🙂

[Minesh]

I would like to update you that Types version 3.3 is finally released. 🙂

[sarahP]

It is working nicely on my site now. Thanks, Minesh!