Recently revisioning has begun erroring out on creating new revisions of existing pages. I have replicated the issue in 3 separate drupal instances. The issue appears like so- when editing a revision, the edits go in per normal, then on save, the save message is presented with a 404 underneath where the revision number for the page is quite high (e.g. The requested page "/node/12/revisions/7495/view" could not be found. ) however you can navigate to the node page (e.g. "/node/12/revisions") and view the newly created revision - and see that it's a much lower number (in this case "node/12/revisions/25/view" was the valid URL). However, the revision that's saved is entirely devoid of content.

Any Suggestions?
Thanks in Advance.

Comments

rdeboer’s picture

rdeboer
Location Melbourne
commented

Hi Ncouraud,

"Recently it has begun...."
Yep that's the time bomb virus I put in to intermittantly do what you describe, starting 10 Dec 2012. It will slowly get worse....

But seriously.... If you haven't changed to another version of Revisioning, then something else must have changed, don't you think? Some other module that interferes, perhaps?

ncouraud’s picture

ncouraud commented

Apologies - I'm just coming into this environment, so I don't quite know what's been updated since the site's content was last edited. As far as maintenance I've run; this appeared post updates to core (7.15->16), pathauto, redirect, chaos tools, and views. As I've been troubleshooting this, I've been able to build out a staging instance of all 3 sites with the same architecture and module configuration, and I am unable to reproduce what's going on in the production instances, so I feel as though module interference would be improbable.

Are there known incompatibilities with the latest versions of any of those modules?

Looking into the DB- it appears as though the revisions are saving in the field_revision_body table with the revision IDs that initially come up, but that the number assigned in the node_revision table is different - causing the discrepancy.

rdeboer’s picture

rdeboer
Location Melbourne
commented

Of those modules Redirect sounds like a possible spoiler.
Have you checked its issue queue?
Rik

ncouraud’s picture

ncouraud commented

Ok, I think I've isolated the issue - and I can't tell if it's with revisioning, core or the DB. I'm inclined to think it's the database environment, however looking over the code I can't seem to come up with what could be causing the issue.

Essentially the issue I have is this - node edits are being saved to the DB but with differing values for node_revision.vid and field_revision_* tables. looking at node_save, field_attach_insert, and the revisioning module code, they all appear to use the vid stored in node_revision, and that's all that should be in the node_save workflow. I am not sure how or where this second value is getting introduced at all.

rdeboer’s picture

rdeboer
Location Melbourne
commented

Thanks for the update Nicolas.
If you get any closer to a solution for this issue, let us know.
I wish I had any smart ideas, but I haven't...
Rik

ncouraud’s picture

ncouraud commented

This issue was in fact caused by the SQL driver being used in the environment.

ncouraud’s picture

ncouraud commented
Status: Active » Closed (works as designed)

Closing Issue.