Your comments
Great ideas, thanks! I've submitted this as a feature request.
For the record, I support the idea of using geolocation tags for a number of reasons:
1. They don't get "mixed in" with regular keywords. And you can still do query rules on them.
2. Because they are fixed, you ensure better conformity in terms of spelling.
3. Geolocation tags are hierarchical and can allow you to target big areas or small, depending on the tag. Plus, the hierarchy creates semantic value and relationships.
4. Geolocation tags have some structured location data associated with each tag, which could potentially be useful data in the future.
For the record, I support the idea of using geolocation tags for a number of reasons:
1. They don't get "mixed in" with regular keywords. And you can still do query rules on them.
2. Because they are fixed, you ensure better conformity in terms of spelling.
3. Geolocation tags are hierarchical and can allow you to target big areas or small, depending on the tag. Plus, the hierarchy creates semantic value and relationships.
4. Geolocation tags have some structured location data associated with each tag, which could potentially be useful data in the future.
Hi Kevin!
Thanks for the post.
This is definitely something that has been on our radar and is something we've been working towards for a long time. We've made many upgrades to make sure our sites are as HTTPS-friendly as possible, such as changes to our Content Delivery Network, our Ad Manager systems, our template front-end markup, etc. - to have better support for secure environments. These changes ensure than when a BLOX page is served in a secure environment, all links, scripts and images are also secure.
One of the last big steps is to move to the "Server Name Indication" (SNI) protocol.
http://en.wikipedia.org/wiki/Server_Name_Indication
This would allow customers to purchase and upload their own secure certificate for their domain, and serve all of their pages securely. There would be a cost involved to purchase the certificate, and likely a cost from TownNews.com to support it.
Unfortunately, SNI is not supported by older versions of Internet Explorer - specifically Internet Explorer 6 and Internet Explorer 7. But we hope that relatively soon the stats on those browsers will fall enough to where this becomes more viable.
I hope this helps!
Christine
Thanks for the post.
This is definitely something that has been on our radar and is something we've been working towards for a long time. We've made many upgrades to make sure our sites are as HTTPS-friendly as possible, such as changes to our Content Delivery Network, our Ad Manager systems, our template front-end markup, etc. - to have better support for secure environments. These changes ensure than when a BLOX page is served in a secure environment, all links, scripts and images are also secure.
One of the last big steps is to move to the "Server Name Indication" (SNI) protocol.
http://en.wikipedia.org/wiki/Server_Name_Indication
This would allow customers to purchase and upload their own secure certificate for their domain, and serve all of their pages securely. There would be a cost involved to purchase the certificate, and likely a cost from TownNews.com to support it.
Unfortunately, SNI is not supported by older versions of Internet Explorer - specifically Internet Explorer 6 and Internet Explorer 7. But we hope that relatively soon the stats on those browsers will fall enough to where this becomes more viable.
I hope this helps!
Christine
Hi Greg!
What kind of design are you wanting? Like, a slideshow?
Also, is this Flex or Zen?
Thanks!
Christine
What kind of design are you wanting? Like, a slideshow?
Also, is this Flex or Zen?
Thanks!
Christine
We have a "workaround" way to do this - a custom property.
On the YouTube asset, go to "other" and then enter:
name = position
value = showcase
Available position values:
showcase = Large and on top of the article
top = Top of the media box
bottom = Bottom of the story
On the YouTube asset, go to "other" and then enter:
name = position
value = showcase
Available position values:
showcase = Large and on top of the article
top = Top of the media box
bottom = Bottom of the story
Hi Lindy!
Right now we don't have the ability to style the images when they are inline. Unfortunately, because of the media box and ad which is floated inside the article, we don't know when the image will bump up against them, so we had to make all the images small.
I would recommend using the "longform" article type, which allows the images to be full width across the page. If you have ONLY inline elements (meaning, no extra photos or pull quotes) then the longform article it a full-width article with 100% images.
Right now we don't have the ability to style the images when they are inline. Unfortunately, because of the media box and ad which is floated inside the article, we don't know when the image will bump up against them, so we had to make all the images small.
I would recommend using the "longform" article type, which allows the images to be full width across the page. If you have ONLY inline elements (meaning, no extra photos or pull quotes) then the longform article it a full-width article with 100% images.
Hi Laura and everyone!
We have been discussing something similar to this - maybe even for all announcement types:
- Military
- Birth
- Birthdays
- Obituaries
- 4 generation photos
- Weddings
- Anniversaries
- Engagements
- Pet Memorials
- Promotions
I don't think we need an asset for each type, maybe a 'general announcement' type will handle most of them.
What kind of announcements do you guys have?
What kind of fields would you want to see on an obit, wedding, or announcement obit?
We have been discussing something similar to this - maybe even for all announcement types:
- Military
- Birth
- Birthdays
- Obituaries
- 4 generation photos
- Weddings
- Anniversaries
- Engagements
- Pet Memorials
- Promotions
I don't think we need an asset for each type, maybe a 'general announcement' type will handle most of them.
What kind of announcements do you guys have?
What kind of fields would you want to see on an obit, wedding, or announcement obit?
Hi Mike!
We have something like this! If you open up each schedule, we have the ability to click on one of the times and hit "exclude." This will then remove that instance from the occurrences of this event.
So that means when you see an 'unrolled' list of event occurrences, or if you search by occurrence, that day will not show up. Also, on the event page, it will not show up when you see the list of dates and times on the left side.
One thing that is unaffected, however, is the schedule description. Like, where it says at the top, "Repeats every day, running all day." or whatever.
Hope this helps! Happy Thanksgiving!
Christine
We have something like this! If you open up each schedule, we have the ability to click on one of the times and hit "exclude." This will then remove that instance from the occurrences of this event.
So that means when you see an 'unrolled' list of event occurrences, or if you search by occurrence, that day will not show up. Also, on the event page, it will not show up when you see the list of dates and times on the left side.
One thing that is unaffected, however, is the schedule description. Like, where it says at the top, "Repeats every day, running all day." or whatever.
Hope this helps! Happy Thanksgiving!
Christine
Customer support service by UserEcho
What would you think of just removing the articles at the bottom and ONLY having the timeline? Then users will have to page through the timeline, which may make more sense for the presentation? We are also looking at adding thumbnails to the small story cards in the timeline itself.