Your comments

Ian, this sounds like a good idea to drive reader engagement. There are quite a few things that would need to change on the back-end to get a feature like this to work, but I'm in the process of looking over the entire commenting system to see how it can be improved and this feature just made it onto my list. Obviously this would impact only those using the TownNews comment system as we have no way of attaching information to a 3rd party system like FB. No promises it will make the final cut, nor how quickly we'll see any changes :)

Kevin, my bad. My excuse is this is week 3 here at TN as a Product Manager so I'm still learning. It's scheduled right now for release in 2.23 (no ETA on that, there is a bug holding it up right now). 2.23 still has the "old" menu style, but does include the asset start time reset feature.

This is in the latest version of TotalCMS. You'll just need to update and you'll have it. I'm sure it's going to be a huge time-saver and problem solver for many reporters.

You can also check out the following sites:

  1. http://www.mississippivalleypublishing.com/journalpilot/news/daily_news_live/
  2. http://lufkindailynews.com/multimedia/podcasts/
  3. https://www.aberdeennews.com/sports/ (about 1/2 way down the page)

We are also in alpha testing upgrading the player to share the code base with the new video player and extend a bit with some new features.

Dakota, it looks like at some point someone on your staff added a css rule to move the top ad unit to the left and have text wrap around it. This then breaks on mobile view size. I updated your site component css.utl file to add a conditional size check and to only apply that float if the screen is larger than mobile. I hope this helps!

Brad, I did some research on this and it is a configuration issue between most of your site and the multimedia page. The working 'multimedia' section is configured to use blox ad manager's default vast feed, while the rest of the site is configured to use DFP. Please submit a support ticket, you can reference the research ticket I submitted (#724371), to have this corrected.

Brad, I'm checking with Templates to find out if this is expected behavior or not. More details to come.