Test4 User
@test4
-
When you restart AEM using a remote server access SSH tool like Putty or Gitbash, you are restarting the underlying HTTP server process (e.g., Apache HTTP Server) that hosts the AEM instance.
-
When you restart AEM from the OSGi Console, you are essentially restarting the AEM instance itself. This restart is specific to the AEM application and only affects the AEM process.
-
When you restart AEM from the OSGi Console, you are essentially restarting the AEM instance itself. This restart is specific to the AEM application and only affects the AEM process.
-
Restarting AEM from the OSGi Console and from a remote server access SSH tool like Putty or Gitbash are two different approaches with distinct implications. Let's dive into the details:
-
- Check the cards list initialization: In your CardDustReviews class, you have a @ChildResource annotation on the cards list. Make sure that the cards list is properly initialized and populated with data. You can try debugging the code to see if the cards list is empty or if there's an issue with the data retrieval.
-
- Verify the Angular mapping: Double-check that the Angular mapping is correct and that the CardDustReviews component is properly mapped to the JSON output. Make sure that the Angular code is correctly referencing the cards list and that there are no typos or incorrect property names.
-
- Check the Exporter configuration: Ensure that the Exporter configuration is correct and that the CardDustReviews class is properly registered as an exporter. You can try checking the Sling logs to see if there are any errors or warnings related to the exporter configuration.
-
Check the cards list initialization: In your CardDustReviews class, you have a @ChildResource annotation on the cards list. Make sure that the cards list is properly initialized and populated with data. You can try debugging the code to see if the cards list is empty or if there's an issue with the data retrieval.
-
Yes, it is possible to set traffic filter rules, including rate limits, in AEM as a Cloud OOTB Fastly CDN. Some of the advanced WAF-based rules require an additional WAF or advanced security license, but the basic filter rules can be used OOTB.
-
ability to view source code of previous versions is currently not available in the version history feature. We have added this in our roadmap for next year.
-
If you anyway need custom code to capture this new category, maybe a line of code would solve the issue rather than introducing a whole new extension?
-
Yes it is OOTB dependencies depends on the version of cloud ,If cloud server uses the old version then map the same old version to your main pom and also try to change the analyser version 1.1.2
-
If extensions are blocking then please try to open the page in another browser (Mozilla, Safari) or you can also check in incognito mode.
-
I almost suspect there is an issue with these diagrams (but it's hard to prove).. but in my case, our "orders" are subscriptions... users can only purchase a single subscription at a time... so there should be no way to have multiple orders in a visit that could cause calculation issues with a flow diagram, and yet, the orders are way off for us... leaving me even more convinced there's a bug in that visualization.....
-
Personally I don't use the flow diagrams much... While I appreciate the ability to see the pathing through multiple channels like you are trying to do... Since the numbers don't align it causes confusion...
