For my specific implementation, it makes sense to only use the 2 column layout on both the site and user dashboards. I want to make this the default layout and pick which dashlets I'm going to use, as I'm going to create a large number of sites and users and don't want to manually go through and edit the layout for each one.
I've successfully commented-out sections of the presets.xml located in /tomcat/webapps/share/WEB-INF/classes/alfresco/site-data/presets such that when I create a new user, only the dashlets left uncommented are shown, however the dashlets are still shown in the 3 column layout. If anyone could tell me what I'd need to edit to make this layout default and/or how to define the region-id's, I'd be extremely grateful.
I've been looking for where the user's layout config is stored so I could set the dashboard up as I want it to be in the preset and then look at this user's config to get figure out how to put this in as the default in presets.xml but I can't find where they're put.
http://mafshan89.blogspot.in/2012/05/dashboard-customization-for-existing.html
see if this helps...
pow: http://forums.alfresco.com/en/viewtopic.php?f=47&t=37001&p=107959#p107959
Related
i want to edit an existing Typo3 Backend configuration page.
I want to edit a configuration page like this here:
Where can i edit the extensions backend?
To be more clear: where can i change the edit page that an editor can use to change content.
Can someone give me a hint to the right directory or file in generall?
I'm using Typo3-7.6
Thanks
Sorry, can't manage to put all questions in an unformatted comment.
there are a lot of questions, as you are not clear what you want. Maybe that is a problem of the correct words, the vocabluary, but in TYPO3 we have some fix terms for specific object. And I think you do not handle these terms according to the TYPO3 community.
let's define some terms:
first the concept of TYPO3:
all data is stored in record of differnt database tables. All records are organized with some fields and teh main field is uid, the unique ID.
the main table is pages according to the folders of your disk. those folders can contain other records (like files). (nearly) each record in TYPO3 has a relation to a pagesrecord ina field named pid. even pagesrecords have this field and so they build a tree of pages and subpages.
There is one special page, which is no real page: the page with the ' uid' zero. As there is no real pagesrecord with the uidzero, there are other records with are stored in that page by having a pid zero. for example the start of your page tree is anchored in page zero, or global records like languages, user, storages.
Aside of being the anchor to other records, the pagesrecords have information themself. (page name, kind of page, a teaser image, SEO-information, visibility, accessibility, ...)
your screenshot looks like a content record (normaly in the table tt_content), in the lower right corner there you can see the table name and the uidthe the currently edited record.
'Backend': with backend we name the view to the data where an editor can change the content of the website. The real website is the frontend. This can be seen by everyone without the need to login in the backend (you might have access-restriccted areas of your website which need a login, but that still is 'frontend' as there is no option to edit content.
in the backend the editor might be restricted what he can access and what he can modify. An adminuser has no restriction (up until version 9 where the role of a maintainer occured to manage more general and basic options)
so we have not a single 'backend configuration page' but multiple places where we could configure special aspects of the website.
also there is no special 'extension backend'. we have global extension configuration and records belonging to an extension. (And an extension can enhance existing records with additional fields.)
Please be more specific what you want to change
I think only one thing is missing...
but I do not get this point :p
i created an user and I created a group, both didn't work
What I want is a group with specific rights, one with read and edit rights and one with only read rights, but all only works for the "root page"
how can I inherit this to the following pages?
All the things from older versions of TYPO3 do not really work at my version (my version is 7.6.14)
Update 1:
Okey, I could set the rights by hand for every single page in the access category. But I think there should be a possibility to inherit the rights to all the subpages?
At last it may only be one checkbox ore option I have to activate?
One picture to make it more clearly what my problem is:
For those who don't understand german, "Berechtigungen" means access and "Tiefe" means depth.
Solution
I finally got it and it and it is working fine.
I just need to set the depth at the right place here:
One more hint: be_acl is a good extention, if you need more than one group for a page or more specific rights for different users.
Maybe the group does not have access to the subpages?
In the backend under System -> Access you can change the ownership of pages -
owner, group and all.
When editing access control of one page, you can change the depth to automatically adjust subpages.
You can find a really good article about right management in the blog from Marcus Schwemer here: https://typo3worx.eu/2017/02/typo3-backend-user-management/
For other things it would be useful if you could provide a little bit more informations about what does not work?
For example it could be that your user has no access to the page tree, if this is the case there is an extra "Access" Backend module. You can find more information about this here.
I'm creating a DokuWiki and have a specific template for new pages. One section uses the include and data plugins, so they are for display of external data only. I don't want users being able to mess with this code, so it would be handy to block them from editing those particular sections. I couldn't figure out any particular strategy to achieve this.
There is no way to do that in DokuWiki. DokuWiki's ACL system only works on the page level. Your only way to achieve something close to this is to work with the include plugin. Make your main page readonly, then include different pages for the different sections. Make the pages for the sections you want to have editable editable and the others read only. Then point your users to the individual pages for editing.
I am new to typo3, i am trying to create a new backend layout for my home page.I need add few custom sections to edit contents.I am not able to find option to do so.
TYPO3 7.2 is out of support and has know security issues. Please update to 7.3 at least.
You can create backend layout records in any folder in the page tree. To select those backend layouts, you have to add this folder as the general record storage in the page properties of the page where you want to use your backend layout.
I suggest you take a look into the Getting started tutorial which will walk you through your first steps.
http://docs.typo3.org/typo3cms/GettingStartedTutorial/
In case you use a distribution, it might be that the backend layout is added in another way, e.g. via TSconfig or directly using PHP. Please consult the according documentation of the distribution in this case.
Figured out myself.
Go to List in Web, then click on add new + icon, then select Backend Layout under System Records.
I am trying to get specific content on a confluence cloud wiki to display content based on a specific user. The scenario here is that there are links on a page but only 1 should display, the one that displays is based on whom ever is logged in.
I have been told how a macro is the way forward, but I have read the documentation and I am at a loss. I do not understand what I have to do or how to write a confluence macro. could someone help me out with either an example or some links? I have searched like crazy, but maybe i am not asking the right questions but hopfully you can all help me out?
There's a plugin for this:
https://marketplace.atlassian.com/plugins/net.customware.confluence.plugin.visibility
But I'm not sure how thoroughly it hides the content. It might still be visible if users view the page source. If you're trying to hide content which needs to be really protected, you'll probably need to do something else.
Depending on how many users are going to be using the page, you could also just make separate spaces for them, add the permissions to those spaces, and then use a page-include on your "main" page to display the content. If they don't have access it shouldn't show up. You might experience some formatting issues with that solution, however.
Finally, you could grab the username with jquery and display stuff based on that. This solution will be pretty easy if you are familiar with javascript/jquery.
Edit: Here are some helpful resources on how to use javascript and jquery within confluence:
https://confluence.atlassian.com/display/CONFKB/How+to+Use+JavaScript+in+Confluence
https://developer.atlassian.com/confdev/confluence-plugin-guide/writing-confluence-plugins/including-javascript-and-css-resources