Post by dwgjanny on Jan 7, 2023 11:03:19 GMT -8
Hi everyone, first time posting here.
This isn't happening with all plugins (or even all versions of one plugin), but it's occurred more than once and forced me to use ancient versions of some plugins. Very inconvenient. This makes me think it can't be just the specific plugins, which seem to be working fine for other users, but a deeper issue or something else I'm doing wrong.
This isn't happening with all plugins (or even all versions of one plugin), but it's occurred more than once and forced me to use ancient versions of some plugins. Very inconvenient. This makes me think it can't be just the specific plugins, which seem to be working fine for other users, but a deeper issue or something else I'm doing wrong.
Essentially, when my forum loads in the browser, it will load all the scripts associated with the plugins we're using (e.g. GET https:// storage.proboards.com/7078629/js/aDiprJGgWqTJTripCPcX.js) - except for the plugin affected by this problem, which returns with a 403 error response and fails to load. (e.g. Loading failed for the <script> with source “https://storage.proboards.com/7078629/js/aDiprJGgWqTJTripCPcX.js” will be the browser console message.) Thus the site acts as though that one plugin isn't there or is disabled, but the other plugins all work fine.
All of the plugin's user/theme permissions are right in Plugin Manager, and the 403 error occurs at both staff and member access level. I've tried disabling and re-enabling the plugin to no end when this happens; no luck. I've tried enabling it both via the checkbox and via the plugin's settings page; made no difference. Tried changing browser; exact same issue occurs.
An example of the response headers, in case they're relevant:
In this specific instance the plugin is Name Icon (and the error has struck both on a direct install of v1.1.0 and on a later attempt at importing v1.1.1 via its .pbp file). Whereas downgrading to the 3-year old v1.0.5 doesn't elicit the 403 error.
HTTP/2 403 Forbidden
date: Sat, 07 Jan 2023 18:33:52 GMT
content-type: text/html; charset=iso-8859-1
cf-cache-status: MISS
vary: Accept-Encoding
server: cloudflare
cf-ray: 785ec8c20a1bb2e7-MAN
content-encoding: br
X-Firefox-Spdy: h2In this specific instance the plugin is Name Icon (and the error has struck both on a direct install of v1.1.0 and on a later attempt at importing v1.1.1 via its .pbp file). Whereas downgrading to the 3-year old v1.0.5 doesn't elicit the 403 error.
But as I mentioned before, this isn't the first time the current version of a plugin has refused to work while older versions have been successful. Could something wider be wrong with my plugins, permissions, forum settings - anything at all? Could it be something to do with my storage (I have plenty free) or the size of the plugin file? I just can't work out why or how this would ever happen.
Alternatively, has anyone heard of anything like this happening before? Is it an existing resolved problem?
Any help would be fantastic. Thanks for reading.
(EDIT: Looking in my browser console at the request headers for all the working plugins and the 403ing plugin, the only difference is that the latter contains "TE: trailers" while the others contain no TE (Transfer-Encoding) header. No idea if this is a clue or just coincidence, but I don't want to miss anything out. Turning off network.http.enforce-framing.strict_chunked_encoding and restarting/reloading causes all of the requests to contain TE: trailers, but does not fix the 403.)