Pimcore: [Bug] Renaming unpublished object is no more possible.

[Yivan]

Hello,

On the online demo Pimcore website, if you do on the backend :

• create a new "News" object at the root of the object tree and call it "test"
• save it (not published)
• rename it in the tree

You will get an error with message: You can't relocate if there's a newer not published version

Actually we cannot rename in the tree unpublished object. I think it is a pretty new bug because we haven't this one on older Pimcore.

[dvesh3]

this is the case if there is "a newer not published version", please see https://github.com/pimcore/pimcore/issues/4905 and also https://github.com/pimcore/pimcore/blob/ce2138fb35fe84ab3fa22ba7cf0a882c6cb9341f/bundles/AdminBundle/Controller/Admin/DataObject/DataObjectController.php#L997-L1004

[Yivan]

You mean it is intended ?
Now we must publish object to be able to rename the key ?
I mean the 3 step actions i done (see first post), are pretty common and many users can fall in this message.

I think we really must be able to rename the key not depending the published state, like it was before.
Content/data managers need this to be able to prepare datas without publishing objects (same for documents).

I link it to this issue, maybe related or at least in the same scope:
https://github.com/pimcore/pimcore/issues/5136

Thanks.

[jms-gsulcer]

Not just objects, this also affects documents as well. This is a new behavior, somewhere between 6.2.1 and 6.5.3 (we have both versions running).

This is a big issue with documents because it is common that documents are created with "placeholder" values while SEO strategies are developed, but the document remains unpublished until all information is final, including the document key.

Currently, we are forced to first publish the document, then rename it. It's not catastrophic, but it does mean the document is "live" on the site for a brief period, which is unexpected behavior