sureshr19072451

Re: AEM 6.3 - Version Exception After Author edits the page - Adobe Experience Manager 01-05-2019

Thanks Scott. I will reach out CC through day care.

4.7K

Re: AEM 6.3 - Version Exception After Author edits the page - Adobe Experience Manager 01-05-2019

Yes this appears to be a bug in AEM 6.2. And the docs says, its fixed with an FP for 6.2 and won't be seen in 6.3. My point is it is still an issue in 6.3. As Laura mentioned, Adobe has to investigate to see if it was ever fixed in any AEM version and do the needful. I totally understand, unlocking the page prior to publishing it will solve the problem. But in the first place, AEM should not allow publish action when a page is locked is what I believe. Thanks for the response.

4.7K

AEM 6.3 - Version Exception After Author edits the page - Adobe Experience Manager 29-04-2019

I am exactly referring to this issue - VersionException after author edits a page but in AEM 6.3. This issue should not occur in AEM 6.3 as there was an FP released in AEM 6.2 per the above link. I am currently seeing the same behavior in AEM 6.3 following the below steps - - Login as non admin user - say user1- Edit the page - And lock the page after edit. - Later sometime, use request for publication without unlocking the page - - User with admin/publish rights could publish this page ignoring...

4.9K

Re: Issue in Dispatcher Rewrite rule - Adobe Experience Manager 03-04-2019

It would be helpful if you can post what solved your problem with some details. Note: on turning off DirectorySlash - # see security warning below! DirectorySlash Off SetHandler some-handler Security WarningTurning off the trailing slash redirect may result in an information disclosure. Consider a situation where mod_autoindex is active (Options +Indexes) and DirectoryIndex is set to a valid resource (say, index.html) and there's no other special handler defined for that URL. In this case a req...

1.3K

Re: configuring RTE plugin for content fragment editor - Adobe Experience Manager 19-02-2019

You could try manually overlaying the StyleTextEditor.js file under /apps - Don't forget to define the categories and dependencies as done for clientLibraryFolders under /libs. For ex: Thanks.

4.8K

Re: configuring RTE plugin for content fragment editor - Adobe Experience Manager 20-01-2019

One quickest way to add subscript & superscript to CF Content Editor by editing /libs/dam/cfm/admin/clientlibs/v2/authoring/contenteditor/editors/StyledTextEditor.jsHere's my updates that adds these two plugins for both normal and full screen mode editors -1. "inline": { "toolbar": [ "#format", "#justify", "#lists", "links#modifylink", "links#unlink", "subsuperscript#subscript", "subsuperscript#superscript" ],2. "multieditorFullscreen": { "toolbar": [ "#format", "#justify", "#lists", "links#modi...

4.8K

Re: Expose aem assets as a service - Adobe Experience Manager 16-01-2019

If its AEM 6.4, content service is enabled by default. And for AEM 6.3 you have to enable the service. The ideal case is to use content fragment models as opposed to templates. And in both scenario's the easiest and reliable way you can access the CFs content in json format is using below URL -https://localhost:4502/content/dam/we-retail/en/cfs/orders/cancellations/jcr:content/data/master.jsonRemember these CFs are created using CF model not template. You can replace master.json with any variati...

2.3K

Re: Install AEM 6.1 on AWS EC2 Linux instance - Adobe Experience Manager 09-01-2019

As kautuk mentioned, this change must be made to either Default or custom security group that you mapped to your instance. You will then see -

1.3K

Re: configuring RTE plugin for content fragment editor - Adobe Experience Manager 24-10-2018

Even though this is an old thread, I am hoping Adobe is working towards identifying solution to these valid use cases. I will give some example scenario's One of the solutions we are proposing to the customer involves shifting all the page level disclaimers to content fragments in DAM. Authors are used to enter the content for the disclaimers on every page and sometimes the same disclaimer is being used on multiple pages, so more authoring effort. In order to solve the problem, we proposed using...

4.8K