• Resolved Antipole

    (@antipole)


    I have started seeing a problem with Mobile Menu as follows:
    In the backend, I use Quick Edit to change a post status from Published to Pending or visa versa and click Update. The progress disc with the circulating dot displays indefinitely and I have to cancel the operation. This happens every time.
    I have reduced my plugins to just 3 essential (error logging, SSL and plugin organiser) + Mobile Menu. Testing with theme Twenty-Twenty.
    If I disable Mobile Menu the problem goes away.
    Help, please!

    WP 5.5
    PHP 7.4

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Rui Guerreiro

    (@takanakui)

    Hi @antipole,

    That’s strange when you are quick editing no scripts from WP Mobile Menu should be enabled.

    Can you also try to switch theme to see what happens?

    When you are performing those operations can you open the developer tools of the browser to see if there is any javascript error. To do that press the F12 key when you are in the browser.

    Let me know.

    Thread Starter Antipole

    (@antipole)

    I have tried theme Twenty Nineteen as well as Twenty Twenty – no difference.
    JavaScript console shows in all cases (with or without Mobile Menu):

    [Log] JQMIGRATE: Migrate is installed, version 3.3.2 (load-scripts.php, line 5)
    [Error] Failed to load resource: The file “purify.js.map” couldn’t be opened because there is no such file. (purify.js.map, line 0)

    And if Mobile Menu is active (and only then) an additional line:

    Failed to load resource: the server responded with a status of 403 ()
    https://testsite.xxxxxxxx/wp-admin/admin-ajax.php?_fs_blog_admin=true

    Does this help?

    Plugin Author Rui Guerreiro

    (@takanakui)

    Hi @antipole,

    Need to ask something in private. Can you fill the form in this page so I can reply to your email?

    https://www.wpmobilemenu.com/support-contact/

    Thanks

    Plugin Author Rui Guerreiro

    (@takanakui)

    This situation was sorted. The fix will be included in the next update.

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