Is there possibility to enable specific themes for tenants on Orchard console?
After created tenant all themes are available to enable/disable. But how can I add only selected themes to tenant in Orchard Console as I can do in Orchard Admin Site for specific tenant ?
All tenants see all themes as well as all modules available in this Orchard instance by design. To activate a theme from command line for a single tenant only, use command theme activate "<theme name>" /t:<tenant name>.
/t switch denotes a tenant for which a given command is to be executed. It's applicable to all commands.
I found solution by creating new module and implementing new console command.
There I can inject orchard tenant service and update specified with my own themes list.
Useful information here: http://docs.orchardproject.net/Documentation/Using-the-command-line-interface#AddingCommands
Related
I've created an Azure account and added an application to it.
On company level I changed the branding (added a background and banner to the login page).
This is working great.
But I would like to create a branding on application level.
Let's say I have two applications: app1 and app2.
When pressing the login button on both applications it will redirect me to the login.microsoftonline.com/....
After filling in my email, I'm able to see the on company level defined background and banner.
But I would like to add different background/banner (or text) for both applications.
So the login.microsoft... of app1 needs to show the banner that belongs to app1 and app2 needs to show the banner that belongs to app2.
Is this possible?
I noted that there is also a branding item on application level where I can add a logo.
However, when I add one there it will only be shown in the azure environment itself.
At present, app registered in azure ad may not able to have its own customized login page UI like in azure ad B2C .It may due to some functionality issue in branding option. You may See this thread
You may give try Set-AzureADApplicationLogo (AzureAD) by checking guidelines of size and dimensions and by selecting an absolute path for file path.
Set-AzureADApplicationLogo [-ObjectId <String>]
-FilePath <String>
Otherwise You can provide any feedback or idea or suggestion here > https://feedback.azure.com/forums
We have a self-hosted gitlab solution and are trying to integrate a third-party application. For that we created a new account and wanted to set up a new application. But we were greeted by the following screen:
'Adding new applications is disabled in your GitLab instance. Please
contact your Gitlab administrator to get the permission'
I have an admin account and have looked everywhere to set this permission but can't find it. In my own account it is also impossible to add application, but in the admin area the possibility is there.
In the pricing table there does not seem to be any option that adds this feature so I don't think it is a blocked feature.
Any help would be much appreciated.
Go to https://gitlab.example.com/admin/application_settings
On the general tab beneath "Account and limit", there is a checkbox called "User OAuth applications".
Once you toggle this every user gets the ability to define her or his own OAuth2 Applications.
I'm using VS Online Monaco; trying to figure out how to add users to my Azure web site so they can edit in Monaco. Adding them to the VSO group didn't work.
the Monaco editor is actually a site extension on your normal website, you actually use it through your webpublish account credentials, so it's actually not something you can easily override i think
What are the minimum SharePoint 2010 permissions required to allow a user to personalize a web part page, allowing updates and adding web parts to the page but completely restrict the user modifying the shared version?
I initially copied the built-in “Read” permission level and added the “Manage Personal Views”, “Add/Remove Personal Web Parts” and “Update Personal Web Parts” permissions from the Personal Permissions group. This custom permission level was then applied to a user who then viewed a web part page created by the Administrator, which contained only a very simple prototype SharePoint web part. This web part contained a modifiable label which was edited using the “Miscellaneous” section from the Edit Web Part from the standard SharePoint chrome.
With the custom permission level applied the “Miscellaneous” option it is not available to the user upon personalizing the page and selecting Edit Web Part. The “Miscellaneous” option only becomes available to the user when the permission level is further modified to have the “Edit Items” from the List Permissions group. This has the undesired effect of allowing the user to be able to modify the shared version of the page.
Is what I’m trying to achieve even possible?
Many thanks
Check this out: http://akifkamalsyed.wordpress.com/2011/01/17/personalizable-web-part-custom-property-not-shown-for-users-with-contribute-permission-level/
It's probably because you don't have a safecontrol for the webpart with the attribute SafeAgainstScript
I have a dnn site that allows users to have child portals. The child portals are either basic or advanced. The advanced portals is basically unrestricted. However the basic portals should be restricted to only being able to change the content provided to them but not being able to add any pages or modules. Is that possible? Is there a security module that will aid in that?
Your description of basic portal security is possible to implement in DNN's role based access control.
The role assigned to the users:
should not have page-level edit
permissions
should have edit
permissions to selected modules
The problem is how to conveniently assign these permissions to new pages.
I recommend creating template pages first with the correct permissions, and then copying new pages from these templates. It is also possible to make a helper application for this copying. DNN API and the IPortable interface help here, but my experience is that with 3rd party modules you'll often need to implement the copy functionality yourself.
You can hide the control panel (ribbon bar) from Module Editors who are not Page Editors. This can be done from the Admin - Site Settings: