Advanced location rules dropdown causes all the fields to disappear

Support General Advanced location rules dropdown causes all the fields to disappearResolved

Viewing 15 posts - 1 through 15 (of 15 total)
  • Author
    Posts
  • #39674
    SolaceSolace
    Participant

    Something 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?

    #39697
    SolaceSolace
    Participant

    I can confirm that this issue doesn't exist in version 5.6.12.

    #39699
    SolaceSolace
    Participant

    Actually ignore that, I just downgraded to 5.6.12 and the issue still exists.

    #39700
    SolaceSolace
    Participant

    Just 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"

    #39702
    SolaceSolace
    Participant

    Just opened up the console to see if these errors might help. Here's a link to the screen recording.

    #39703
    Ryan MaiettaRyan Maietta
    Participant

    Something 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.

    #39714
    PeterPeter
    Moderator

    Hello,

    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?

    #39717
    SolaceSolace
    Participant

    Thank you so much! That did fix the issue 🙂

    #39722
    Mustapha MMustapha M
    Participant

    Hello,
    Is this issue similar to this?:
    https://komododecks.com/recordings/LFbagSOvG0Drm7u41Cvi

    I applied the changes from the above commit, but I still see the issue. Maybe I have missed something?

    #39723
    SolaceSolace
    Participant

    Hey 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.

    #39724
    Mustapha MMustapha M
    Participant

    Hey 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.

    #39729
    SolaceSolace
    Participant

    That 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.

    #39731
    Mustapha MMustapha M
    Participant

    Hey 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.

    #39732
    SolaceSolace
    Participant

    That's great to hear!

    #39733
    Ryan MaiettaRyan Maietta
    Participant

    This fixed it for me as well! Thanks.

Viewing 15 posts - 1 through 15 (of 15 total)
  • You must be logged in to reply to this topic.