we want to set up a new Author environemt and wanted to export all users and acl from an existing author to the new one.
Is there an simple way to do this?
No LDAP available.
Thanks and Regards
Patrick
Edit:
Found this http://www.wemblog.com/2011/11/how-to-create-package-based-on-xpath-in.html and could export all Users and reimport them on a fresh system.
Users and groups can be activated from Author to Publish - You could try configuring the old Author to replicate to the new author, then using the Tree Activation to push the users to the new instance.
My colleague Jason reminded me of this: users and groups are content like everything else. So you can make a content package from all or part of the /home JCR node.
Related
I started my github account and I used a chat room handle for the root folder so that when you go to github.com/caverdude it's my stuff. I'd now like to change this caverdude to something more professional. Like my business name, or my name or something.
A google search turned up something totally different like changing the root folder in a repository.
Man, I've been there. I believe once you change your github username it will effectively change your repo root url.
fyi - I believe they will create redirects from the old urls to the new ones but only so long as another caverdude account isn't created. If another user named caverdude comes along at a later time the redirects from the old name to your new name will stop working.
Recently on a project I followed but hadn't really bookmarked or forked changed their name to something mysterious and it was a brief mystery as their old profile showed Github's custom 404/ not found. Eventually I tracked it back to their new, not-very-obvious name. All this to say, the whole "old redirects to new account" seems a might bit tenuous.
You can change your username in your account settings:
Click profile picture
Settings
Account
Change username
This will change your root folder on your profile page to the new username, and any links with your old name will show 404 error. So, you’ll need to update your links, but your repos will be updated with your new username. Here is the article from GitHub docs which gives you the steps and what happens after changing usernames :). Hope that helps, take care!
I am new Vuestorefront, I am trying to change product catalog
for that, everywhere is returning to go admin panel but can anyone tell me how to get the user name and PWD of demo admin panel
http://demo-magento2.vuestorefront.io/admin
reference page https://docs.vuestorefront.io/guide/cookbook/data-import.html#_2-1-recipe-a-using-demo
thanks in advance
The Magento demo is purely for demo purposes. If you intend to begin working in Magento on catalog and orders you will need to spin up your own instance of Magento (or desired backend).
I have an issue with a dotnetnuke 7 site, where the administrator cannot edit a minority of the pages.
When logged in and on such a page, the edit page menu missing.
When on the page management view, there are only options to view or make homepage. On clicking, properties are not shown.
What could be causing this?
Cheers, mark
I've seen in the past where the Administrator Role Id is incorrectly defined in the database.
Unfortunately there isn't a UI way to change this, you'll need to go into the DB to see what Role ID is defined. I believe AdministratorRoleID is stored either in the Portals table, or in the PortalSettings or PortalLocalization table. Check the # and see if that matches the ID of the Administrators role for that portal.
It could also be a CSS issue if it only affects some pages. Can you try changing the skin on those pages to the default skin and try again...
Just noticed this old question, so I thought that I'd update with what the actual problem was.
We imported pages using a direct to database program - we naturally assumed that the site administrator could, as a default be able to edit pages within their own site.
As it turns out, DNN actually creates correct access rights to each page as they are created, and rights are added and removed as required. This means that if you create pages you must directly create access rights for the correct site administrator.
Kind Regards, Mark, IA
I want TRAC to generate individual pages for specific user name.
For example USER1 after successful login will see:
USER1_logo.jpg
USER1_welcome_text
USER1_link_to_http_ftp_file
The same way USER2 will see his/her individual page/pages. Especially I'm interested in putting links exclusive to user name in welcome page or sub pages.
Does anyone know a plugin or a way to do this?
[SOLVED]: Install those TRAC plugins: TracMyPagePlugin and TracUserPagePlugin. Read documentation for them on trac-hacks.org
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.