This support ticket is created 6 years, 5 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.
I'm developing a site and noticed that when I follow the 'Post Field Control' link to /wp-admin/admin.php?page=types-field-control&domain=posts, all I'm seeing is the spinner (see uploaded image). This applies whether custom fields exist or not.
I have:
1. reinstalled a vanilla site using Astra theme, up to date Types, Views, Access & Forms - the problem persists
2. changed to 2017 theme - problem persists
3. rolled back to View 2.6 and Types 3.0 - problem persists
This install is multi-site. I have a live multi site and a live non multi site and they are both fine. All use the same host.
Thank you for trying to replicate this. No error logs are being produced (I have debug.log and server-side error logs enabled). No errors being returned in browser either.
I've repeated a fresh install again this morning, uploaded and activated Astra theme (no child) and only Types. Still the problem persists.
What I have noticed is I'm not being asked to register Types. Could this be something to do with it??
I have files and database dumps ready if you could take a look?
What I have noticed is I'm not being asked to register Types. Could this be something to do with it??
=> NO, i dont think so that could be the issue here.
I've realised I had been redirected back to the post group page when I activated 2017 so mistakenly thought the issue was solved but it isn't. I'm unable to see all my custom fields via post field control even with 2017.
I've used my browser's inspection tool and this is showing as an error:-
Uncaught ReferenceError: Unable to process binding "checked: function(){return allVisibleItemsSelection }"
Message: allVisibleItemsSelection is not defined
at checked (eval at parseBindingsString (knockout-3.4.0.js?ver=3.4.0:68), <anonymous>:3:60)
at init (knockout-3.4.0.js?ver=3.4.0:88)
at knockout-3.4.0.js?ver=3.4.0:72
at Object.w (knockout-3.4.0.js?ver=3.4.0:39)
at knockout-3.4.0.js?ver=3.4.0:71
at Object.q (knockout-3.4.0.js?ver=3.4.0:11)
at m (knockout-3.4.0.js?ver=3.4.0:71)
at k (knockout-3.4.0.js?ver=3.4.0:69)
at g (knockout-3.4.0.js?ver=3.4.0:69)
at k (knockout-3.4.0.js?ver=3.4.0:69)
This error isn't coming up on any other wp-admin pages.
I've tried changing PHP from 7.0 to 7.2 but no change.
I imported the fields via a module created using Module Manager at a time when the origin site was using a version of Types pre 3.0. Could this be the issue?
I imported the fields via a module created using Module Manager at a time when the origin site was using a version of Types pre 3.0. Could this be the issue?
=> Yes - it could be - could you please check with backup which is before you imported the fields and check if that helps.
*** 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.
I have some good news! I've been making some changes to some of my Content Templates this morning and inexplicably I can now see custom fields via post field control! I can't pinpoint anything precisely but I think it might have had something to do with using a types field shortcode for an non-existent custom field. Seems a bit odd; I would expect to simply not see any output in this scenario but it's the only explanation I can see.
I'm going to keep an eye on things and keep my file & database dumps in case the issue re-occurs.
