Hey folks-We're trying to limit the filesize of assets uploaded into the
DAM.I saw this Managing Video Assets about raising the limit... but
we're trying to lower the limit. So far - I've tried the instructions in
the article, without any luck. Any ideas?Below is what I've done (this
should limit uploads to 200 bytes as I understand, but no dice)... Note
that I'm trying this on AEM 6.4.3 on my local machine.
gauravb10066713 - we just fired up a fresh copy of 6.4.0 and
tab.click.js looks like it does in our 6.4.2 version - I'm pretty sure
that this won't work with CoralUI3 without the way the one you have
looks...
gauravb10066713 - I didn't apply a breakpoint, because it never gets
there as the binding action is different; it never binds to the tab with
the code we have. We're running 6.4.2; so I'm wondering if this isn't
fixed in 6.4.3...
gauravb10066713 - So my tab.click.js looks different... see below...
What version of AEM did you pull that from? It seems concerning that
it's different and it seems likely that this is the reason we're seeing
the issue we're seeing...Thanks!tab.click.js code: /** * Handler to
show/hide the MSM action buttons according to the selected tab. */
$(document).on("click",
".coral-TabPanel.cq-siteadmin-admin-properties-tabs >
.coral-TabPanel-navigation > .coral-TabPanel-tab", function(e) { var
$tabPan...
So - We're working on an AEM 6.4 upgrade project coming from AEM 6.2. I
did the work to upgrade our configurations and such to get everything
working and we've updated our dialogs to coral3, but it seems that now
when you switch to either the blueprint tab or the livecopy tab
(depending on the page) in the page properties for a given page, the
button in the upper left don't show up. By inspecting the DOM, I can see
they're there, but they never get unhidden. Looking at one of the
environments we...
Handling this on the front end is incorrect, IMHO because it'll cause a
shift in layout as the page loads. It's worthwhile to note that this is
mainly an issue in the author because we don't display the wrappers on
the publisher and on; so given that, I guess we could use JS to 'shim'
this for the author env - but given the author looks at the page DOM to
setup the areas for the authoring interface, I wonder if this will cause
issues...
So - we don't use Bootstrap; but that being said, most grid systems rely
on parents and children to define a containerThis is how most systems
work: = could be 100% width of the page This is a six column row = could be 50% width of the
row This is a three column row = could be 30%
width of the row This is a two column row =
could be 20% width of the row This is a one column
row = could be 10% width of the rowIn AEM, this looks
like: = could be 100% width of the grid-wrapper This is
a six colum...
Yeah - we have something very similar to that and the issue is that
modern responsive grid systems allow you to do things like reorder
columns at different breakpoints or change the size of columns at
breakpoints, ect... Our design folks are asking for a level of
flexibility we need to find a way to provide.So having fixed patterns
for columns isn't going to work for us; we're trying to create a
component that lets us define a 'row' component and then a 'column'
component - but wrappers create a...
Arun - yes; you can change the tag name, but I'm looking to change the
name of the classes. Also - as I understand it, if you remove the tag,
then the component becomes un-editable.
The problem with that is that if we hide the wrapper completely; then
the dialog doesn't work 😕Also - I've tried `.getOptions(getRequest(),
true).getCssClassNames().add("TEST_CELL");` for IncludeOptions and it
doesn't seem to work.
We're trying to implement a solution a bit more dynamic than this to
allow grids to be more freely authored. I think we'd still like to see
if there's a way to programmatically change the wrapper classes for a
component OR use a component's HTL to include another component that has
it's dialog as still being author-able.
Hey folks,I'm working on a custom grid building component. The problem
I'm having is that the wrapper div is negatively effecting my ability to
build columns (the columns set a width of the parent, but on the author
this looks weird, because the column's parent is actually the wrapper,
not the row element)I know I can remove the wrapper, but then the column
isn't editable, which won't work for me. I know I could use the
cq:htmlTag node to edit the tag, class and id - but because the size of
the ...
So It seems like I'm not doing a very good job of explaining this....
Let me try again:I've got an editable page with a tab nav on it. That
tab nav is not an AEM component. Those tabs in the tab nav do have AEM
components (they're used for configuration). On tab one, which is
active, I can see those AEM components and they're editable. However,
the author can't interact with the second tab to switch over to see the
second batch of components on that tab.We're looking for a way for the
author to ...
When you're in the authoring edit mode, it displays the content in an
iframe, and the authoring ui in a div with id="OverlayWrapper" - but
because that 'overlaywrapper' is 'above' in terms of z-index of the
whole content area, an author can't interact with the content behind it
to use the tabbed nav to switch between the various configuration
components we have.Simply put - we're looking for a way to either bubble
up something from the content level to allow it to be interactive (and
then refres...
Hey folks,There's alot on how to make components, but in this specific
example, we have a configuration page node that calls in configuration
components that the author needs to edit in the authoring mode. We
received an ask to reduce the screen clutter by introducing a way to
separate some of these configuration components; we have a tab nav ui
element we use on the public facing page nodes, but the problem I have
is that you can't interact with it because the authoring 'overlay'
paints over it...
Typically we're trying to load alot of our critical path first and
blocking things that aren't styled, but I've been looking into it and
maybe this is the route we want to go.The only thing that is concerning
is the JS that would be part of the component, rather than trying to
pull everything to the top of the head, Is there a way to defer the JS
load for particular components to the bottom of the body?
These answers confirmed what I suspected, so I'm trying something a bit
different where at the page level, I run a query against the children
JCR nodes looking for the component, then if I find it, I add the
clientlib on the template...Thoughts?
Hey folks,I haven't seen a way to do this, but is there a way to load
CSS/JS in your conditionally when a specific component is on
page?The use-case is that we have a component with quite a bit of CSS/JS
that is ONLY used on a given page or two, so rather than load that
CSS/JS everywhere, we only want to load it when that component is
on-page. I'm sure I could query the page I'm on and see if the component
is on page, but I was wondering if there's a more performant/built in
way to do this.Than...
