PLC marks files modified

We have two Publish LiveSite Content deployments - one to our resting region and one to production.

Somewhere in the workflow files that are added to the PLC to testing get marked "modified." Since we just dropped our LSCS database we need to redeploy everything (see post about active user community.) That will mark everything as modified when they truly are not.

is there a way to either
1) push content to our LSCS Runtime server without setting the modified flag
2) clear the modified flag in TeamSite without doing a Submit?

Find more posts tagged with

Comments

nipper

Have you customized the PLC ? It will attach some EAs on the files, though I am not certain if it is in 1 of the 2 attach metadata steps, attach deployment target or attach dependencies steps.

It would be worthwhile trying to figure out which step it happens (though that may take some time)

If it is in the deployment target, then your only choice is to scrap the PLC deployment step and build your own. Not horribly difficult, but certainly some effort.

Rick Poulin

1) push content to our LSCS Runtime server without setting the modified flag
Unfortunately not. The deployment task writes to the "DeploymentAudit" EA on all files and there's no way to turn this off (believe me, I've tried). I'm pretty sure the startdeploy.bat/sh does this too, but it's worth testing to confirm.

2) clear the modified flag in TeamSite without doing a Submit?
Setting the value of that EA back to what it was before obviously counts as a different change, so won't clear the flag. You'd have to trigger a 'revert to staging copy' on all files that weren't already modified before you started.

Bowker

Man - you guys are both buzz kills.

I was afraid of that. I looked through the CSSDK to see if there was a "setModifiedFlag([boolean])" method - nope.

Thanks.