About the development of new requirements and optimizations of the Content Management System.
Chat funtionality must be enabled twice!
- in tab CONTENT SETTINGS at the bottom to enable Chat in general
- in tab TOPIC OVERVIEW per topic that should show the chat
Until now when unsubscribing from newsletter it takes quite long to get a response from the form. The user does not see that the action is being processed in backend which is not optimal.
Therefore an waiting indicatior has been implemented for the Newsletter form (subscribing and unsubscribing) but also for other forms to make the process more visible for the user.
Other adjusted forms:
Info:
Only newsletter unsubscribe has a longer waiting time after clicking submit button. Other forms have nearly no timespan between sending and thank-you-page display. However they have been adjusted too in case longer timespans appear.
It was noticed that in the value primaryCategory of the digitalData.page within the data layer was set to "n/a" on the Consumer Homepage.
This has been optimized to primaryCategory=Home.
Until now we had following behavior for canonical tags/links:
If an article can be seen on several pages and the canonical page is not explicitly defined (manually), then by chance one of these pages becomes a canonical page. This one page would reference itself as set in the canoncal link, the other pages would refer to this one page.
This has been optimized to following behavior in determining the canonical link:
In the following the canonical link will be set with following conditions in priority order.
If there is an assortment page which is located under the coverage area of a product viewer page in- then that page will be chosen as canonical page.
The search stops as soon as a suitable page is found. For example, if a type 1 page is found, then it becomes the canonical page and 2-4 are irrelevant, etc.
In order to remove duplicate recipe pages and replace them with recipe copy templates, it was noticed that the rollout process was not working the ES regions.
The Problem here was the move from "recipe" to "recipe-old".If the recipe is renamed from the blueprint, the reference to this recipe in the live copies in BAL and CAN is automatically updated. The LiveSyncConfig nodes then point to "recipe-old" (this also without a new rollout) However, the name of the live copies is not updated, even after explicit rollout.
This results a broken connection between blue print and live copy.
In this case it was decided to work with a different procedure instead of performing a code change.
To Do:
Skip the step with renaming the recipe to "-old" and direclty delete "recipe", then roll out so that "recipe" is also deleted in BAL and CAN. Then create the recipe-copy and re-rollout.
Info:
From the moment of the deletion until the creation of the recipe copy (and its activation and rollout) the recipe page will not be accessible by our customers on the website. But this should not be more than a few minutes. If you experience long down times, please contact us
Daily importer for BELU has been improved.
Following aspects are covered now in the daily importer:
Info:
We will open a SUPP-Ticket for communication and test run of the importer after PROD Deployment.
A new shoppinglist template has been introduced that will replace the old version
Major features are:
Info:
Every market will get assigned a SUPP-Ticket with explanations what needs to be done to set up shopping list.
Once all tasks are completed assign the ticket back to Support team. Then Dev team will exchange the link behind shopping list icon to new list
Group Ticket: SUPP-3336
ES - House number missing in Store Picker
The JSON file has been adjusted with a combined field with street and number.
You can check the result with the following steps:
If only one article is maintained in the dialogue of the component in the multi-field, then this is saved as a string (and not as a string-array) in the JCR. This difference in storage format results in the adjustPropValue(...) method in the ImageMapAssetLoader not showing up including the article data. - This has been fixed.
Recipe filter - diet type not available
The diet type filter on the recipe search was missing and is now integrated: Please insure to have the corresponding labels translated.
To check if the Filter is available:
Recipe filter - Strange behavior regarding amount of recipes displayed
The search results overview for recipes and also for offers are not displaying all found items even without any activated filter. - This bug has been fixed.
To check if the search results are working properly please check the following steps:
Recipe reset filter difficulty, all filter reset and filter counter
The recipe filter has been optimized with the following adjustments:
BE - Product detail page price button (wrong color theme)
On the product detail page all articles have the color theme (red) selected in the article tile group on the overview page. If you then open an article details page, the default theme (grey) is displayed.
The issue occurs when the article is placed on a tile-by-category component. Even if the product viewer is not used. - The issue has been fixed and the correct color theme should be shown.
Short reminder:
To update our contact list we kindly want to ask you to list down all of your team mates via email to aldi-support@mrm.de.
Please also let us know which teammates:
ALDI Einkauf SE & Co. oHG |
Department ATS | Loyalty & Marketing Solutions
The use of the male form when referring to persons or functionaries in the following text does not mean a gender-specific definition. Members of both sexes should be addressed on an equal footing.
The release integrates new functionalities, optimizations and bug fixes into the software.
Please read these release notes to be up-to-date concerning the new program version and to get important information on handling new functions.
If you have any questions about this update, please contact MRM / McCANN external support at aldi-support@mrm-mccann.de
Eine Erinnerung ist nicht mehr möglich
Die Erinnerungszeiten für diesem Artikel sind bereits abgelaufen.
Erinnerung aktiv!
hh
Sie erhalten Ihre Erinnerung am ${date} um ${time} Uhr.
hh
