Change Object Parent / Key without Flushing Saved but Unpublished Changes

[cancan101]

If I have "saved" but not "published" (ie in DB) changes to an Object, is there anyway to change an Object's Parent (or Key) without also flushing (i.e. saving) those other changes to the DB?

We would like to change an Object's Parent as it moves through a workflow (so that our users can easily find all of the Objects at a given state). However we are not publishing (to the DB) until the final state of the workflow. Unfortunately any change to the Parent field requires a "save", which then flushes all the other saved but unpublished changes to the DB.

Is there any way around this, where I can selectively update in the DB only certain fields (ie the Parent)?

[markus-moser]

This is a quite complex question. There is definitely no way to selectively update single fields only. But when you load the current object from the database you will get the currently stored database state/entry. When you then only change the parent and save the object with disabled object versioning (Version::disable()) you will only change the parent in the database and not infect or create any versions. In the unpublished version you would then need to ensure that it does not get moved back to the original folder as soon as it get's published.

When you want to do this some kind of event listener within the workflow you could do something like: $object = AbstractObject->getById($object->getId(), true) to force getting the database state of the object.

[markus-moser]

Just calling save() should not load the version from the file system and persist it to the DB, the file system version should still exist and be ontouched.

[cancan101]

Just calling save() should not load the version from the file system and persist it to the DB, the file system version should still exist and be ontouched.

What is the process in PImcore that causes Pimcore to cleanup the file system record? (ie to mark it as "applied")

[cancan101]

So far I still can't get the publish logo to show:

This is the logic used to determine if the publish icon should be shown:

renderer: function (d, metaData, cellValues) {
    var d = Ext.Date.format(cellValues.get('date'), "timestamp");
    var versionCount = cellValues.get('versionCount');
    var index = cellValues.get('index');
    if (index === 0 && d == this.object.data.general.versionDate && versionCount == this.object.data.general.versionCount) {
        if(this.object.data.general.o_published) {
            metaData.tdCls = "pimcore_icon_publish";
        } else {

The mismatch is here: d == this.object.data.general.versionDate, so what causes that to be set?
I am currently using this:

$object = DataObject\AbstractObject::getById($object->getId(), true);

$parentId = $parentObject->getId();
$object->setParentId($parentId);
$object->setKey($key);
$object->setModificationDate($object->getModificationDate());
$object->setUserModification($object->getUserModification());

\Pimcore\Model\Version::disable();
$object->save();
\Pimcore\Model\Version::enable();

[markus-moser]

This version date is based on the modification date. The reason why it does not work is that the modification date only is set as dirty when it actually changes:

https://github.com/pimcore/pimcore/blob/11.x/models/Element/AbstractElement.php#L162

All of this seems to be really some kind of hack, but if you would like to achieve that the published checkbox is still there, you would need something like this:

$object = DataObject\AbstractObject::getById($object->getId(), true);

$parentId = $parentObject->getId();
$object->setParentId($parentId);
$object->setKey($key);
$modificationDate = $object->getModificationDate();
$object->setModificationDate(0);
$object->setModificationDate($modificationDate);
$object->setUserModification($object->getUserModification());

\Pimcore\Model\Version::disable();
$object->save();
\Pimcore\Model\Version::enable();

[cancan101]

That worked! Is there anything I should be concerned with as far as the object cache?

pimcore/models/DataObject/AbstractObject.php

Lines 738 to 739 in d44ada0

	//set object to registry
	RuntimeCache::set(self::getCacheKey($this->getId()), $this);

[markus-moser]

No the cache is no problem at all.

[cancan101]

For my understanding, what does the concept of a field being marked dirty mean?

[markus-moser]

dirty means that the field value got changed

[markus-moser]

What is the process in PImcore that causes Pimcore to cleanup the file system record? (ie to mark it as "applied")

The data object (so the database state) and it's version are two relatively independent things. The version is a php serialized version of the object on a given timestamp in the filesystem. So it contains all attributes 1:1 as they were when you saved the object and the version was created. So when you are working with the normal PHP API you will not get the latest version but the data object (database representation). The whole topic of "replacing" the data base state with information from the filesystem version is done in the Pimcore backend (see e.g. here https://github.com/pimcore/admin-ui-classic-bundle/blob/d191bcd0184f77e3ac9d25270ee02a4fcc2496aa/src/Controller/Admin/DataObject/DataObjectController.php#L302). So when you open the object you will see the latest version instead of the database content. When you then publish the object the version information will be persistet in the database.