Metadata is only preserved in the hi-res version of the photo data if that is being stored in BLOX. All other images are stripped and have optimizations applied against them at this point.

Field59 syndication channels now support workflow as a choice.

It's probably best to submit a support ticket so a customer service representative can help troubleshoot what might be happening with this account. There are a lot of variables that could cause a user to have issues ranging from browser plugins (like ad blocking), account sharing, or just plain old user error.

Chris - you should be able to use the /tncms/webservice/v1/editorial/search - I see that is not documented. That end-point accepts the same parameters as any search URL.

This feature was released with our Tuesday update to the CMS.

I've added a change request for this. It should be logging in the revision history which user removed or restored an asset.

Issues with saving multi-byte characters in the editor view was correct a release or two ago. Testing of hard returns looks like they are preserved - are you still experiencing issues with that?

The HTML block is forced through a clean-up process using a library called Tidy to make sure that it is sanitized HTML to prevent the page from breaking. This is a standard problem in the HTML asset which is why there is also a future change coming to that to modify it's behavior to also be sanitized.

As a light step towards this, would it be useful just to have a link to directly edit the item in BLOX admin itself? Something like that could very easily be provided - it would direct the user to the admin, if not logged in - they would log in - and then it would go to editorial and open the edit asset UI.

Well, I'm not sure why it's not working. It's possible there is something else preventing this from working - so at this point I'm going to file a change request to add an explicit option to the tncms parser to set the author from an option as was asked about earlier.

The authors property I looked at in the code was a property of the incoming source - it was not an option to the parser so that was my mistake. Try setting as a filter with field name set to authors, regular expression set to /^$/ and replacement set to kevin.cox@galvnews.com.