Are you guys using workflows? Does the start time of the asset pass before the the publish setting is enabled?
Are you sure they aren't hitting "save as draft"? "Save as draft" will do what you say (saving it as a draft until it is published - even if the story goes live). "Save and send" will send it as soon as possible, which would be when the story goes live.
I will do some testing of this to confirm the above behavior... if it is not doing that I would agree it is a bug.
As a follow up to this question, regarding the "large image" display on Twitter cards, we require that you set up the Twitter username field in the URL properties -> Meta data properties before we add the Twitter card data to your site.
Once you fill out that field, you'll get meta data on your articles like this:
meta name="twitter:card" content="summary_large_image" /
meta name="twitter:site" content="@pantagraph" /
meta name="twitter:image:alt" content="Bomb Cyclone Colorado" /
That summary_large_image is what determines the "large" display that is mentioned in Allie's original post.
So, as long as you add that username, the large image card will be default.
Here is the help doc that talks about this: https://help.bloxcms.com/knowledge-base/integrations/social-media/twitter/article_36e82a6e-6f66-11e4-949f-a75641b24dfe.html
Thanks for adding that. I definitely agree with that for BLOX Comments, and possibly other less-popular commenting systems.
And I do feel that having to post under your real Facebook profile will deter some users from posting bad things.
The problem is that it facilitates bad actors on Facebook to be able to post more easily, and that offsets the gain from requiring real names.
That's just my opinion though, it would be interesting to actually look at real data.
In addition - there seems to be a big reduction on troll versus real comments on Facebook in the last several months.
I was going over this with another publisher who was asking for the same thing, and I feel like in the end he just decided to put commenting behind the paywall as a "membership" bonus, but look at ways to better promote the existences of the comments on the page (without being able to read them).
We've actually done this as a customization in the (long ago) past, and there could be awkwardness in how this would look to the non-subscriber.
So, you go to the article, and as a non-subscriber, you can't actually READ the article itself. But, then you scroll down and you can then read the comments about the article which you haven't read.
In some cases (this is also popular on link boards like Reddit), one of the users will actually summarize the article so that non-subs can learn about it and don't have to subscribe or log in (or so they can just TL;DR it).
So, in effect that could then be a disincentive to subscribe, because now you can glean information about the story without needing to subscribe.
That being said, when I was discussing with this other publisher, we did come to the agreement that there needs to be better promotion of the comments when you're behind a subscription. Maybe there could be one comment there, and it says something like, "There are 24 more comments to read if you become a subscriber now!" or something.
Anyway, let me know your response to that idea, if you agree with the premise, and if not, what are your thoughts. And if so, what ideas you may have for promoting the comments better when they are behind the paywall.
We have a few contacts at Facebook, so I can see if we are able to at least get a little more information about what this means or making sure they understand that this basically means the plugin doesn't work on nearly half of all pages. Across our network, iOS is 41% and Mac is 4%.
That being said, we've seen a trend among our customers to actually move off of Facebook commenting in recent years. I think a few years ago we (we = media industry) thought that making users post with their Facebook identities (i.e. real names, usually) would cause them to be more civil. But, that certainly didn't happen. If anything, Facebook comments has almost made it easier for troll types to participate in article-page discussion. (I don't think this is a controversial opinion - I'm curious if anyone disagrees.)
And, since the Facebook comments plugin does take TIME to load on the page (and since it is on an external server there can be random latency issues) it does end up being a page speed "investment." (My philosophy is that anything you put on your site - especially third-party widgets - requires that you "spend" some of your valuable page load time on that widget. If it takes 2 seconds to load, even asynchronously, it increases your page abandonment, which costs you money via ad impressions and ad viewability scores).
(Sorry about the overuse of parenthesis in the two paragraphs above! (I need to work on that.))
So, what are the other options? We have built-in support for:
Livefyre - This is now part of Adobe Experience Manager, which is $$$
The World Table - My recommended third-party vendor. They have great engagement features and robust moderation tools. It also has a page you can set up that has all the most recent comments, so a user can just go into that area and reply to other comments, sort of like a forum. It is ad supported, but not as many ads as Disqus.
There is also BLOX Comments. We don't have as many features as other third-party systems - however, since it is not an external system, it has almost no additional weight page load.
As a side note, if you chose to implement your comments with a "load comments" button, it should not have any impact on your regular article page speed - though I assume you would lose some commenting engagement. So if you're using a third party, that could be a way to go.
Some sites recently have been implementing Viafoura. We don't have an official integration with it, but it can be done. I'm not familiar with the pricing or other details, but it looks like it has a lot of media customers.
Correct... images for content blocks are automatically "alt"ed.
Ads have an alt text that just says, "Advertisement" or something along those lines. We would have to create a new field for the alt text for BLOX Ad Manager assets, so that would require a bit of additional development. I would recommend looking at Google Ad Manager instead, which does have an alt text feature for image ads.
Any block type that is specifically image-related, such as Utility: Image or Utility: Site Logo (as Ian noted), has an alt text field for that image.
This would indeed solve the problem with the wrapping headlines. I am a bit nervous about this because in terms of the interface, it would be a bit confusing to the reporter / admin user. They would need to know that in this specific case, the headline was the message and the message wasn't used. If they wanted to re-write the headline to be more specific, they would need to know that the headline wasn't the headline, but the headline was the message.
In the "code" it is sending the "title" and the "message." The title is optional. But, I would feel uneasy making the "message" the title in just this one case, if that makes sense.
In addition, it is possible that Apple could change the display of the message in the future, and the fact that we've changed the meaning of "title" and "message" could backfire.
That being said, I agree with the premise of your post. I will talk to our dev team to see if they have any ideas on how we can communicate this clearly.
I'll go through each item step by step:
1. Currently, you can re-notify a message by just posting an additional manual message. You can do this ahead of time (one post today, one post tomorrow) or when needed for breaking news. The automatic trigger will not re-trigger (which is good, because you wouldn't want that) - but if you create a new message for breaking news, it will re-post it.
2. To define a custom Facebook message, you can type the message in the notifier message area. I believe that it will also use the Summary text as well.
However, you may be talking about the summary that is in the news "card" area on Facebook, which is scraped from the page itself. See my docs here:
3. What you're describing here is the "Twitter card" layout, which is specified on the page that is scraped by Twitter. For the example you have there, Butter is overriding the card type through their API.
Usually, this is something we have by default as part of Flex templates. We have built-in logic that will specify a large photo in most circumstances. For some reason, this isn't showing on pantagraph. If you could submit a CRM ticket to see if there is something custom on this site or why the Twitter card logic isn't displaying for you.
Let me know if you have more questions!
Customer support service by UserEcho