nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Delete contents in LSCS stores from TeamSite

juanrod

Hi all,

we have created lot of contents in TeamSite and then we have deployed them using the PLC workflow.

Then, we have removed some of them from TeamSite.

After some time we have noticed that the contents have not been removed from the lscsauth-store and lscsrt-store.

How should we proceed to remove the contents from all the stores?

I will appreciate your help!

Find more posts tagged with

Comments

nipper

What OS, version of TS, LSCS, etc?

Did you submit the deletes to the PLC workflow ? That should clean them up,

Rick Poulin

The LSCS portion of the PLC will correctly remove content when you submit the *deleted files* and not *deleted folders*. LSCS has no understanding of folder structures, so when you submit a folder deletion, it doesn't match any LSCS key and nothing gets deleted. If you want to make it user-proof, you'd want your workflow to "undelete" the folder, recursively traverse the folder tree and attach all files, delete all files, deploy, then delete the folders, then submit.

There's no way to manually delete entries from LSCS other than to delete the whole branch/project and redeploy current content.

GRD

There is also a 7.2.1 bug where files are never deleted from the LSCS store. If you are on 7.2.1, check with Support.

-Greg

juanrod

Thanks ... but the files do not appear in TeamSite as the users did not send them to Staging, they deployed them using the PLC workflow straight ahead... any idea to fix this?

With the OTB PLC is necessary to "Submit" the contents first and then deploy them?

GRD

Thanks ... but the files do not appear in TeamSite as the users did not send them to Staging, they deployed them using the PLC workflow straight ahead... any idea to fix this?

With the OTB PLC is necessary to "Submit" the contents first and then deploy them?

This is a classic problem, and will bite you also with DataDeploy. You deploy files without versioning them, and there is no deletion to submit to LSCS or DataDeploy. It is best to version the files by submitting to STAGING.

Even the out-of-the-box PLC workflow, invoking the LSCS deployment to the development node can suffer from this.

Can you get by with user training?

-Greg

juanrod

Unfortunately it is a customer requirement, to publish contents in one click...

nipper

Obviously something is screwed up, either with your workflow or your process (user training). In a properly setup WF that should not happen.

If you cannot live with it, you will need to dump the project and then rebuild it. That is a time consuming process.

nipper

Unfortunately it is a customer requirement, to publish contents in one click...

Then whoever built it, built it wrong. Rewrite the workflow properly and then dump the LSCS project and resubmit it.

Adam Stoller

There is also a 7.2.1 bug where files are never deleted from the LSCS store. If you are on 7.2.1, check with Support.

-Greg

I think I just experienced this (TS/LS 7.2.1 on Linux).
I deployed a Page file as part of a test of my fanout process (partially working!) - and the file was deployed to the intended path on both app servers and inserted into both server's associated LSCS server (yay).

I then deleted the page file and re-submitted it with the same workflow (custom variant of PLC) - and I notice in the teamsite-areadiff logs on the receiver side that the deletion directive is associated with the temporary directory for the file, not the actual directory for the file. E.g.:


LIB: ... Deleting item [/usr/LSCSRT-Store/98dewn5.../content/sites/ABC/dir/FILE.page] -- does not exist to be deleted.

So - the file doesn't get deleted from the file system.

Are you saying there's a patch for 7.2.1 that fixes this?
An official patch (there's at least one out there) or a "special" patch that you actually have to explicitly ask for?
If the latter, do you have a bug id or case # that we can use as a reference to get the right patch?

GRD

Be sure you are using 7.2.1 P1, as it resolves several bugs. You'll especially want this if you are on Linux as it fixes the 32k folder limit problem, and the IDOL indexing-backup issues. I'm not sure about the deletion bug--check with support.

Sorry, I don't have a ticket number handy.

Also, are you using lscsclient.jar? There was a nasty bug where content requests would get mixed-up if you had more than one LSCS project. I don't see it listed in the P1 release notes, but I helped track this one down in Sep. 2011, and the lscsclient.jar for 7.2.1 P1 is dated 11/9/2011, so it's probably there.

-Greg