blakmarkit

So, extra wrinkle. Back on 3.3.101 again. Saving a template isn’t working on that version either. It has been a while since I’d needed to edit (over 2 months ago), so I haven’t noticed how long this might have been going on. I’m getting a similar 403 on the POST to admin-ajax.php as well as a followup JS error (seen below). I’m guessing that a large part of the JS error was made obsolete in the refactoring, but it’s interesting that the saving problem persists across versions. My hunch would be that this is user error or a server configuration issue, but it’s strange that the issue never manifested itself previously, and I don’t believe there have been any underlying permissions/server changes that should be affecting this. I even tested on a different environment with nearly identical settings that was on 3.3.100, and that one is saving correctly (I don’t know that the version number there is actually relevant).

Other info:

• first env: WP 6.5.4, PHP 8.2.19
• second env: WP 6.5.3, PHP 8.2.19

Uncaught (in promise) TypeError: a is not a function
    sendServerRequest <site>/wp-content/plugins/uipress-lite/assets/js/uip/v3.5/utility/functions.min.js?ver=3.3.101:1
    saveTemplate <site>/wp-content/plugins/uipress-lite/assets/js/uip/uibuilder/toolbar.min.js?ver=3.3.101:1
    onClick <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js line 6 > Function:178
    Xt <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:1
    en <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:1
    n <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    Xi <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    tl <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    patchProp <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:6
    w <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    C <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    y <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    E <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    w <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    C <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    y <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    E <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    w <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    C <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    y <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    effect <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    run <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:1
    update <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    L <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    M <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    F <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    y <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    effect <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    run <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:1
    update <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    Xt <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:1
    _n <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:1
    promise callback*hn <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:1
    dn <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:1
    effect <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    Ae <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:1
    Re <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:1
    Rt <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:1
    set value <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:1
    setup <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    promise callback*setup <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    Xt <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:1
    s <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    M <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    M <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    F <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    y <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    E <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    w <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    C <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    y <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    O <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    A <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    y <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    effect <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    run <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:1
    update <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
    Xt <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:1
    _n <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:1
    promise callback*hn <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:1
    dn <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:1
    effect <site>/wp-content/plugins/uipress-lite/assets/js/libs/vue-esm.js:3
vue-esm.js:1:15963

@admintwentytwenty Tested the 3.4.05 update. The jQuery errors are gone, but I’m still having trouble saving template changes, and the Admin Menu block that I had in my existing template went back to horizontal scroll (seen in the previous screenshot) instead of vertical. If I add a new block, that one is correctly vertical, but since I can’t save the template, that’s not helping yet. I should clarify that it looks like the “bad request” error is actually a 403 on the POST to admin-ajax.php. I’ve checked every file permission setting I can find, and everything should be fine.

There aren’t any PHP errors—I have some deprecation notices from another plugin (Toolset Views/Types), which I thought might be connected, but I deactivated it and several other plugins that seemed like they had thrown any warnings or notices anywhere in the console (Matomo, TinyPNG, Updraft) or might otherwise interact with uipress or file permissions (RankMath, Wordfence, Admin Menu Editor), and those didn’t resolve the saving issue.

I can send you the JSON—do you want the JSON from before or after updating the plugin? Where should I drop it for you?

Also adding, rolling back to 3.3.101 fixes all of these issues. So something about the JS refactoring in 3.4.x seems like it’s a problem.

I’m not the OP, but I updated to 3.4.04, and that resolved the whitescreen issue, but the console is still full of jQuery is not defined (and other related) errors.

This seems to also be causing a “Unable to save template: bad request” 400 error whenever I try to save changes to a template.

One other thing that broke, the basic Admin Menu block went from a vertical list to a horizontal one, with no changes to the template. It seems like the base styles must have changed.

• This reply was modified 8 months, 3 weeks ago by blakmarkit. Reason: missing screenshots

Same thing happened to me. My admin template, which was based on the Modern template (I think) is broken after updating to 3.4.

Thank you to the cleantalk team. They were able to reinstall and the notices were finally cleared. Not sure why my attempts didn’t work, but we can close this out.

Hi @dimitrycleantalk. Thank you for the quick response. Unfortunately I’m still seeing the notices in Query Monitor after installing the patched version. Let me know if there are any other things I can try.

Thanks!

Confirmed the new menu option is working. Love it! Thank you for the quick updates.

For those looking later, you can open your admin template from the Settings > uiBuilder menu, select the Admin menu block that controls the sidebar in the uiPress editor and enable the “Disable auto load on top level items” option. Save then do a full page refresh.

Error appears resolved. Thank you!

Awesome! Looking forward to it.

@admintwentytwenty are you saying that the latest release has a setting to disable loading the page of the menu item when attempting to navigate to a submenu while in either the inline or dynamic admin menu modes? If so, it doesn’t seem to be working, or it isn’t clear how to configure it. There should at least be an option where the contents of the frame do not load/reload on clicking a top-level menu item unless there are no submenu items, as the UX intent is rarely to go directly to that page, but often to a different (non-first) submenu item.

I would also like the option to be able to set this behavior, especially when using the “dynamic” admin sidebar.

Thanks for looking into it!

@jtewes

As an update, the Elementor devs are pointing back at FastSpring’s plugin as the source of the conflict. Please see the github bug report. Can you work with their team to address this issue?

https://github.com/elementor/elementor/issues/7093