elgopa
Forum Replies Created
-
ah,
sooo, if don’t disable it
it keeps the setting “do not edit htaccess” from the settings from the previous version of this plugin?
correct?
And everyone who had this setting in previous versions can not use “Prevent code execution in the public ‘Uploads’” folder?(Why not keep it really simple? (schoenmaker hou je bij je leest) Wordfence has this option also and many more)
@rogier ,Sorry for coming back again….
I see “redirection method” —> “no redirect” ,
does this prevent editing the htaccess file überhaupt maybe?
This is not the same as “stop editing the htaccess file” in the previous versions.
I do not see the option “do not edit htaccess” in the new version.I do understand now, thank you very much for explaining!
You do not have the option “do not edit htaccess” enabled? (just checking).
That’s the culprit!
I always had that enabled, because i did edit the .htaccess myself!thank you!
I don’t get what you mean with
option is already handled, it will show as “on”, but disabled
buttons have a lighter green colour than normal,after enabling the recommended options once, and cannot be disabled
To make things even more complicated for you guys;
One third site does not have a .htacces file in /uploads folder, but does not give the warning “Prevent code execution in the public ‘Uploads’ folder”
i already tried several times, maar helaas…
(pitty also you have only the option “Enable recommended hardening features in Really Simple SSL – Enable” once when logging in after the update, and by the way after you do this you can not disable these options anymore)
No it is not there.
One website does have a .htacces there, but it has only a Wordfence code execution protection file.
Another website does not have a .htacces at all in the uploads folder
Both websites do have a different hosteri do see a code-execution.php file
<?php /** * Test file for Really Simple SSL to check if uploads directory has code execution permissions * */ echo "RSSSL CODE EXECUTION MARKER";
Bam! Means: it seems fixed , the plugin is available again here
bam!
thx, i’ll look into it further
Had no Wordfence warnings yetThanks!
Thank you Dan,
I do have this disabled now.
Just hoped it was possible to add some kind of attribute to the script, so it would not been processed by defer non-essential JS.BR
Thank you Michelle,
Deactivating Critical CSS did not help, the issue persists,
but deactivating Defer Non-Essential Javascript , did let disappear the issue.Thank you Jeremy!
This clarifies a lot!
Thanks again!