Like in the example, I have created a .js file that lives in the
component folder. It works on my localhost:4502, but when I open the
page at localhost:4503, nothing from the component shows up. Here are
the component files:/[my
I'm not sure this is the right answer. I want a group that can edit all
of the pages, and a group that can edit all of the pages under that
parent, but not the parent. Your solution would create a group that can
only edit the parent. Am I missing something?
I'd like to restrict editing on the top page of our site, as well as a
few key child pages, while at the same time allowing users to edit pages
beneath these key pages.For example:example.com/homepage is our parent
page that we want to restrict access to.example.com/homepage/topic1 is a
child page that anyone can edit as necessary. Because of cascading
permissions, if I deny access to /homepage, then I'm denying access to
all child pages.I can, of course, deny access to /homepage, and then
We have a unique situation where our AEM content is reverse proxied into
an HTML container. This outer container holds the tags for the
page, as well as all the CSS and JS calls for the site. While authoring
in AEM, I want to be able to use one of the CSS files to help authors
see the final styling. I have a solution that is 90% of the way there,
however, it fails when an author chooses the "View as published" option.
I'm using this conditional statement: This works for editing and
the preview ...
Hello again, @Nupur_Jain, thanks for your original reply. It helped me
greatly. Now, however, I've run into a new situation: I want to be able
to have the clientlib available in AEM's "View as Published" mode, which
appends "wcmmode=disabled" to the end of the authoring URL. I thought I
could test for "wcmmode.disabled = 'true'" but it turns out that when
you publish the page, the value for wcmmode.disabled is also true, and
so the clientlib is getting included and published along with the page....
From time to time, I get requests for a list of authors in AEM who
belong to a specific permissions group. We don't yet have an integrated
sign-on solution set up (which would allow us to tie internal teams to
permission groups), so I'm stuck manually assembling these lists. I know
AEM has always been more page-oriented, but I'm wondering if there's a
tool that I'm unaware of that would let me export an author list.
Hi Anudeep, thank you for this suggestion. I agree it seems simpler to
hide the items rather than try to remove them from the DOM. I do have a
question around the clientlib: I have an existing clientlibs folder,
with a "clientlib-authoring" folder under that. I'd like to place this
new clientlib there, but does that mean creating a folder inside
"clientlib-authoring" with a name like "linktargetfix" (for example) and
the creating the .content.xml file, js, and txt files there? The
I've been asked to modify the Link dialog in AEM's rich text editor to
remove unneeded target options like "parent frame" and "top frame." I
found this method of removing items, but it's giving me an "undefined"
error when I try to use it. I've searched for any information on
possibly modifying this in the component dialog's .content.xml file, but
there doesn't seem to be anything out there. In other components, we
just have a simple URL input field along with a checkbox for "open in a
Ultimately, all I needed to do was create a data-attribute on the
richtext node that I could target with authoring-specific CSS. The
answers below all point to that, but I think maybe went in a direction
that was too complex for what I was trying to do.
I'd like to use the RTE for a title component, which generally implies a
limited number of characters. Titles rarely exceed more than a few
words, and having the full RTE box might suggest to our authors that
they can insert longer than normal titles. I don't think we're at the
point of limiting characters through validation. We just want a visual
reinforcement of the idea that titles should be kept short.
Unfortunately, I don't think we have dialog markdown that I can modify.
I've only ever built the dialog using nodes/XML. I'm assuming that maybe
I can add a custom data variable that can be used for targeting by CSS.
A designer on our team is asking us to modify our Title component to
allow the use of bold formatting on part or all of the title. Bolding
the whole thing would be easy enough, but it's the partial bolding of
text that I can't figure out. I've tried switching the field to richtext
and then eliminating all plugins except the bold formatting. But the
problem there is that now I have a huge text entry box and I can't
figure out how to make it one line. I'm wondering if there's a different
TL;DR - I'm trying to apply a clientlib to the page content in
editor.html without it being included in the published content. AEM has
a clientlib for FontAwesome here:
is included in editor.html, but because the content of the page is
actually in an iframe, the font-awesome styles don't apply to any of the
components. I'm trying to figure out how I can either 1) use the
existing CSS call to apply to the contents in the ifr...