nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Disable 'Create site' link

criskolkman

Hello all,

Been searching for ages for this function and I know it has been asked a lot, but no real solution to this yet.

Why would you have to implement/edit/install all kind off different mods and pages etc while a function like this (let the 'Create site' link see to people only member of (a) specific group(s)) should be a default on Alfresco.

Doesn't seem like there is any easy way to make this happen.

Find more posts tagged with

Comments

ddraper

Since you've said that you've already searched a lot I'm going to assume that you've already encountered the "showCreateSite" boolean option on the AlfSitesMenu widget that you can reconfigure following the customisation pattern described in this blog post?

But to answer your more general question, the basic reason why we've not exposed every conceivable customisation option as some kind of configuration parameter is because we don't know all the customisation use cases (or how popular each individual use case might be) and to trying to implement everything as a configuration option would be complex and expensive with no guarantee of return on that investment.

By providing a more generic customisation solution we can allow 3rd parties to essentially change Share as much or as little as they want to according to whatever criteria they need (i.e. role, page, user, etc.). Whilst this means that there is an overhead on very simple customisations, the approach required is applicable across all use cases.

jego

You could use the addon GitHub - jpotts/share-site-creators: An Alfresco add-on that limits site creation to those in a specific group.

This limits the site creation to a certain group in Alfresco.

Please mark my answer as helpful if this helps you.

criskolkman

Hello Dave,

This is an option which has been asked quite a lot for, but only can be implemented after a lot of code changing or third party scripts which require you to know how to install them ( GitHub - jpotts/share-site-creators: An Alfresco add-on that limits site creation to those in a specific group. )

The AlfSitesMenu requires a file header/AlfSitesMenu.js which I cannot find on the system:

[root@shared header]# find / -name AlfSitesMenu.js
[root@shared header]# find / -name *AlfSitesMenu*
[root@shared header]#

And I don't really want to hide the menu button, but to make members able to create a new site when they are member of a specific group.

Thanks for your answer!

ddraper

That's really useful, ‌ I didn't know that ‌ had implemented that. I just took a look through the code and (on the Share side at least) it is doing exactly what I've suggested in terms of re-configuring the AlfSitesMenu.

criskolkman

Jens thanks for your answer.

I was already looking into that one but it's not really clear on how to install/implement the addon.

jego

Hi Chris,

please look into the README of this addon. It describes the manual installation as well as integrating it into another amp projects you may have.

Very easy and used several times.

Thanks

Jens

ddraper

Hi Cris...

I guess it really depends on who has been asked (I wouldn't say that I've heard this request significantly more times than any other customization request). Ultimately it will be down to the current product manager for Share to make a call on what gets implemented. Any request for simpler solutions to specific customization requirements will then need to be traded off against other requirements that need to be delivered by the team. Given that there is already a well documented solution to this problem I doubt that it is likely to be a priority (although it's not my call).

When you create an extension module that re-configures the a widget you can apply evaluators to the module to determine when it gets applied. There are custom evaluators provided out-of-the-box or you can write your own so applying the module if the current use is a member of a specific group or groups is easily achievable.

With regards to not being able to find the widget source code, they will be in the Aikau JAR file in the share/WEB-INF/lib folder.

Regards,

Dave

criskolkman

Jens,

Thanks I checked that, but I have no experience at all installing with AMPs etc, that's why it's hard to implement such a thing