Apache Sling Request Parameter Handling configuration for the Default
parameter encoding is set correctly to UTF-8, that is not the
problem.With lack of any other answers the workaround mentioned here is
still the best approach
Hello Kiran,thank you for the answer. Yes, we are using the default one
and the encoding is set to UTF-8. I think that shouldn´t be a problem,
because the body of the emails is always displayed correctly and if we
set the subject in code
viaorg.apache.commons.mail.HtmlEmail.setSubject() then the subject is
displayed correctly as well. Problem is when the subject is taken from
the mail template.
Hello,we have a long-term problem with encoding in email subjects, where
characters like "šáěíéščřý" are not shown correctly. Until now, we have
been changing the subjects to use basic ascii letters. But now we are
expanding to russian customers, and with azbuka (cyrilic) letters we can
no longer do this.In principle, our mechanism is the same as described
they are discussing the same prob...
Thank you for the info, I tested it now and it seems to work! Now I see
only the logs about the service/servlet registrations again.Since I
didn´t find an existing config in system/console/configMgr I´ve added
the configuration manually through
adding here an edited binary jcr:data from another config
with:resource.change.types=["ADDED","CHANGED","REMOVED"] I will raise
the ticket as well, just nobody in our compa...
Hello Jurgen, unfortunately not 😣 I´ve been through many settings in
console and the maintenance UI but nothing helped so far. My only hope
is Service Pack 4 for AEM 6.5 which we haven´t tried yet, but I don´t
have much hope for that.
Hello @Jörg_Hoh,I have checked the system/console/events after deploying
a component zip with bundle but the total length was longer than 250
lines, which is the limit of the console there. But I am enclosing it
below through Pastebin:https://pastebin.com/X44sU1YD Also the whole
error.log concerning the deployment of the package and bundle inside.
Maybe it will be helpful:https://pastebin.com/jMw3W8Dr part
1https://pastebin.com/3kQ0591n part 2
When we moved from AEM 6.2 to 6.5.3, bundle deployment started taking
more time. According to log, each servlet and service registration is
accompanied by some Adobe Granite Maintenance Scheduler Update Task.I am
enclosing below the initial log snippet when starting the deployment of
a content package containing our OSGi bundle. After this it goes on in a
similar manner for 25 seconds before finishing. Is there a way to
disable the Update for development environment? 07.03.2020 21:35:08.135
Hello Vishu,this has been a problem for us as well, after the update.
Could you please elaborate about how to redirect the warnings? I haven´t
been able to find a configuration for this.Best RegardsMartin