Though TownNews.com representatives often participate in discussions, this is not a customer service site. For immediate help, call 800-293-9576 or submit a support request via our online ticketing system.
We are moving to an umbrella site and found out that this will cause all our sites to have a url with the base site. For example our TV station is currently bgdailynews.com/wdnz instead of wdnz.com. That address will take you there but we would like the browser window to show wdnz.com. TownNews has told us they don't have a way to provide masking to accomplish this. Has anyone found a way to do it on their own?
We have been getting tons of spam submissions via a feedback form on our site. It's regarding CBD and vaping stuff. TownNews says it's people submitting so a spam filter or recaptcha wouldn't stop it. But just curious if others are seeing anything similar. Ours just started in the last month.
So let me pose this scenario:
We've got a story on our the site. Let's say the New Orleans Saints are making roster cuts on deadline day. Our guys are updating their story w/ new player names every couple of minutes. The story tells readers to 'check back frequently' or 'reload the page' for the latest info. How can we best display this info in BLOX so that people who visit a page frequently during a breaking story actually see the most up-to-date info?
Here is the doc which discusses how you can use flags to reduce caching times for important articles:
As the doc says, there are a few limitations, but in general you'll get updates about every minute or so.
However! Note that this does not affect the users' local browser cache. That is still subject to a 5-minute cache. (You could, if you could find the right words, tell users to force reload the page. It is different in different browsers though, so I'm not sure if there could be an elegant way to say this.)
So this doesn't really work for "live blogging" - but it should address the needs of corrections and story updates and breaking news that you want to push to the front page.
We did have a discussion internally today about some enhancements we can make to bring us closer to having some kind of live blogging environment... I will look into that as a possible future feature.
We have been voting on this feature for over 3 years, I would assume the would be common functionality. Ending a poll manually or automatically after the ballot has run it's course. I am asking incase I am missing something. Otherwise please consider this a request.
Making a feature request for the ability to have the purchase subscription page also capture account (login) creation information and establish that user profile in a singe step-page-process ... thus eliminating the multi-step process of a site visitor having to first create an account before he/she can actually purchase a subscription.
This would enhance the user experience and eliminate a bottleneck/bail out point in the subscriber acquisition process.
Please support this post so it climbs the feature request ladder faster.
We are looking for someone to beta test two urgent initiatives we are working on…
Firstly, a “Support Local Journalism” page which will ask readers to contribute money or subscribe in order to support journalism during this time. It can be paired with messaging throughout the site that says something like, “We are providing coronavirus coverage without a subscription out of public interest.” And then a link to contribute or subscribe if they want to help.
Secondly, we have a new Photo Sales vendor (Fotomoto) to replace the other one, which is currently down.
If you are interested in helping with either - or both - initiatives, we just need a site for testing, and some of your time to provide feedback.
Each of these items will require some minor set up on your side, such as creating a new account with Fotomoto and Donorbox.org, and possibly connecting a Paypal or Stripe account for payments.
I realize this is a crazy time, but if you feel you have the time to help us test these things, we can do almost all of the work (except for setting up the accounts and reviewing the work) for you!
Let me know if you are interested!
An option to prevent the following from appearing in blank/null searches
or searches including Articles + Images:
• Photos that are both child assets and don't have a section tag assigned to them •
1. What problem(s) does this idea solve?
Prevents duplicate photo resources from being displayed (often alongside each other) in searches.
There are photo child assets that are technically required to have titles, those are usually the assets whose titles we want the least visible. Asset titles are effectively hidden unless a search is performed.
2. How often would you use this feature?
When I run a blank/null search to chronologically see what users will see.
I sometimes direct users to blank/null searches when they want to see a chronological list of content.
3. How many people in your organization would use this feature?
I would likely be the only one internally.
There's currently no feature that allows author names of articles to be indexed by the search utility. It only works if the byline is entered in manually as opposed to adding an author by registered user account with the CMS. The only way to access a curation of all of the author's articles is to find an article they wrote and click on their author name, where it prompts to a url address like this www.siteaddress.com/users/profile/authorfirstname%20lastname/
Does anyone have examples of staff directory pages they've created outside of static HTML pages on their sites? How about newsletter list landing pages that are more than the out of the box "list" of newsletters available.
At this special webinar, the TownNews team shared ideas and best practices for serving your audience and generating revenue during the coronavirus pandemic.
- How to quickly build a high-traffic special section to cover breaking news with BLOX CMS.
- Leveraging the TownNews Content Exchange Network to augment your local coronavirus coverage with nationwide content.
- Using subscription rules to disable your paywall/meter for specific sections of your site.
- Hosting virtual business and career fairs to strengthen ties to your community and grow revenue.
- Using programmatic advertising—and the expertise of the iQ Ad Ops team—to generate incremental revenue from breaking news traffic spikes.
"Sponsored content" is becoming a larger part of news organizations' revenue offerings to advertisers. But it's important that sponsored content be flagged as such in all formats to ensure the reader can differentiate between what is sponsored and what is actual news content. So we use the "SPONSORED" flag when posting articles through BLOX. However, when we pull articles into an email newsletter, the "SPONSORED" flag does not show up in the newsletter, so the content appears in the newsletter just like any other editorial content. We'd just like the option to have the "SPONSORED" flag show up in the newsletter, and ideally, for the sponsored content to be somehow distinguished, such as a shaded background. This would avoid confusing the reader and keep the delineation clear between actual news content and sponsored content.
Hey folks, I submitted an idea to Town News, and they said I should post it here to see if this development idea would help others, too. Anything else think this would be helpful?
The idea is basically to add a few new controls — either on the section level or on specific photo types — to allow editors to turn off the "buy now" button on all mugs, all crime stories, or other examples like that.
Town News asked me to answer these questions:
What problem(s) does this idea solve? Why do you need this idea implemented? Provide as many problems or use cases as possible.
A: There are dozens of photos used daily on our website that we do not want to sell. Many of these get automated tags that remove the "buy now" button (AP photos, for instance), and that's great. But still a large number of photos get manually tagged with #nosale to keep that button hidden. It would be very helpful to have more specific, targeted and automated ways to blacklist some photos from being sold. For instance, we NEVER want to sell a photo of a criminal who just committed some heinous crime. And a huge number of the mugs we run on our website are handouts that we can't sell, and even the ones that are ours are not any real source of revenue. My proposal would be that we have some ability to turn on/off the "Buy now" button for specific photo types (like all mugs) or sections (so you could turn off sales for all photos attached to stories categorized as crime, for example).
How often would you use this feature?
A: This would be used daily. The automated button removal would impact dozens of stories and several dozen photos each day.
How many people in your organization would use this feature?
A: All online editors would gain from this function, and reporters would no longer have to alert online staff to photos that got missed during the tedious and error-prone manual #nosale application process. Dozens of employees would be impacted.
We have now added more logic to our "automated" photo sales option. See this updated doc:
We have also added the ability to turn off photo sales per section (via custom properties), as well as batch update photo sales.
Hope this helps!
We have five pages that we want to add to the daily e-Edition, Each page has segmented areas that link to interactive puzzles on our website. We want the ability to copy these pages from one e-Edition to another without having to re-segment the pages each day.
Customer support service by UserEcho