I have an issue where at a specific path the sidekick items are disabled and I can't edit components on those pages. I'm logged in as admin and from the siteadmin I can't delete or move pages. If I go a node level lower or switch websites I have all of these permissions.
All if the items in the sidekick are visible but are greyed out. I can't see page properties when I'm on the siteadmin page either.
After reviewing the javascript console I see this happening:
charset=utf-8&cq_ck=1389020093589">http://testsetver.com:4502/home/users/a/admin.permissions.json?path=%2Fcontent%2Fwebsite&charset=utf-8&cq_ck=1389020093589 404 (Not Found) widgets.min.js:19516
I've seen similar behaviour when we had content moved via a package and it ended up creating a page without an associated jcr:content node. This doesn't have to be on the page that you are having problems with, it could be a sibling page. I would check the integrity of the pages under that website.
Related
I have a single page which I built from the same blocks as other pages in the same category, which do work. This page redirects to the 404 page.
I checked to make sure the page was published- it is.
I am able to preview the page in the Experience area and it looks good.
From what I can tell, no other 301s have been set up to override this.
What else can I check?
Try Checking your log files. There are additional information about what is happening.
There were dependencies that were on the page that no longer existed. Apparently, whoever cloned the page used an older (previously working) page, which no longer worked.
The specific element in question was an object reference to an image in a gallery.
We removed the element in the editor, published the page, and it worked great.
I am new to TYPO3 and have a big problem. I deleted the page with the id 1 (startpage, I know its stupid) and now I woudl like to know if it is possible to restore the page somehow.
Install extension Recycler, it ships with TYPO3 by default. You can then restore pages and content you deleted using the backend UI it has.
https://docs.typo3.org/typo3cms/extensions/recycler/Introduction/Index.html
You can use the recycler that is found under the web module and click on a page in the page tree at a higher level than the deleted page. You can also set the depth to infinitive if not certain where the page used to be in the page tree. Then put a tick beside the page you want to restore and click undelete. Note that PID is 'Parent ID' (not Page ID), and UID is the ID of the deleted page.If you click on the little + you will get additional information, e.g. the original path to the deleted page. If part of the path is highlighted in red, then that indicates another deleted branch or page. Remember to leave the Recycler module with 'Depth' NOT set to 'Infinite' (leave it at 'This page' or '1-4 levels') otherwise the recycler will hang if you use it on a larger part of your page t ree. Hope this will help you.
In the AEM page trying to add a new tab for the page properties dialog. The new added elements are showing and those are working fine when I logged in as a administrator, but when I logged in a authoring user, in the page properties the newly added tab is showing as empty. Tried all other alternatives and checked the permissions too. Any help on this is really appreciated.
Give Read permission to content-authors group for etc/cloudservices, it will resolve this issue.
I am using a template "home-template" for two pages.
First page is root page called "CompanyABC"
root page child page is "english"
"english" child page is "home"
"CompanyABC" and "home" pages created using same template "home-template"
"home" page is working as expected.
But "CompanyABC" page is having following errors in browser console and page is not working as expected ( All parsys and included components divs have "display : none" )
Following is the error in browser console
I really appreciate if anyone could shed some light on this, If I create any new root page, or immediate child page with the ANY template the issue is reproduced.
A corrupt/missing jcr:content node somewhere in your page hierarchy could cause this issue. See CQ5 sidekick elements disabled.
I recommend using Content Explorer as an admin and looking at each node in your /content directory all the way down to the pages where you see issues to make sure each one has the jcr:content node it should.
We have implemented login functionality like geometrixx site in our existing website(with close to 700+ pages).
We want to show protected pages only to logged in user, every user who is registered gets assigned a group/ CUG lets say "listed users".
now in page hierarchy I have products page and under product page I have 8 products pages.somewhere On homepage I have a nav bar component which fetches all product children pages and shows a left nav bar with 8 entries.
If I enable CUG in a way that only "listed users" should have access to 2 out of 8 product pages, any access to direct links are redirected to login page. Which is fine.
But the nav bar component which earlier used to show all 8 product pages now shows only 6 pages.
The main idea behind putting pages behind login is lead generation.So if non logged in users dont see the link itself where would they click to get redirected to login page and subsequently feel like registering with our site.
Requirement is that my existing nav bar should continue showing 8 links and on click of 2 protected page links, he should get login/ register option.
We are using most of things Out of the Box.
any pointers helping in how do we achieve this would be great help ? PS: i have given a nav bar as one such component affected in existing site like this there could be many more components fetching their content from site hierarchy and stand chance to get broken in such case.
There are two entities involved, JCR and Sling.By default any un-authenticated request is associated with a user called Anonymous, the JCR sessions will have ACL's associated with anonymous.
In JCR, if a user does not have access to nodes, that session will not see those nodes.We access the JCR via Sling ,by default if you don't have permission the request will result in a 404 error(because for underlying JCR session the resource does not exist). Sling can be explicitly instructed to request for authentication for specific paths.
The combination of these concepts are leveraged to create the CUG functionality. Sling is instructed to force for authentication for CUG enabled pages. The JCR is instructed to show these nodes only for users who have access.
When you directly request the product pages without login, it is sling that is redirecting you to login page. When your navigation component is looping over nodes to create the menu for anonymous users JCR is only showing it 6 pages as the other two are out of reach for anonymous.
The only* way to work around this is to make the Navigation component configurable. Instead of node iteration, the content author will have to configure the the url and page title so that the links show up for everyone.
You can ignore the session associated with the request and use a custom JCR session that has access to all the product pages, but that would be disregarding the ACLs and you don't want to do that .
The nav bar can pick up all child pages as per page structure. That should not restrict the page title display on the nav bar.
As for the pages the access can be controlled by template level page properties by adding the 'listed users' group over there. In the jsp you can give an initial check for the user if they are a member of 'listed users' else redirect to login page
Hope that helps
Thanks for all your suggestions
Below is how we ended up doing it.
- Protect the page you want to enable CUG with proper CUG.
- Hide the page in nav.
- Create a redirect page in same hierarchy with same title as the one you wanted to protect.redirect it to your protected page.