WebDev1998

Raising your memory limit to 512MB or even 1GB is not really a great solution here, as that is way too high. I would look into why you need this much memory to begin with. Maybe segment off some things, or trim some fat.

This issue ended up having nothing to do with Cleantalk. The media upload path in WordPress had been modified and was not correct.

This would be extremely helpful. We have a theme that updates then requires a DB update afterwards and this plugin severely hurts performance until that DB is updated, or it is deactivated and reactivated. Simple flush cache option would be helpful as that is an action we could comfortably tell people to perform.

ok

• This reply was modified 1 year, 1 month ago by WebDev1998.

I am afraid that I still receive the exact same error on install. “Unable to create directory uploads/2023/10. Is its parent directory writable by the server?”

• This reply was modified 1 year, 1 month ago by WebDev1998.

Hello @eugenecleantalk

I tried the new version you posted. Upon activation a screen loads that says “Unable to create directory uploads/2023/10. Is its parent directory writable by the server?”

I then look at the activated plugins and cleantalk is not activated.

Hello @katereji

After a complete deactivation and removal, we attempted to install the version you supplied. We got an error message saying “Unable to create directory uploads/2023/10. Is its parent directory writable by the server?”

Assuming it was talking about wp-content/uploads/2023/10, we attempted creating this folder, but the error still presented itself. I double checked the directory permissions on the wp-content folder, the uploads, folder, the 2023 folder, and the plugins folder… everything looks correct

Nothing should be limiting the plugin’s rights… The actions I am doing are being done through an admin account in WordPress. The folder permissions look accurate. I have tried disabling ModSecurity, and disabling the security plugin on the website, but no luck.

Yeah it is bloatware now. Going to be removing it from our standard plugins. They are trying to be a security plugin instead of a really simple SSL plugin. Just use one of the many others Security plugins that have been around with a proven track record. As far as forcing HTTPS… it can be easily scripted, or manually added to your htaccess.

• This reply was modified 1 year, 4 months ago by WebDev1998.

Just happened again and it overwrote the default WordPress htaccess section

It seems to have worked that time. Did I do something wrong last time?

I’ve tried that a few times now. I get a green check mark but the error remains on top

same issue, kind of ridiculous that this hasn’t been addressed.

see https://github.com/ktquez/vue-disqus/issues/21