Hi Alison,
Thanks for your message. I also received your email.
From past experiences this is caused by a security plugin or overly strict .htaccess rules. Are you running a security plugin and is so, which one?
IF you could send me the .htaccess rules as a text document to the same email address, that would be great.
I will try to assist you further.
Kind Regards,
Damian Baker
-
This reply was modified 6 months, 3 weeks ago by
wipeoutmedia.
Damian,
Thank you for your quick reply. How do I get you the .htaccess information?
These are all of the plugins on our site:
Activated:
Bottom of every post
Brightcove video cloud
Comment hierarchy adjust
Comment moderation email only to author
Contact form 7
Css & javascript toolbox
Duplicator
Edit flow
Google XML Sitemaps
Greg’s Threaded comment numbering
Network shared media
Nextend
Nextend Smart Slider 2 Full
Organize Series
Print-o-matic
Relevanssi
Relevanssi Dashboard
Simply Exlcude
TablePress
Deactivated:
Email pick up
Feed wrangler
Friends only
Hello dolly
JSON API
Sidebar Login
Simple Fields
Types – complete solution for custom fields and types
Wpml json-api
Wpml multilingual cms
Wpml translation management
Hi Alison,
The answer as to why it is not installing seems to be leaning towards the .htaccess file.
Can I suggest, making backup copies of this file as well as any others that may exist in folders such as the wp-admin folder.
You would then need to move those files off the server for now.
Then create a new .htaccess file with the default rules for WordPress as shown here: https://codex.wordpress.org/htaccess
You can then upload the new .htaccess files onto the root of the server as well as the wp-admin folder.
See if that allows you to install the CSS & JavaScript Toolbox plugin.
Good luck!
Kind Regards,
Damian Baker
Will we be able to add the .htaccess rules back in after installing? Will doing that make the plugin not work?
This is an email from our engineers. Will you please address his concerns?
I infer that the plugin developers expect that the change to the .htaccess file(s) is temporary. If so, do they expect the plugin to continue to function after we restore to our current configuration?
Do they understand our configuration/environment? We have an AWS scale group, and modifications to the filesystem on the running machine are not allowed. Any such changes are not propagated to other members of the scale group, and are reverted when the current instance is replaced.
I believe that the changes that FS has in these files are there to allow it to work in our configuration/environment. Have the developers compared the differences between what we have and their recommended versions? Or are they recommending that we only modify the “default” rules in our htaccess files to match the WP example? If the former, I suspect that the result is not what they expect. If the latter, help me to understand how the result of our modification to the rules is different. Bottom line: What, exactly, do they want us to do? I sent the .htaccess stuff to you. I infer that they want all removed except the one at the root. We do not have one in the /wp-admin folder.
In any case, I am not inclined to do any of this to our current production system. We have a beta system for this “development” type of stuff.
Steve Howes
Hi Alison,
Thanks for your email.
Your configuration looks to be customised for your environment and may need further investigation.
I will send you an email shortly.
Kind Regards,
Damian Baker
