We have moved to GitHub Issues
Created by Emil Rasmussen 16 Sep 2014, 12:53:38 Updated by Shannon Deminick 05 Jun 2015, 15:31:57
Relates to: U4-4809
What did you do?
What did you expect to happen?
I expected to see the changes published at the date set.
What actually happened?
But when I click "Save", the the Publish at feature works.
This is similar to what is describe in U4-4809.
This isn't a bug, this is expected behaviour, surely? Think about it... When you click "Save and publish" the behaviour is always to publish the page. If it it was then re-published again at a future "publish at" date there would be no change to it. The way it currently (and always has) worked makes sense once you understand it.
Well, I would expect the "Save" part of "Save and publish" to save the page, and set the publish at date. But I understand that this is the convention, but in version 7, the Save button is "hidden" under the arrow - so the "always has" argument is not holding 100 % :)
The average new content editor is - in my experience - confused about how to use the Publish at feature. I spent 30 minutes yesterday testing things out, before I where confident about how it worked. For me that is a sign that we could do better.
In U4-4809 it was suggested to change the validation message to "You cannot publish this item, it is scheduled to be published at dd.mm.yyyy". That could be a way to give the user feedback about the system status.
That's a fair point. I think a notification would definitely be helpful rather than changing the behaviour (which would just confuse people who are used to the way things currently work).
Thanks for seeing my point :)
For example, see as organized the scheduled publishing info of Wordpress post.
Perhaps, when there is a 'publish at' date set the button should change to 'Save and publish at' to avoid the confusion?
@drobar Great idea!
I would like to attach this issue U4-3105 regarding the UI for published and not published content.
When you click save and publish with a publish at date specified it actually does work, however you will get a warning stating that it could not be published (but the save absolutely works). Sure, we can probably hide the save and publish button if a publish at date is specified. This will need to wait till 7.3 though.
I discussed this issue in this thread http://our.umbraco.org/forum/umbraco-7/using-umbraco-7/55045-Getting-the-Publish-at-property-in-a-view
To change the button text to "Save and schedule" or "Save and publish at" when a date i selected as @drobar suggested is a great idea!
Another more advanced idea that solves the issue with having "Publish at" as a property when it really doesn't behave as a property is to: Remove the "Publish at" and "Unpublish at" properties from the properties-tab. And instead add an extra option on the "Save and publish"-button named Schedule. kind of like the attached image but with time and optional end date.
I think [http://en.support.wordpress.com/posts/schedule-a-post/ the way wordpress handles this] is pretty good (Wordpress should look at Umbraco at how it handles everything else though :( )
I think both ideas make sense. I kind of like that the act of scheduling as publish requires one to actively take the decision, and not just fill out a property. It's not that intuitive, but I think it's OK and it's easy to learn. +1 for the "advanced idea".
Assignee: Shannon Deminick
Backwards Compatible: True
Affected versions: 7.1.6
Due in version: