I have created a user group that specifically has access to three asset folders in the AEM DAM. These users have read/modify/create/delete permissions, yet they cannot add metadata tags to an assets detail page.
Any suggestions? Is there a step I am missing?
The metadata fields do not even render on the asset detail page for this user group. As an admin, I can see the metadata list field populating. I believe I am missing a permissions box. I have read documentation that says that read/modify access to the folder should be enough, but this is not working.
Application AEM 6.3: DAM
The user group must have read access to /conf/global/settings/dam/adminui-extension/metadataschema since the metadata fields are rendered from the above path.
Related
Whenever I am creating a site following the steps in SFCC infocentre I am getting two sites with name as RefArch and RefArchGlobal but I want my site with my id and my name, I was able to do that by creating a custom site and then assigning the same catalog as RefArch and also the same content libraries as RefArch and then by importing the slot config of Refarch to my custom site, I want to know if there is any other way of doing it easily.
Thanks,
Faizen
You can pull on your local -> Storefront Reference Architecture Data. This is a repository for the RefArch site data that goes with Storefront Reference Architecture (SFRA). After:
Clean up the demo_data_sfra folder by removing what you don't need. An example is all related to RefArchShared site if you need just
RefArch
Replace in the XML files RefArch with your site ID
Rename folder names in the sites with proper site names.
Rename catalogs and make a proper link between them.
Cross check all files to see if there are other references. For example, in the jobs.xml you might have a site context and you need to use a proper site ID there.
After all those steps, archive and import the site to your sandbox. Run reindex and clean cache and check storefront. It should work.
I need for certain users to only be able to create pages in certain categories based on their permissions. One reason for this is approvals ("flagged revisions"). If a user can create content outside of any category, then it could show up live on the web site. Even thought it wouldn't initially be linked anywhere directly in an existing page (except other unapproved pages) this can still be a problem.
I can prevent the user from creating a new page in the global scope (apparently this corresponds simply to "edit" permissions as I don't see a special permission for creating new pages), and then I can grant them permission to edit pages in the category their group is authorized to edit. But I can no longer see the "Menu:Wiki:Create a Wiki Page" option, and I can't figure out how to allow the user to create a new page in that category.
I can edit the group and set the "Default category assigned to uncategorized objects edited by a user with this default group" to the desired category. When I do that, a user in that group now has a "Create a Wiki Page" option show up in the Menu:Wiki sub-menu, but clicking on that does not bring up a new page for editing; instead if just brings up a list of existing wiki pages, without the option to create a new one!
If I create a link to the new page from an existing page, I am unable to edit it in any way. Clicking the link takes me to a page which indicates that the page does not exist, but which does not provide any way to edit it. Putting the title of the page directly in the URL, as in tiki-editpage.php?page=New+Page+Name brings up a "You do not have permission to edit this page" error page. Since any new page created by the user should have the category they have permission to edit, this does not make sense unless the category isn't set until after the initial edit permission check occurs, which creates a catch-22!
How do I let the user create a new page in any of the categories they have permissions to edit in?
If Categories are not the best tool for the task that's okay too. I don't really understand the difference between Categories and Structures with regards to which is better for what I'm trying to accomplish, however it seems Categories are the more "native" feature, which is why I am trying to use them.
I need to restrict the template to be available only for a set of user. The template should not be available for other users while creating new page. How can I do that in CQ5?
First, read this documentation page. After that create an group containing all users which should be able to create a page using the template. Then add following ACLs to the template node (eg. /apps/myapp/templates/mytemplate):
deny jcr:all for everyone
allow jcr:read for (created group)
When I click on tag in tag clouds web part, I have a tag profile page (mysite.domain.com/tagprofile.aspx?termid=9e183a42-9603-43ea-8e9c-173e62dbe34c) which is empty.
How can I see the data in a tag profile?
UPD: If I click a search tag link, I have query like
SocialTagId:"9e183a42-9603-43ea-8e9c-173e62dbe34c", but no data in result.
I found how to search for tagid, if write in search box query: owstaxIdTaxKeyword:"9e183a42-9603-43ea-8e9c-173e62dbe34c", we have all documents with this tagid.
But how to get result on TagProfile page?
The Tag Cloud in SharePoint leverages social tags, not just any enterprise keyword. Though most tags are pulled from the Managed Metadata Service, social tags are stored alongside the User Profile Service Social Database.
You need to make sure that the library you are tagging documents have social tagging enabled. You do this by going to the Library Settings > Enterprise Metadata and Keywords Settings. Within there, you will be able to enable Save metadata on this list as social tags:
Then, make sure you are using the Tags & Notes board to ensure that your documents are tagged appropriately.
Finally, make sure that you Search Service application is actually crawling. If you have only performed an initial crawl, setup a crawl schedule or switch to using Continuous Crawling.
How do I hide the content resource field from non-admin users?
So you'd like a user to be able to change document fields such as title, alias etc but not the content?
You can not lock individual fields to admin user (as far as I know). You can either lock the whole page/resource or you could put the content that you want to be locked into the template for that document and lock the template to only the admin user which would achieve the same effect.
Make sure you don't have a reference to [+content+] in the template and even if the user enters document content it won't impact the page.
New answer instead of editing the above as this is a much cleaner solution.
Create different user groups eg. Admin & Editor
Make sure admin is in the admin user group
Create a template variable for your content and in the Access Permissions section only tick the admin group.
Assign the TV to your template.
Now if the user isn't in the admin user group the TV won't even be visible when they are editing the resource.
Hey, thanks for the answer.
I thought I'd post what I ended up doing.
With MODx Evo 1+, you have managermanager included. After removing the included file(which is used rather than the default chunk) using the rules in there I can rename hide and sync content.