Who's with me... 

Right now, it seems that all metadata is stripped after four fields are transferred to the asset's menu... Headline, Photographer, Caption, Keywords, except on the hi-res image which does not serve.  

If we can't retain ALL, can we at least get a few additional fields... Copyright info, original date the photo was taken, what else. 

And can this data STICK with the images, no matter the size.  

Thanks!

When we crop an image preview in Blox, it doesn't always retain the crop on the website. Also, what is the ideal size for cropping image previews so they don't zoom in on strange parts of the photo?

When we upload images to BLOX, it seems to be stripping the metadata out.  If I pull an image of the site, I cannot tell where it was created.  Can we keep that in please?

Hi there, 

At the request of Joanne Sandy, I'm posting this here as a feature request. 

The Columbia Missourian has an editorial cartoonist, Jon Darkow, who is well known in our area. We would like to be able to run his editorial cartoons on our site, behind a hard paywall. 

Right now, the TownNews paywall configuration is to either protect all images on the site, or none. Because these editorial cartoons are images, we'd like the ability to paywall just those images within a given section (in our case, /opinion/darkow, but this would vary at other TN sites). 

She asked me to answer these questions: 

1) What problem(s) does this idea solve? Why do you need this idea implemented? Provide as many problems or use cases as possible.

The problem this would solve for us is allowing only certain types of content to be paywalled, rather than an all-or-none solution for photos. 

2) How often would you use this feature?

Several times a week. 

3) How many people in your organization would use this feature?

In the organization, only a couple of people who design the opinion section. But for the community and for subscription purposes, many more. 

When I go into blox, and "Write an Article", I paste text into the body and all returns are removed.  

I understand if all formatting is removed, but why must all my paragraph breaks and returns be removed.  Seems like a bug, and I wanted to report it.  Happens on iOS and Android, Chrome. 

We have noticed an uptick with this problem. Whereas all of my Googling says it is likely an issue with malware on the user's device -- how can we know for sure that the problem isn't on our website? (For the record, about 98% of our ads are served through OAS or Blox. We have NO Google ads on our site -- that I'm aware of, but I don't control the advertising part of our site and don't know much about it. We do have an AP video player that shows Google Ads.)

I have followed all of the advice I see, and even I am still getting the pop-ups (not on every story, but enough to be annoying). 

Thanks in advance! 

There really needs to be an accounting / reporting function for the user groups that admins are assigned to.

I can easily see how many people are in each group, but the only way to figure out who they are is to open the account of each admin user one by one.

Similar to the Positions dialog under Banner Ads (with Assign/Remove function) I should be able to see which admins are in each group from this window as well as remove and add them without having to open the user accounts individually.

Similar to this request from 3 years ago, I'd like to auto-expire some flags. We add "breaking" and "developing" flags to many stories. These flags make sense when they're added, but after a few hours (definitely after a few days) they can be confusing to readers. I'd like for those flags to disappear after a set amount of time. I can recommend how much time that is, or you can let individual sites set that time. 

I don't want to remove the flag — we're using those flags to track stories. (So we can tell reporters whether breaking news stories perform better than an enterprise story, for example.) But if the flag was not visible to the reader after X hours, then I'd have the best of both worlds.

So this is my official feature request. It would solve the problem outlined above. It would be used daily. It would be used by/available to all of our reporters and editors. 

We all know what "wire" means. I don't think readers do — at least, not from the readers I've talked to so far. This, however, is one of the flags that's protected. 

I want to change the "wire" flag so that the public sees a flag that says "news service". (It's OK if our staff sees "wire" in the CMS.) Otherwise, I have to adapt an existing flag ("hot"? "special section"?) so that it will say "news service" to readers, but that description will not be changed in the CMS — we just have to remember that marking "hot" means "news service". 

(I know I can create a custom flag on an asset. But I need this to be assigned in syndication, and I can only apply existing flags there.)

1) What problem(s) does this idea solve? Why do you need this idea
implemented? Provide as many problems or use cases as possible.

Currently when you go into the hamburger menu for past eedition all you
see is the date you do not know right away which one was Sunday or
Wednesday without clicking and opening up multiple dates to find the one
you want. Usually the older subscribers are the ones that use the
eedition the most so this would provide a better user experience for
subscribers and users in general to reduce the number of clicks to find
what day of the week they are looking for. Also Tecnavia and Olive
provide the abbr day of the week with the physical date. Just makes
sense as I forget what day it is most of the time.

2) How often would you use this feature? This would be daily and would
want the list of past eedition in the hamburger menu to update daily as
new eeditions are added.

3) How many people in your organization would use this feature?

All of the BH Media sites would use this enhancement and want this feature to be added as our customer service averages about 10 calls a week asking us to add the Day of the week to the past eeditions list to help them find it quickly.  I would think others would be getting the same type of requests from their subscribers as well..

We've gotten several complaints about the login not recognizing the user on mobile (but they login fine on desktop).  We've discovered that mobile auto-save and auto-correct is mostly the problem.  Here are the problems we've helped our customers with:
1) Often times there will either be a leading space or trailing space in the username or password. This will fail every time.

2) Sometimes mobile will capitalize the first letter or auto-correct and again will fail the login.

The biggest problem with this is that many of our subscribers don't realize it's happening - and even with our assistance have a hard time trying to un-capitalize a letter (it will keep happening), or to back space to get rid of spaces.

This feature would help many of our users, and prevent them from getting frustrated and unsubscribing. We get 3-4 calls or emails a month on this right now.

This feature would help across the board - and would help every-time someone logged in. 

I'm very curious if other newspapers get this complaint as often as we do?  If so, how do you combat it, besides trying to walk the customer through it?

Thank you!

I've heard a few people who've called for other reasons complain about the new e-edition being too sensitive on mobile. When I tried it I found the swipe is too sensitive. For instance if you're trying to pinch to enlarge it's very easy for the system to interpret that as a swipe and advance the page.

In my experience it seems like any horizontal swipe of any distance changes the page. So if while you're trying to pinch you inadvertently swipe to the left or right before starting the pinch the page will change.

Can anything be done to make it not so sensitive? Maybe require a longer swipe distance to advance?

When users change credit cards or have new ones issued when they reach their expiration date,  it creates a problem when it's time for a subscription to auto-renew. It would be helpful if the Blox CMS system stored credit card information and allowed a user to go into their Dashboard and change it, just like they can change their email address or their password.