Skip to content
This repository has been archived by the owner on Sep 2, 2022. It is now read-only.

Insufficient rights in customizer at wordpress multisite install with custom domains #7

Open
pavl1 opened this issue Aug 5, 2018 · 6 comments

Comments

@pavl1
Copy link

pavl1 commented Aug 5, 2018

I have wordpress multisite install with custom domain for each site, except main. When I click on publish button in customizer at custom domain site, wordpress notify me "You need a higher level of access" and in dev console show response from admin-ajax.php: data: "invalid_nonce", success: false. If I deactivate "Multisite URL Fixer" customizer works great, but links to network parts wrong and can't upload images.

@JulienMelissas
Copy link
Contributor

Hmmm, I've not run into this, and I run multisites all with separate domains using the customizer. That said, I'm using this plugin as an MU-plugin. Can you try that?

@pavl1
Copy link
Author

pavl1 commented Aug 19, 2018

Sorry for delay. I try this plugin as MU-plugin, but no success, error the same: insufficient rights and invalid nonce in dev console

@JulienMelissas
Copy link
Contributor

@pavl1 -- did you ever figure the issue out? Did you try with all of your plugins disabled and a default WP theme? I have managed over 5 multisites running this plugin and have never run into this issue (or seen another mention of it), so I feel like it might be related to something else?

Feel free to reopen if you are still having this issue.

@jmrcs
Copy link

jmrcs commented Aug 24, 2019

REQUEST TO OPEN THIS ISSUE.

This problem happens to me in a MULTISITE with Gutenberg active. If I deactivate Gutenberg editor, everything works.

There is something wrong with Multisite Url Fixer + Gutenberg editor + Editing Permissions.

Thank you so much!

@hofmannsven
Copy link

I also get an error 403 for all API requests.

@JulienMelissas
Copy link
Contributor

JulienMelissas commented Jul 19, 2021

I've reopened the issue. Thank you all for writing in regarding this.

Unfortunately, I don't have time to solve this right now personally, but would welcome anyone who is able to look at this to submit a fix or PR.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants