I have created control panel theme following bootstrap standards. For some reason, we are using liferay 6.1 which doesn't provide responsiveness and hence has to be taken care of.
As we know control panel contains many pages e.g: MyAccount, User Administartion e.t.c.
As of now,these pages are looking fine with the old theme(non-bootstrap).
As and when I update these pages to bootstrap standards, I want to be able to apply bootstrap control panel theme for them.
Question here is - How do I apply old theme for MyAccount Page and bootstrap theme for User Administration page. Is there some property file that I need to update?
I did my research but couldn't find anything substantial.
Please let me know if I need to be more specific about the query.
Related
I am working with a site using the Microsoft Developer Program. I am able to use the new Change the look feature on modern Communication sites to adjust the theme.
I created a theme using Powershell
I created a Communicators site and selected the Custom theme and used a PowerShell cmdlet to set that site as the homepage. I am still able to change the theme on that site by going to Settings > Change the look > Theme. The default and custom theme appear in the menu to select.
I attempted to follow the instructions on creating a Site Design to test out the feature of potentially exploring site designs. I ran into some issues of the feature I was attempting to use was not supported yet. I did not create any site designs. I use the Get_SPOSiteDesign cmdlet and nothing is returned.
I then created another communications site. I was just going to build these one at a time since Site designs did not meet my goal. I wanted to change the theme to the Custom theme, I go to Settings > Change the look > Theme and it closes the Change the look menu in the panel and returns me to the Settings panel.
I am able to go to Settings > Change the look > Header, Navigation and Footer successfully. Only the Theme option causes this error. I am unable to change the theme.
I used a PowerShell cmdlet to ensure the themes were not hidden, Set-SPOHideDefaultThemes $false. This is set.
I then created a second, third a fourth Communications site (using the Topic, Showcase and Blank designs) and the same error above occurs not being able to access the theme menu.
I then created a Team site. I am able to access the Theme and change to the Custom theme or one of the default selections.
I need help as to why new Communication sites I create in my environment will not allow me to access the theme menu, but homesites and team site do allow this. What do I need to do to correct this?
I too am coming across the same issue. I have attempted it in difference browsers and in incognito to verify it wasn't an extension or browser specific issue. Have you discovered a resolution or opened a ticket yet?
We have the same issue on our tenant and have opened a ticket a MS support. They confirmed that this a bug and are going to solve it.
For now we have a workaround via PNP Powershell.
When you set the theme first via Set-PnPWebTheme -Theme "Custom Theme", the option to modify the theme via the browser works again.
How to change design dialog content in specific locale?Example the design specific constructs that would be different accross locales were logo, branding elements etc... Please suggest various alternatives and best approaches?
Design dialog are not locale or site specific in case of multisites rolled out on same instance of AEM. Design dialog properties gets stored on template/component basis in designs (/etc/designs/<your-site>/jcr:content/<path/page component name>/<component>). You can look at the sample for geometrixx site # /etc/designs/geometrixx/jcr:content/page/logo
For the scenarios where in the content/imagery that needs to change per site/locales you should use normal dialogs.
For components like header and footer which needs to stay consistent across site and usually the requirement is that they should be authored once and not be edited every time a new page is created, you could use iparsys component for the inheritance of these sections to pages in the hierarchy. This would require the inheritance system to be setup on a base page/template from which other templates extend so that inheritance get extended to all templates.
I am developing components for CQ5 and wish to control them so that component A is only displayed in the sidekick if the page is of template T_A, and components B and C are only visible if the page is of type template T_B, however I have so far not been able to find a set of properties to allow this.
Does anyone know of any way to achieve this functionality?
I am also able to retrieve the page template in code via the use of
currentPage.getProperties().get("cq:template", "").equals(MyTemplate) however, once I have not been able to find a way to control sidekick component visibility.
I have also attempted variation on Disabling The Components Tab, however this too has met with no success (even at the level of disabling the entire components tab).
This feature is baked into CQ5 and requires no special coding. The general way of controlling what components are visible in the side kick (specially what components are allowed for a given parsys) is controlled via a design. The remainder of my answer is based on the assumption that you have no special requirement other than controlling what components are allowed for a parsys (i.e no run time requirements).
The components (or component groups) allowed for a parsys are stored in the design of the site . You can control this behavior by editing the design dialog of the parsys.
The steps for achieving this are as follows
Go to design mode by clicking on the ruler icon at the bottom of the side kick
Click on edit button of the required parsys
Check the components required from the allowed component list
The allowed components are stored on per template basis. Since this data is stored in a design , all the pages must have the same design. The design must be exported too, for this to work across instances [ref : https://stackoverflow.com/questions/17049259/limiting-allowed-components-in-a-template-in-cq5
]
I have just started learning DNN. I dug a little into this but I just can't change the layout for whole site. I am using Awesome cycle template as starting.
I need to redesign site header and footer. If I made change in Skins\Gravity\Home.ascx then these changes are only appearing to my home file.
I can change the CSS the way I want but I am just unable to change the base html of header in entire site. (like we do in master pages in ASP.NET or layout in MVC)
Your problem probably has to do with DNN supporting different skins for different pages.
You have to check if all pages use the same skin. I think that in DNN7 default site template pages use different skins. You can check this if you go to Edit Page -> Page Appearance -> Page skin
If you set all the pages to use the Gravity skin, then changes you make at the .ascx file will apply to all pages.
A uniform way to change the layout for the whole site is to set every page skin to 'None specified' and then only select skins from Admin -> Site Settings -> Basic Settings ->Appearance ->site skin.
You can update the DNN database using an update query on the Tabs table:
update Tabs set SkinSrc = REPLACE(SkinSrc,'OldSkinName','NewSkinName')
where SkinSrc like '%OldSkinName%'
You can also rename the containers using a similar query:
update TabModules set ContainerSrc = '[G]Containers/MySkin/NewContainer.ascx'
where ContainerSrc = '[G]Containers/MySkin/OldContainer.ascx'
In the latest operation remember to clean the dnn cache using : Host > Host Settings > Advanced Settings > Performance Settings , click on the “Clear cache” button.
I'm currently in the process of building a wordpress multi-site for a client. I've completed aspect #1, which was creating Theme-1. Theme-1 was built utilizing excessive amounts of the AdvancedCustomFields PLUGIN.
I'm working to build Theme-2, this one is the primary theme that will be utilized for all of the sub-sites created through the multi-site option. The issue I'm having is that the AdvancedCustomFields are no longer an option, I need to build all of the customization into the functions.php file directly.
Is it possible to create custom fields through the theme directly - without utilizing a plugin?
I need the theme pages to have "Left Side" "Right Side" "Footer" as WYSIWYG editors. So if someone goes to create a new page all of these field settings are there by default.
Is this possible?
It's possible, using the wp_editor function to get the WYSIWYG functionality. See this question on the WordPress stackexchange site. It's demonstrated as a plugin, but you could just as easily put the code in your theme.