I wish to change the built in blue colours for the admin pages.
I used Firebug in Mozilla to try and find the colours around different style sheets I found in the Django.1-3 folder, but none seem to come up.
In what directories would I find the .css files for pages that have the header dark blue colour and the light blue table captions colour?
What actions must I take in order for the changes to work(eg. move folder to main project folder)?
https://docs.djangoproject.com/en/1.3/howto/deployment/modwsgi/#serving-the-admin-files
The admin files live in (django/contrib/admin/static/admin) of the Django distribution.
You have the source. You can change these files.
One common approach is to (1) copy the static admin files to a separate directory that your web server can use, (2) configure your web server to serve these files, and (3) change your settings.py to reflect this new location for your admin media.
https://docs.djangoproject.com/en/1.3/ref/settings/#admin-media-prefix
No template changes are made.
Nothing needs to be moved into your "main project folder" (whatever that might be).
Related
I am trying to generate a MSIX-installer for a Win32-OpenGL-application, which is supposed to be deployed in Microsoft Store. Therefore, I have first built the .exe-file in Visual Studio and packed it with MSIX Packaging Tool to a .msix-installer. After that, I edited the .msix-package and added the required images (Square44x44Logo.png, Square71x71Logo.png,...). Unfortunately, I found out that the icon in the task bar was plated. I tried to add another image (Square44x44Logo.targetsize-44_altform-unplated.png) to the .msix-package by editing it again with the MSIX Packaging Tool, but the task bar icon remained plated. How can I change my task bar icon to unplated?
Unplated assets
By default, Windows uses a target-based asset on top of a colored
backplate by default. If you want, you can provide a target-based
unplated asset. "Unplated" means the asset will be displayed on a
transparent background. Keep in mind that these assets will appear
over a variety of background colors.
Unplated assets and themes
The user's selected theme determines the color of the taskbar. If the
unplated asset isn't specifically qualified for the current theme, the
system checks the asset for contrast. If it has enough contrast with
taskbar, the system uses it. Otherwise, the system looks for a
high-contrast version of the asset. If it can't find one, the system
draws the plated form of the asset instead.
Follow the steps below to solve this problem:
Obtain the correct 44x44 images and then copy them into the folder
that contains your images (i.e., Assets).
For each 44x44 image, create a copy in the same folder and append
.targetsize-44_altform-unplated to the file name. You should have two
copies of each icon, each named in a specific way. For example, after
completing the process, your assets folder might contain
MYAPP_44x44.png and MYAPP_44x44.targetsize-44_altform-unplated.png.
In the manifest file, set the BackgroundColor for every icon you are
making transparent.
Continue to the next subsection to generate a new Package Resource
Index file.
For more details, refer: Add Target-based unplated assets
Here is a similar case for your reference.
unplated taskbar icons in Desktop Bridge apps
I'm migrating my website to another hosting, but I have problem with the font.
When you open site for the first time font is not working, it's just showing blank squares, after you go into any subpage it starts to works. Do you have any idea what might be causing it?
its depends on where you added font awesome in opencart.
Mostly it should be in
catalog/view/theme/default/template/common/header.tpl
And if you added with some custom condition then check it.
because in opencart only Except then home page, other inner pages open with Query parameter.
ex. index.php?route=common/home
So, for inner pages check source code and look at the CSS path is proper or not.
Just to add (I cannot comment), if you're not using the default theme, you'd want to navigate to catalog/view/theme/(your theme name)/template/common/header.tpl
If you're using the Journal theme, you'll want to check the template/journal2/headers folder.
Try these and tell us if any of them makes a difference:
Edit your config.php and check that the HTTP_SERVER and HTTPS_SERVER variables are correct.
Make sure that the link to Font Awesome is correct, this also means making sure that if your site mainly uses www.domain.com and not domain.com that your link to Font Awesome has www. in as well. Same goes for http:// vs https:// and vice versa.
Check the casing of the font filename. Font-Awesome.min.css is not the same as font-awesome.min.css and your new server may care about that.
Koda
I installed a DNN skin which comes with several templates. Now these templates share the same footer for example: contact us, gallery, about us etc. . .
Is there a way where I can make these modules all share the same content using different templates? I am importing about 7 templates in the website but when I can the content of one of the footers the others content is not changed. Any Ideas on how I can link these together so in the future when I need to change something all of them follows?
You can share content across pages in DNN using the "Display On All Pages" setting in the module settings.
1) Install a module into the Footer on ONE page.
2) Configure the Module Settings for that module to "Display On All Pages"
3) Done
Any changes made to the module, should reflect across all pages. It won't matter which page you make the change on either.
Note: Modules that are set to display on all pages will attempt to load in a PANE of the same name, so if your "layouts" all have a FooterPane, the module will appear there. If you have any layouts that don't have a FooterPane, the module will appear in the ContentPane of that page.
Deleting a module from one page is possible through the module Actions.
To remove the module from all pages, you have to go to the Module Settings, and unselect the Display On All Pages option. The module will then remain on THAT page, but not on any other pages.
All the "deleted" modules (after unselecting Display On All Pages) will be in the Admin/Recycle Bin
I searched...can't find any good references. I have what I think is a pretty simple question: What are the basic concepts behind a system that allows customers to specify and generate a website, from a choice of style templates?
Say for example I created a simple website consisting of four static HTML pages. I can make those pages look like anything I want by using different CSS templates...good.
But if I wanted to give my clients an interface that says "hit this button and your site will be generated" -- I don't know what the basics are underneath that idea to make it happen. Is it simply a matter of creating the directories and copying files?
Before I go down a dumb path I just need some general guidance about how this type of thing is usually done. There are notable services out there that offer people the ability to sign up for an account, and in "three easy steps" generate a simple website. I want to learn the theory and basics behind how that is done.
Thanks...
EDIT:
I know how to change an existing set of static HTML pages using CSS. What I want to do is build a true website generator. You log into my system, pick a theme, hit a button and your site (e.g. www.foo.com or foo.parentsite.com) is ready to use. I can figure out how to allow customers to change content -- by integrating tinyMCE for example. I just need the basic concepts behind the "hit a button...generate a new site" idea.
You can change with javascript the css used. This will change the looks of the current page.
But you need to make multiple css with an unique look.
I suggest you to make a generic css and add the theme of your site into a small css.
The small one should contain only what is unique with this theme.
generic.css => Place content,menu, footer, etc...
theme1.css => Change background color to red, change text color to blue, etc
theme2.css => Change background color to blue, change text color to blue, etc
theme3.css => Change background color to blue, change text color to red, etc
JQuery Ui allow to change his interface easily.
Check this and change selected gallery on left
I don't think you can generate an website than customer will be very satisfy.
There's always something than client want to change.
EDIT:
You need to create folder on the server.
Put all necessary file with his selected themes into the folder
Configure apache for his domain. Then reload it for the new config.
I suggest you to use PHP or cgi.
The thing I don't know how is to register the domain if available and how to redirect his domain to your ip easily and automated.
Found something else tonight: There is a full set of APIs that can be used to gain access to cPanel functionality. So, almost literally, using their PHP wrapper it looks like only a few lines of code to instantiate a subdomain, set up email accounts, domain pointers, etc.
Looks promising...but being a total noob I have a lot of reading to do...
I tried creating a new theme in Magento by creating the following folders:
/app/design/frontend/interface/default
/skin/frontend/interface/default
I copied into these folders the entire content of the base/default folders (in both skin and design).
I enabled the theme bu putting "interface" in "current package name" for a website and expected it to look like the theme I had copied, but for some reason, nothing in the head is loaded. No css, js, ...
I checked and all my xml/css/js files are all there though ... What might the problem be?
The .phtml files are all being loaded.
EDIT:
I also noticed that selecting "base" as default package does not work either, but if you select "default", then it does load the base theme phtml files with some base and soem default css ...
EDIT2
Fixed, not sure where the error was ...
Did you refresh the caches?
On development stations its good practice to disable all Magento caches, until everything works, because sometimes it's really easy to forget to refresh them.
Magento have a structure, its better to put your custom magento theme design folder into app/design/frontend/default/themename this is PHTML path and for CSS and JS you can put the folder in skin/frontend/default/themename
After that just delete the cache and enable the theme from either admin > system > configuration > design or from admin > system > design and select you custom magento theme