CSS Quit Working

[fletch]

I've been using PP for about a week with no problems. Today I made a post with some description that had quotes(") in it. The CSS has quit working all together in IE and Firefox. I removed the description but still have the problem. I've uploaded the template and css file in ascii.

I've read all the forum posts about this and nothing works. I'm running 1.4.3.
Any advice is appreciated. My site is http://www.nodirectionhome.net

[jkn]

Seems to look fine on this end... is it a cache issue?

[fletch]

I've deleted the cache. It just doesn't format on my two pcs. The admin page is formatting ok.

[jkn]

I flipped through a number of your photos (very nice, by the way - love the waterfall and bridge shots) - all are maintaining the same formatting.

Quotes tripped up my formatting as well last night - Connie mentioned that 1.5 will fix that issue.

Clearing cache fixed my issue. I haven't been around PP enough yet to recommend something else.

[Connie]

well,
with IE it is not enough to clear the cache from inside the browser, as one user told us lately,

it was necessary to delete the files in the cache-directory from a filemanager...

could you try to find out where IE and FIrefox store the cache and whether there are some files left?

it is for sure a browser problem and not a problem of PP, as I can open your wonderful photos (with OPERA in the moment ), with FireFOx and with IE without problems

this red bird is wonderful! what great photos!

[photovernacular]

Fletch, I think I can see the root of your problem. You have the comments template tag in image_tempate.html wrapped in a span that is calling "addcomments" as a class. In your CSS you have this selector defined as an ID. The span will therefore never apply the "#addcomment" style. You need to either change the span attribute to id="addcomment", or change your CSS selector to .addcomment {}.

I think this correction might only get you one step on the way to correcting the problem. Testing it form my Firefox Web Developer extension, the style still seems to be out of whack. Think you will need to play with the style definitions for addcomments a bit.

Hope that helps. Shout if you find yourself still stuck!

-Tim

http://photovernacular.net/

[fletch]

Thanks for everyone's input.
I just took the entire comments html out of the image_template page and still no go. Very frustrating that others see it correctly, yet I have 2 computers with no CSS. The site worked fine until the last post, comments and all. Also I copied in the the original light.css and it still didn't find it. Guess I will just delete the entire site and rebuild it.

[Joe[y]]

don't delete your site! that's crazy. try updating to 1.5beta.

[fletch]

I upgraded to 1.5. When I first loaded the home page I had the same problem. However, because I am now using the default image_template, I had the light/dark css options at the bottom of the page. When I clicked on either light or dark, the CSS loaded! I guess I will have to leave those links on the page to get css to work. Thanks.

[photovernacular]

Fletch,
I had a similar problem to you after launching my site a few days ago. If you don't want to make the style switcher a feature of your site, you must either remove the <script> reference in your template files or comment out the lines of JavaScript that run when the page builds (it's easier just to delete the JS include SCRIPT tag from the HEAD section of the template!). Do this for all templates in your chosen site style.

What was happening in my case was that I replaced the 'simple' light.css file with a newly named one and referenced this in all my templates. However, the Pixelpost stylechanger script had set a cookie in my bowser that was referring to the old, nonexistant CSS file, and so the page was getting rendered without any style (for me).

I wonder if you might have this cookie set in your browser...? This would explain why others on the forum were reporting everything to be working fine. They wouldn't have had the styleswitcher cookie set and the browser would therefore be able to load the correct CSS.

-Tim

[fletch]

Tim,

That very well might have been the problem. I do remember deleting cookies but what you've described makes sense. I had a third computer which did not have the problem but the two I use every day did have it.

Thanks for your help,
fletch

[e300]

I was having the exact same problem - I have identified the REASON for this problem and I am currently working on a full fix for it.

The problem is that in the templates the following code is present:


<!-- META -->
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
<meta http-equiv="content-type" name="keywords" content="PhotoBlog,<SITE_TITLE>,<IMAGE_TITLE>,Pixelpost" />
<meta http-equiv="content-type" name="description" content="<SITE_TITLE>-PhotoBlog: <IMAGE_TITLE>, <IMAGE_NOTES_CLEAN>" />
<!-- CSS -->
<link rel="stylesheet" type="text/css" href="templates/simple/styles/light.css" title="light" />
<link rel="alternate stylesheet" type="text/css" href="templates/simple/styles/dark.css" title="dark" />
<!-- SCRIPTS -->


Now, when the page is rendered, the IMAGE_NOTES_CLEAN and/or IMAGE_TITLE has Quotes in it, actually breaks the page and the browser is not sure how to render it properly.

The simple solution is to remove the IMAGE_NOTES_CLEAN from the meta tag - the problem will be immediately solved.

I am working on a somewhat more complex solution so that there is no need to remove this from the template. This is not a simple bug that should be dismissed, but one that definately needs a bit of attention to put together a "proper" fix.

What I am working on, is to simply add a couple more template tags and a few extra lines of code as necessary to sort this all out.

This problem is evident in both 1.4.3 and 1.5B1


EDIT -
I have managed to fix this problem with a few lines of code - if one of the developers would like to contact me, I will provide them the solution I used to put this all together. I do not want to post the code here as it would only confuse those who do not fully understand what is going on with it.

[Connie]

please send your code by Personal Message to the developer of your choice, that is the best way!

send it to me for example ;=)

[e300]

I have been busy, but I have sent you the full details of the modifications that I did to correct this problem in PM. The only thing I did not do was to write the comment about the new tag I had to implement to go into the documentation, but it is pretty self-explanatory once you read what I have done.