The skin I've installed (foreground) runs fine on all my pages including special pages except the login account page.
I've tried going to my skins/foreground/assets/stylesheets folder and do some editing on their CSS scripts, but they just implement minor changes.
I want to see if there's a way I can rebuild/modify the CSS or general template of just the login page, with the foreground skin I've already installed.
Many wikis use pages like MediaWiki:Common.css to create a custom 'theme' for their wiki. However, due to security reasons, site-wide CSS on restricted special pages was disabled starting with MediaWiki versions 1.19.20.
By default such style sheets no longer load on login or preference pages creating an inconsistent user interface. In order to fix the UI you need to set the variable: $wgAllowSiteCSSOnRestrictedPages to true in LocalSettings.php.
This will enable the skin for the special pages mentioned.
Related
I was creating a custom template for a wordpress webbsite and for the first time after I add new classes in the style.css and I apply the changes, the website doesn't save them. I tried many times to delete the cache and change browser but nothing. When I open the style sheet from wordpress ACP I can see the changes but from google chrome with the webmaster tool I see nothing, like it shows the old css version. I am using WP Super Cache also.
Anyone knows the solution?
Adding a query killer at the end of the css file might also override any possible caching mechanisms.
Ie: example.com/style.css should be accessed via example.com/style.css?test
I have been trying to edit a particular style in my theme. My browser inspect shows that that the stylesheet file is local/css/template.css, i navigated to the Joomla template customize panel to edit the style sheet but the changes i made is not reflecting. please help
View template.css in your web browser to check if you can see the change. You may need to clear the Joomla cache and any other caching (e.g. via your hosting control panel or your CDN control panel etc) before you see the latest version of the CSS file.
Alternatively, this may be a specificity issue.
I often use small, page specific CSS files for a page in Typo3 using css_select. These styles usually apply only to some special element on these pages. Putting these styles in a global file doesn't feel right.
Using css_select I can select a bunch of files that may be included into the page's header, so that it loads it's special styles.
Now I'm looking for a way to do something similar in Django CMS 3. The only built in solution I'd know is to create a new template which seems a bit excessive for a single page where an image needs to be handled a bit differently from all the others, to name just one example.
Is there a way to do this using nothing but django CMS?
If not, is there an app that would do that?
If not, how could an app extend the page admin form in such a way that this function could be added.
You could extend the page.
See http://django-cms.readthedocs.org/en/latest/extending_cms/extending_page_title.html
A good example is https://github.com/nephila/djangocms-page-meta
This the above package allows you to add additional meta tags to page header.
I have created a custom styles css and registered it as follows in v4.master using SharePoint:CssRegistration option name="<% $SPUrl:~SiteCollection/Style ibrary/Custom.css%>" after="corev4.css" runat="server"/>
I assumed that my custom styling would be applied to any new site, however any new sites open in the standard default style, obviously I want my custom branding to automatically apply..
I have to mess around in site settings to use the parent theme etc, but even that does not always apply the styles correctly, so I have to go to the parent site and apply the parent styling to substitutes etc.
Other users will be using the site so I want to make it as easy as possible, can anyone offer help?
In order to apply your custom styles & master pages, you need to create sharepoint module (your styles, files & configuration) and Feature with Event receiver(when activated in sharepoint site/sitecollection, it'll apply your module, when deactivated, it rollback default settings related to styles/master page).
Here is the step-by-step article,
Article 1
Article 2
We want to distribute our .NET Themes out to edge of the Cloud.
However, my research through Google and Help files tells me that ASP.NET Themes (App_Themes) must be served from a physical sub-folder of the web server folder or an IIS virtual directory; ergo: Themes cannot be served from a CDN (we are currently using AWS). This seems a major failing and I hope that I am just going to get flamed for not researching properly, but I have to ask:
Does someone know of a way of serving ASP.NET Themes from a different server (and URI) than the web application that uses the Themes?
(Windows Azure could be a possibility, if it is a/the_only way to achieve this.)
Using themes and skins you primarily style server controls. Then it doesn't make sense to have theme files in CDN, since they are processed by the server.
Themes vs. Cascading Style Sheets
Themes are similar to cascading style sheets in that both themes and style sheets define a set of common attributes that can be applied
to any page. However, themes differ from style sheets in the following
ways:
Themes can define many properties of a control or page, not just style properties. For example, using themes, you can specify the
graphics for a TreeView control, the template layout of a GridView
control, and so on.
Themes can include graphics.
Themes do not cascade the way style sheets do. By default, any property values defined in a theme referenced by a page's Theme
property override the property values declaratively set on a control,
unless you explicitly apply the theme using the StyleSheetTheme
property. For more information, see the Theme Settings Precedence
section above.
Only one theme can be applied to each page. You cannot apply multiple themes to a page, unlike style sheets where multiple style
sheets can be applied.
Source: ASP.NET Themes and Skins