Can we edit CMSNavigationNode from Component Editor in SmartEdit? - sap-commerce-cloud

SAP Commerce 1811
As per documentation, In SmartEdit, we can add, update, remove parent child navigation node via Navigation Management Tab only.
When we go to site, and start using the navigation node, we can only select it from tree structure.
For example, Account Navigation Component
In this component, We can only select the navigation node, there is no way we can add, update navigation node from here.
Is there any way to do so or there is only Navigation Management option available where we can manage all the things?

Check if the user has access to create items under the content catalog. You could try assigning cmsmanager usergroup to the user, and making sure cmsmanger has write access to the content catalog.
Also, SmartEdit is somewhat buggy. So, try to refresh the page after you make the changes.
See Assigning Users and Usergroups to Content Catalogs: https://help.sap.com/viewer/9d346683b0084da2938be8a285c0c27a/1905/en-US/d94aa34f24fe4613b0f0f2590f544ba7.html
xxx
UPDATE 7/10 21:18 UTC+8: In Hybris 1905.13, SmartEdit has an option to add a child or a sibling node.

Related

Liferay: Page to portlet mapping

I have a requirement in liferay portal to allow user to add some specific portlets on a particular page. Same can be done in 2 ways:
This will require some custom code to be plugged in add panel code
create a custom portlet which will be present on left hand
side of page and allows portlet to be added and dragged on page.
On add of portlet it checks if the page can have this portlet and accordingly remove it
The question I have is which of these 2 approaches shall be used, and how?
Note: I was unable to find much about this on google as well
I believe Liferay permission system is strong enough to express what you need.
The portlet list shown in "Add more portlets" menu can be customized through a Regular Role. See How to customize which portlets to show in “Add more portlets” menu for detailed info.
To restrict the options for a single page (or several pages), modify its permissions, so that only the new Regular Role is be able to update it.
Based on your comment to Tomáš Piňos's answer, my suggestion would be to create a custom portlet that uses Liferay's API and enables you to do just this: On the page where it's available, use it to enable/disable the portlets you'd like to be there by use of Liferay's API. You'll find quite a lot of sample when you're looking for the old sevencogs example (that sadly does not compile any more, but in general the API has only changed marginally). The most up to date resources with further links to the ancient code are these 2 blog articles.
About your third option (as you ask in the comments): Yes, it's possible: You can override Liferay's Services as well as react to model changes. This means that you could add your own check on updates. However, I'd feel it inappropriate to offer the option to add any portlet only to prohibit it whenever a user indeed uses the offered option. That's why I didn't include this option in my initial answer.

sitecore permission on the visibility of the Alias ribbon menu

I'm trying to find what is the permission security for allowing visibility of the Alias function in the Presentation tab ribbon.
For the user in question i've browsed to the core database, and under Access viewer, i'm looking that all the items under Applications/Content Editor have read-enabled permissions, specifically the item /sitecore/content/Applications/Content Editor/Ribbons/Strips/Presentation/Page Urls as well as /sitecore/content/Applications/Content Editor/Ribbons/Chunks/Page Urls are read-enabled
However, when login as this user there is no presentation tab.
I've tried resetting the cache and still nothing changes. I'm using sitecore 6.5.0
I think you are almost there, but you still need to give the user sufficient access to the /sitecore/system/Aliases item.
Create a new role(or use an existent one), for example sitecore\Sitecore Client Aliases. Use this role to add the following permissions.
Switch to the Core database and allow Read permission for the /sitecore/content/Applications/Content Editor/Ribbons/Chunks/Page Urls item and its descendants
Switch to the Master database and unprotect the /sitecore/system/Aliases item by using the Unprotect Item checkbox in the Configuration tab.
Allow Read, Write, Create permissions for the /sitecore/system/Aliases item and Read, Write, Create, Delete permissions for its descendants.
Protect the /sitecore/system/Aliases item back.
Add user to the sitecore\Sitecore Client Aliases role.
Found here: http://wiki.evident.nl/Sitecore%20alias%20role.ashx
The easiest way to enable the presentation tab is to use a sitecore standard role.
I'm not totaly sure but i asume it was sitecore\Sitecore Client Designing.
And as far as i know you have to use those standard roles to enable access to certain chunks.
Try using the Access Viewer for the user which doesn't see the Alias Tab. You can manually switch to the core database and then click on the different tabs with the specified user / role to see what causes this behavior. Most of the times you will find out that some role / restriction was set to a higher level item dat denies read rights.

