If the ordering is not being respected and it was working then it sounds like interference from some other code (that was maybe updated).
I'm guessing this is a staging site?
Can you check if ordering is still wrong if you disable all plugins except Types and Views? And if you switch theme to twentytwenty?
Try turning on Views debug mode (at Toolset > Settings > Front-end Content) which will add a debug pop-up on the page with the View that will let you inspect the query arguments (and generated SQL statement) to verify whether Views is trying to specify the ordering correctly. (If this is a staging site and you leave debugging on, I'll be able to check, too.)
I'm going to turn on debugging right now so you can take a look at the query. I took a look a look as well and nothing immediate jumped out. We did have an employee making soome changes to some custom fields but I backed out most of them.
I'm not seeing the debug window when I visit the page.
Let me set a private reply to get access credentials from you. I'm actually done for the day and I'm pretty sure we're in different timezones, so if I get them from you now I can look straight away when I start.
Hey Nigel, is there any way we would be able to do a web conference and I can pass you my credentials? ou drive and Im in the passenger? Working from home for the time being so I can essentially be available whenever you need.
You can just fill in the fields in this private reply (I'll set another one for you now).
It will ask for the WP admin credentials as well as FTP, but I don't actually need FTP you can fill that with dummy text.
No-one can see the private replies (and when this thread is resolved they are automatically deleted from the system, so there is no permanent record).
I recommend rather than giving me your own credentials, you create a new temporary admin user and share the credentials for that, and as soon as we are done you can delete that user.
To add more clarity, the specific issue lies within our E-D components custom post type. The other CPT are working as normal but the views that use the E-D Component and order the content by the order number field are the ones not responding.
I can see with the debugging info for Views that it is set to order by the Order custom field but doesn't, and I need to do some more debugging work to find out why.
Your version of Views wasn't up-to-date and the site on this server isn't registered, so I deleted Views so that I could manually upload the current version, that triggered an error, I couldn't complete it (a limitation on your server uploads, I think, nothing to do with the plugin itself).
So, I've taken a copy of your site to install locally to work on, but your site is currently missing Views.
I registered your site with Toolset using my account so that I could get the latest version of Views installed to check something, but it hasn't helped, though you do now have Views installed and active again.
Hate to snowball on top of you but there is also one more issue thats prevalaent relate to toolset. It pertains to the conditional logic for three fields:
1. Button Link 2
2. Button Text 2
3. Button Color 2.
These are all custom fields with conditional logic used with the E-D Component Custom Post Type.
The logic in those fields mirror production but they are disabled and hidden when trying to use them. Im just not sure why the logic is disabling them but all of the issues seem to stem from somethign going on with the E-D Component Post Type.
I can open another ticket to address these issues separately if needed.
Thanks for that, it is likely related, I'll check.
I had found on my local copy of your site if I deleted all the other fields in the custom field group for E-D Components than the Order field and re-saved the group then the View worked correctly.
The problem appears to be related to the custom field group (rather than the post type) and I'm trying to focus in on what specifically is the cause.
I'll take a closer look at those fields (and the fields their conditions depend on).
I found that both the problem with saving the large custom field group *and* the actual problem with the View not using the custom field for ordering were resolved by raising the PHP max_input_vars.
In my case I raised it to 5000, I didn't try to finesse what minimum value was required.
I guess your staging server has different settings to your production server.
In any case, can you please try the same and let me know if that resolves the problems.
