WordPress.org

Ready to get started?Download WordPress

Forums

Page Security by Contexture
[resolved] Clicking on Restrict Access on a new post brings up 'An e (6 posts)

  1. cdaluk
    Member
    Posted 2 years ago #

    When authoring a new post, clicking on the 'Protect this page and its decendants' check box in the 'Restrict Access' sidebar leads to a popup message saying 'an error occured:'

    I'm using the latest version of Page Security on version 3.3.1 of wordpress.

    Old posts still have their page permissions set and still have access to the Restrict Access group select drop down lists, it appears this only affects new posts.

    site: http://www.barnstormers.org.uk

    Thanks for a great plugin.

    http://wordpress.org/extend/plugins/contexture-page-security/

  2. mophilly
    Member
    Posted 2 years ago #

    I just installed the plugin in WordPress 3.3.1, activated the plugin and visited a page to mark as private. I clicked on the checkbox in the sidebar and the same error was raised.

    A dialog is presented saying an error occurred but no explanation text is presented.

    Looks like a good plugin. I hope this fixed quickly.

  3. tdawson
    Member
    Posted 2 years ago #

    *3 on this error

  4. cdaluk
    Member
    Posted 2 years ago #

    For those with this error I have discovered a way around the problem.

    If you create your new post and click 'Save draft' you'll then have access to click the 'Protect this post and it's decendants' You should then get the 'An error occurred:' pop up. If you then dismiss the pop-up by clicking 'OK' and click 'Save Draft' again you should gain access to the list of groups and you can apply rules as normal by selecting relevant groups and publishing as normal.

    Hope this helps whilst the plugin is being fixed!

    S

  5. Matt van Andel
    Member
    Plugin Author

    Posted 2 years ago #

    Hey all,

    I'm going to try to iron this out with a few other bugs this weekend (no promises, things are still extraordinarily busy through the second week of February). It's simply due a minor change in the way newer versions of jQuery work with the latest WordPress releases. The permissions will still be saved, but that first "protect" click doesn't correctly recognize the success response that WordPress sends back.

  6. Matt van Andel
    Member
    Plugin Author

    Posted 2 years ago #

    For anyone stumbling on this. The bug was fixed in 1.5.5.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic