Ok…. so I’ve worked it out using good old determination – nothing to do with your plugin of course ??
So, if you’re on a bitnami stack like me, the htaccess file works differently in that it is written by a separate file:
(https://wiki.bitnami.com/Components/Apache/htaccess_configuration)
Basically, you need to write what you want to be in your htaccess file in a different file – httpd-app.conf, which is in the /apps/wordpress/conf folder.
Once you’ve added the code as per the media vault activation helper you then need to restart apache (https://bitnami.com/forums/forums/lampstack/topics/restarting-apache-on-the-lampstack) and you can then enable media vault activation.
You may need to make the httpd-app.conf file editable by changing ownership from root to bitnami (using chown unix command). Remember to put it back after.
Beltran’s response helps explain this a bit (https://community.bitnami.com/t/wordpress-htaccess-permissions-override-on-ami/24408/5)
I hope this helps people in a similar predicament enable your plugin as it seems ace – haven’t used it yet but I’ve got high hopes!
Thanks,
Rich
