Hi manvig66636792, Not sure if you have the same issue as others had on
this thread. The fix I provided was for mainly for 6.4 and not tested
for 6.5. Adobe included this fix for their next release which might have
got released in September. So you can check the latest service pack or
cumulative fix pack available and see if it still works.Some other
context :Please check if in the page properties of your root page you
have configured the /conf/ in the advaced tab else it
will point to the old ...
Hi shubhamg94002854 alissonxavier0105 suniln13212398, I create a
daycare ticket and they acknowledged that there was an issue at the
publish. They will release the fix with the next cumulative pack
somewhere in September, 2019. Meanwhile for testing purpose they sent me
a code fix package which if you install via the crx/packmgr works fine
for me. I'm attaching the code fix for 6.4 (I haven't tested it yet with
6.5) but its soley for testing purpose and adobe doesn't recommend to
use it on pr...
Hi there, With the OOTB workflow implementation I see that its not
possible to prevent the rendition creation of SVG files. It works fine
for skipping renditions of other mimetypes for example when I checked
for image/jpeg it doesn't create renditions of it when skip mime type is
configured in the workflow but its not the case with SVG. I checked in
6.2 and 6.3 sp2 both but its the same case. Anyone else faced this issue
or know how to fix it in the OOTB workflow itself just to make sure no
Thanks it worked for me It's bit of a inconsistency that other sections
of the page properties still have issues if you extend OOTB page
component as they are still with the old one. NVM I'll update to use the
new coral ui one
Hi All, After using the default datepicker
(granite/ui/components/foundation/form/datepicker) in page properties
when I try to fill in the value in the dialog it works fine as expected.
But later when I try to empty the field or remove value from there then
it still stays and also in the repository.Anyone has idea about it ?
Hi BigT168, the issue was with eaem-multifield=“” for coral ui 2. It
should be acs-commons-nested=“” in the dialog above when using coral ui2
components.Coral UI 3 makes it in a form of node and Coral UI 2 keeps it
in json format and I wanted it in json.