Revisionary user now suddenly seeing only PublishPress
-
Unlike Revisionary, I see no way to SCHEDULE the revision after I create it. ?? If it’s an Administrator vs user issue, I also did NOT have that problem with Revisionary.
Kevin Hilley
101.9 The WaveThe page I need help with: [log in to see the link]
-
Kevin,
It sounds like your previous process was to use the “Manage Revisions” screen to set a future date for the Pending Revision and then schedule it. We’ve decided to replace that screen with a combination of the native post editor and the front end.
In the current release, here’s how you would replicate your process:
1) In the Revision Queue list or Revision Preview, hit the Edit link for the revision (not for the published post).
2) Set the desired future date and Update the revision.
3) Hit the View / Approve button. You should see the requested publish date displayed in the top bar. Hit the Approve button to schedule it.
We will probably further streamline this process in a future release.
-
This reply was modified 5 years, 4 months ago by
Kevin Behrens.
-
This reply was modified 5 years, 4 months ago by
Kevin Behrens. Reason: fix item 3 caption
Thanks Kevin. Ok, I feel really dumb because I do NOT see a place to update the revision. I see “save” revision and (as you see) the date has been corrected to what it needs. I tried to follow your instructions using “save revision” but then can’t find the Preview link. Again…feeling dumb. Screenshot link attached.
Thanks
Kevin
Hi @kevinhilley. Please check this documentation article: https://publishpress.com/knowledge-base/schedule-revisions-future/
@kevinhilley Sorry, I didn’t realize you are using Classic Editor, and also gave you the wrong button caption. I see that you are scheduling the publication of revisions that were submitted by Revisors. That’s a different sequence from the “Editor scheduling their own revision” doc that Steve linked. In your case, after using the Edit Revision screen to update an existing Pending Revision with a future date, you can schedule it through the “View / Approve” button:
https://publishpress.com/revision-view_approve/
In the Gutenberg editor, it looks like this:
https://publishpress.com/guten-revision-view_approve/
The View / Approve button leads to a front end preview of the saved revision:
https://publishpress.com/revision-view/
You can use the “Approve” button to schedule it:
https://publishpress.com/revision-scheduled-view/
-
This reply was modified 5 years, 4 months ago by
Kevin Behrens. Reason: image links
-
This reply was modified 5 years, 4 months ago by
Kevin Behrens.
-
This reply was modified 5 years, 4 months ago by
Kevin Behrens.
-
This reply was modified 5 years, 4 months ago by
Kevin Behrens.
-
This reply was modified 5 years, 4 months ago by
Kevin Behrens.
Hey Kevin- Yup, I see the Publish Now and other buttons at the top but for some reason they are not live links. I thought maybe it was a flash thing so I made sure that’s enabled, but that doesn’t fix it. Any thoughts?
-
This reply was modified 5 years, 4 months ago by
KevinHilley.
Another question- I had 3 weeks worth of revisions scheduled to go before Revisionary became PublishPress and I don’t see them anywhere. Did the update wipe them out? The first one was supposed to go live this past Monday morning.
@kevinhilley Your old revisions are not wiped out. There is an import script but shortly before releasing PublishPress Revisions I inadvertently removed the trigger that launches that script on plugin activation. Watch for an update to correct that soon.
@kevinhilley Can you look at that Publish Now button with browser developer view and tell me what the actual link URL is? Maybe there is a CSS conflict with your theme.
I’m unclear where it is on this, Kevin but hoping you can find what you’re looking for. Here it is- https://drive.google.com/open?id=148WkEtRbc3zyhPKnfNYUZudRPKwDf9tb
@kevinhilley Can you try another capture, clicking on the Inspector arrow first and then “Publish Now”?
https://publishpress.com/wp-content/uploads/2019/10/Browser-Inspector.png
After inspecting the Publish Now button, you should be something like this:
https://publishpress.com/wp-content/uploads/2019/10/Revision-PublishNow-Inspector.png
Thanks for your patience. Really trying here! This is what I see after I click on the inspector arrow and then Publish Now. That whole bar seems to be one unit without any individual links.
https://drive.google.com/file/d/1RE71E6uyTEUUC_Uegnmu8EQxrnOsgCSb/view?usp=sharing
Since you clicked on the Publish Now button and instead get Inspector date for the your “background-cover” div, this looks like a conflict with your CSS. I’m adding a new rule to the PublishPress Revisions CSS that might force clickthrough to the button links. That will be included in the update that I have ready to go out this hour. If the PP Revisions buttons are still being covered by your background div, you may need to adjust your that CSS on your side.
The upcoming release will also correct the import issue.
Ok, 5:34 pm Central time and problem persists. When I click on Publish Now or any of those buttons on that top bar, there is no lonk there. Nothing “live”. I also don’t see my previously scheduled revisions, but that may not have been addressed yet either.
I’m a bit above my nerd status with a lot of this, so if I go to my company web person about the CSS issue (if it turns out that’s the problem), what should I tell him to look for?
@kevinhilley I haven’t published the plugin update yet. It’s going out in about 5 minutes.
-
This reply was modified 5 years, 4 months ago by
Kevin Behrens.
PublishPress Revisions 2.0.5 is now available. If you don’t see your old revisions in the Queue right away, try manually deactivating and reactivating the plugin.
The CSS workaround should be considered just an initial attempt. If you still can’t click the buttons in the preview top bar, please open a support ticket on publishpress.com and I’ll take another look tomorrow.
-
This reply was modified 5 years, 4 months ago by
- The topic ‘Revisionary user now suddenly seeing only PublishPress’ is closed to new replies.