Your comments
I'm not sure how excited our developers would be about removing fields (because some of our 1600 customers may still care about them), but yeah - MySpace, ICQ, AIM are all pretty dated. I will ask about this.
But I can definitely put in a request to add some new things. What would we want to add?
What about Snapchat? Vine? Medium? Periscope?
Maybe we just need some "other" fields people could enter (but would have a generic icon)?
This is correct... for trying out blocks and playing with page customization options (especially in Flex), having a test URL or a test URL map would be the way to go.
To play with templates, you'd have to create copies and then set them up on a test URL.
One thing to note, however, is that in Flex we've provided many more easy options in the page customization panel, and when you save those, it is LIVE. It was added as a group ACL, so if you want, you can ask that those capabilities are removed from some members of your organization (if you're worried about them changing stuff without approval). However, we do have a feature on our roadmap to allow previews of page customizations and layouts, before you "publish" the changes live.
Hopefully this helps a little! =)
A few things to note, that make this confusing:
Ashley is right that we don't have specific banner ad regions in eEditions, so that's what she was answering. But, it is indeed possible for a customer to create them using the opt points.
The opt_ hooks are specific to Flex templates. We have made an effort to make sure that all Flex option macros are named the same, so like Michael said, you can search for them now. But, also, here is a doc:
On Zen, we also have include injection points, but we didn't think to implement a naming strategy, so they are hard to find. There is a doc for Zen here:
Hi Michelle!
As part of evaluating ways to improve the speed of our system, we looked at the amount of time it takes to query each service and wait for it to return with count data for each page. This process could take a few seconds, which is added to the download time of the page. This hurts SEO (because you get a page rank boost if you're speedy in Google results), and it hurts usability (there are studies that show that each additional second of download time on the page, you will lose a percentage of your visitors). So, when looking at that, we felt these counts were too "expensive" to add into Flex by default.
However, if this is worth it to you, it is possible to override our code to use your own counts on the pages. You can submit a ticket to our Customer Support team and they will point you in the right direction.
I should mention, however, that Twitter discontinued their count mechanism (again, due to speed and performance issues) at the end of last year. So the Twitter count is no longer available for any of the widgets.
https://blog.twitter.com/2015/hard-decisions-for-a-sustainable-platform
I think this is an example of what you're talking about?
https://postbulletin-dot-com.bloxcms-ny1.com/site/forms/announcements/wedding/
Customer support service by UserEcho
I've added this as a bug ticket to our system. It looks like our front-end plugin and the software do not always agree on what a "word" is, so we'll have to change some of the rules. Thanks!