Quantcast
Channel: DevNet Hotfixes
Viewing all articles
Browse latest Browse all 491

Hotfix 13.0.63

$
0
0
Be sure to check our Hotfix instructions before starting the hotfix process.It might save you some trouble afterwards.

Fixed bugs:
  • Caching - Moving a page to another location in the content tree did not clear the page's original parent from the cache.
  • Content editing - For pages with fields based on the 'Rich text editor' form control, notifications about unsaved changes were incorrectly displayed twice on the 'Content' tab in the Pages application.
  • Dialogs - Selecting a file in a media selection dialog that was limited to a specific media library made it impossible to select files in other media dialogs that were limited to a different library. For example, the problem could occur when editing pages with two fields based on the 'URL selector' form control, each with a different media library selected in the form control's 'Available site libraries' setting.
  • Email marketing - If a marketing email recipient viewed an email in a client that blocked images used for open tracking, and then clicked on a tracked link in the email content, the system logged the open statistic for the email, but didn't log the 'Opened marketing email' activity for the given contact. This could lead to marketing data inconsistencies between the email statistics and the activity log. After applying the hotfix, email open activities are logged when the action is recognized through a link click (depending on the site's consent requirements and the cookies stored in the browser where the recipient opens the link).
  • Import toolkit - When using the Import toolkit utility to add a new culture version to an existing page, the import incorrectly replaced one of the page's existing culture versions instead of creating a new version. To fix the issue, the hotfix must be applied to the Setup files (switch to advanced mode in the hotfix utility).
  • REST - Authentication hash parameters generated for REST service URLs with the HTTPS schema were invalid. The resulting requests failed to authenticate and returned the 401 Unauthorized status code.

Viewing all articles
Browse latest Browse all 491

Trending Articles