Suppose we have a page and it has header and footer links. For which we can edit the value using the header/footer dialogs of the components. Now, I want to check that who all have updated those links in any specific environment. How can I check that?
From the page properties, it just shows who made the last update (cq:lastModifiedBy property), but I need the specific versions/history of the page.
Do you want to check this in AEM or in your Code?
The sitekick provides a list with versions that have been created. See the official documentation.
If you want to load versions in AEM, please have a look at this (older) Blog post which describes how to use the VersionManger to work with Versions.
Versions are stored in /jcr:system/jcr:versionStorage within a node named by the first letters of the UUID assigned to a page (jcr:uuid)
Related
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 2 years ago.
Improve this question
I'm using AEM,and meet a problem.
Firsly follow these steps
Secondly the page is below:
I create the page based on the Summit Toys Base Content Page template.
step1
but click next button ,the page shows like below:
step2
why and how to solve this issue.
Thanks advance!
This should be your problem. From your reference application, You have created a template under:
--apps
-- summit_toys
-- templates
and then the corresponding page rendering component under
--apps
-- summit_toys
--components
--structure
I am 90% sure, your page rendering component /apps/summit_toys/components/structure/contentpage is missing property sling:resourceSuperType = wcm/foundation/components/page. This brings the page properties dialog on the create page wizard. Check for spelling and case sensitive to exactly match above.
Other possibilities:
Make sure template sling:resourceType points to relative path of page rendering component (like summit_toys/components/structure/contentpage)
Check for typo, spelling errors. JCR standard prefers to keep all nodes in lower case (for good reason). Make sure your nodes are lower case; hyphenated if required.
Issue should get resolved with sling:resourceSuperType = wcm/foundation/components/page. If still fails, you might need to share /apps package to check further.
which version of aem you are using.
if it is 6.3, after creating your page, check if your page is there or not under content node in CRX
If it is there the check resource type is correctly mapped accordingly or not.
Hope this helps
I faced the same issue and is resolved
check this image
issue is related to value of cq:allowedTemplate for /content/wetrain/jcr:content
This issue can occur if you have not created dialog(cq:dialog) for your page component. Either you can create cq:dialog/ or extend out of the box page component using property sling:resourceSuperType as mentioned by Dhiraj Khursade.
If you are using editable templates, check for sling:resourceType property under /conf/<project>/settings/wcm/templates/<template-name>/structure/jcr:content and /conf/<project>/settings/wcm/templates/<template-name>/initial/jcr:content both should point to correct page component <project>/components/structure/<page-component>
Also make sure that, page component has correct value for sling:resourceSuperType with valid page component from core components or wcm core component. Try creating fresh new page and validate instead of trying on existing page.
We have a site which sometimes delivers a wrong content for a specific URL.
The page has a plugin and by default should show the records listing (or the first record listing as the listing is grouped by initial letter). After clicking a link some records are viewable in detail on the same page.
Every now and then a cache problem occurs:
Instead of the listing a detailed record is shown.
Although we use realurl, all problems occur also with the basic urls.
For overview I will only write the url-parameters, assume www.domain.tld/index.php? in front.
The page to call is id=61.
What I see is
cHash=3df3421afc42d3d5bfa1bc50603ea00d&id=61&tx_citkoegovservicelight_ansprechpartner%5Baction%5D=show&tx_citkoegovservicelight_ansprechpartner%5Bansprechpartner%5D=282.
In the HTML-source of the page I show the page calling parameters with the extension page_params. Here I see:
tx_citkoegovservicelight_ansprechpartner[action]=show&tx_citkoegovservicelight_ansprechpartner[ansprechpartner]=282&tx_citkoegovservicelight_ansprechpartner[letter]=kontakt&id=61
Two strange notes: there is no cHash parameter, there is an additional parameter tx_citkoegovservicelight_ansprechpartner[letter] which never should be used with detail view and never should have the value kontakt (only single characters were used for the listing of all records starting with that letter = no detail view)
Using these parameters does not show the detail-view but the the list view (for letter 'A').
I do not find a reason why this special URL should be called (no link) and I don't know why TYPO3 should cache a content which belongs to another URL.
And it is a problem with TYPO3 cache as all works correct if I clear the cache of this single page.
Please check my answer to another issue. The accepted answer is right in that case, but in your case it can really be caused by failed cHash calculation, because it is not related to RealURL.
Try to clear the cache and then right after that go to tx_citkoegovservicelight_ansprechpartner[action]=show&tx_citkoegovservicelight_ansprechpartner[ansprechpartner]=282&tx_citkoegovservicelight_ansprechpartner[letter]=kontakt&id=61.
And then simply open the page id=61. If you see the wrong cached result, then the reason is in a combination of following factors:
Plugin's action is cached
Cache fails are allowed in installation
cHash calculation failed
To prevent this you should enable pageNotFoundOnCHashError in Install Tool. Then the problematic link above will just trigger 404 and will not force TYPO3 to render the page.
To a question where the link is coming from. If the website is already live, it can be everything: from a crawler, which somehow builded the link itself to a user who tried to play with parameters.
When I create a live copy of a blueprint website, and rollout pages using standard rollout config, links in the pages are updated to reflect the live copy version.
ex. /content/myblueprintwebsite/home.html -> /content/mylivecopywebsite/home.html
But when those paths are buried inside properties of the page content nodes, they are not updated, and still points to the blueprint pages.
... is this the intended behavior? If so I guess I would have to write my own rollout config? Or is there another solution to this problem?
Thanks for your answers.
As per: https://docs.adobe.com/docs/en/aem/6-1/administer/sites/msm/msm-livecopy.html
"
When the blueprint source contains links and references that target a paragraph in a different chapter, the targets are not updated in the live copy pages. For example, a live copy is created from the Geometrixx Demo Site blueprint. Links in the Toolbar chapter that target the Services chapter are not updated in the live copy, and continue to target the original pages in the Geometrixx Demo Site.
"
My interpretation of the above:
- If the link to the target is created on a page that is in the ancestral line, the change will reflect in live copies.
I tested this by configuring a link to bp/en/parent/child-page on the bp/en/parent page and also on the bp/en page.
In both cases, the corresponding live-copy/... pages reflect changed paths to the live copy specific child page.
Moreover, the change is happening for links no matter what widget is used - OotB List, a customized link widget, or hyperlink configured in the text widget.
Further question:
Editors may want to create links from pages that is not in the ancestor line. What then? Is there a configuration that can be set to allow the change to happen ? Or are we required to write custom rollout action?
When ever a page rollout is done it updates all the individual content references for ex:
paths in property nodes, if it is stored individually i.e., not concatenated with any other text like: hello /content/test/master/en.
It doesnt update if the path is in the mid of other text.
And
Creating custom roll out doesn't server your purpose.If u really want to create custom roll out to meet this requirement then you have to create following custom live actions and write logic to find paths and then modify them.
1.ContentCopyActionFactoryCustom
2.ContentDeleteActionFactoryCustom
3.ContentUpdateActionFactoryCustom
Creating custom roll out is a risky option as roll out is called from many places like while creating live copy,from blue print section , roll outing a page and its sub pages and background execution etc.,We have to handle any exception caused in this explicitly.If u start changing one file then u end up changing all related files has roll out implementation on many java classes.
Ideal Solution : Save all the paths in a individual property and AEM will take care of updating there references
Cheers !!
Is there any existing way to generate a what-links-here report for a gollum wiki? In other words, a list of the pages within the same wiki that link to the current page: a list of the local inbound links.
I wasn't able to spot any feature like this, nor find anything suitable in the API, but I may have missed it. Is there a third party add-on for it?
I do understand the reason it probably doesn't exist in the core: as these are plain text files, there isn't any table of links maintained anywhere. For the same reason, when a page is renamed it breaks all the inbound links to that page from other pages.
A function for this could use the API to read the generated source of each page (so that only html with normalized names needs to be parsed), producing a list of the local links from each page and the page they are on. Cache the results at page level until the next commit of that page.
This could be used to enhance the existing page rename feature as well. Has anybody already done this?
I am wondering what the function is of the Publish field of items in Sitecore. Just to be sure I am clear about what field I am talking about it's the field in the "Publishing" section of an item which is only shown when you check the "Standard fields" option.
Normally that field is not filled in and I expected it to be filled automatically by Sitecore when an item is published due to it's publishing restrictions settings but I am no longer sure about this.
Regards,
David
The Publish field of Publishing section contains a date and time for an item to be published from. If you do not specify anything here, the item is publishable by default. These changes are applied to the whole item (the field is shared). If you'd like to change this for different versions, use the LifeTime section instead.
I would encourage you to get acquainted with Content Cookbook for more details.
If I remember correctly, these fields can be used to properties of the publishment. For example, the date range when your page should be online.
If not, please give me a list of fields that are available.