eZ Community » Forums » Developer » eZ LS: Node disappeared from content...
expandshrink

eZ LS: Node disappeared from content structure

eZ LS: Node disappeared from content structure

Friday 02 May 2014 2:14:01 am - 4 replies

Hi everyone,

I have an installation where some nodes have wound up disappearing from the content structure. This happened a total of 3 times. We're unsure what triggered the issue.

System Information:

  • eZ Publish LS 5.1 (pure LS, pointing to ezpublish_legacy folder entirely)
  • PHP 5.4.17
  • Apache 2.2.23
  • MySQL 5.1
  • There are 5 languages (content translations) in the system: English, Korean, Japanese, Chinese(TW) and Chinese(CN).
  • Clustered installation (DFS)
  • There is no special workflow or customization to the installation on the admin interface that would affect the last user who modified this content.
  • No special permissions for the user (they were in the administrator group)
  • No error appeared for the user (as far as we know)
  • No errors in logs

One piece of content had a node_id: 8075 and object_id: 5602. It was not accessible via /content/view/full/8075 or its nice URL (kernel error 3)

Accessing via content/versionview/5602/7/eng-US/site_access/admin would work.

You could see its versions via /content/history/5602 and the last reported edit was the Korean translation.

After some digging into the MySQL tables I found that the entry in ezcontentobject_tree had a version number, 8, which is one ahead of what's reported as the latest version in ezcontentobject_version, 7. The version number 8 had no attributes available in ezcontentobject_attribute for the contentobject_id of 5602. Only entries for version 7 and prior.

The entries in ezcontentobject_attribute for version=7 contained 20 entries, 5 attributes per language. The version was missing the chi-TW translation, but reported it existed.

Two scenarios make the version numbers become remedied:

  • After running a MySQL update on the entry in ezcontentobject_tree with the version number 8, the node was then viewable in the admin interface
  • After going to /content/history/5602 and copying a eng-US translation and re-publishing the node brought it back into the content tree

Any ideas? Any issues with translations?

I haven't seen an issue like this before, any insight would help and I am happy to provide more info as long as my client's info isn't displayed.

Friday 02 May 2014 4:20:59 pm

standard publishing actions should all be using transactions to guarantee integrity, even in case of aborted operations

1. which version are you on?

2. do you use custom workflows/edit-handlers/import-sripts/similar ?

Friday 02 May 2014 5:34:24 pm

Quote from Gaetano Giunta :

standard publishing actions should all be using transactions to guarantee integrity, even in case of aborted operations

1. which version are you on?

2. do you use custom workflows/edit-handlers/import-sripts/similar ?

Gaetano, thanks for the reply however, if you would have read my post you would have the answer to your questions. eZ LS 5.1 and no special edits to the admin interface or workflows.

Thanks

Monday 17 November 2014 1:26:11 pm

Hi Guys,

We are on version 5.3.2 enterprise and we experienced the same issue. At the beginning I though it is human error but after it happen three times it must be system bug.

Brandon, does it still happens to you?  

Saturday 06 December 2014 2:21:49 pm

I have a gut feeling that this is a concurrency issue.

I haven't dug to the bottom of this pit, as I'd really need a good reason to do so, but I'm reasonably convinced that there are a couple cases, in a multi-language / concurrent editing situation, where nodes could get foobared. Your symptoms sound like they could match.

One easy way to figure it out would be to enable asynchronous publishing. The asynchronous queue reader will only permit publishing of one version of each content object at the same time, and will preserve queue ordering.

If I'm right, enabling it will make the issue disappear. Let me know happy.gif Emoticon

expandshrink

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from