3.17.1.x Hotfixes
DISCLAIMER
Product Information contained within this document, including technical information and functional specifications, is subject to change without notice. Naviga reserves the right to make any changes to the information in this document at any time without notice. Naviga makes no warranty, representation, or guarantee regarding the suitability of its products and services for any particular purpose.
Attention - Enhancements
Removing dependency on the EZPAY Component for Applepay Payway in the Autopay flow
The dependency of Autopay flow on the EZPay CMS component has been removed for ApplePay Payway newstart transactions. The new start flow will now follow the EZPay settings configured in the SolCon offer regardless of the EZPay component's inclusion in the CMS presentation:
EZPay Required selected in the SolCon offer: New starts will be submitted with EZPay set to 'true' regardless of the EZPay component's presence in the CMS presentation.
EZPay Not Required selected in the SolCon offer: New starts will be submitted with EZPay set to 'false', even if the EZPay component is included in the CMS presentation. (Note: Including the EZPay component in the presentation when 'EZPay not required' is selected in the offer level is considered an incorrect setup.)
EZPAY Optional selected in the SolCon offer:
If the EZPAY component is not included in the presentation, new starts will be submitted with EZPay set to 'false'.
If the EZPAY component is included:
If the Auto pay checkbox is checked by the end-user: EZPay is submitted as 'true'.
If the Auto pay checkbox is not checked by the end-user: EZPay is submitted as 'false'.
If the checkbox display is disabled on the UI for an optional EZPay: This is a setup issue.
This update ensures accurate submission of the EZPay data based on the SolCon offer-level configuration.
Redeployed the deprecated /DigitalAccess endpoint
The /DigitalAccess (POST) endpoint was deprecated in Subscribe version 3.17 as part of a major API refactoring. However, to ease the migration, this endpoint has been made available again.
Bug Fixes
InApp subscribers not getting website access
Users who successfully purchased subscriptions via In-App Apple Pay and were created in Subscribe did not gain access to the website. This issue was due to the large download_id sent by Apple Pay, which led to incomplete user details being recorded in Subscribe and thus preventing website access.
This issue has been resolved. After the fix, the details of successful In-app Apple Pay subscriptions are now updated correctly in Subscribe, ensuring that subscribers now have valid access to websites as per their subscriptions.
This fix is also merged into the 3.16.3.15 and 3.17.0.4 releases.
Instant access issue when restarting a subscription
When a stopped subscription was restarted from the Subscription Panel, users did not receive instant access to the subscribed site. Additionally, a different account number appeared in internal records for the restarted subscription, though it was corrected to the original account number after the nightly sync process.
These issues have been resolved. After the fix, restarting a stopped subscription now grants users instant access to the news site as per their purchased subscription.
This fix is also merged into the 3.17.0.4 release.
Custom CSS class not set for the CMS link
Previously, it was not possible to set a Custom CSS Class in the CMS for the SS footer link. This issue has now been resolved, and users can successfully assign a CSS class to the SS footer link in the CMS. This fix is applicable for both Horizontal and Vertical DisplayType.
This fix is also merged into the 3.17.0.4 & 3.17.2.1 releases.
UI label Misalignment in the Dashboard
The misalignment issue of week-day labels with checkbox icons in the Subscription menu and Billing menu label values has been resolved. After the fix, checkboxes are now center-aligned below the week-day labels, and the Billing menu label values are right-aligned. This update ensures a cleaner and more structured display of the Subscription and Billing menus on the SS dashboard.
This fix is also merged into the 3.17.0.4 & 3.17.2.1 releases.
OneTrust Modal not opening in the footer link
The issue where the OneTrust Modal did not open upon clicking the Self Service (SS) Dashboard footer link has been resolved. After the fix, clicking the SS Dashboard footer link now correctly opens the OneTrust modal on the same page without refreshing the screen.
This fix is also merged into the 3.17.0.4 & 3.17.2.1 releases.
Incorrect Trial End Date displayed in Trial Banners
Previously, instead of the trial end date, the subscription expiration date was incorrectly displayed on the trial banners in Self Service and SubCon Admin. This issue has now been resolved.
After the fix, for a trial subscription:
If the trial end date is null, a static message will be displayed:
Self Service: "This is a Trial Subscription. The trial end date will be updated soon."
SubCon Admin: "This is a Trial Subscription. The customer will be charged if the subscription is not canceled before the trial period expires. The trial end date is currently not available."
If the trial end date exists (not null):
Self Service: The message configured in CMS will be displayed along with the trial end date: "This is a Trial Subscription that will end on <Trial end date>."
SubCon Admin: A static message will be displayed with the trial end date: "This is a Trial Subscription ending on <Trial end date>. The customer will be charged if the subscription is not canceled before the trial period expiration."
This fix is also merged into the release 3.17.2.1.
Issue with Cache Refreshing
When refreshing the CMS cache using the “Refresh CMS + Site” button, not all cache servers were being refreshed. This issue has been fixed now.
This fix is also merged into the 3.17.0.4 & 3.17.2.1 releases.
Issue with the Restart page
The Restart page freezing issue—where the page became unresponsive, preventing user interaction, and eventually timing out with an error—has been resolved.
Omission of Grace Amount in One-time payment flows
The issue where the grace amount (a negative balance which is due to the publisher) was omitted from the Rate Table and the total amount calculation during One-time payments has now been resolved.
After the fix, when a user opts for a One-time payment, and if a grace amount exists:
It will be displayed separately below the Rate Table.
It will be included in the total amount calculation.
The field label for the grace amount can be configured in CMS via: Content > Payment (Filter by page) > ‘DebtAmountLabelText’.
This fix is also merged into the releases 3.17.0.5 & 3.17.2.1.
Applications Covered:
Subscription Panel, Self Service, CMS, API
Attention - Enhancement
Modification in POST /Purchases API endpoint
Two new parameters (PaymentAuthCaptured and PaymentInformation) have been added to the POST /Purchases API endpoint.
When PaymentAuthCaptured is 'true', the processed payment details provided in the PaymentInformation object are validated and sent directly to the circulation system to create the Subscription.
When PaymentAuthCaptured is 'false', the existing flow is followed - the /Purchases API authorizes and captures the payment before sending it to the circulation system for subscription creation.
For more information: Check Purchase API 3.17.1.2
Bug Fix
Issue in Starts with Billed & Check payment method
During new starts, the payments using the Billed (Payment Type Id: 5) and Check (payment Type Id: 4) payment methods were failing with an error message “The Customer Reference Number is required.”. This issue has been resolved. After the fix, new starts are now processed and completed successfully without triggering an error message.
This fix is also merged into the releases 3.17.2.1 & 2025.1.1.
Application Covered:
API
Newstart Subscription being incorrectly considered as a Restart
When a subscriber attempted to purchase a subscription who previously had a stopped digital subscription against the same product, it was incorrectly treated as a restart by Subscribe instead of a new start. This issue specifically occurred when the stopped subscription had a full address, whereas the new subscription was a Zip-only subscription without any address, and both subscriptions had the same zip code and email address.
This issue has now been fixed.
After the fix, Subscribe will attempt a restart only when the addresses are an exact match, not just based on the zip code. Otherwise, it will treat the subscription as a new start.
This fix is also merged into the releases 3.17.0.5, 3.17.2.2, & 2025.1.1.
Incorrect House Hold Level (HHL) updates
When performing a Subscription Start call in SubCon Admin or selecting an account in Self Service, the HHLs were incorrectly updated to ‘Premium’ using the value set in the MG2Control Api setting DefaultHHSubscriptionLevel. Ideally, this update should occur only when the subscription status is Stopped in Subscribe and Active in the Circ system. However, the update was happening for all subscriptions regardless of their status in Subscribe, resulting in unnecessary HHL changes. This issue has now been fixed.
After the fix, the HHL of a subscription will only be updated if the Subscription status is Stopped in Subscribe & Active in the Circ system.
This fix is also merged into the releases 3.17.0.5, 3.17.2.2 & 2025.1.1.
The following fix has a dependency on the Circ version. Minimum NCS Release Version required: 2025-3.0.
Issue with Restart flow for a Stopped subscription that should step up to the next rate
When a stopped subscription was restarted via Self-Service, the correct payment terms and amounts were displayed and deducted from the user, but the next rate code was not applied when applicable. The subscription was saved with the old rate code instead of the rate code applied for the payment. This issue has been resolved.
After the fix, whenever a restart occurs for a stopped subscription, the appropriate rate codes are applied and saved correctly in the system.
This fix is also merged into the releases 3.17.2.1, 2025.1.1 & 2025.2.1.
User Orchestrator - Newsletter Subscription Issue
When a user registers on a site, they are automatically subscribed to the newsletter. However, after a client upgrade, it was observed that registered users were not being automatically subscribed. Instead, they had to manually subscribe by logging into their profiles.
This issue has now been resolved. After the fix, users registering on news sites are automatically subscribed to newsletters as expected.
Note: This is applicable only for clients using MG2 authentication.
This fix has also been merged into releases 3.17.1.4, 3.17.2.2, 2025.1.1, 2025.2.1, 2025.3.1, and higher versions.
Last updated
Was this helpful?