I don't have access to the cloudways back end. The Google Drive link you shared is restricted and I cannot access it.
(Christopher is currently on vacation.)
Let me set a private reply and you can share the login credentials there (I don't need the FTP details).
On my local test site this is working normally (the same with Access active and managing pages as when it is not activated) so I need to look at what is particular to your site that might account for it not working.
Hello Nigel,
Thank you for replying. You check the environment that we have cloned our site to Cloudways then you will found the issue.
Check this link for creds hidden link
Also check we have provided steps how the issue is occuring.
I managed to isolate what was required to see the issue on the cloudways copy of your site, and then reproduce the same on a clean local test site.
Specifically the issue happens when you have Advanced Custom Fields Pro active along with Toolset Access, WPML, and a classic editor plugin.
So a very specific combination to provoke the problem.
Before escalating this any further, I note that ACF was active on the cloudways site but is not actually being used (no custom field groups have been created).
Hello Nigel,
We have checked the same by deactivating "Advanced Custom Fields Pro" plugin. On cloudways the ACF field groups not pushed don't know why.
We have pushed Field groups on cloudways and our site completely made on Advanced Custom Fields Pro. So can you please check the issue on your end with ACF plugin why that causing an issue while activating the plugin.
Hope Toolset team will fix that as soon.
OK, in that case I will escalate this to the developers to investigate further.
To manage expectations I should point out that they have criteria to prioritise work that includes how many users are affected by an issue, and this is something of an edge case affecting one client.
I'll let you know when I have some feedback to share.
The developers just completed a development cycle (most Toolset plugins received updates yesterday) and they are now beginning a new development cycle.
The internal ticket I created for this issue is included in the board for this cycle, but I can't say when they will work on it.
I get notifications of changes in the ticket, and as soon as I do I'll update you again here.
I just checked and work on this hasn't begun yet, I'm afraid.
I have raised the priority of the internal ticket to bump it up the developer queue so that it receives attention sooner and added a comment to the ticket noting you contacting us again asking for updates.
They tend to prioritise tickets based on how many users are reporting the issue and how serious its impact, so it is to be expected this may take some time, but hopefully the nudges on the internal ticket will mean it being handled sooner.
