Can you check that your .htaccess file in the akismet directory got updated? Line 15 should look like:
<FilesMatch "^(form\.js|akismet\.js|akismet-frontend\.js|akismet\.css)$">
Thread Starter
cjlim
(@cjlim)
Yes, i do see this.
<FilesMatch "^(form\.js|akismet\.js|akismet-frontend\.js|akismet\.css)$">
<IfModule !mod_authz_core.c>
Allow from all
</IfModule>
<IfModule mod_authz_core.c>
Require all granted
</IfModule>
</FilesMatch>
But i’m using Bitnami, so I think they do not honor .htaccess files in plugins directory. after adding akismet-frontend\.js to the correct .htaccess file, it’s now working. thx
i thi
Thanks for confirming; I’ll direct anyone else with this issue to try that as well.
Hi cjlim;
i use bitnami. how did you solve this problem? which .htaccess file did you change?
Thread Starter
cjlim
(@cjlim)
@gurhansahin
I refer to bitnami documenation.
The .htaccess location for bitnami is
/opt/bitnami/apps/APPNAME/htdocs/.htaccess
for wordpress, APPNAME is likely wordpress.
however, I noticed if I enabled mod_pagespeed, i’ll still get a 403 error. not sure why and not sure how to configure for mod_pagespeed
@cjlim Does that mean the issue will be fixed after an update for Akismet soon? Or we need to manually fix the issue? Thanks!
Thread Starter
cjlim
(@cjlim)
@nonasun
this has nothing to do with Akismet. it’s just the way bitnami is setup as far as htaccess config is concerned.
Bitnami has documentation around how htaccess should be configured.
But this should be a new issue. Was it because of an Akismet update? Or other update?
Thread Starter
cjlim
(@cjlim)
yes and no.
yes: akismet did have an update where a new file (akismet-frontend.js) was introduced. prior, i think there’s only this file (akismet.js). and akismet did include this new file in the default htaccess file.
no: it really depends on how you setup bitnami htaccess. if you had setup pointing to the default akismet htaccess file, then you shouldn’t experience above issue (since the new file is automatically granted access).
But if you had copied and pasted the content in default htaccess file into bitnami’s htaccess file, then you will have 403 error with the new akismet plugin since the new file isn’t granted permission.
I didn’t copy/paste anything. Under /site/wwwroot/wp-content/plugins/akismet/_inc, there’s only akismet.js, no akismet_frontend.js file.
Thread Starter
cjlim
(@cjlim)
what version of akismet plugin are you using?
Sorry, I looked at wrong website, which didn’t get update. For the website with issue and with latest Akismet, I can access /wp-content/plugins/akismet/_inc/akismet.js. But when I tried to access /wp-content/plugins/akismet/_inc/akismet_frontend.js, I got this error: “Forbidden You don’t have permission to access this resource.” So when we did site audit, we got error “Broken internal JavaScript and CSS. HTTP Status Code 403”. Resource URL “https://humidi-cure.com/wp-content/plugins/akismet/_inc/akismet-frontend.js?ver=1659481471”.
Thank you!
Thread Starter
cjlim
(@cjlim)
again, Bitnami has documentation around how htaccess should be configured.
follow the instructions there. if you are not familiar with these server stuff, maybe get your webmaster to help?
I’m not sure if this is a recent update but my .htaccess in Akismet has this;
# This configuration has been moved to the /opt/bitnami/apache/conf/vhosts/htaccess/wordpress-htaccess.conf config file for performance and security reasons
I had to add akismet-frontend\.js to the FilesMatch in /opt/bitnami/apache/conf/vhosts/htaccess/wordpress-htaccess.conf to fix the 403 error.
