lastest update messes up entire WP UI

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

Same here, on one of my pages the full backend is white with the error:

ReferenceError: Can't find variable: jQuery

Hey, sorry to hear about the issues.

We just released v3.4.04 which should fix the issues you are experiencing. Please ensure you clear cache after updating. If you are still experiencing issues after that please respond with details in this thread with screenshots where applicable.

Thanks,

Mark

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 5 months, 1 week ago by blakmarkit. Reason: missing screenshots

Thanks for that, it appears the problem as far as i can see is, in general UIPress is designed to allow us to make pretty drastic changes to the UI and these changes can’t be accounted for when the plugin is updated – this is without the most problematic update so far. I’m leaving it uninstalled for now and ill revisit in the future since its not a critical element of the installation. As an indie dev myself i know the pressures when its one pair of hands to the wheel 24/7. I still rate this as one of the best WP plugins out there (a real gamechanger) but as i stated in my original thread it needs to be more consistent with the updates. I wont mark this as ‘solved’ since others seem to be adding updated issues.

Thanks

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.

@blakmarkit,

Yeah, i think i did the same a few versions ago and i kept the old version for ages ignoring all new updates just to avoid another bunch of new surprise changes. Its a lot of fun dabbling with the editor and making cool customisations then you find they alter after the next update. I’ve used the export & import a few times and it works ok so long as your doing it within the same version. Hope he finds the fix soon.

@blakmarkit – uiPress doesn’t use jQuery so the errors won’t be be the reason for the problems saving the template. Regarding that issue, is there anything in the PHP error logs about that bad request? I am not able to replicate any of those issues on my end.

Regarding the menu issue, we haven’t changed any base styles so I am not sure what has caused that, i’d recommend a fix but it would involve being able to save the template. Would you be able to export the template and send me the json file so I can investigate?

@trutherone – Thanks for the patience and understanding, it is indeed not a simple plugin to maintain as it’s so far reaching, each update is thoroughly tested and I have not been able to replicate any of the the above issues on my test setups. That being said, I have work to do to minimise situations like these from happening again.

Thanks,

Mark

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

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

@blakmarkit – Thanks for digging in to this, I am not able to replicate it at all though, I have tested across all major PHP versions from 7.4 upwards and no luck. It’s strange that it’s just one function too as the uiBuilder uses the same security and ajax endpoints through out so you’d imagine if it was a setup issue they would all be returning a 403. I am assuming you can create new templates etc?

Is there any way you can setup a staging server where the issue is also happening so I can take a look. If this is possible you can send the credentials via the online chat on our website, however we will need to continue to communicate here to adhere to the repository rules. You can also send the json there.

Thanks again,

Mark

@admintwentytwenty ok, so I think I managed to isolate the source of the issue, inadvertently, in solving a different issue. I’m using the auth0 v5.x plugin for user authentication, and there were a variety of nonce/cookie issues that I thought I had fully resolved, but there was one still outstanding that quietly manifested itself in seemingly random circumstances—single API calls returning 403 in the Bricks editor as well as UiPress, as far as I’d noticed. I didn’t see the connection until just now. There is a setting in that plugin for enabling “rolling sessions,” the option was previously broken (since patched), so I didn’t know when I was testing that it was always defaulting to enabled. Disabling that option (in the patched plugin) resolved the 403 error in Bricks. A day later I remembered that this one was also 403.

https://github.com/auth0/wordpress/issues/895

The Admin Menu block is still switched from vertical to horizontal scroll after updating to the latest (3.4.06), but I am at least able to add a new block (which displays correctly) into my existing template (or modify the existing block) and save it. As a separate issue, there’s something weird happening with the Modern template in the latest version, where the Admin Menu element doesn’t seem to be correctly saving text colors, even on a brand new template. I ended up rebuilding the menu based on a different template, instead.

I believe this is now resolved for me.