• Resolved maryb1

    (@maryb1)


    Hi,

    I’ve noticed that when this plugin is activated, within each page/post, the visibility of all posts is set to “Private”, and then underneath it says its status is “Published publicly” (or “Archived” depending on what you choose…). See: https://imgur.com/a/8sMZYBU

    I tried switching the Visibility from “Private” to “Public” but it reverts back to “Private”. If I deactivate the plugin, this issue is gone.

    Now, the posts are not really “private”, I do see the posts when logged out, but it’s a bit confusing. Also, since the post visibility seems to be set to Private, the SEO framework plugin thinks the posts are private and puts its default index setting to “Default (noindex)”. Again, they’re not really not indexed, but this is confusing and is based on the “Private” setting that seems to come from this plugin.

    Is there a way to keep the default posts visibility to “Public” instead of “Private” while this plugin is activated?

    Thanks!

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author shawfactor

    (@shawfactor)

    I’ve not seen this behaviour. Does it occur when you deactivate all other plugins?

    I just installed latest WP (6.6.1) & latest plugin (3.10). So no other plugins. No modifications.

    View post on imgur.com

    If plugin is not activated, you can change post status on top (#1).

    After plugin is activated, post-edit pages gets 2 status sections (#1, #2 in bottom), where you can change status. Plugin still works, and if you look at bottom part (#2) , everything looks OK. But let’s say new editor comes, he is used that you change status on top (#1) and now it always show “Private” for all posts (drafts & public ones). If you try to change it, it will not work and have no effect. Very confusing. In past top section (#1) was called “Visibility”.

    p.s. Plugin was great, but from WP 6.6 I think you can not use this plugin anymore. You use old WP or remove plugin…

    Plugin Author shawfactor

    (@shawfactor)

    Okay so the issue is real since 6.6, although I completely diagree with your statement that the lugin is no longer usable. Its just confusing

    Anyway the plugin is a combination of my own work and that of @imath who has a wondeful library that tries to work around the fact that wordpress does not have a proper api for custom post statuses. I’ve raised the issue and followed up with him on upgrading the library to work with wordpress 6.6.

    see here:

    https://github.com/imath/wp-statuses/issues/94

    Plugin Author shawfactor

    (@shawfactor)

    The latest version of this plugin incorporates a fix implemented in the wp-status library. So this issue should be resolved now. Can you please test?

    Everything looks good and clear now.

    Plugin Author shawfactor

    (@shawfactor)

    resolving for good order then, thankyou

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.