Hi,
I am trying to add the 'Future Status' field to a Simple Edit Layout for a News Item. That way, an end user can create a news item, but set it to go live at a later date.
I am using the keyword listed: %details-F_status_future_status%
Only problems is, it won't display at all - just blank white space. All the other keywords for metadata fields and other asset properties seem to display correctly. It is not a CSS / Javascript issue as I have tested it with a blank design…
Any ideas?
Noone from Squiz has any idea about this one? Has anyone successfully implemented this on their site?
Hey Befuddled
Not sure what is happening for you but if I create a layout and add the keyword you are using to it, then go to the layout manager and add news item to the defined layouts, then add a customisation for the details screen, then set the layout for the details customisation…take a breath…then go to the front end edit of a news item, viola the future status is there.
You may want to check that all your ducks are lining up, and maybe a few other things like setting the limbo css to print from the layout and make sure everything is getting into the source of the page and all the js is there etc. Something I had to get around recently for layouts and front end editing was the fact that the css and js was being automatically inserted right before the closing head tag and the limbo css was conflicting with the clients site css. This was jiggering up the site while in limbo and I had to move a bunch of css into the body just to get around it.
Sorry I realised I have made a mistake in both the title of this post and the content of this email. The problem I am having is with an Asset Builder page, and not a Simple Edit Layout. So I am using the %details-F_status_future_status% keyword on an Asset Builder page that creates a new News Item. Any ideas why this would not display?
Those system-level keywords wont work when creating a new asset. Only attributes and metadata can be displayed on the create interface. The Asset Builder doesn't know how to process anything more complex like future statues, permissions, designs etc.
So you could get tricky if you want to make it simple for the user on create. Use metadata to capture a live date on create and then a trigger to set the future status with the date from the metadata. Or you could let the user add the future status by setting the created screen of the asset builder to be the editing screen of the created asset. That way the user could add the status after the asset is created.
How would you do this please???
I would just do a javascript redirect to the editing screen for the asset that was just created.