- General
-
Ideas
+5
Started
Moving the "Save" and "Cancel" buttons in the asset creation window
We've had several times when reporters are writing stories and they accidentally move the mouse a half an inch too far and click "Cancel" when they meant to click "Save." I know in this tech savvy world they should know to save, but at the same time auto-save exists in other programs and so they're used to the system saving for them. I think an easy fix(I changed it in the in-browser CSS code in about 15 seconds) to this would be to move the "Save" button and the "Cancel" button a few inches apart.
That's the easy way. I think another thing that would help this issue would be to add a "Are you sure you want to cancel?" prompt if the "Cancel" is clicked and the asset hasn't been saved in a while.
I know TownNews is proud of its in-browser asset creation, but I think the majority of the reporters here have been burned too many times and just write in a word processor, then copy and paste it in TCMS.
That's the easy way. I think another thing that would help this issue would be to add a "Are you sure you want to cancel?" prompt if the "Cancel" is clicked and the asset hasn't been saved in a while.
I know TownNews is proud of its in-browser asset creation, but I think the majority of the reporters here have been burned too many times and just write in a word processor, then copy and paste it in TCMS.
Customer support service by UserEcho
You're absolutely right on the copy/paste. Except in breaking news situations our staff doesn't write inside the BLOX window.
Bypass your companies official workflow at your own risk.
Doesn't that sound like a good solution?
Have there been any updates with this? I ask because I heard someone cursing the BLOX gods from across the newsroom.
I can envision ways it would still work,,, for example we don't use site tags but if the reporter or editor doing the entry doesn't assign a section tag then it wont show up on site...
Alternately the autosave function could create a "draft" asset which isn't live until a human hits "Save and Publish" or something similar...
In the breaking news example the reporter could enter Police Stand-Off at 9th and Walnut as a headline, add breaking news section... hit save and publish and the headline shows up in breaking news ticker... He leaves the asset open and types notes in as he's in contact with the field and with the police... During this time every 5 minutes the system saves a "draft." 15 minutes later he composes notes into an initial report and hits save and publish... and the website is updated.
The draft status could be a status flag on the asset... so you could look at the revision history and see the initial "live revision" where the asset was saved, several "draft revisions" where changes were saved but the changes aren't live and the the updated live revision...
The system would always publish the last "live" revision.
Has this moved any on the roadmap? I think the auto-save would be nice, but what if the asset has never been saved the first time. I realize saving early is something everyone should do, but for a lot of people this just doesn't happen. For whatever reason they don't save right after creating the asset. So would this update auto save all created assets regardless of whether they've been manually saved in the first place?
I saw the update from August that adds an auto-save feature of sorts to BLOXCMS. This is a step in the right direction for preventing articles from being lost. I think a bigger concern of ours remains the cancel button. Can the cancel button not be given the same exact function and prompt of the close/X button?
screencapture.mp4
I agree, cancel should get the same warning as the X.