Hi,

We run Scheduler on a news website that posts all its articles at 1am on a Saturday. The content is created during the morning Friday. Through Friday afternoon, different people edit and update the articles.

Our issue is that often (but not always) we have a problem where the article that is then published on the Saturday morning is the original piece, not the edited, updated version.

It's very hard to recreate this in a test environment, and generally hard to pin down whats happening where.

We've disabled 'Scheduler-Publishing-"Create a new revision on publishing" thinking it may relate to a weird revisioning issue.

We don't believe it's a user error issue, but that can't be ruled out.

Sorry this lacks specificity, but any general ideas/hints/potential problem points would greatly assist.

Thanks,

Rupert Dance

Comments

rupertdance created an issue.

jonathan1055’s picture

jonathan1055 CreditAttribution: jonathan1055 commented

Hi Rupert,
Sorry to hear you are having a bit of trouble. You mention revisioning and that must be the key to this, as Scheduler does not store any old content, it merely changes the status and optionally creates a new version. So if an earlier version ends up being the 'published' version then my first thoughts are (a) Scheduler (or another module) is setting the revision id back to the earlier one, or (b) the new edits are somehow are not marked as the 'newest' after editing is complete.

Some questions:

  1. When the problem happens, what can you see in the 'revisions' tab when viewing the node? i.e. is a new version created which is a copy of the original?
  2. To track what is happening you really need to look in the node_revisions database table, do you have access to this?
  3. Check the node_revision rows when a node is set up for scheduled publishing, then check the table again after the node is published, and see what has changed
  4. Do you have any other modules which might be setting/changing the version id?
  5. Does it make a difference if the final edit is just setting the publish-on date, ie not altering any content?
  6. If you have several versions, is it always the first which is reverted to after scheduler has published the content?

That's enough to get us started, I'm sure we can help resolve this.

Jonathan

rupertdance’s picture

rupertdance CreditAttribution: rupertdance commented

Hi Jonathan,

Thanks for getting back to me so quick!

Revisioning was certainly our first though, but we have disabled it in the obvious places as best we can.

In answer to the questions:

1. No, currently we don't see any anything in the revisions tab of any of the stories.

2+3. Yep - I do have access. In our attempts to try to recreate the problem, we have made some dummy stories, then had someone else edit them, then schedule for publish. They rows in node_revision for the story does not change OTHER than the UID going from initial poster, to editors #, then to '0' - which I take it is the Scheduler.

4. Not that I'm aware of, we are running many modules though - do you have any hints as to which/what sort may affect things?

5. I'm afraid I'm not sure on this one. We are frustratingly unable to reproduce the error at all during the week. It occurs on our publish date (Saturday) but Scheduling pieces overnight throughout week all works correctly so far.

6. We aren't ever really 'versioning' it. We simply save it, then later proof-read it and need to change words/images. So we just edit+save over the original.

Is there somewhere in the DB other than node_revision that lets us see if a node does have multiple revisions? We only need 1 version of things, as its always the most up-to-date.

Hope this helps!

Thanks again,

Rupert Dance