Cannot view Custom Fields screen after Toolset Access upgraded to 2.4.3.3

This thread is resolved. Here is a description of the problem and solution.

Problem: After upgrading to Access 2.4.3.3, I am no longer able to use the Custom Fields editor screen in wp-admin. My site uses the M2M betas.

Solution: There appears to be a compatibility issue with Access 2.4.3.3 and the M2M betas. For now you can either install the stable Types and Views (no M2M) or downgrade to Access 2.4.3.2.

This support ticket is created 6 years, 10 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.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	-	-
13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	-	-

Supporter timezone: America/New_York (GMT-04:00)

Tagged: Access plugin

This topic contains 5 replies, has 2 voices.

Last updated by Chris 6 years, 10 months ago.

Assisted by: Christian Cox.

Author

Posts

January 11, 2018 at 2:50 pm #605463

Chris

After upgrading to Toolset Access 2.4.3.3 I can no longer view the Custom Fields screen - it looks as if the page does not load completely. (See attached screenshot.)

I've set up a test site which shows this, with all other plugins deactivated: hidden link
To access this page please use username 'flywheel' and password 'witty-language'.

January 11, 2018 at 7:47 pm #605545

Christian Cox

Hi, I'm able to use those login credentials to get past the basic HTTP authentication, but I cannot log in to the wp-admin area. Can you provide login credentials in the private reply fields here? I see this is a Flywheel environment. It is quite difficult to debug issues on Flywheel sites because they don't allow cloning plugins and we often need to install a copy of your site locally to diagnose problems.

January 14, 2018 at 4:15 pm #606074

Christian Cox

Okay thanks for the additional information. I see the problem, and it appears to be caused by an interaction between the beta plugins and Access 2.4.3.3. Let me inform my 2nd tier support team about this so they are aware of the bug in the betas.

For now, I recommend downgrading to Access 2.4.3.2, or switching to the stable versions of Types and Views if you do not need the features from the beta versions. I will let you know if I receive any additional information about the conflict with the beta plugins. Thanks for the report!

January 15, 2018 at 11:08 am #606253

Chris

Hi Christian,

That's great, thanks for looking into this. As you suggest, I'll revert to 2.4.3.2 for now.

Best wishes,

Chris

January 16, 2018 at 2:30 pm #606759

Christian Cox

Hi, just a quick update to let you know the latest version, Access 2.4.3.5, has been released and is now compatible with the M2M beta plugins.

January 16, 2018 at 2:53 pm #606773

Chris

Great!

I have installed that new version, and all is now working fine on my site.

Thanks again for your help.

- Chris