This article summarizes all the bugs fixed for Maropost for Marketing in the month of April. To get a summary of bugs fixed in March, see Bug Fixes - March 2020.
This list, however, doesn't include the bugs fixed for our new user experience changes and hence, you must see Bug Fixes for that list.
17th April
-
Fixed: When connecting to the Facebook accounts, some users were encountering a whitelisting error.
-
Fixed: For fields with 'datetime' data type in relational tables, the drop-down fields were created in UI with only 10 years range. Now, the range is increased to 150 years.
16th April
-
Fixed: Error in some campaign statistics because of the changes made to custom fields that were used in segments. Now, the custom fields used in segments cannot be altered.
-
Fixed: The newly created landing page was displaying unwanted hover texts.
-
Fixed: The users were able to edit a sent email by having the campaign open in edit mode before the campaign was sent and then making changes to it after the campaign was sent. Now, an appropriate validation and error message is in place to avoid such incidents.
-
Fixed: The acquisition builder was only subscribing contacts intermittently.
-
10th April
-
Fixed: Some users were unable to access certain features despite having the appropriate privileges.
-
Fixed: In some cases, the user permissions and account access related changes done through UI were not reflecting on the Admin panel.
9th April
-
Fixed: When editing the links in contact tags, the delete functionality for the links was not working.
-
Fixed: The Facebook custom audience action element was not working correctly. The contacts added to journeys using the element were not going through the entire journey and were skipping to the end element.
-
Fixed: Some users were unable to add images in the drag-and-drop (beta) editor.
-
Fixed: A contact was missing from the list due to contact ID discrepancy. The contact ID issue has been fixed now.
-
Fixed: The users were getting an error when saving a survey with a survey header.
7th April
-
Fixed: The functionality for assigning privileges wasn't behaving as expected.
-
Fixed: Few users were unable to export campaign reports from the notification panel.
6th April
-
Fixed: For content created in the drag-and-drop editor, if the name contained backslash (\), the content was being displayed in a distorted manner.
-
Fixed: The users were unable to deselect the fields in Table Field Updated trigger in the journeys.
-
Fixed: The segment details were showing code instead of rule condition value.
-
Fixed: The spam check process was getting hanged for content that contained Liquid script conditions.
-
Fixed: The users were unable to save a footer using an existing name. Now, the application accepts duplicate footer names.
-
Fixed: The users were getting a dead link when saving a preference page using an existing name.
3rd April
-
Fixed: For a few users, the download button for the custom report was missing.
2nd April
-
Fixed: The unique click data showed a discrepancy between the user interface and the downloaded report.
-
Fixed: The confirmation link in double opt-in signup forms was resulting in a dead link.
-
Fixed: In the recurring campaign report, the emails were not being displayed for the 'total opens' and 'unique opens' statistics.
-
Fixed: In the A/B campaign report, the emails were not being displayed for the 'total opens' statistics.
-
Fixed: The users were unable to download the recurring custom reports.