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.
Like the addition of the "teaser" image on article files, but for purposes of training staff and passing meta data on, shouldn't they be consistently named "preview" instead of "teaser?" - or are they serving different functions?
Thanks Robert and Bob! Yes, Robert's description was accurate. I'll give you two use cases for the Teaser that will illustrate it's purpose:
1. Using a teaser image so that you don't "give away" the mystery of the story or the main story photo. For example, an article like, "The two Hermiones just met and I'm crying" would show and example of two Hermiones from the movie, which would work to draw the user in to find more information. The teaser image does not show on the article though.
On the article itself, the main photo (which is the revealing photo that users clicked through to see) can now be shown. This just a child asset which would show as usual. See this example:
2. The second case where this may be useful is where a media organization has a goal or mandate to have more photos on more articles. They may want to add "stock" images - such as some crime tape to go with a crime story -but because it isn't actually a picture of something important, they don't actually want it to show on the article page itself. That way, you can have a teaser thumbnail, but you don't have to have it on the article page.
Is anyone currently delivering their GA and Quantcast tracking code to their AMP pages? Is that automatically included in the markup that TN is providing to Google AMP or do we need to add that using their insertion macros in option.head.utl?
I was manually sending AP assets to the web and found myself having to open them all to make sure they hadn't already been given a site tag. We do this every day and it finally occurred to me what would make it a much simpler process.
It would be nice to have a separate column for the presence of a site tag just like we have a "Sections" columns for section tags. Even a little box like this...
where can i see example of a TownNews site using content exchange?
It would also be nice to have the stories broadcast to the social media sites at the publication time set by the reporter.
We have customers that may have a TCMS site feeding multiple websites. The Broadcast channels may not line up one to one from TCMS to the website - it almost needs to be tied into the site tag somehow.
I am probably not the first to suggest this feature, but for those of us in TCMS, are there plans to expand the options of column views under search results? Currently available are: Slug/Status/Sections/Authors/Priority/Start Time/Delete Time/Workflow/Print/Depth/Modify time/Modified by
Is there a way to disable the importing of assets from a Syndication channel?
We created one in TotalCMS that allows us to easily search our website since it contains years of articles that aren’t in TCMS. However when users import these articles is creates the potential for them to show up on the website twice.
It would be great if there was an option for a “read-only” syndication channel that disables the Add to Site function.
For example, the tagline in TCMS(before it hits the page) is:
Reporter John Smith writes about education and other local topics. Contact him at email@example.com, on Facebook or at 555-1234.
And the byline is:
By JOHN SMITH
The Brunswick News
But when it is placed on the page the template styling/snippets alter that to fit on multiple lines. So when it hits web it looks like...
writes about education and other local topics. Contact him at firstname.lastname@example.org, on Facebook or at 555-1234.
And the byline looks like:
By JOHN SMITH The Brunswick News
So something in the design templates is overwriting what's in the asset. I understand why from a page layout standpoint. But this doesn't make sense from a web standpoint. It should allow the template to edit the design on the printed page but leave the web version unaltered.
Basically, the bylines and taglines should look the same online as they do in the users' accounts. The InDesign templates shouldn't alter this.
Mapping the subhead in TCMS to CMS would eliminate the need to copy subheads from the Print tab in TCMS to the Other tab so the subheads could be shown online. Doing this would allow the subhead (which may be modified on the page) to be consistent with the subhead online. Because editors don't go back to the asset to copy & paste the subhead from one tab to another, subheads online are missing. (NOTE: This only affects people with both TCMS and CMS.)
Our staff is really loving the ability to print assets directly from within BLOX (TotalCMS). They are using this as a proofing tool and it works much better than printing in our old system.
They do have one request though…
The print format that is generated (see attached images for clarification) includes child image assets. However it does not include the captions along with the images which seems like an important oversight.
Would be be possible to have captions included below the photos in this print view?
We are about to begin using the Assignment tool in TCMS for our newsroom. In testing, it appears that the only asset types that can be assigned are Article or Media - and media being ONLY a photo.
Is there a site setting to include other asset types? I could see this being useful for video assignments, graphics like PDFs, etc.
We have several publications, both online and in print. If we want to post the same story in two places online, it's no problem: Add another section tag, and the story appears on both sites (and redirects to the main story). Print is a different issue. Stories often are duplicated for print because headline space or story lengths are different.
So two possible solutions: Optional trims and headline fields for secondary and tertiary publications so everything stays in one file in TCMS. Then someone would have to figure out Or group those stories together in TCMS so copies have a child-like relationship to the parent — they're grouped in searches, and the "parent" or main story is always on top; the copies are listed below. Those copies aren't (OK, shouldn't be) published online. But it's easy to edit a headline on a copy, thinking you have the "real" story.
We move to TotalCMS in May, and based on my research and talking with our project manager, we won't have the same ability to preview the asset online that we do in Blox CMS.
We use the preview button on almost every asset. We find it very helpful when embedding items or when we want to know how a box or quote will look or how long a headline looks. Since adding the site tag in TotalCMS publishes it, we don't get the same opportunity to check it before it publishes. This was one of the things we were most excited about in our move to Blox CMS, so it feels like we take a step backward if we lose it.
Posted this as a feature request and sharing here to get support.
Customer support service by UserEcho