This article summarizes all the bugs fixed for Maropost for Marketing in the month of July. To get a summary of bug fixes for the month of June, see Bug Fixes - June 2020.
23rd July
-
Fixed: The feature for archiving dynamic content wasn't working.
-
Fixed: In Journey builder, when the journey elements were spread across multiple pages, the Journey elements menu was behaving erratically.
-
Fixed: Users were unable to unsubscribe from SMS campaigns.
-
Fixed: Some users having permission to create and download reports were denied access. The reason was found to be that the custom reports were using APIs that had a dependency on the campaign role. The dependency has been removed, making the APIs accessible to the custom reports.
21st July
-
Fixed: The search within a custom campaign report wasn't showing all campaigns.
-
Fixed: Unclear notification message for segment export was causing confusion. Now, the notifications are immediate and clearer.
-
Fixed: In the campaign builder, if a Brand was selected and then subsequently removed, the final campaign was still sent to the contacts associated with the Brand.
16th July
-
Fixed: Upon duplicating a scheduled campaign, the Send Now button on the review page of the new campaign was giving error.
15th July
-
Fixed: The A/B campaign send count was showing in a negative value. The issue happened due to rounding off of contact count and has been fixed.
-
Fixed: A deadlink was observed when editing the email address on the profile page.
14th July
-
Fixed: In the app cluster, the error messages in the landing page creation process were exposing the IP address. Now, CNAME is being displayed instead of the IP address.
-
Fixed: Sorting functionality was not working for campaign tags.
-
Fixed: The custom campaign reports were showing incorrect data for the unique open, unique click, and click-to-open statistics.
-
Fixed: Discrepancy in the 'year to date' data in Email Usage widget and Performance Summary widget because of timezone mismatch.
-
Fixed: Custom reports were missing the option to select the date format.
-
Fixed: Users were experiencing difficulty in moving sub-folders to root directly.
-
Fixed: Few users were experiencing failure in automated imports in Data Journeys.
9th July
-
Fixed: The icon to the export segment wasn't consistent with other export icons across the application. The arrow-head was pointing in the wrong direction which has been corrected.
-
Fixed: Some campaigns that were associated with both campaign folders and content folders were not showing up on the Email Campaigns Index page.
7th July
-
Fixed: The MD5 Hash checkbox in Email Segments remained selected even after the previous export was complete. The user had to refresh the page in order to deselect the checkbox which should have happened automatically.
-
Fixed: A glitch was observed in reset password flow where users were seeing old UI.
-
Fixed: In the ISP Reports, the ISPs with no data were showing 0 and blank for Values and Date columns respectively, which was causing confusion. Now, the Date field will show 'No Data Available' when there is no data to show.
-
Fixed: Some users were unable to view Customer Engagement Journey data on the Contact Overview beyond 7 days. The issue was identified to have been caused due to the campaign and journey name being the same. This has been resolved and users can now expect a flawless experience.
-
Fixed: Some users were unable to duplicate the existing custom reports that were created in old UI.
-
Fixed: Users were unable to perform the submit action when creating the custom reports.
-
Fixed: The contact count for the parent A/B campaign was not updating when the winner AB campaign had no percentage left for sending.
2nd July
-
Fixed: The email preview link was preselected by default when creating a journey campaign.
-
Fixed: In the campaign builder flow, the address field was not getting populated based on the selected list.
-
Fixed: The segment export in MD5 hash format wasn't working.
-
Fixed: The row selection on the acquisition form wasn't intuitive.
-
Fixed: The favicons on landing pages were not showing for Google Chrome and Safari browsers.