Your comments

Note that for customers who do not have a locally cached page, they would be seeing the ad much sooner.

Yeah, this is subject to a few caching layers... such as the JS files updating and the page updated. It should take around 15 mins if you cache bust as Ian explained.

Hi Jeff... You have "optimize PDF files" enabled in your editorial -> application settings -> asset settings -> Optimize new PDF files. Optimizing PDF files removes a lot of information in order to make them smaller and flatter.

If you turn this off, even temporarily, in order to upload your file, it should fix the issue.

I tested it, and when the "Optimize PDF" setting turned off, the PDF keeps the fillable information, and when a user downloads that form, it will allow them to fill it out.

https://flex-showcase.bloxcms.com/example/pdf_691077b4-4f6b-11e9-9e00-1f280866c63e.html

You can then turn back on this setting if you want other PDF files to be optimized.

A few quick things:


1. The BLOX Notifier alerts should look like the BLOX Email Reach alerts. This is something we're working to fix.

2. We can make changes to the asset page "email" mode design in a generic way, so let me know what type of thing you'd like to see there.

3. We are working on a new way to be able to send better branded emails of all kinds... email alerts and reset password, etc. We are building a "Site Branding" panel where you can set your colors and your logo, etc. That way we will be able to use your logo and colors in a standard way on system-built items such as this.

There are several different ways to do this:

- Tell your breaking news block to only show items that are less than 2 hours old. So whenever a article is two hours away from its start time, it will be removed from the block automatically. This is great when you are OK with all breaking news being promoted for the same period of time. If there is an edge case that needs to be online for longer, use can use a pinned asset with a schedule.

- Add an archived date to your breaking news article, and then create a rule on your breaking news block that doesn't show items that are archived. This is helpful when you want to have custom "expiration" times on a per-article basis.

- Use a pinned asset that has a scheduled time to unpin. You can use this in combination with the above two solutions.

- Create a new schedule which shows the breaking news block for a period of time. This is likely overly complicated since you'd have to go into the block editor to create a schedule. This is more likely to be useful for recurring events (like afternoon updates or Friday night prep sports) rather than breaking news. But, if there was a big specialized layout with multiple blocks for the breaking news initiative, a scheduled layout may be helpful.

With all that being said, we are looking into new ways to indicate "alerts" and things along those lines. For example, if you find a breaking news article from 2013, it will still say BREAKING next to it, or it may even say that in the headline. Those are things that are still in discussion.

I'll have to check into this more... Other than creating two accounts... it looks like our Here maps integration will be available as soon as next week.

Yeah, so it looks like I need to change the instructions to not create a new service account, but assume that one is already there! We had two people run through this as a test and it seemed to work... but perhaps they just chose the other account randomly. =)

As a side note, I am working on a few new blocks or promos that will ask for Notification sign ups at other places in the site. For example, at the bottom or in the middle of articles, or maybe even a popup overlay (a popup overlay that you have to agree to, which then triggers a browser permission popup).

Let me know if you have any thoughts along these lines.

I think that's part of the issue Aidian... if you go to your manage service account permissions area, do you see two firebaseadminsdk accounts? 

I think when you click on service accounts, in Robert's screen below, it is generating a key from the service account that is connected to your firebase. So, that may be a more clear way of instructing you on how to do it.

It also could be that Firebase is automatically creating a service account at some point. It didn't do this before, but if it is doing that now, that should be the only account you need.

Hey Robert, would you mind giving me ready only access to your firebase? cmasters at townnews dot com. Generating a key should be the same in both places, as long as it is connected to your firebase project.

We'll still allow it on our "Social Links" blocks, and stuff like that (though I'll need to remove Google+) but I will go ahead and remove it from the user profile data.