granite/ui/components/foundation/form/radiogroupgranite/ui/components/foundation/form/radioPutting a radio group / buttons in an existing component.The default worked fine for me with the above components ( they aren't coral)

Thanks Esteban,My Publisher ACLs are different as they are exposed to the outside word so I have spent a lot of time in the past correcting them using the security ACLs or useradmin permission grid, whereas the Author is protected by sign-in. I only have the above code problem in the lowest environm...

hi folks, I've a weird problem, only on one environment and only on the publisher server. If I try to view path ACLs permissions either by security.html or useradmin, the screen is blank.I see error messages in the console.Uncaught ReferenceError: tpl is not defined and Uncaught TypeError: CQ.Ext.ux...

Thanks Suresh, They seem to be able to use the .form. selector to break into the system.I don't know why that selector allows it.I don't know if blocking the .form. selector would break AEM forms if you had them(we don't)Once I block the .form. selector, they can't get at /etc/truststore anymore.I w...

 hi folks, Hackers told us that they can access various urls using a selector "form".We don't have AEM forms so I am just going to get rid of this selector like this,I assume this is o.k.? /0xxx { /type "deny" /url "*" /selectors 'form' } The hackers told us they could download a truststore file wit...

I found the problem. The Author had clicked on Authentication Requirement on their home page but we don't have that set up

Hi! I'm having exactly the same problem. Do you remember the solution ? tnx Fiona

The problem seems to occur when we are reusing old artifacts on Stage environment. There is a pipeline directive that you can use so that you stop the pipeline reusing old artifacts so I'm going to do this. Hopefully this will resolve my problems.

Thanks Santosh. I might proceed to deploying to Prod, but keep a backup file of the configs on Prod just in case, the same thing happens in that environment. At least I can recover then.

The filter for the aem.config...<timestamp> package has a mode=update and runs after the aem.apps one.You don't suppose the order of these could ever get mixed up?