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; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

How to Edit and Expiry content in WCM?

shmu80

Hi all,

I am fresh in alfresco, I just wonder, after I submit the new content to Staging and deploy it, how can I do some edition for the content (may be in the future I need to add in some new information)? and How can I change the expiry date of the content, in another way, is how to delete the content which had been submitted?

Please advise.

Thank you.

Find more posts tagged with

Comments

kvc

Welcome to Alfresco.

When your content is committed to Staging, it is snapshoted. A snapshot is analogous to an edition and you can rollback to any snapshot or redeploy any snapshot at any time.

If you notice in your Submit Wizard, in 2.1 you have the ability to set an expiration date on the content contained within your latest Staging snapshot (your list of items to submit). You can set a global value or override on an asset by asset basis. There is a separate Quartz job auto-configured in scheduled-jobs-config.xml. Nightly at 3:30am, the server retrieves all expired items and assigns them as change request to the publishing author.

Take a spin and let us know how it goes.

Kevin

shmu80

Hi KVC,

Thanks for your reply.

Base on your idea, if I submit 3 new content in once to staging sandbox, and after I want to edit/expired only 1 content from the 3, so how can I make it? Is it I need revert the submission and recreate all content again? Or during submission, I had to submit content by content?

Please advise.

Thanks again.

kvc

Hi -

When you commit your finalized changes to Staging (check-in), our Submit Wizard prompts you for an Expiration Date. You can set a global expiration date for all assets contained within your submission package, and then you can update each asset individually to override the default or remove the expiration date entirely.

When content expires, a change request is assigned to the user, who can determine whether the content should be deleted or refreshed. We do not presume to know whether or not the content should be deleted; our out-of-the-box workflow makes this an editorial decision (of course, you can do whatever else you want here. We do recommend this as a best practice, though).

If you either delete or update the content and submit your finalized change request, after whatever approvals you've configured, you will have a new snapshot committed to Staging that you can then deploy to your live environment. In the simplest case, that new Staging snapshot might only be defined as a single change to the site, a deletion of a single asset.

Try walking through this in the GUI. Please note that the expiration job is scheduled in our schedule-jobs-config.xml Spring config file and by default runs at 3:30am (you'll see this when you look at the config file). If you are testing content expiration, I recommend on a test system to change this default to something that supports a bit more rapid dev and test - for example, changing this to run every 5 minutes or so.

Kevin

himanshu

Hi Kevin,

I was using the content expiration mechanism in Alfresco Labs 3c.

I faced the bug reported here : https://issues.alfresco.com/jira/browse/ETWOTWO-752

Is this bug unresolved in the 3c labs version or am i making some mistake??

Thanks for the help.

Regards
~~Himanshu Seth~~

http://www.IntelliGrape.com