July 12th 2024
Fixed
Vero Cloud
Vero Connect
There’s a common saying we’ll forgo here, because suffice to say small things CAN have a big effect. With that in mind, here’s our latest batch of tweaks and tinkerings that might float your boat.
Improvement
Format dates correctly in multi-language campaigns - We have added a with_locale
filter that will format a date in the language of the locale passed to the filter. For example:
purchase_date = "2015-04-01 11:33"
{{ purchase_date | with_locale: '%Y %b %H:%M', 'es-MX' }} => 2024 abr 11:33
Read more about using with_locale
in multi-language campaigns in our help documentation.
General Bug Fixes
Hidden on desktop and mobile fix
Added a fix to the drag and drop editor when selecting the ‘desktop’ or ‘mobile’ responsive options on a block. This makes sure blocks can never be unintentionally set to hidden on both desktop and mobile.
Invalid email address causing failed imports
Fixed an issue where an invalid email address in the results of an SQL query or in a CSV could prevent in some rare cases cause the import from completing successfully.
Cloud Specific Bug Fixes
Error when accessing team members page
We’ve fixed a bug that would sometimes prevent admins from accessing the team members page.
Exporter only exporting 50 campaigns
We’ve fixed an issue when exporting campaign results that only returned the first 50 campaigns no matter how many were selected.
“Service Unavailable” when making team changes
We’ve fixed an bug that would sometimes present a 503 Service Unavailable
error when adding team members or changing their permissions.
Only able to access invoices/billing
We’ve fixed a bug that prevent you from accessing the billing or invoices page if you were not in the first project you created.
Log exports failing
Fixed a bug where attempts to export a person’s log history would fail if one of the event logs had been deleted from the system.
Customer merge failure
We've fixed an infrequent failure that would occur when a customer profile was attempting to merge in our backend system. This failure would sometimes occur when two profiles which had both engaged with the same email communication were merged.