My Gitlab version is Community Edition 9.5.10.
But I can't find the menu settings => applications.
How to fix it?
Given the fact your version is about 3 years old, which is comparable to a geological era in terms of gitlab developement (1 minor release a month, several patch releases in between, and 4 major versions up since yours....), I would first make sure this feature was actually available in 9.5.10.
By the way, I strongly recommend that you upgrade your gitlab to the latest version available and put an upgrade scenario in place to keep it up to date on a very regular basis.
Now, I will not install this old version just to test. But in the latest releases (I don't know since when), there is a setting in the admin area to disable that feature for regular users in admin > settings > general > accounts and limits (All those settings might have totally changed place between versions...).
If you untick that box, only admins are able to reference global oauth applications in the admin area. Meanwhile, on my current version (13.2.6), this does not disable the menu in user settings but only shows a notice asking you to contact your admin.
speaking of upgrading GitLab, GitLab 14.0 (June 2021) proposes:
Streamlined top navigation menu
Streamlined top navigation menu
GitLab 14.0 introduces an all-new, streamlined top navigation menu to help you get where you’re going faster and with fewer clicks.
This new, consolidated menu offers the combined functionality of the previous Projects, Groups, and More menus.
It gives you access to your projects, groups, and instance-level features with a single click.
Additionally, all-new responsive views improve the navigation experience on smaller screens.
See Documentation and Epic.
You will get to your settings even faster now.
The rest has also improved:
Sidebar navigation redesign
Sidebar navigation redesign
GitLab is big. And it’s getting bigger. As we’ve introduced new features and categories, navigating the densely-packed left sidebar has become less intuitive.
In GitLab 14.0 we’ve redesigned and restructured the left sidebar for improved usability, consistency, and discoverability. We’ve moved some links to features around, split up features in the Operations menu into three distinct menus, improved visual contrast, and optimized spacing so all the menu items can fit comfortably on a smaller screen. These changes are intended to better match your mental model of the DevOps lifecycle, and provide a more predictable and consistent experience while navigating within your projects and groups.
See Documentation and Epic.
Related
I am facing problems with interface customizations in the latest OBIEE release.
Is it possible to "hide" the Mobile, VA and BiPublisher options - marked red in the appendix.
(Privileges in Administration and roles in EM are configured - users can not access Mobile, BiPub however the buttons are still visible - OBI 11 did not display them afterwards...)
I am looking for a "clean" design.
Any help is much appreciated
Unfortunately up to and including 12.2.1.2 (the current version) the "Visual Analyzer" menu point will keep being rendered even if they permission has been removed from the application role(s) of the user.
Mobile and BIP disappear completely on the other hand.
So the question to be asked is: how did you configure your application roles and policies? Did you reuse vanilla ones? Then it may just be the case that some rights still persist due to ootb inheritance between roles and hence some rights stay even though you think you removed them.
I'm using Gitlab and I've several projects.
project1;
project2;
project3;
Is it possible to have a common Wiki for these projects?
Every wiki is linked to a project, but there is a workaround:
Go to Settings → Services → External Wiki for your 2nd and 3rd projects and set External wiki URL to the URL of your first project wiki:
Or you can host your own wiki, for example, gollum on your server for the same purpose.
Is it possible to have a common Wiki for these projects?
Yes: (October 2020, 4 years later)
GitLab 13.5 proposes:
Group wikis
For many teams, using GitLab wikis for planning and documentation is a critical part of their workflow. Wikis are so popular that they get over a million views each month on GitLab.com. Despite this popularity, teams have struggled with the limitation that wikis were only available at the project level.
Teams working on multiple projects needed to create separate wikis for each repository, leading to a fragmented experience.
In Gitlab 13.5, we are so excited to bring you group wikis!
With 680 upvotes this was the most upvoted feature in the entire GitLab backlog. While highly requested, making a large project-only feature like wikis available at the group level has been a non-trivial operation. We’ve worked tirelessly over the past year to make it happen and now we can’t wait to get it in your hands and hear your feedback.
Group-level wikis open up tons of possibilities to keep your information at a higher level and accessible to a broader set of people. A few examples of what you can put in your group wikis include team-specific information, coding style guides, and designs for your brand or your company.
We know a lot of folks have been looking forward to this feature and shared their input pre-release. We hope all of you will continue to weigh in now that group wikis are available and we’ve opened up a dedicated issue for your feedback.
See Documentation and Issue.
I'm looking for simple way to update custom translations in Liferay without redeploy of language hook. Restart is no option for me too :).
UPDATE:
The customer has quite big portal with about 50 different portlet-applications. Each application has rich user interface in four languages. Together the portal has about 800 keys that must be translated.
For this translation work the customer has specific department that works with appropriate tools. This tools can generate Liferay compliant property files.
Furthermore, by 800 key-words / translations, that is frequently necessary to change the translation.
Hence, I'm looking for method to update UI translations live - on the fly. Without redeploy of language-hook and without restart the Liferay.
If you're thinking of translating the content that you already enter to your portal, that's already changeable through the UI, no hook or anything necessary. However, as you mention hooks I believe that this is not what you're looking for.
Redeploy of a language hook is the simple option to update the application's language (i.e. Liferay's own UI). You can hot-deploy a language hook without restarting the server. All the other solutions I can think of are at least an order of magnitude more complex and would involve program code that overrides the mechanics how Liferay looks up translated UI elements.
IMHO you can choose either one, "simple" or "no redeploy of a hook". You can't eat your cake and have it, too.
Update (after your update): What I described above is Liferay's mechanism, which you're free to use or to ignore. If your plugins have specific needs that their translation must be updated without the plugins being updated at all, you're free to choose any different language lookup mechanism of your choice. The Liferay mechanism - in this case - might not be what you need to use. Or you'll need to talk to your business users and get their information on how often they believe that the translation will be required to update when the plugins stay unchanged. Or how often they are prepared to redeploy the plugins (and if they can wait for this amount of time)
I have created and deployed a MOSS Site defintion using VseWSS 1.3
I install the site definition and create a new site and everything works fine. However, when anybody goes into any site on that WebApplication (in any site collection) and goes to the feature list then all these features are in the list.
I have about 15 content types, with 15 lists based on these content types each with their own instance and ItemRecievers. As you can imagine this is a lot of features in the list. My Sharepoint administrator saw this and had a meltdown...
He wants to see a single entry like you see for the MOSS Enterprise features etc, that activates all the features for my solutions. I have seen somebody menation the term 'feature pack' - in relation to this but I don't know if that's just their terminology.
How can I do this? Can this easily be done is VseWSS or do I have to go in manually and hack the IDE generated files?
james :-)
VseWSS isn't great for producing solutions - it can pull out elements of a solution, but tends to (in my limited experience with it) set things up like they're all going to be seperate features.
The unfortunate thing is, your Admin is right. What you've got - those content types, list definitions, and list instances - are a lot of feature Elements. A single Feature can have many of those, usually in a file called 'elements.xml'. There's a good description of this at:
http://msdn.microsoft.com/en-us/library/ms460318(v=office.12).aspx
(Note, in Visual Studio 2010 parlance, these elements are 'SharePoint Items' within the visual studio project. But I digress)
I've always tended to use VseWSS to create the files that I need - my list definitions, etc. - and then copy these files into a WSPBuilder project for packaging, ready for installation. If you've not used WSPBuilder, I recommend it for SP2007 development - though it's largely superceded by Visual Studio's own tools for SP2010. It takes a little understanding, but then you'll realise that if you simply copy the files into the right places, you can easily build your solution.
(You should be deploying your solution in a WSP file. ALWAYS deploy solutions in WSP files.)
(Also, you shouldn't have to 'hack' any of the files, just rearrange them on the file system so WSPBuilder packages them correctly. See the WSPbuilder documentation.)
An easy option to do is simply modify the feature elements to hidden, and create your primary feature as a visible feature with activation dependencies. This means that once the primary feature is activated all the dependency features will be activated automagically.
http://blogs.msdn.com/b/jjameson/archive/2007/03/22/scope-dependencies-for-sharepoint-features.aspx
I have a small Sharepoint Feature project in VS2008 with STSDev 2008 which comprises of a WebPart, a List and a List Instance (of the aforementioned List). The WebPart depends on the existance of the List as does the List Instance.
Would I be better creating one feature that deployed all three components, or packaging up the three components as individual features and creating feature dependancies in the WebPart and List Instance upon the List?
I can see several advantages and disadvantages:
Pro:
simplified testing as the list can be tested seperatly from the WebPart and Instance
more extensable as further features can be added that depend on up-level features
more efficent, only activate the features you need
Con:
increased development time to create features
development environment dosn't really allow you to split up features except for as different projects
could clutter the Site Features page in Site Settings
I would probably split them out into multiple features so that you can updat ethem seperately if need be. You could always create a parent feature which has ActivationDependencies on the child features. If you mark the child features hidden, the parent feature will automatically activate the child features and they won't clutter up your features page.
Also consider the administration of the features. If you're in a large company environment with lots of features being deployed, you'll want to consider breaking things up. It will help with deployment and, if one of those features become wildly popular while the other two are only somewhat popular, it will save you a ton of time with enhancement requests and bug fixes.