CSS changes after 7.01 upgrade ???

I've just recently finished the visual changes on our D7 site, using only 8 css files and some custom images. Now I'm thinking about upgrading to 7.01 but I'm concerned about losing things that I've worked on. Here are the 8 css files that I've been editing:

base/css/anchor.css
base/css/common.css
base/css/forms_adv.css
base/css/general.css
base/css/index.css
base/css/top_menu.css

modules/boonex/blogs/templates/base/css/blogs_common.css
modules/boonex/news/templates/base/css/view.css

Is it possible to simply replace just those 8 files after the upgrade, or will the upgrade have an effect on any of these that might ruin some of what's been done? Is it possible that the upgrade won't even touch those css files? My preferred method of upgrading would be via the admin panel, anyone have any experience with that particular option? Aside from the store/shopping cart functions our entire site seems to be working alright. On one hand I'd like to not have to worry about making the update at all, but on the other hand there've been a couple of hundred fixes .... making me think that any D7 really needs to be updated, right ???
We do have some Rayz Flash mods too and a couple of other minor tweaks (no flash promo for logged in members). Any thoughts from anyone about  an upgrade would be sincerely appreciated since I'm not big at all on SQL and PHP. (I can back up the SQL and the entire site though, that's not an issue).

Quote · 29 Apr 2010

That's why I told you several weeks ago NOT to make css changes in the base directory.  You should do it from the template directory.

I know, but when I tried to go back and undo some of those changes, followed by switching to the other template, my homepage and a couple of the other screens got totally screwed up. So I put everything back the way that it was and worked with the base/css. I don't really understand why that's a problem if I have copies of all of the files? Are you saying that an upgrade to 7.01 will actually replace all of those worked on files?
And if so, why couldn't I just dump my changed css files back into the base/css folder afterwards?

Quote · 29 Apr 2010

Good point houston.  Brilliant

sup
Quote · 29 Apr 2010

I haven't looked at them to see what the changes are... but I don't have to, because I made the changes in those files from my template/css/ folder.   That's why you don't change the base directory files....

Geeez, this is just confusing the crap outta me ....
I thought that base und uni were two completely separate templates, working independently of one another?
The whole reason why I started working with template/base/css files is because I searched for answers like you're supposed to, coming across numerous posts where some of the answer read change this in base/css/blahblahblah file or change that in base/css/blahblahblah file. I never read anything about making changes in UNI or anywhere else ... ???

Where specifically (path & folder) are you making your changes? After you told me to butt out of base, I went ahead and started replacing files in UNI. That's how I got those pages messed up which is why I switched back. Now I don't know what to do or what to change and I hate the thought of starting over from scratch after coming this far ... the site's pretty much done.

Quote · 29 Apr 2010

Uni is a template of sorts, the basic template.  Copy the uni to make your template file and add any changes in your template file.  The file will call all the /base/ variables and then change them in the template file before presenting.

Quote · 29 Apr 2010

Uni is a template of sorts, the basic template.  Copy the uni to make your template file and add any changes in your template file.  The file will call all the /base/ variables and then change them in the template file before presenting.

Well, I thought that's what I did last time? For example, I went ahead and took the base/css/common.css file that I had changed and placed it into the uni/css folder after first making a backup of the file that I was replacing there. But for some reason one or two of the files that I replaced caused the formatting to get messed up on the homepage. Should I instead just find the specific portions of the files that I edited in base and then insert those into the existing uni/css files (after first backing them up)?

Quote · 30 Apr 2010

Uni is a template of sorts, the basic template.  Copy the uni to make your template file and add any changes in your template file.  The file will call all the /base/ variables and then change them in the template file before presenting.

Well, I thought that's what I did last time? For example, I went ahead and took the base/css/common.css file that I had changed and placed it into the uni/css folder after first making a backup of the file that I was replacing there. But for some reason one or two of the files that I replaced caused the formatting to get messed up on the homepage. Should I instead just find the specific portions of the files that I edited in base and then insert those into the existing uni/css files (after first backing them up)?

That is where you went wrong. The common.css in the uni template is empty except for one line that imports the base css. The way your suppose to do it is make a copy of the ini template, change the name from uni to your name.

Then when you need to change css values you place it in your own common.css under the import line. This way it still holds the origional base settings, and the ones you put under the import line will over ride what was set by base.

I know its confusing. But once you work with it for a while, it becomes obvious.

https://www.deanbassett.com
Quote · 30 Apr 2010

RE:

Well, I thought that's what I did last time? For example, I went ahead and took the base/css/common.css file that I had changed and placed it into the uni/css folder after first making a backup of the file that I was replacing there. But for some reason one or two of the files that I replaced caused the formatting to get messed up on the homepage. Should I instead just find the specific portions of the files that I edited in base and then insert those into the existing uni/css files (after first backing them up)?

EDIT:

I should add, that after you've copied the content of all the css files that you changed into your new templates css files, you can edit those files to remove the css that you did not change, since it will be importing it from the base/css directory.  You should probably do this while the changes you've made are fresh in your mind, so that your new templates css files contain ONLY the css rules that you changed.  If you do this, six months in the future, you won't be staring at a css file, wondering which parts you changed, and parts that are the default.

Thanks a million houstonlively. That clarifies things.
Umh, did you actually think that none of my changes are documented ... Surprised

Everything I do is commented everywhere to avoid future problems with additional adjustments. Isn't that what the #### are used for ... LOL

Quote · 30 Apr 2010

Geeez, where's your sense of humor?
Didn't you notice the ... LOL ... at the end of the sentence? LaughingCoolInnocent

Quote · 30 Apr 2010

Page is not reading the extra css from new template..

--------------------------------------------------------------------

I have followed these instructions

New template is tmpl_lworld

I get to the point of switch to your new template in admin to lworld.  Clear the /cache folder and your browser.

I have not made any changes yet to any of the CSS files in tmpl_lworld and my site looks perfect.

Then I went to tmpl_lworld/css/common.css and added

body {
font-size:12px;
background-color:#ECECEC;
background-image: url(../images/lbdbg.png); 
background-repeat: no-repeat; 
padding:0 0 20px 0;   
}

so it looks like

@import url(../../base/css/common.css);

body {
font-size:12px;
background-color:#ECECEC;
background-image: url(../images/lbdbg.png); 
background-repeat: no-repeat; 
padding:0 0 20px 0;   
}

Now it is not reading

body {
font-size:12px;
background-color:#ECECEC;
background-image: url(../images/lbdbg.png); 
background-repeat: no-repeat; 
padding:0 0 20px 0;   
}

Has no background color or background image. Its not reading the addition css I've added to the tmpl_lworld/css/common.css

Help would be appreciated.

Thank You

Jennifer

RE:

Well, I thought that's what I did last time? For example, I went ahead and took the base/css/common.css file that I had changed and placed it into the uni/css folder after first making a backup of the file that I was replacing there. But for some reason one or two of the files that I replaced caused the formatting to get messed up on the homepage. Should I instead just find the specific portions of the files that I edited in base and then insert those into the existing uni/css files (after first backing them up)?

This will get you started:

In your /templates directory, you will see a folder named tmpl_uni

Create a new folder in the /templates directory, and name it tmpl_SomeName   This directory name MUST begin with tmpl_

Copy all the files from the tmpl_uni directory to the new tmpl_SomeName directory that you just created

In your new tmpl_SomeName/scripts directory, Open the file BxTemplName.php file for editing

You will find the line:

$sTemplName = 'UNI';

Change it to reflect your new template name like this, and save:

$sTemplName = 'SomeName';

In the directory tmpl_SomeName/css  you will find all the css files that begins something like this:

@import url(../../base/css/categories.css);


What you can do, is copy and paste ALL of the css from the files that you changed, into the corresponding css file in your new template, below the first line, and below any existing css.   Do this for all the css files that you changed.


Once you're done, you can switch to your new template in admin.  Clear the /cache folder and your browser.  When your site loads, it should reflect all the changes you have made even when you replace the existing templates/base/css files

Then.... if you need to make any further css changes, just place the new css in the css files within your new template, and it will override the default css in the templates/base/css directory.

If you want to change the default css, you only need to change the specific css rule in your new template.  For instance, here's some css from templates/base/css/common.css

body {
font-family:Verdana,Arial;
font-size:11px;
color:#333333;
background-color:#ffffff;
margin:0px;
padding:0 0 50px 0;   
}

Let's say you want to change the background-color from FFFFFF to FFFFAA  in your new template.  You do NOT need to copy ALL of the above css to the common.css file in your new template.  You only need to add the specific css that you need to override.  You would only need to add the css below to your templates common.css file:

body {
background-color:#FFFFAA;
}

You new template will now use  #FFFFAA as a background color.   The same concept applies to every default css rule that you need to change.  This way, your new css files contain only your changes, and are much easier to manage.  And... you'll never have to worry about upgrading the default files again.

EDIT:

I should add, that after you've copied the content of all the css files that you changed into your new templates css files, you can edit those files to remove the css that you did not change, since it will be importing it from the base/css directory.  You should probably do this while the changes you've made are fresh in your mind, so that your new templates css files contain ONLY the css rules that you changed.  If you do this, six months in the future, you won't be staring at a css file, wondering which parts you changed, and parts that are the default.

Jennifer Bogan .. Acc. Dip. Psychology - EMAIL: jennifer.bogan@gmail.com
Quote · 31 May 2010

 

You should know by now, I have no sense of humor.

 You should be able to tell that by his over the top, Jack Nicholson 'One flew over the god damned cuckoo's nest' avatar

http://towtalk.net ... Hosted by Zarconia.net!
Quote · 31 May 2010

You should know by now, I have no sense of humor.

You should be able to tell that by his over the top, Jack Nicholson 'One flew over the god damned cuckoo's nest' avatar

I am not trying to be a wise guy Sky I have a problem I am asking help for.

Jennifer

Jennifer Bogan .. Acc. Dip. Psychology - EMAIL: jennifer.bogan@gmail.com
Quote · 1 Jun 2010

You should know by now, I have no sense of humor.

You should be able to tell that by his over the top, Jack Nicholson 'One flew over the god damned cuckoo's nest' avatar

I am not trying to be a wise guy Sky I have a problem I am asking help for.

Jennifer

I don't believe he was talking to you. Unless you have a wolf avatar, of course, then perhaps he is.

I'm not entirely sure what the cause of the problem is, but it would appear to be the fact that you're importing the contents of the base directory's common.css file before your custom code, which may be causing conflicts with the style sheets. Try adding the entire contents of the base directory's common.css file to your new common.css file and make the changes in there. And of course, what do I really know? I got that off a box of Frosted Flakes.

BoonEx Certified Host: Zarconia.net - Fully Supported Shared and Dedicated for Dolphin
Quote · 1 Jun 2010

Page is not reading the extra css from new template..

Your site doesn't seem to have a /templates/tmpl_lworld/  folder.   Either that, or the folder does not have public read permissions.  If this folder does really exist, make sure the permission is set to 755.

Hi houstonlively,

sits is a test site at http://lworld.com.au/goldengoose/ and just checked yes 755.


Regards

Jennifer

Jennifer Bogan .. Acc. Dip. Psychology - EMAIL: jennifer.bogan@gmail.com
Quote · 1 Jun 2010

In that case, you need to put a copy of lbdbg.png in the goldengoose/templates/tmpl_lworld/images/ folder.  Your template is looking for the background image in this folder, but it's not there.

Oh thank you so much that was so obvious and I still couldn't see it. Much appreciation!

Regards

Jennifer :)

Jennifer Bogan .. Acc. Dip. Psychology - EMAIL: jennifer.bogan@gmail.com
Quote · 1 Jun 2010

In that case, you need to put a copy of lbdbg.png in the goldengoose/templates/tmpl_lworld/images/ folder.  Your template is looking for the background image in this folder, but it's not there.

Oh thank you so much that was so obvious and I still couldn't see it. Much appreciation!

Regards

Jennifer :)

It's always the ones with the crazy-man avatars that know the solution.

BoonEx Certified Host: Zarconia.net - Fully Supported Shared and Dedicated for Dolphin
Quote · 1 Jun 2010

In that case, you need to put a copy of lbdbg.png in the goldengoose/templates/tmpl_lworld/images/ folder.  Your template is looking for the background image in this folder, but it's not there.

Oh thank you so much that was so obvious and I still couldn't see it. Much appreciation!

Regards

Jennifer :)

It's always the ones with the crazy-man avatars that know the solution.

Why do you think he's crazy?

Quote · 1 Jun 2010

In that case, you need to put a copy of lbdbg.png in the goldengoose/templates/tmpl_lworld/images/ folder.  Your template is looking for the background image in this folder, but it's not there.

Oh thank you so much that was so obvious and I still couldn't see it. Much appreciation!

Regards

Jennifer :)

It's always the ones with the crazy-man avatars that know the solution.

Why do you think he's crazy?

Crazy-man avatar is just how I like him and I wouldn't want him any other way. :P

Jennifer

Jennifer Bogan .. Acc. Dip. Psychology - EMAIL: jennifer.bogan@gmail.com
Quote · 1 Jun 2010
 
 
Below is the legacy version of the Boonex site, maintained for Dolphin.Pro 7.x support.
The new Dolphin solution is powered by UNA Community Management System.