WordPress.org

Ready to get started?Download WordPress

Forums

Role Scoper
[resolved] blank post status in new update (10 posts)

  1. gyutae
    Member
    Posted 2 years ago #

    I'm running Role Scoper with the Edit Flow plugin (which adds in custom post statuses). In Role Scoper, I have the the "post status" checkbox unchecked so that the two plugins play nice and don't cause any conflicts.

    However, with the latest update (1.3.29), the post status when going to an Edit Post page comes up as blank. Works fine on 1.3.28, however.

    Any ideas on why this may be happening?

  2. kevinB
    Member
    Plugin Author

    Posted 2 years ago #

    In Role Scoper, I have the the "post status" checkbox unchecked

    Where is that checkbox? I don't recognize that description.

  3. kevinB
    Member
    Plugin Author

    Posted 2 years ago #

    the post status when going to an Edit Post page comes up as blank

    Is that the dropdown in the "Publish" metabox? Does this happen for administrators or others? If others, what role assignment is their basis for editing the post? Any RS Restrictions in place?

  4. gyutae
    Member
    Posted 2 years ago #

    Hey Kevin,

    Thanks for the prompt responses!

    The checkboxes I'm referring to are under RS Options > Realm > Taxonomy Usage > post_status, and also RS Options > Realm > Term Scope > post_status.

    Yes, I'm having issues with the post status drop down in the Publish metabox on Edit Posts pages (i.e. they're coming up as blank and nothing is showing there initially). It happens for administrators and all roles, and I don't have RS restrictions in place.

    With Role Scoper and Edit Flow together, I used to get the same problem when those checkboxes for post_status were checked. Now after upgrading to the new version, I'm getting the problem even when those checkboxes are unchecked.

    Any ideas on why this may be happening? Thanks so much for the help!

  5. kevinB
    Member
    Plugin Author

    Posted 2 years ago #

    The only way I'm seeing this error is if "post status" is enabled under both "Taxonomy Usage" and "Term Scope".

    If the options edit form is failing to save your setting (forcing it to enabled), see the "problems with types / taxonomies?" link in the Post Type Usage section.

  6. gyutae
    Member
    Posted 2 years ago #

    Hey Kevin,

    That's what I was seeing as well (error with the Publish meta box when those two settings for post_status were enabled). However, after upgrading to the new version, I'm getting the same error even without the checkboxes enabled.

    Works fine again once I downgrade to 1.3.28, so I'm thinking it's because of one of the changes in the new version. Any ideas?

    I'm not having any issues saving the settings.

  7. kevinB
    Member
    Plugin Author

    Posted 2 years ago #

    What if you disable Roles > Options > Features > Internal Cache?

    Prior to RS 1.3.29, that feature was unavailable on new WP 3.1 installations.

    Note that I'm not seeing your error with RS 1.3.29/1.3.30, with or without Internal Cache enabled and none of the code changes look suspicious. But enabling Internal Cache will use some additional memory, so if you were running close to your server's PHP Memory limit that may have pushed you over the edge.

    My guess is something is preventing the Edit Flow javascript from loading/executing. What would be helpful to me is the contents of your PHP error log and/or browser javascript error log.

  8. gyutae
    Member
    Posted 2 years ago #

    Hey Kevin,

    I tried disabling the Internal Cache and still no luck. However, when I deactivate the Edit Flow plugin with the new version of Role Scoper active, the problem goes away.

    So I think it's clear that it's some sort of incompatibility with the Edit Flow plugin that was introduced in the new version of Role Scoper (1.3.29). The two work fine with 1.3.28 as I mentioned.

    Does that help at all?

    I'm not seeing any errors in the PHP or Javascript logs.

  9. kevinB
    Member
    Plugin Author

    Posted 2 years ago #

    Since I still haven't been able to reproduce the problem, I'll need some diagnostic access to pursue it any further. Drop me a contact if you want.

  10. kevinB
    Member
    Plugin Author

    Posted 2 years ago #

    This is fixed in Role Scoper 1.3.31. Basically, a change in 1.3.29 prevented RS filtering from being totally disabled for a taxonomy.

    Thanks for your cooperation in tracking it down.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic