Is anyone else having issues creating poll assets? Every time we try to create a new poll we get the message "Preparing asset editor," and that's it.

I'm wondering if this s something unique to us or is it a larger problem.

I've worked with BLOX/CMS for four years and noticed about half a year ago that the quality of photos, especially those that are more vertical and when viewing on a phone, were a lot less crisp. Specifically I've noticed a lot of jagged edges. 

Has anyone else noticed this? 

Is there any setting or adjust I can make to improve this? 

Has anyone moved away from using Google for site analytics?  We are thinking about migrating to a service like Plausible.io which we pay for vs. using Google for free and giving them info about all of our readers.  Plus, managing it appears to be an order of magnitude simpler.

Has anyone made this change? Any feedback or other services we should look into?

That's all!

Thanks

Adam

https://admin-newyork1.bloxcms.com/desktop/#/countylinemagazine.com/marketplace-business

When someone forgets to designate a workflow stage for a budget/story, it automatically publishes to the web. This is a very bad idea. Can it be changed??

We have an on prem TCMS appliance and we are trying to figure out a feasible way to allow our page designers to work at home without requiring VPN. The internet lag seems to be the biggest hurdle but we also struggle with giving access to the shared files without VPN. Is anyone doing this successfully and wouldn't mind sharing the setup? 

I get that promo codes generally aren't very difficult, but as a tech guy at a newspaper I run into customers who just seemingly find a way to create unnecessary issues.   I think it would be neat to be able to add something in the Subscription URL so that the promo codes are already displayed.  

Example:   www.tdtnews.com/users/admin/service/purchase/?serviceid=478#RESUB would take you to the online-only subscription page, but the #RESUB or ?RESUB would activate the promo code without needing to type it in.  

Thank you, 

New Blox user here.

I think it would be useful if a pinned asset in a block could show it was not yet live ... whether by icon, or a different colour shading. Yes, we can quickly edit the article to check its pub date/time, but it would be nice to see visually which pinned asssets aren't live.

Also, can the block be smart enough to show the maximum number of live articles? If we pin 5 live articles and 5 future articles into a 10-article block, the block shows it's full even though the block on the live site is pulling in 5 articles from query because 5 pinned articles aren't yet live.

Thanks,

Tim

It would be great to have an autosave feature like in Google Docs. Being able to write in Blox makes the process faster, but not when you accidentally hit "cancel" instead of "insert," and that's from experience.

When placing assets in-line in Longform displays — particularly image and video assets — it would be nice if the "Inline display options" could be a little more robust. Right now for horizontal photos, the "default" and "full" widths display at the same size. Ideally, the "default" width would display images & video assets at 945px wide, and the "full" width option would display them at 1,140px wide (the same width that images display when the images asset is set to "Showcase". 

It would also be cool to have an option to "tile" images side by side, for instance have 2, 3 or 4 images display all in a single horizontal row across the 1,140 display area, and have their individual captions display beneath each image.

These options would give us more robust display options for long-form articles.

We have a team of freelance journalists who all have BLOX accounts and submit their articles through the CMS for review and publish. Their BLOX accounts use their personal email addresses like Gmail and Yahoo. We would prefer that these email addresses are not visible to the public when the article is published with the author's credit. If would be great if there was a way to choose an "email alias" that would be visible on the frontend of the website instead of the personal address. That way we could collect responses to the articles internally.