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.
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.)
Let's say we have some CSS and JS in the global skin and UTL components. It's on the CDN as the other JS/CSS files as Core TN stuff. This works great!
However, can there be a way to access a minified version of those files? For example, if we have a file in global in resources/scripts/somefile.js (which would translate to something like https://bloximages.newyork1.vip.townnews.com/example.com/content/tncms/live/global/resources/scripts/somefile.js on the CDN) can we have a minified version like https://bloximages.newyork1.vip.townnews.com/example.com/content/tncms/live/global/resources/scripts/somefile.min.js ?
Just a humble idea by me. Thanks!
What is Wireless LAN? A Wireless Local Area Network or WLAN helps to connect different devices through wireless communication.
The wireless LAN enables people in the workstation or in homes to have a connection to various devices through the use of the internet. It is imperative to note that there are no cables or wires needed to connect the computers or the devices.
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..
Hi there -- our newsroom has been frustrated for awhile with the logic in the subscription module that requires users to register for the newspaper's website before buying a subscription. It's creating a bit of friction when e.g. we want to give out a complimentary subscription to an advertiser or other user, and is also a difficult workflow for some of our users if they don't get a confirmation email for registration.
I understand the logic of registration being different from subscription status; and I also understand the internal logic of someone needing a registration before they buy a subscription. However, I'm wondering if the subscription page could be streamlined, either to allow people to register while buying a subscription or to create a user registration record as part of a new subscription (that is, prompt for a username when purchasing a subscription).
Thoughts on that?
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?
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?
Our organization uses VDIs (virtual desktops) hosted in Microsoft Azure as our means of doing business. The site looks great in the VDI without any issues whatsoever. When I click the login link, I receive the login screen. However, when I submit my credentials the server returns with an HTTP 429 error. "Too Many Requests"
Is there anyway to avoid this message? Perhaps the system thinks that I (along with all other Azure traffic) is the same individual attacking the CMS? Is there a way to relax this restriction so we can avoid purchasing physical machines?
I spoke with our systems department about this - it seems as though that server is being flagged as a bot (we have many rules in place to help protect sites from invalid traffic, attacks, or bad bots). If you submit a ticket to our Customer Support department, they can work with you on possible ways to identify your requests so they are not throttled. Let me know if that makes sense! Thanks!
I have an AP Channel set-up. Are these stories supposed to flow into my site automatically? Do I need a JOB setup? My intention is to have a small widget that flows in AP stories dealing with NBA.
Eva from TownNews did indicate to me that along with an AP Channel..you will also need an "Importer" setup. This should not be confused with "Jobs".
We are trying to sell our masthead banner ad space, but advertisers frequently ask to have it scroll with the page.
We would like to be able to use the Skyline Utility Region while the Navigation option is set to Fixed on Scroll, and have the option to allow any custom blocks in that region to also scroll with the navigation header (above it).
How the Better Ads Standards will matter to your bottom line
Digital advertising is about to get even more complicated. In an attempt to make ads less annoying for users, Google Chrome browsers will begin broadly enforcing the Better Ads Standards on February 15th, 2018. At our February customer webinar, Phil Pracht, revenue product manager, Christine Masters, director of product management, and Stevie Longwith, Ad Ops program manager, discussed these new digital ad requirements and the steps you need to take today to keep your ad revenue flowing.
- An overview of the Better Ads Standards and how they apply to BLOX CMS sites
The impact of Chrome Ad Filtering on ad servers—including BLOX Ad Manager
How to use Google’s Ad Experience Report to help you understand if your ads violate the Better Ads Standards
. . . and more!
Ready to learn how you can comply with these new rules and keep your ads from being blocked? Webinar recording now available.
With FLEX's reliance on 4:3 and 16:9 cropping it would seem that many photos will end up cropping off the subject in order to adhere to the ratio. And most sites surely have some blocks that pull an asset in 16:9 and others that pull the same asset in 4:3. I propose a quick-crop tool that allows users to select crops for both ratios without the user having to work out the math or upload a previously cropped photo.
I'm thinking something like the image below that would allow users to select the ratio in a dropdown box and blocks would pull the appropriate ratio.
Would anyone else with FLEX use that?
You may have heard, but in case you haven't, The Lenfest Institute for Journalism is offering a 650k grant to help newsrooms deepen engagement with audiences using either of these tools.We are considering going for the grant, but I am having a hell of a time getting anyone from TN / Blox to tell me if the tools will work inside our system.
Any experience or confirmation from the mother ship?
We're seeing a large increase in comment spam lately so I'd like to formally make the feature request for something that I know I talked to support about in the past. We require email confirmation when new accounts are created but obviously the spammers have automated their way around that.
I'd like an option to require an active subscription to post comments on the site. This offers numerous benefits to all Town News customers:
• Provides another perk or subscriber benefit to paying readers.
• Potential to increase Day Pass sales for those who aren't subscribers but really want to share their opinion or comment.
• Reduces comment spam to virtually zero.
I could see it being useful to allow this setting to be toggled per URL/section so that for example you could allow anyone to comment on obituaries but not news stories.
1. All of the items listed above.
2. Every day.
3. Every reader.
Please let me know if anyone has thoughts or questions!
Customer support service by UserEcho