You're right Nick, I think we're kinda on the same page here in relation to my open post.
I haven't noticed any problems with taglines yet, but maybe we just haven't gotten that far yet.
I appreciate the update Christine and understand the issue of backwards compatibility. I assume that means you have some customers using HTML and line returns in their bylines right now?
Sounds like Aidian is looking for a way to batch export the JPGs out of BLOX. I agree this would be a useful feature, in our case for TotalCMS.
Our old CMS exposed the area where photos were stored so we could quickly browse and find them if needed. In our case this is usually because AP calls and a photographer who didn't shoot the images (and thus doesn't have quick access to them) needs to download and move them to the wire. If we could simply select all the images in BLOX and then just download the JPGs to a folder it could come in handy in a pinch.
That said, working with the BPM file isn't totally horrible. Aidian, you can simply rename the .bpm file to .zip and extract it like you would any other compressed file. Once inside you'll see the the .json file that contains metadata and other BLOX information, plus a folder that contains the images. "hires" is probably the one you are looking for, so just slap a .jpg extension on it and open as normal.
Obviously if you have a ton of photos this could take a while, but for just a single image every once in a while it isn't too bad.
It could be interesting. For us I imagine how "white label" it is, how much we can brand it locally, would determine if we would use it.
So in response to Ticket 591133 I'm going all formal here. Other users, please let me know if y'all would like to see this as well to avoid having to place the <br> code in your byline field.
I am requesting: "... the ability to display a new line when the enter key is pressed in the byline text area of editorial assets within the Blox Admin."
This should also apply to the E-Edition "river of news" as well.
1) What problem(s) does this idea solve?
Inconsistency of display between print and online; relates to both TotalCMS users and non-users. Also inconsistent behavior from what is displayed in the BLOX admin and what is displayed on the public site.
2) Why do you need this idea implemented? Provide as many problems or use cases as possible.
The Byline field in BLOX functions consistently in TotalCMS when placing bylines onto InDesign pages. However this same field does not function consistently when publishing articles online; replacing a line break with a single space. This creates a different look between our print and web products.
It would also reduce confusion and frustration between all users of BLOX who don't see their formatting translated exactly from the admin to the public site.
3) How often would you use this feature?
Every single article, every single day, 365 days per year.
4) How many people in your organization would use this feature?
Every single employee who creates Article Assets in BLOX.
This seems like something super simple to implement. I can't see any downsides to making the information typed into the back-end of the system display the same way on the front-end.
Bumping this back up. Now that we've switched to TotalCMS (and thus have the second line in every single byline) this issue has become very apparent to everyone.
Customer support service by UserEcho