[Resolved] Custom fields bugs since latest update

[Author]

Posts

[matthewL-7]

Hi

Custom fields are no longer appearing on post types for some users since the update.

Also I can't edit content templates they don't load correctly anymore either since the latest update.

Are you aware of bugs with the latest update?

[Nigel]

Hi Matthew

The problem with custom fields sounds like this known issue which should be fixed in a Types hotfix later today or tomorrow: https://toolset.com/errata/cannot-edit-or-see-toolset-custom-fields-if-using-access-for-any-role-below-administrator/

I haven't heard any reports of problems editing content templates, can you give more details?

Are you seeing any JS errors in the console, or PHP errors in the logs?

[matthewL-7]

Hi Nigel,

Any update on this bug being fixed? This is causing a lot of issues.

Also I have attached a screenshot of the content template issue I am experiencing on both Safari and Chrome.

I looked in console on Chrome (not sure if this is the right place?) and this is what I saw:

knockout-3.4.0.js:7 Uncaught ReferenceError: Unable to process binding "spinnerActive: function(){return isAnySectionUpdating }"
Message: isAnySectionUpdating is not defined
    at spinnerActive (eval at parseBindingsString (knockout-3.4.0.js:7), <anonymous>:3:66)
    at update (ct-editor.js:12)
    at function.a.B.i (knockout-3.4.0.js:7)
    at Function.Pc (knockout-3.4.0.js:6)
    at Function.Qc (knockout-3.4.0.js:6)
    at Function.aa (knockout-3.4.0.js:6)
    at Object.a.m.a.B (knockout-3.4.0.js:6)
    at knockout-3.4.0.js:7
    at Object.q (knockout-3.4.0.js:5)
    at m (knockout-3.4.0.js:7)

Cheers

[matthewL-7]

Toolset what is going on?

This latest update has so many bugs, were is the fix?

I can't edit a single content template. Custom fields are not working on new posts for some users.

Can you not just revert back to the previous version? Why is this taking so long to be fixed?

[Nigel]

Sorry, the last round of updates included several new features—with major changes to Forms in particular—and an uncomfortable number of bugs made it through to the plugin updates, meaning support is very busy gathering reports of such problems, and the developers are working on fixes.

The issue with custom fields not visible to non-admin roles is already fixed if you update to the latest Types and Access. If you find it is not—after updating—then please let me know, but other users have all confirmed the fix.

As for content templates, I suspect a browser caching issue.

Can you clear the browser cache and perform a hard reload and try again.

(Try using a different browser than normal, which would confirm that is the problem, sometimes clearing the browser cache can be a bit erratic.)

[matthewL-7]

Hi Nigel,

Great using private browser has solved this actually must be cache issues on all my browsers so guess need to clear out cache.

I have tried updating the plugins but keep getting error messages:

Access update: "Update Failed: The package could not be installed. PCLZIP_ERR_BAD_FORMAT (-10) : Unable to find End of Central Dir Record signature"

Types update: "Update Failed: Download failed. Not Found"

Matt

[Nigel]

OK, unfortunately, in that case you are one of a number of users who have a problem with the custom Installer bundled with Types.

There is no alternative but to manually update Types, after which automatic updates should resume working.

Delete you current Types plugin, download the latest version from toolset.com/account/downloads and then upload the zip file to the Add new plugins page.

Sorry for the inconvenience.

[matthewL-7]

Hi Nigel,

OK great a little messing around but this is fixed now.

However, the bug when you go to add a new post that has custom fields still exists. Where not all custom fields work.

For example;

1) Date fields don't work they are just greyed out you can't enter any data or load the calendar.

2) Custom field groups are stuck saying "Loading..."

These only exist when you are adding a new post, if editing an existing post you can edit this data and it loads correctly.

[Nigel]

Can you confirm which post type this is editing?

I'll take a look at your site as soon as I have a chance.

[matthewL-7]

Hey Nigel,

This is TV Shows (tv_show).

Ok thanks! :).

Matt

[Nigel]

Hi Matt

I can see JavaScript errors in the browser when adding a new TV Show post.

Seems like you have a live site but no staging site for testing?

I've taken a copy of the site to install locally and perform some basic debug steps.

I'll let you know what I find.

[Nigel]

The errors persist after stripping back your site to the essentials.

It seems related to using CPT UI to register the post type rather than Types, but I've passed it on to my colleagues for further debugging.

I'll keep you posted.

[matthewL-7]

Hi Nigel,

Hmm ok is there a way we can just switch to using Types to register the post type instead of CPT UI? I tried once but couldn't get it to work.

[Nigel]

My colleague has already started looking at your site, but if you want to switch the post type to Types you should just be able to take a note of the settings used when registering the post type with CPTUI, in particular the slug, which must be identical, then deactivate the CPT UI plugin and add a new post type using Types with the same settings.

All your existing posts should then appear, as normal.

Obviously you would want to be testing this somewhere other than the production site.

[matthewL-7]

Hi Nigel,

I have managed to disable the CPT UI plugin and add the post type in Toolset, however the bugs when adding a new post for this post type still exists. 🙁

Is your colleague still looking at this?

Thanks