ERROR "Headlines: this post can't be referenced." in creating new edition
Sat, 01/05/2010 - 13:17
i'm starting a new discussion topic here in reference to a comment/question i posted at: http://www.prosepoint.org/node/491#comment-1383
i am very new at ProsePoint and Drupal...
i have a client who is trying to schedule an Edition to go live this coming monday, the 3rd of may, 2010. however, she keeps on getting error messages after she assigns headlines to this edition. "Headlines: this post can't be referenced." the stories are Published but not yet Public until the Edition is Public. (see attachment) any ideas for how to fix this? the expected behavior is that the client would be able to create layouts for future editions and preview them without them being public. maybe this is not how ProsePoint works? please advise. thank you!
Mon, 03/05/2010 - 14:15
#2
publishing future editions
to answer your questions:
- the story nodes w/ nid's 192, 223, 218 were created by the client so yes they have access to those nodes.
- they are Published nodes in that they all have the Published checkbox checked.
- their states were all "Ready for Print" (ie: not Public).
- i believe the message occurred both when they first tried adding the stories to the editions and subsequent tries after.
- i removed the Basketball Team Thrives [nid: 192] story and tried re-adding it to the Headlines again, but it did NOT appear in the autocomplete textfield's dropdown list even though it is assigned to the "Fit Life" channel under ../node/192/edit
other strange behavior we're noticing:
- even though those three stories in question [nid's 192, 223 and 218] for the upcoming issue were not Public yet, they were showing up in the sub-channel block listing of the Current Issue.
- when i look at the website at 1:50am as an anonymous, the new Issue 7 for the Fit Life channel is showing up even though its publish time is supposed to be 5am on May 3rd, 2010. (see attachments) is there a place to figure out which time zone the site is using?
please advise. thanks for you help!
| Attachment | Size |
|---|---|
| edition_adminview_5am.png | 149.65 KB |
| edition_publicview_150am.png | 298.08 KB |
Wed, 05/05/2010 - 10:03
#3
...
Hi,
> but it did NOT appear in the autocomplete textfield's dropdown list
This is a clue. If the story does not appear in the dropdown list, then it isn't a valid story which will be accepted when you try to save the edition.
For example, if in the past the story was already part of the edition, but later something happened to the story to make it not a suitable item (for whatever reason), then if you save the edition, it will complain that the story can't be referenced.
The story has to be available via the dropdown list before it can be accepted. So now the issue turns to why those stories are not in the dropdown list.
Hmmm.... I might have to have a very close look at your site ... either by logging in via an administrator account, or you sending me a copy so I can recreate a test site. Please contact me through the contact form (or email) and we'll work out something.
> is there a place to figure out which time zone the site is using?
Try visiting .../admin/settings/date-time, maybe change it's value to something more suitable for yourself, and see if it fixes anything.
Wed, 05/05/2010 - 11:20
#4
valid stories
thanks, beng.
i'll send a message via your contact form to get instructions for giving you a copy of the site.
ardith
Wed, 05/05/2010 - 23:47
#5
TIME ZONE SETTING + NEW EDITION TEST!
UPDATE:
#1: changing the time zone settings at .../admin/settings/date-time fixed why we in NYC and LA were seeing content going live before our Schedule for dates. it's one of those things that i had been searching and searching for but couldn't find only because i didn't look hard enough. thank you for pointing it out!
#2: after creating a test edition scheduled for the future w/ test stories also scheduled for the future, i discovered that i COULD lay out the edition behind the scenes as long as the story states were "Private". using any other state in our custom workflow would render a story invalid for the future edition. maybe we need to adjust something in the workflow settings??? my client has a pretty extensive workflow for their team. it would be unfortunate if their web editor couldn't lay out stories in the edition until the workflow were complete because oftentimes their story approval process takes all the time they have right before the edition needs to be published.
long story short, i believe we were receiving the "cannot post" error message because the stories had started off as "Public." they were all Public because we were having the time zone issue and it felt easier to make everything the same state. then, we were having issues with future stories showing up in the Current editions. therefore the story states were rolled back to one of our custom "Ready for Print" states, which as i mentioned, unfortunately does not appear to be a valid state for a story to appear in an edition. shall i open a separate discussion thread about the workflow states?
thanks again for your help!
Thu, 06/05/2010 - 12:33
#6
...
Hi,
Ouch, I think there is a setting within story_view which needs to know about your additional workflow states. The way you described it made me think of it.
So I'm going to have to get you to edit story_view. But first, you have to enable the Views UI module. Here goes ...
Visit .../admin/build/modules on your site and enable the module Views UI.
Then visit .../admin/build/views on your site, look for story_view and then click on Edit to edit it.
On the resulting page, look for the Filters box and then look for the sentence "Workflow: Current state in ..." and click on the blue part of it. (See screenshot)
In the box which appears, you need to select your additional workflow states for which a story is considered published or ready for layout.
Then click Update and Save. And hopefully it will fix your issue.
Let me know how it goes.
| Attachment | Size |
|---|---|
| Screenshot.png | 246.47 KB |
Thu, 20/05/2010 - 03:10
#7
editing story_view
apologies for the delayed response. just tried this solution... just wanted you to know that editing the story_view worked like a charm! THANK YOU!
Hi,
If you have story nodes which are published but set to states such as Private (ie. not Public), they can be included into the Headlines field of editions. I've just tested and confirmed this.
Are your story nodes with nid's 192, 223 and 218 published nodes? If your client visits .../node/192, are they allowed to view the node?
The other thing to check is ... when this message occurred, were the nodes 192, 228 and 218 already part of the edition? Or are they new additions?
If you try to add the story Basketball Team Thrives [nid: 192] to the Headlines again, does it appear in the autocomplete textfield's drop down list?