How to remove My Pages and My Submissions from Liferay Control panel

I'm currently working on a Liferay project and want to get rid of the My Pages and My Submissions menu items on the right side so that users of my site do not bother with them. Tried looking for the jsp that renders the left side menu, but could manage to remove the item from there. Any ideas how to proceed? Thanks!!!
You could add the following lines to your portal-ext.properties (usually found in webapps/ROOT/WEB-INF/classes under tomcat):
#deactivate Personal Community with *private* pages
layout.user.private.layouts.enabled=false
#deactivate Personal Community with *public* pages
layout.user.public.layouts.enabled=false
#hide Personal Community from my places
my.places.show.community.private.sites.with.no.layouts=false
and restart the server.
Recently I had the same task assigned. Fortunately removing this items from the menu is quite straightforward since the control panel is nothing more than a special layout for displaying portlets that are deployed in the portal server. You can read my blog post here to check the simple steps on how to customize the Control Panel and My Account portlet.
http://liferay.bdedov.eu/2012/02/clean-up-control-panel-from-unnecessary.html
You probably rather want to limit the permissions to people. Don't give out global administration roles, but create your own roles, "Define Permissions" for them as you need them and leave out the permissions that you don't want to provide to your users - e.g. "access in control panel" or the general permission to add a page.
Otherwise you'll miss other ways to use the interface and still allow them to add pages through other means (e.g. "Manage/Page").
Edit: The easiest way to get rid of "My Submissions" is to undeploy the workflow plugin (kaleo-web) - of course you can only do this if you don't need workflow.

Update panel error in custom page when logging with a user other than the administrator

I made a custom page and added it to a MOSS 2007 site.
the custom page has an update panel and some ajax controls
when I'm logged in as an administrator with full control permissions, the page works fine.
but if another user with even Full control permission logs in and browse the page, an error appears:
The control with ID 'UpdatePanel2' requires a ScriptManager on the page. The ScriptManager must appear before any controls that need it.
where UpdatePanel2 id the id of the update panel in the page, and the strange thing is that the master page of the site has a script manager addded to it.
so what can be the reason of this ?
thanks
This is one of the Common Behaviour when you dont approve the changes of the MasterPage after chaning the master page through SharePoint designer. To resolve this problem make sure that you have approved the changes of the MasterPage you did. Usually admin has fullpermission to view the unapproved changes as well, while normal users dont.

SharePoint 2007 Publishing site with deep menu structure

I am a beginner in SharePoint and I need to create publishing site that will have multilevel menu. Requirement is that levels will not be fixed and that client should be able to add pages and customize menu.
If I am not mistaken pages can be created only in the first level under the site. I don't see something like folders concept. For the navigation purposes I can add heading and it will be shown as another level. If I need more levels I need to create sub sites.
Site
Page1
Page2
Heading
Page3
Is this correct?
Site
Page1
Page2
Sublevel_1
Page1_1
Sublevel_2
Page2_1
Sublevel_3
Page3_1
...
Can I do something like this without creating SharePoint sub sites ?
If I don't need I will skip writing some custom menu control or write custom SiteMapProvider. I will than need to write UI for managing navigation also.
EDIT:
I have managed to create Folder in Pages list and create (actually move) pages to that folder and even create sub folder but they are not showing on the menu not even in the navigation settings page. I can't approve folder, it is in pending status what ever I try.
I looks like this is not possible by the Andrew Connell: Subfolders are not Supported in the Pages Library in MOSS Publishing Sites
Out of the box, you can modify the navigation for a Publishing site manually.
I assume that you are after a more automated way to do this. Unfortunately, the way to modify the navigation for a PublishingWeb is through the object model and the PublishingWeb.CurrentNavigationNodes object, which would require a timer job or some other method to update as pages are edited/added/deleted.
This is non-trivial and you will still need to create a solution/feature package.
The other way is to create a custom navigation provider.
The issue with both of these options (aside from the actual coding and release) is caching the navigation structure. We have used the standard web cache for the object holding the navigation structure, but using the standard user browsing (i.e. the menu code itself) to kick of a refresh of the navigation is fraught with threading issues.
You can create multiple document libraries in a site and then put the pages in the various libraries. That way you wouldn't need to create sub-sites

Resources