I tried following the example shown here:
modify the MANIFEST.MF file and install the Google Cloud Storage jar. It
was relatively successful, in that the google cloud jar installed and
our custom bundle no longer failed to activate due to Google Cloud. But
it instead failed to activate due to another incompatibility -
javax.annotation, version=[3.0,4) -- Cannot be resolved. It's definitely
related/connected to the Google Clo...
I have also tried adding to the pom.xml file:
and then I tried
Neither worked. And lastly, I tried installing the jar directly, which
failed because of a server error: java...
I am trying to use the Google Cloud Storage Client Libraries for the
Google Cloud Storage API within AEM 6.5. The eventual goal is for a job
to export some AEM content straight into a Google bucket. But for now,
I'm trying to run some tests, and it doesn't work. The bundle with the
Google Cloud storage codel,refuses to activate due to the cloud storage
not being able to be resolved. com.google.cloud.storage -- Cannot be
resolved As per
We have a nightly backup on our 6.3 authoring environment. We have a
script that shuts down the server, then makes a tar file of the
authoring directory, grabbing the crx-quickstart directory, license,
initial jar file, and so on. Once it's done, it restarts the server and
gzips the backup file.The tar process is taking a very long time -
around 12 hours or more - which impacts when we can use the authoring
environment.I cannot exactly say how big the repository is (the du
command never finishes...
We were facing some memory/garbage collection issues on one of our AEM
6.3 publishers. We did a heap dump analysis and the one suspect
said:243,406 instances of
"org.eclipse.jetty.server.session.HashedSession", loaded by
0x741a1fee8" occupy 1,421,271,104 (66.52%) bytes. These instances are
referenced from one instance of
"java.util.concurrent.ConcurrentHashMap$Node", loaded by ""This lead me to this article: AEM instance cra...
We ended up restarting the system, and when we did, the issue went away.
So we did not need to code change. Moreover, once the issue was gone, we
could no longer dig into the problem and find the cause.I think the
takeaway is the knowledge that when it says "Request Publication"
instead of "Publish Page," it indicates there's an issue with
replication in that environment. But the exact nature of that
replication issue is going to be specific to that environment. One
option to correct the replica...
Digging deeper and looking at
:I can deduce that these are the different conditions which will trigger
"Publish Page" or "Request Publication." "Publish Page" has the
conditions:Can ReplicateIs not a launch resourceIs not locked"Request
Publication" has the conditions:Is not a launch resourceCan not
ReplicateThis tells me that in the "Request Publication" environment
I am facing a situation similar to yevhenii.d on "Request Publication"
shown instead of "Publish Page" in Touch UI. One of our AEM 6.3
instances started showing "Request Publication" and "Request
Unpublication" instead of "Publish Page" and "Unpublish Page".and I can
implement yevhenii.d 's solution:I found the actual problem at
actual trouble on line №53... After getting path trough
cmp.getExpressionHelper() it r...
I know that to upgrade to AEM 6.4 or 6.5 you need to do a lot of
restructuring to get things out of /etc. Does AEM 6.3 support those
restructuring changes? As in, if, on my custom code, I start making the
restructuring changes needed for 6.4/6.5, moving things around and
changing the references in code, but still run 6.3, will things keep
working or will things start breaking?
Hello,We are running AEM 6.3. We just migrated from Classic UI to Touch,
but we still have Classic UI users. We were planning on upgrading to 6.4
this year, and then 6.5 came out. Which path would be better - upgrading
straight to 6.5, or upgrading to 6.4 first and then upgrading to 6.5? Or
doesn't it really matter, because it will probably involve the same
amount of work? Thank you.
Much to my chagrin, the problem was indeed due to custom code. We had
some code someplace else that was creating predefined table styles, and
this custom class was extending CUI.rte.commands.Table extend:
CUI.rte.commands.Table,The fix was to instead extend
CUI.rte.commands.CUITable,Thank you, all who looked into this.
Thank you very much for looking into it. We are using 126.96.36.199. We will
see about upgrading the service packs. We're using desktop, not mobile.
And I just found out today that it there may be some interference from
custom code I wasn't aware of. I will look into that and let you know.
Thanks Gaurav. This actually isn't my exact use case. It's a simplified,
non-business-specific version, using the we-retail text component to
make it easier to reproduce the issue. Our actual use case is a custom
component from Classic that was brought over to Touch, with Touch
dialogs then added to the component. But the example I gave highlights
the exact problem without all the extra baggage.
I wanted to expand the default text component from we-retail by adding
the table functions in the rich text editor. I already had a
"cq:editConfig" that put the table RTE plugin into the Edit dialog, but
because I like the Configure popup interface better, I wanted to be able
to do it from the Config icon as well. So I added a "cq:dialog" with
this node structure:
While this added the Configure button with
a rich text editor dialog with the table icon, not all the ...
I am using AEM 6.3, Touch UI. I wanted to expand the default text
component from we-retail by adding the RTE table plugin into the rich
text editor. So I added a "cq:editConfig" with this node structure:
Now I can click the table icon and create
and manipulate tables. If I want those changes, I hit the next checkmark
and save and close it up. But if I want to discard my changes, I hit X
to just close.If I just close, the next time I open up that component
instance, the tables icon...
Thank you for the advice - I appreciate the replies.Even though those
options didn't fix it, I have figured it out. It's not about recompiling
the jsp or java. It's on the thumbnail.png node. After the thumbnail.png
is uploaded and used in the UI, AEM automatically generates different
sized thumbnails, stored in
thumbnail.png/jcr:content/dam:thumbnails.Even though the parent
thumbnail.png is updated, these are remaining the same. The way to clear
them out is to go into crx/de and delete the dam:...
We are using 6.3. We were using Classic UI, and we are making the
transition to Touch UI.One of our static templates uses a thumbnail
file. In Touch UI, on the sites.html page to select content
(http://localhost:4502/sites.html/content), all the pages using that
template automatically show up with that template's thumbnail. We
changed the thumbnail.png file for that template. The change is
reflected with the content creation, when selecting the template, but
all the pages using that template sti...
Is there a way to prevent certain templates from showing up while in
Touch UI, yet remain available while in the Classic UI? We have been
working on moving from classic to touch. We have only enabled some of
our templates to work in Touch UI. Some of them will remain only
workable in Classic, so we do not want them to show up in Touch.Thank
Hello,I am using AEM 6.3. I am trying to understand the relationship
between template policies (i.e. policy_123456) and the configuration
stored in etc/design//.content.xml.In
[template]/policies, you can store mappings
(sling:resourceType="wcm/core/components/policies/mapping") which sets
the cq:policy value.* They map to policy_xxxxx nodes
(sling:resourceType="wcm/core/components/policy/policy"), often (if not
always) stored in /apps/settings/wcm/policies. And those policies store
things like ...
Thank you Gaurav for the information you provided. Although I ended up
going a different route, I appreciate you taking the time.What I ended
up doing was overlaying
/libs/cq/gui/components/common/wcm/clientlibs/wcm/js/copy.js , and
within the .cq-wcm-paste-activator onClick function, the naming page
service gets called and put into a new destName parameter. That is put
in with the outputData array ( outputData.destName = newPageId;) before
outputData is pushed into outputParams (outputParams.pu...
Our project is moving from Classic to Touch (AEM 6.3). Our content uses
a custom service (generating a numeric string) for naming pages (i.e.
"12345"). For page creation, the default pagename field has been
replaced via overlay to have a hidden input field that is automatically
populated by the service. The problem comes with copying/pasting pages.
By default, when pasting the page, the /bin/wcmcommand call in AEM
appends the parent page name with a number (i.e. "123451"). We want it
to instead ...
I'm still trying to process and understand what Gaurav put in there.
I've tried adding and configuring 'cq:deviceGroups' property on my root
page's jcr:content, but that did not seem to change anything. The rest
is still new to me, so I'll keep trying to figure it out.So you
understand, I'm working with content/legacy page rendering components
that started with Classic and recently moved to Touch that were all
static template pages. My end-goal is to see if there's any way to
change those static...
Thanks Prashanth (and Peter and Scott). Adding that client library did
the trick.Now that I know the answer, I found places where it even says
No, this is not about editing a page by another author. This is about
the fact that after the static is locked, if I, the admin and owner of
the page, go into that page to edit it, I am unable to edit it or unlock
it or preview it, because the global bar functions no longer work. When
TypeError: Cannot read property 'shared' of undefined" from core.js at
AEM 6.3, Touch UI. I have a simple template and page component,
described in detail at Layout Mode Not Showing Up. When a page using
error:Once this error occurs, the globalbar buttons, like Edit, Preview,
Unlock, and Page Information are all non-functional. I have seen it
happen with other templates too, sometimes with the same error happening
in page.jsIn this particular example, the page template component looks
I'm using AEM 6.3. I have static templates that were using parsys
(foundation/components/parsys) and now I'm trying to switch to layout
(wcm/foundation/components/responsivegrid). I've tried following the
instructions in Configuring Layout Container and Layout Mode, but it is
still not working.Here is a simplified version of my setup:I've got a
template in /apps/matt/templates/mattplate It's sling:resourceType is
In the end, what I ended up doing is grouping the , the
coral-anchorbutton link the show dialog, and the in a div
with an id. Then I put a .on('coral-overlay:close') listener on the
element to move the dialog box back into the group so it
is back within the form when it the dialog closed.Here is the revised
componentProps = null;String pagePath =