Is it possible to set default page properties value in CQ5 when you created a page? Either by specifying it in templates, component, etc...
Found it, just need to add the attributes directly under
templates//_jcr_content
Related
Kentico 12, not MVC:
I have a page template that is used on several pages. On some of those pages I want to display a form. (a biz form from the Forms application) I don't necessarily want the same form on each of those pages. I need a way to specify which form to display. I expect I could create a field in the page type to specify the form name, but it would be nicer to be able to have designers add a page with the form on it, and have a repeater display that page in a webpartzone on the aforementioned page template. I'm not sure how to do this, though. Anyone have an example or suggestions?
If you’re using portal engine, then you should easily be able to add an editor zone to your template. Content editors can then add the online form widget to individual pages. The widgets work at page level rather than template level, so should give the control you
The page from the docs will show how to setup an editor zone:
https://docs.kentico.com/k12/developing-websites/preparing-widgets-for-users/setting-up-widget-zones-on-pages
In addition to adding a widget zone, you can simply add an editable text webpart to the template and in the WYSIWYG editor you can click on the BizForm icon to insert that widget there. This doesn't require you to change the page template to a widget zone template.
when I add a custom attribute to a user, I can access this programmatically in my client application using custom mappers. But when a user logs into its account settings (URL /auth/realms//account/), he or she does not see or update this attribute. Only the required ones first and last name and email are visible.
How can I make a custom attribute visible and updateable on the account page?
You have to create custom theme and override account.ftl template to add custom attributes.
Read through Theme Creation, it's really easy to create custom theme.
I need to change and customize the login page, implementing the
"IviewService"
isn't not good enough, i need the full layout.
any idea ?
Implementing a custom IViewService is exactly how you change the full layout.
However, if you want to change only the login page, you can do so by adding your own html that implements the same angular logic as the existing login page and adding it to a folder named templates with a file name of _login.html.
If you want to modify the layout (the headers) then you need to do the same this time naming the file _Layout.html.
This is all detailed in the documentation, with the above listed as "Replacing partial views".
I have created menu component, through which authors enter name, url field values.The component script renders the menu based on name, url entries.
Question : how to make this menu component common across all CQ5 pages, so it is not drag and dropped on each page.
Thank you,
Sri
ACS AEM Commons now supports this functionality without use of an iparsys - Shared Component Properties (http://adobe-consulting-services.github.io/acs-aem-commons/features/shared-component-properties.html)
Configure your menu with Shared and/or Global properties and you can simply template it directly onto all of your pages (no iparsys required). You can then edit the menu from any page on the site and it will by updated on all pages.
I have a Liferay site. I have several pages that needs to be tagged so I can get them in a custom portlet.
I also need to present a page with an alphabetic index of the tagged pages.
I have read documentation and I have seen that Liferay can put a tag or a category only on "assets" (web content, etc.) and not on a page/layout.
Can you suggest me a way to do it?
You are right about tag/category, these can't be applyed to layout (unfortunately).
The best alternative is to use custom attribute and define the extra fields for the page.
See this image
You can read the custom attribute for the page using ExpandoBridge API.
Here an example to read an extra attribute within the theme velocity template.
#set ($customField= $layout.getExpandoBridge().getAttribute("CustomFieldKey"))
Note: Remember to set the permissions on each custom attribute. It's very important!