Advanced location rules dropdown causes all the fields to disappear
- This topic has 14 replies, 4 voices, and was last updated 2 years, 4 months ago by
Ryan Maietta.
-
AuthorPosts
-
December 11, 2022 at 9:20 AM #39674
Solace
ParticipantSomething strange is happening in the latest release of Meta Box v5.6.13 and AIO 1.16.7. When I go to my custom fields settings and try to define the advanced location rules all the fields disappear. I have to reload the page to get to the settings but it's a never ending loop. I tried disabling all the plugins but the issue persists. Here's a link to the screen recording. Is this a bug?
December 12, 2022 at 7:25 AM #39697Solace
ParticipantI can confirm that this issue doesn't exist in version 5.6.12.
December 12, 2022 at 8:06 AM #39699Solace
ParticipantActually ignore that, I just downgraded to 5.6.12 and the issue still exists.
December 12, 2022 at 9:13 AM #39700Solace
ParticipantJust reached out to the hosting company and they shared this error. Hope this helps:
WARNING: [pool site-url.io] child 43 said into stderr: "NOTICE: PHP message: PHP Fatal error: Uncaught Error: Call to protected method RWMB_Post_Field::query() from scope MBB\RestApi\Base in /www/wp-content/plugins/meta-box-aio/vendor/meta-box/meta-box-builder/src/RestApi/Base.php:61"
December 12, 2022 at 10:05 AM #39702Solace
ParticipantJust opened up the console to see if these errors might help. Here's a link to the screen recording.
December 12, 2022 at 10:19 AM #39703Ryan Maietta
ParticipantSomething is definitely bugged. I'm having a similar issue. It doesn't enter a reload loop; but, every option under the advanced location rules comes up with "No options found". If you try to type anything in the field, it deletes it and replaces it with a blank tag.
December 12, 2022 at 10:05 PM #39714Peter
ModeratorHello,
Thanks for your feedback.
This issue has been fixed in this commit https://github.com/wpmetabox/meta-box/commit/0cf256eaae651eb5652b81b2167f9f334ab8cf98
Can you please apply the changes to your site and see if it works?December 12, 2022 at 10:16 PM #39717Solace
ParticipantThank you so much! That did fix the issue 🙂
December 12, 2022 at 10:46 PM #39722Mustapha M
ParticipantHello,
Is this issue similar to this?:
https://komododecks.com/recordings/LFbagSOvG0Drm7u41CviI applied the changes from the above commit, but I still see the issue. Maybe I have missed something?
December 12, 2022 at 10:48 PM #39723Solace
ParticipantHey Mustapha, not judging your coding skills here 🙂 did you delete the old lines and replace them with the new lines from the commit? The red lines need to be removed and the green lines added.
December 12, 2022 at 10:51 PM #39724Mustapha M
ParticipantHey Solace,
I appreciate your input. Happy to be judged 🙂
Yup, I deleted the whole red lines and replaced them with the new additions (green). Otherwise, it would trigger a fatal error taking the whole thing down I guess.
Thanks again.
December 13, 2022 at 12:48 AM #39729Solace
ParticipantThat is strange! Did you try the usual troubleshooting steps? Disable all the plugins except for Meta Box and AIO (if present) and change out the theme etc? That should at least confirm if the issue still persists for you, or find out which plugin is conflicting with Meta Box. I started with the conventional troubleshooting steps before I received the fixed code and no matter what I did the issue was there. But as soon as I replaced those lines within the 5 files it started working.
December 13, 2022 at 2:59 AM #39731Mustapha M
ParticipantHey Solace,
Surprisingly it is working now. All I did is restarting Litespeed. Not sure if this affected the result. but it works like charm now. 🙂
PS. I've already done the basic usual troubleshooting steps before.
Thanks again.
December 13, 2022 at 3:27 AM #39732Solace
ParticipantThat's great to hear!
December 13, 2022 at 8:51 AM #39733Ryan Maietta
ParticipantThis fixed it for me as well! Thanks.
-
AuthorPosts
- You must be logged in to reply to this topic.