I would submit a ticket to our Customer Support team to ask what your options are based on your situation and based on what products you currently have and what specifically you're looking to accomplish (a one-time download or a job process, etc.) For example, our Total CMS product can serve as a local backup on an on-premisis appliance.

As for .bpm, it is just a proprietary extension and isn't really meant to be opened outside of the BLOX environment.

Hi there!

Actually, the dateModified schema.org property is already available. It looks like this in the code:

<meta itemprop="dateCreated" content="Tue, 28 Apr 2015 21:22:00 -0500">
<meta itemprop="datePublished" content="Tue, 28 Apr 2015 21:22:00 -0500">
<meta itemprop="dateModified" content="Mon, 10 Aug 2015 10:07:18 -0500">

If you are not seeing updates, look in your application settings for editorial. You may have "Manually declare important updates" turned on. In this case you have to check the box in the save button to denote something as officially updated. Then (after a few minutes) it will get the updated flag.

Note that stories more than 30 days old will not show an updated flag to avoid robots getting confused that a story is new when it was just updated. We may change this policy soon as it appears robots have fixed that issue, but we are testing this.

Hi Nick!

For that specific section, I went in and create a 400px preview and uploaded it to the edition, and that made it look a lot better (you can do this for any previous edition that has a small preview size).

Going forward, you'll now get 400px previews as well because I added that to your publication settings (in the general tab).

We use the appropriately sized preview image, and then use a proxy service to resize it to the optimal size that is displayed on the front end. In this case, I used 400px, but you could do 1200px and it would still resize to an optimized size for the display.

For future eeditions, you should have the 400px size already created for you, and you shouldn't have the blurriness problem.

You may want to add in a larger size if there will be the possibility of showing that ad on a larger size screen (maybe on tablet)?

Also, you may want to add a larger preview size to other publications as well.

Thanks Laura! That helps! I will report back when I hear from Second Street.

I have added this as a feature request.

Sounds good, we should be able to add this pretty quickly. Thanks!

Hey Robert,

Can you tell us more about your specific use cases? It will help us determine what specifically is needed and to make sure it meets all requirements.

From what I can tell, it looks like we are actually sending the PDF filename via the URL. The way we set it up with MyCapture, we have a partially obfuscated URL to the file that is sent through the URL. MyCapture knows the "secret" to converting that partially obfuscated URL into the file path.

For PDFs, it looks like we're just sending the PDF filename through the URL.

So, I sent an email to MyCapture customer support asking them why they are not accepting the PDF in these instances. It could be that there is an additional rule of "ispdf=1" as Ibj56 says, in which case we'll have to do a template release to fix that.

I'm going to ask to see if they could perhaps look to see if it ends in .pdf - that will also tell you that it is a PDF.

Anyway, I'll let you know what I hear! We should definitely be able to get this to work though, it is what we build it for! =)

Can you show me an example? It should be creating the image based on the 200 DPI image for eedition, but maybe eedition does somethign different, so I'd have to see it.

Hi Kevin!

This should be very easy to add. Just to make sure - is "Staff" the right verbiage? Maybe, "admin"? It would have to be the same always, though.