On the admin environment of Drupal 7, I have changed the Administration theme by going to the Appearance page. Under section ADMINISTRATION THEME, I have selected a theme from the dropdown list and clicked on Save configuration.
The selected theme is applied. This is on my localhost. I would like to export this settings or configuration and push it to my git repository to apply this theme settings or configuration on my testing server. How can I export this theme settings on Drupal 7?
The best option here would be to install the Features module. You can then configure it to export all of your site-wide (including theme) settings and also have the added benefit of 'reverting' to the exported settings if anything were to change.
Give it a try and drop a comment if you get stuck.
Related
I am trying to find a way to replace Keycloak image on the Admin console page using Keycloak.v2 theme which is the default theme starting from Keycloak 19.
Note that replacing themes\keycloak.v2\account\resources\public\logo.svg didn't really help.
In Keycloak, one of the ways you can change the Keycloak logo is by overriding a theme. The benefit of doing it this way over forking and building the entire keycloak-admin-ui repo is you can control and focus only on customizing the components you want, cutting down the size of your new theme and reducing unnecessary duplication.
For your specific use-case (tested in Keycloak 20.0.1), I did the following to change the Keycloak Logo on the Admin Console Page:
Per the Theme Guide for Keycloak, custom themes can be added to keycloak by placing them into /opt/keycloak/themes. After Keycloak starts the theme can then be selected in the Realm Settings. Therefore, I created a new folder in /opt/keycloak/themes for my custom theme, called myCustomTheme.
The new folder will contain the theme definition for different parts of Keycloak. Since we only care about changing the logo in the Admin Console, we create a folder in /opt/keycloak/theme/myCustomTheme for overriding the Admin Console Theme. Per the defined set of theme types, this folder should be called admin. This is so that when you are selecting themes in Realm Settings within the Admin Console, the MyCustomTheme option will be listed under the Admin Console section (see images below).
Inside of /opt/keycloak/theme/myCustomTheme/admin is where the theme overriding begins. A configuration file called theme.properties should be created. This file is the first thing read by Keycloak when loading your theme and contains information about the theme environment. For more detailed information, see the description of Theme Properties.
Since we are overriding the keycloak.v2 theme, we add the parent field to the properties file, specifying the base theme we are inheriting from. We set it to keycloak.v2, so that myCustomTheme will inherit the keycloak.v2 theme for all of its components unless we are overriding something specific.
parent=keycloak.v2
This next step required a bit of exploration and trial-and-error of how the default keycloak.v2 theme is structured, but I found that the place where the Keycloak logo is defined for keycloak.v2 is in keycloak.v2/admin/resources/logo.svg. Therefore, for myCustomTheme, all one would have to do to use a custom logo that overrides the default keycloak.v2 one is add a resources folder to /opt/keycloak/theme/myCustomTheme/admin and add the custom SVG image as a file called logo.svg.
Note that this is different than what the Keycloak Docs suggest, which has you creating the same resources folder but also an img folder inside of it which would contain your images. I suspect this has to do with the fact that we are overriding an image instead of adding one, and the keycloak.v2 theme code does not follow its own guide and instead places its logo in resources instead of resources/img.
Start Keycloak, go to the Admin Console, sign in and go to Realm Settings > Themes > Admin Console theme, and select myCustomTheme. Refresh and you should see your icon change now.
Below is the results of doing the above, showing my resulting folder structure and the Before/After of replacing the Keycloak logo with some random SVG I got from public domain:
Folder structure: https://ibb.co/h9kZqb3
Before/After: https://ibb.co/cJ6t434
The new admin UI (starting from keycloak 19) has been delivered through keycloak-admin-ui.jar. In order to customize any UI components, it has to be done by forking this repo and build on your own.
I want to change the default "Unleash the power of your APIs" text on the portal's home page. Is there a way that I can do that via the API management portal (and not via the distribution folder files)?
I've just found the option on settings > theme to changes overall styles configs.
Thanks
You can do customisations on the portal page, such as changing the default text based on the information in this documentation
Recently, I have applied Fix Pack CF06 to my WebSphere Portal 8.5.
This fix pack provide new feature of asynchronously loading the content in Web Content Manager Portlet. For information Click Here
I have successfully completed step 1, skip step 2 because I don't want to change the loading mask. But I am not able to complete step 3, because I don't know how to enable wp_wcm_theme module in my customized theme. The wp_wcm_theme javascript object is always undefined for my Page.
I have also tried with applying Portal 8.5 Theme, but that also don't work. Any help would be highly appreciated.
To enable wp_wcm_async module in your theme. Open the themelist using WebDav or other client. Move into your theme folder -> profiles. In each and every profile or in the necessary profile add the "wp_wcm_async" inside "moduleIDs" json.
For example :
modeleIDs : {
"wp_theme_portal_85",
"wp_toolbar_host",
"some other modules",
"wp_wcm_async"
}
Save the file and restart the portal server, now you can access the wp_wcm_async theme module inside your theme which gives you access to wp_wcm_async global java script object.
Question: How do I refer to my layout files form the changeLayout.json and layout.json files if the layout-template files are held in a theme ear/ear?
Background:
I'm developing a custom theme with custom layouts in Portal v8. I'm using the ear method for the theme deployment,s o I've got everything segregated into MyThemeDynamic.war and MyThemeStatic.war I've added my layout files to MyThemeStatic.war/themes/MyTheme/layout-templates
When I set the default layout template in the XMLAccess import, I can successfully see my custom layout.
But If I try to change the layout, it reverts back to the Portal 8.0 theme defaults.
I've tried several ways of referring to my layout files from layout.json.
I saw this: http://tinyurl.com/ch2nczp
but it prevents the default theme from working properly, and I want to keep both the default and this new custom theme.
I've also tried adding references to the xml access, as suggested here: https://www.ibm.com/developerworks/forums/thread.jspa?messageID=14909102�
I feel like I'm close, but I'm missing something.
I combined static and dynamic theme assets into a single war file following these instructions:
http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Create_a_custom_theme_without_WebDAV_with_8.0
That was ultimately what worked.
I am new to WebSphere portal themes.Can we migrate the WebSphere portal 6.1.5 Page builder themes&skins to 7.0.0.2 Page builder themes&skins ? If yes,can u please provide the themes migration steps to follow.
Thanks,
Haritha.S
If you have not customized the theme in any way, if it's just a clean out of the box Page Builder theme, the upgrade should not effect it.
If the theme has customizations, then any hard-coded references (paths to artifacts or the context root) will have to be updated.
During the migration process, any custom theme you have present in wps.ear will be moved to MigratedThemes.ear. You'll have to expand that ear file, modify your theme, then pack it back up and deploy through WAS console.
Here are detailed instructions (though they relate to WAS 7): http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Portal_V6.1.x_on_application_server_V7_Updating_custom_themes_and_skins_with_hardcoded_context_root_references_wp8