Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter Fotoura

    (@fotoura)

    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

    Thread Starter Fotoura

    (@fotoura)

    Hi… sorry I found your answer:

    Add this to the theme functions.php

    // show admin bar only for admins ->

    if ( !current_user_can( ‘manage_options’ ) ) { add_filter( ‘show_admin_bar’, ‘__return_false’ ); }

    Thanks!
    Rich

    Thread Starter Fotoura

    (@fotoura)

    Hi,

    I had no idea it was that simple. Is this mentioned somewhere in the plugin and I’ve missed it then apologies. If not, I really think you should make this obvious – it’s such a great feature :). I’ve been wanting to do this for months but had no idea where to even start.

    Thanks for your response and again, thanks for a superb plugin!

    Rich

    Thread Starter Fotoura

    (@fotoura)

    Thanks Michael,

    Don’t get me wrong – I love this plugin! I’ve just recently been using a separate plugin (formidable) to publish 200 pages at a time and they are all using the default page template versus the fullwidth page I want them to have.

    Ideally I’d like to be able to say use single.$posttype.php and create a different template for my theme for each content type…

    Ok if that’s not possible are you saying that I could specify a particular cpt to use say archives.php versus single.php for example – could I modify one of the other standard templates to be fullwidth i.e archives.php and tell the plugin to use that by default?

    Thanks again ??

    Rich

    Hi Ulrich,

    I’m having the same problem as well – the plugin has been great – but recently it stopped working – triggering the same Server error message.

    I use a plugin called s2member – what I’ve found is that if I select any of the standard wp member types the export works, but not when I choose ‘every role’ or one of the s2member type roles.

    Unfortunately I have been using this to tell me about the s2member details – it worked fine but then stopped working but I don’t know why or what triggered it.

    Would really appreciate your help and would be happy to donate.

    Thanks,
    Rich

    I’m having the same problem. I can only assume that it’s an intentional part of the upload process to strip the exif information out. What I do know is that there are other tools out there that allow you or your users to upload images to your site (i.e. TDO mini forms) that don’t strip the exif information out.

    Unfortunately they don’t necessarily resize the images like the wordpress media uploader does.

    Very frustrating as I, similarly, don’t understand the benefit of stripping the exif information out.

Viewing 6 replies - 1 through 6 (of 6 total)