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.
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...
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...
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.
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...
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...
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...
Here;s what I found - When you publish a page that reference a content
fragment that was modified but not published yet, then the publish
screen will show you all the references to Content Fragments so that
Authors are enabled to publish them. On the other hand, when publishing
a content fragment, authors would not know the pages that are
referencing that content fragment. I wish at least the references can be
shown as it currently does for an image asset - Please correct me if my
understanding ...
Latest update we received from Adobe on this through day care - We have
confirmed from the engg team and same has been written in the docs And
an evaluation for improvement on this feature is been checked on this
JIRA (CQ-4236738). Locking a page can be performed when impersonating a
user. However a page locked in this way can only then be unlocked as the
user who was impersonated or a user with administrator privileges. Pages
cannot be unlocked by impersonating the user who locked the page. Als...
I feel it's good to have this doc updated with all AEM versions that
this issue applies to - How to unlock a locked page Applies to is still
referring to AEM 5.2.x. kautuksahni
In my test, adding "workflow-user" seems to have solved the problem in
first attempt of testing, will post if there are any further updates.For
those who are reading this understand that this user won't exist in 6.3
anymore if its a fresh install. But if if you do any in place upgrade
let's say from 6.1 to 6.3, you will find this user in useradmin screen.
Also, I believe in the list of steps provided, should we not change the
service users that is configured to lock and unlock the payload based on
workflow model definition? Please see the highlighted section below - In
my case, applying the below steps didn't work. I will try to change the
service users to our custom user group/user and update the results. In
my case, This issue should be fixed for workflow packages. Workflow
lock/ unlock steps not working in AEM 6.3 To apply configurations to
al...
Yes, that was my understand as well. Thanks for your time. I would still
look forward to hear on the detailed steps to achieve nosamplecontent
runmode behavior on the server which got installed without
nosamplecontent runmode.
Thanks Kunwar. I believe this command is run to initiate the in place
upgrade process. What if we need to add nosamplecontent runmode after
finishing the upgrade process and server is up and running. To my
knowledge it should be the same behavior as fresh install, which is not
possible. Please correct me if I am wrong. And also if possible point me
to any documentation related to adjusting the configurations of AEM to
meet nosamplecontent behavior.
What happens in case of an in place upgrade process? One of our clients
did perform in place upgrade recnently on AEM 6.1 to upgrade to AEM 6.3.
After the upgrade was done, infra team from customer side realized the
nosamplecontent runmode is missing in sling properties. As per the
documentation, the primary runmodes can't be added or changed once the
installation process is complete.I am wondering if there is any clear
and complete documentation around the number of changes that we may need
per...
May I know the default OOB password for "replication-receiver" user in
AEM 6.3. I couldn't find the correct password. some blogs says its same
as the user name. But it doesn't seem to be working when I try to login.
Thanks for your Time on this.Removing the task from the maintenance
would work for sure.I am hoping to get this information through Adobe
Docs or Adobe Internal Staff. We don't want to disable it unless if it
stable. As per Adobe docs, Online Compaction in 6.3 is stable and
recommended maintenance activity.
It maybe helpful for those trying to figure this out on RHEL + Apache
2.4.6Try this SELinux Prevents httpd Write Files - Unix & Linux Stack
ExchangeWorked for me. The commands you have to run after making sure rw
permissions are given for apache user on semanage fcontext -a
-t httpd_modules_t /etc/httpd/modules/mod_dispatcher.sosetsebool -P
httpd_can_network_connect onchcon -R -t httpd_sys_rw_content_t
/var/www/html/semanage fcontext -a -t httpd_sys_rw_content_t
"/var/www/html(/.*)?" restorecon ...
Any ways to disable this in AEM 6.3? We have come across this blog post
when solving inconsistency in AEM publish instance segment
store.Possible reason is missing Repository service. Check
AuthenticationSupport dependencies | And we were able to get the server
up and running after following the steps outlined. However, one thing
that we couldn't execute was disabling the online compaction using the
below step, specifically the first highlighted line. Solution:
Permanently switch off online comp...
Thanks for the response. Below steps helped us solving the problem.
Note: these steps are not documented in adobe docs yet. Also remember to
install, JDK 1.8-Take a fresh backup on running 6.1 environment and
perform the pre-upgrade maintenance tasks.- Move the segmentstore from
/repos folder and move it under /crx-quickstart/repository- Navigate to
/crx-quickstart/install folder and edit SegmentNodeStoreService config
and remove the 'repository.home' parameter- Copy 6.3 Jar along side
/crx-quic...
Here's what solved the problem. This is not documented in adobe docs.
-Take a fresh backup on running 6.1 environment and perform the
pre-upgrade maintenance tasks.- Move the segmentstore from /repos folder
and move it under /crx-quickstart/repository- Navigate to
/crx-quickstart/install folder and edit SegmentNodeStoreService config
and remove the 'repository.home' parameter- Copy 6.3 Jar along side
/crx-quickstart- Run the command to unpack, java -jar 6.3_quickstart.jar
-unpack- Backup and Rem...
I am getting the same error. Were you able to solve this.I hope Adobe
must have helped to solve this problem if any day care ticket was
raised. In that case, It would be really helpful if someone from
community may update this post with a reply on the solution.Raised a day
care ticket almost a week ago and waiting to hear from the engineering
team for an answer...
