• I am aware that this plugin has affected two separate plugins:
    – OneSignal Push Notifications
    – Jetpack Publicise

    The issue seems to come from having a different published status. Usually, posts would be published, and this triggers OneSignal to send out Push Notifications to mobile subscribers, and also triggers a secondary action where I can Publicise the post to Social Media.

    I believe that if we are able to revert back to the standard Publish Post action rather than the Publically Publish Post action, this would be resolved.

    The page I need help with: [log in to see the link]

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

    (@shawfactor)

    If there is an issue it’s not the extra post status as the extra status does not effect the normal published status at all. Post status transitions all still work as per normal

    Can you outline the behaviours you are seeing? I don’t use either of those plugins (and would never use any jet pack functionality) so I’m flying a bit blind.

    Thread Starter dharborne

    (@dharborne)

    I have only posted once since installing the LH Archived Post Status plugin.

    A few things I noticed that were different after installing the plugin:
    – When I create a new post, usually there is no title. The new post automatically adds the title “Auto Draft”. I don’t think this affects anything.
    – The new post is automatically in DRAFT status. If I want to publish the post, then I need to change the status to Publically Publish and click the UPDATE button. Usually, I would see the PUBLISH button. Because I am no longer seeing the PUBLISH button, I am no longer triggering the PUBLISH hook.

    I am not familiar with WordPress hooks etc, so I am hoping this could be resolved.

    Plugin Author shawfactor

    (@shawfactor)

    Thankyou that give me something to start looking at

    However am travelling atm and don’t have a laptop or svn. In two weeks I’ll be back in my office and will look at the issues in detail.

    Your help is much appreciated

    I’d like to confirm all of the above. I love the plugin, I like the way it removes posts from the loop, but still leaves them available through search and would find it extremely useful. But as a non-profit healthcare organisation with 300 non-technical editors, whereas I understand that the title for a post is Auto Draft (instead of Title) and need to change to Publicly Publish then update (instead of just Publish button), I can’t explain this to all of our Editors and I know I would face an avalanche of “what’s going on?” questions.

    If the plugin didn’t alter the standard WP new post workflow, it would be perfect. Anyway, this is in no way a complaint – the plugin works excellently, it’s the best archiving plugin out there. I understand if it simply has to be this way and can’t be changed, this is just an observation of why I am with regret not able to utilise it.

    Thread Starter dharborne

    (@dharborne)

    It’s been a few weeks since an update here. At the moment I am keeping the plugin deactivated until an update provides a fix for the issues I raised.

    After installing the plugin, the Save Draft and Publish button have disappeared…I only have Preview and Update…which means I have no way to save a draft of a post, it gets published when I press Update which is the only way to save the post.

    Plugin Author shawfactor

    (@shawfactor)

    @dupuisg the Save Draft and Publish options are are still there in the status drop down

    Plugin Author shawfactor

    (@shawfactor)

    @stevieboy23 and @dharborne I have raised the auto draft issue with the author of the underlying library, I’ve looked at the code and it there is nothing obvious (and it is library related rather than pertaining to my plugin functionality as it happens when the library is used on a standalone basis).

    Seems a minorish thing though, although I agree it could be confusing

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Conflict with two plugins’ is closed to new replies.