I have a node that was erroneously sent to the recycle bin. It's since been restored to the proper location, but now it can't be published, as it throws an error saying it's in the recycle bin (see this video for an example of this issue). I assume there is just a flag that is out of sync. The node has the message "This document is published but is not in the cache" in the info section, but I've tried refreshing the index, memory cache and database cache, and the issue persists. Any idea what I should do to clear this up?
When the item was removed from the recycle bin, was that on the main site or was it removed from the recycle bin on one site and then synced with the other site.
It entered the recycle bin on one of the development environments, based on the usync config history for the node and was later restored on one of the other development environments after that issue was imported. One possible cause I can think of is that the erroneously recycled content was restored while the import was still running.
Node failing to publish publish with message saying it's in the trash even though the recycle bin is empty.
I have a node that was erroneously sent to the recycle bin. It's since been restored to the proper location, but now it can't be published, as it throws an error saying it's in the recycle bin (see this video for an example of this issue). I assume there is just a flag that is out of sync. The node has the message "This document is published but is not in the cache" in the info section, but I've tried refreshing the index, memory cache and database cache, and the issue persists. Any idea what I should do to clear this up?
Hi Jesse
Just so I can track down any issues.
When the item was removed from the recycle bin, was that on the main site or was it removed from the recycle bin on one site and then synced with the other site.
Kevin
It entered the recycle bin on one of the development environments, based on the usync config history for the node and was later restored on one of the other development environments after that issue was imported. One possible cause I can think of is that the erroneously recycled content was restored while the import was still running.
is working on a reply...