Thanks for reporting this.
We just released a new version which include a fix for this.
Thread Starter
Rookie
(@sofrankly)
Welcome. Ok, now renaming wp-content works, but renaming any folder underneath it such as plugins no longer works. It seems you are setting the L flag in htaccess causing the more specific rules to be ignored after the broad one matched.
Thread Starter
Rookie
(@sofrankly)
May I suggest you add to root files module:
- Block other wp-*.js files
- Block wp-*.css files
Actually, you could provide an option to block all external requests to js and css files except for their combined versions as created by caching plugins (in case that is needed to keep search engines happy?) as some of these files contain WP strings even if the file name does not.
Also:
- Rename wp-json API endpoint
- New component WP admin (just like WP content)
- Rename wp-embed.min.js
would be nice.
Thread Starter
Rookie
(@sofrankly)
One more bug: New Style File Path does not work in version 1.2.2
Hi Rookie,
I’am not able to replicate any of above issues with the latest plugin code 1.2.2 Do you use a cache plugin? If so can you clear the cache? Try clearing the browser cache too.
If still not working, can you please get in touch with me through contact at http://www.nsp-code.com and i’ll check into this.
Thanks for your suggestions, they sound very interesting, definitely i’ll be checking to implement for the next releases.
Thanks
Thread Starter
Rookie
(@sofrankly)
No, no caching plugin used and browser caching is off. Changes I make in the GUI are no longer reflected in htaccess. I need a way to reset your plugin and start over. Unfortunately this is proving difficult to do. Deactivating and re-activating and uninstalling reinstalling fails to delete settings. I can’t find settings in database either. Could you please provide instructions? A reset button in the GUI would be nice as well.
Thread Starter
Rookie
(@sofrankly)
Ok, I found the settings in the database and was able to reset them. Here is how to reproduce the failure of plugin renaming.
1. Rename wp-content to content, block wp-content
2. Rename plugins to apps, block plugins
Result: only wp-content is renamed, not plugins
Also, without touching wp-content, if the plugin default name is not changed, but individual plugins are renamed, those renamings are without effect.
Thread Starter
Rookie
(@sofrankly)
More suggestions:
– display an appropriate error message when the plugin fails to write to htaccess due to file permission limitations
Thread Starter
Rookie
(@sofrankly)
Were you able to reproduce the issue now?
Hi Rookie,
Many thanks for your help and suggestions.
I was able to replicate and fix, many of the things. Hopefully i’ll be able to complete everything in 1-2 days.
If you want i’ll send the new version through your e-mail which i got earlier.
Thanks
Will the fixes be updated soon on the repository? It seems last update is still last three weeks and your your comment is just a week ago?
I confirm the new version will be released today.
Once updated, It will be great if you guys send feedback, with any non-functional features and improvements.
Hi @nsp-code. I understand that t takes time and sacrifice to make plugins but please kindly update if the update is ready.
Thanks.
Hi,
Sorry, just had few last minute changes. The update is not available.
If you guys need a night built, please get in touch with me through contact at http://www.nsp-code.com
Thanks
