cq5 permissions problems viewing content on publish -
i'm having interesting problem w/ content appearing on publish instance. let me run down situation , see if can help.
- i have author , publish instance set up.
- authors have , still replicate items author publish no issue.
- all of code base has been migrated over, jars fine -- rebuilt individual jars in publish instance crx make sure.
------- issue.
i went publish new page , did not show on publish instance. it's not new template or component type, page add list. these actions took , found. have 2 publish instances set up, refer them synonymously "publish" since states appear identical.
activated publish -- did not show in publish
logged publish/crx/de/index.jsp make sure replicated properly.
the content did make fine , in proper path in /content
the acl , access control permissions same other content nodes of same type. (just note, content nodes viewable).
no stacktrace errors in logs. however, when going through dispatcher error: org.apache.sling.servlets.get.impl.defaultgetservlet no renderer extension js, cannot render resource jcrnoderesource, type=xxx, supertype=null, path=/content/xxx/jcr:content
i went ahead , logged in admin in publish/crx/de , hit content page in question , looked fine. means content available administrators not anonymous users.
edit: made sure check anonymous context in 3 instances -- both publish instances directly , through dispatcher.
from here figured had issue w/ access control, new node has identical permissions nodes available anonymous user context.
to check if matter of replication, went , deactivated of other similar nodes, saw disappeared, reactived them , saw them come back. following train of thought deactived group (old nodes + new node) , reactived them -- old nodes showed up, , still same permissions issues w/ new node.
is access control available anywhere else? i'm curious if there other places me @ in order figure out what's wrong piece of content.
thank you, brodie
you can set "read" permissions group "everyone". ultimately, want put dispatcher in front of publishers, , prevent public access publish instances directly (preferably sitting behind vpn).
this means dispatcher denying access /apps anyway, , instances still secure, , acl publisher won't matter long anonymous user can render page under /content
Comments
Post a Comment