Custom HTML widget "Forbidden" error #32648
Labels
[Feature] Multisite
Anything related to the specific experience of using a multisite
[Feature] Widgets Screen
The block-based screen that replaced widgets.php.
Needs Testing
Needs further testing to be confirmed.
Milestone
Comments
Mamaduka
added
the
[Feature] Widgets Screen
|
This worked in my testing. It might be an issue with your server. Do you see anything in the web error logs? |
noisysocks
added
[Status] Needs More Info
@noisysocks Did you test in multisite? Super admin are only in multisite. |
|
Yes, it was the root site in a multisite setup.
…On Thu, 24 Jun 2021 at 18:30, Jonny Harris ***@***.***> wrote:
This worked in my testing. It might be an issue with your server. Do you
see anything in the web error logs?
@noisysocks <https://github.com/noisysocks> Did you test in multisite?
Super admin are only in multisite.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#32648 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOCDRPWSUNDJCYDLVDX5GTTUNTTNANCNFSM46TSIIVA>
.
|
|
Help us move this issue forward. This issue is being marked stale since it has no activity after 15 days of requesting more information. Please add info requested so we can help move the issue forward. Note: The triage policy is to close stale issues that need more info and no response after 2 weeks. |
github-actions
bot
added
the
[Status] Stale
|
I've reactivated version 11.0.0 - the errored widgets seem to be custom HTML widgets. My hosting is with 20i who have been excellent at helping me solve errors in the past. Both before and after viewing the wigets with the plugin activated, I got this error log: (none).
Today's error screenshot:
I'm not 100% sure if relevant but here is the console log of the page loading. The
|
|
If I manually navigate to Were I to guess, the null type might be what I would look at. I'm assuming that the custom HTML Widget is somehow failing to identify correctly and nothing catches the null return to handle the failure. |
github-actions
bot
removed
the
[Status] Stale
talldan
removed
the
[Status] Needs More Info
|
Hi there, 5 mins ago i updated one of my instances to WP 5.8 with activated Gutenberg and all custom HTML widgets show the same "Forbidden" message in the widgets admin page. i also found results about htaccess reating to this and i use WPAIOS which has added rules to htaccess - may there be some relation to security plugins (using a restricted param name?) how do i get to editable widgets again without disabling that new feature? |
|
I'm experiencing this issue in one of my client's sites, where the REST ajax calls to for example
When I run a copy of the site on my local machine, the page This seems to be an issue with too many widgets causing the website to fail on providers that restrict/limit requests or database connections (which should be perfectly fine to protect it from DoS attacks). |
|
Also notice this possible coherence: |
|
Many of the errors reported in this thread seem unrelated to the original error which is The There is a known issue where having lots of data (e.g. a long string) breaks the preview. See #33540. This would cause a It seems plausible that one of the causes of the |
noisysocks
added
[Feature] Multisite
github-actions
bot
added
the
[Status] Stale
|
@lordmatt @sippsolutions @netzgestaltung Hi there, just circling back to this and wondered if any of you would have a moment to provide the info @noisysocks asked about above, to help move this along. Please let us know so we can keep this ticket going if it's still an issue for folks. Thanks! |
github-actions
bot
removed
the
[Status] Stale
|
I'm going ahead and closing this, since no one has been able to confirm that this is still an issue. If anyone gets back to this later and is able to confirm the following, please add a comment with details and I'll be glad to reopen it. Thanks!
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The 10.8 line has improved the issue I have been seeing. Now, instead of all widgets showing Forbidden to the super admin, only some do.
Step-by-step reproduction instructions
Expected behaviour
Ability to edit and interact with those Custom HTML widgets given I have all the rights.
Screenshot
WordPress information
The text was updated successfully, but these errors were encountered: