Front-end plugin installed, worked once

I'm aware of the security problems with front-end edit and would like to enable it, use it and then remove it. I've downloaded and installed the plugin and it worked fine the first time I tried it (aside from a bug message that changes couldn't be saved but they really were saved) but thereafter it remains visible in the list of plugins but the checkbox cannot be ticked. Examination of the code reveals that a confirmation of acceptance of risk is required. I can't get that confirmation box to appear so cannot get front-end to work again. Have cleared browser caches, tried both Safari and Firefox, and I'm not blocking pop ups. I'd just hard-code the acceptance if I could work out the complex of variables but my programming skills aren't up to figuring what variable I'd have to set (and to what value). Using the most current version of Zenphoto (1.4.2.4) in a more or less 'normal' set up. Any help appreciated.

Thanks

Comments

  • Probably you have downloaded the plugin updated for the 1.4.3 release. Thus the bug message. Unfortunately for these "unsupported" plugins we do not try to maintain multiple copies.

    So you should download the 1.4.3 Beta to get this going.
  • Just remove the entire "$plugin_disabled" section, and there you go! The only drawback is that albums are opened when you click on them to change the title.

    Notepad shows php-files as garbage though, so if you do not have a text editor capable of properly displaying php-content, download and use "notepad2.exe" from <link removed by admin>. Good luck!
  • If you wish to display and edit PHP code a free editor such as Notepad+ should work - http://notepad-plus-plus.org/

    John
  • acrylian Administrator, Developer
    @seroxatamad: Rodelion's comment probably was just spam because it does not really make sense with the discussion. But I just left it for now...
  • No, Notepad++ is a really good text editor for the PC.

    And the suggestion to remove the `$plugin_disable` line is exactly the right solution. It was the treatment of disabled plugins that changed between the releases.
  • acrylian Administrator, Developer
    Ok, my mistake..
Sign In or Register to comment.