Skip Navigation

[Resolved] The custom fields position/order in the editor

This support ticket is created 3 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
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Hong_Kong (GMT+08:00)

This topic contains 7 replies, has 2 voices.

Last updated by JoelK2744 3 years, 10 months ago.

Assisted by: Luo Yang.

Author
Posts
#1983469

Thanks Luo, after a bit more investigation yesterday I worked out it does seem to be some sort of caching issue (even though I haven't got caching enabled on the site or via plugin), if I force flush the cache at server level (even though it's not meant to be on) the custom field appears. This wasn't necessary before which makes me think something must have changed with 5.7 but it may be some incompatibility between 5.7 my hosting and Toolset. I don't see any obvious errors and have tried with no other plugins activated and with default 2021 theme. I can live with that and just need to remember to force flush the cache each time a custom field is added.

However, the custom fields position/order in the editor definitely seems to be down to 5.7, I have tested on a local install using just Toolset and default 2021 theme, the changes to the custom field position in the editor are not saved with 5.7, when I try it with 5.6.2 it works fine.

I understand there was a major jQuery update with 5.7.

Thanks

#1983473

Hello,

For the question:
the changes to the custom field position in the editor are not saved with 5.7
I don't see the same problem in my localhost with a fresh WP installation + the latest version of Toolset plugins, please check there is any PHP/JS errors in your test website(just Toolset and default 2021 theme).
https://toolset.com/documentation/programmer-reference/debugging-sites-built-with-toolset/

If the problem still persists, please provide a database dump file of the test website, also point out the problem page URLs, thanks
https://toolset.com/faq/provide-supporters-copy-site/

#1986315

I can duplicate the problem with the package files, will update here if find anything.

#1986465

I have tried it with a fresh WP installation + the latest version of Toolset Types plugin, but can not duplicate the same problem.

And there is a difference between your duplicator package and my locahost fresh WP installation.

When I edit a post, I can see the "UP" and "Down" button without clicking the any "Arrow" button, but your duplicator package does not display "UP" and "Down" button by default, it needs to click the "Arrow" button. See my video capture:
hidden link

Is there any special steps missing?

#1986559

Thanks for looking into this Luo. That's very odd, there's nothing special at all about the package sent through, it is literally a fresh local install of 5.7 with only Types installed. It is completely separate from our website so it's strange that both exhibit the same problem. Can you confirm you are testing on 5.7 as that is the issue for me, it works fine on earlier versions of WordPress.

See this video - hidden link - of the difference between versions. At the start of the video it's WP 5.6.1, and everything works fine and as you described with the arrows appearing, I then upgrade to 5.7 (this takes a minute or so) and then at the end of the video you see what happens with 5.7 which is the issue I described.

Thanks

#1986655

Thanks for the detail, you are right, the problem exists in WP 5.7, I have escalated this issue, will update here if there is anything news.

#1988355

Here is the feedback from our 2nd tier supporters, this is an issue of WordPress core, it occurs with re-ordering metaboxes more generally in WP 5.7.

See WordPress Core ticket here:
https://core.trac.wordpress.org/ticket/52818#ticket

So you will need to wait for WordPress Core team to fix this issue, it might be next version of WordPress 5.7.1

#1988807

Thanks Luo, I'll await the update