Thread

Most of my blog entries are formatted differently now—my typeface is gone and is replaced with what I guess is default browser typeface, and line spacing is weird in places… and more. 

I gather this is happening because my blog entries use things like font size=“3”, which I guess I shouldn’t have been doing; but my entries are pretty much unchangeable now, as I have thousands of them which can’t be changed with a find/replace database operation because they’re all different… 

Can anyone help me get the formatting back in my site?  It looks totally ridiculous and I can’t even keep it online the way it is.  In places, it’s unreadable.  I get thousands of visits per day… this is not good for me…

Do I need to revert back to 1.6.4?

Do you’ve got a link to the site, where we can see for ourselves? Moving to Tech Support.

Ingmar did you know your inbox is full?  I wanted to send my URL privately.

Ingmar prefers to use email, thus pm’s are disabled.  Note the MSG button rather than the PM button.

You can pm over to me.  And in the meantime- in the weblog settings for the relevant weblogs- in ‘Admin- Weblog Admin- Weblog Management’ what are your allowed html settings?  If it’s not ‘Allow all’ might try flipping to that and see if it makes a difference.

OK I see where there is a newer (20081028) build of 1.6.5 now, so I uploaded the core.typography.php file from that, seeing as there is a note in the updated log file indicating a bug in typography —and that seemed to fix half my problems.  My font face returned, but the line spacing still wasn’t right…

I have been using HTML like <font size=“3”> in blog entries, and I find when I change them to <span [removed]> then things work better.

Your suggestion causes my YouTube file codes to display in text, among other things. I embed a lot of YouTube videos.

Greetings DeltaJo!

Can you please PM or Email a link to your site over to us, as well as posting some example template code so we can help you get this sorted out.

Thanks!

-greg

Hi Greg!

As I mentioned I’ve managed to more or less sort it out to some extent on my own.  It’s a politics web site so I had to work fast. 

I’ve changed my last few blog entries to eliminate font size= tags and replaced them with span style= tags.  I guess anything I was using that is deprecated in HTML 4.01 is deprecated to the point where it no longer works in the latest build of EE. 

I don’t know what I’m going to do with my older blog entries.  I haven’t even looked at them yet. 

I’m not sure what template information you want.  Could you be more specific?  I don’t feel like I’m having a template issue.  I did set up a separate new install of 1.6.5 using the default theme/template set just to test whether something I mangled in my live site could be an issue, but got the exact same results, using blog entries copied from my live site to that site.  Similarly, when I uploaded the new core.typography.php file and changed some of my font size= and other tags to span style= tags in that test setup, it fixed most problems. 

I’ll MSG my URL to you and others.

For what it’s worth, I’ve noticed I now also have a problem with any IMAGE files that contain two (or more) dashes in the file name, like this:  “filename—001.jpg” (OK I see in the preview of this post that two dashes are replaced by an EM dash here, but it’s in files which use the -  character twice in a row).  The images don’t appear on the blog’s pages because the two dashes are replaced by % E 2 % 8 0 % 9 4 (I added spaces between each character because again I saw in the preview that the string was replaced by an EM dash) in the output code.  One dash works in file names,  two or more don’t, strangely enough. 

And another thing:  blog entries which use the <strike> tag are now formatted weirdly (one line break is added before and one after the affected word or words).  This was much the same kind of problem I was having with 1.6.5 regarding the font size= tags I have used throughout my blogging career.  I imagine the same thing will occur with the <u> tag.

I guess anything I was using that is deprecated in HTML 4.01 is deprecated to the point where it no longer works in the latest build of EE.

No, that shouldn’t be the case. EE as such is totally markup agnostic, so you can use whatever flavor of HTML you like, from XHTML Strict to browser specific tag soup (not suggesting you do any of the kind, just giving an example).

I’ll MSG my URL to you and others.

Personally, I would like to get a permalink to an article that you feel displays wrong after the upgrade, which was showing fine before.

Joel- I have the link and am poking around now.  EE’s tweaked typography class should leave your font size alone- and treat it as an unknown block level element.  I’m poking around the site to try and double check that’s the case.

I’m also going to try to replicate the file issue.  To do so, I’ll upload a new file with two consecutive dashes in the name.  Then- how are you making the image links- pm code, html- can you try to paste a copy of exactly what you’re putting in the entry that’s getting messed up?  If the forum won’t allow you to post it exactly like you’re doing on site, try putting it in a text file, zipping and attaching.

I have now created two new installs of EE, each one using the default style sheet/theme etc.  One install is 1.6.4, the other is 1.6.5. 

I created an identical blog entry for each, using some of the elements I’ve discussed here.  You can clearly see how in 1.6.4, the blog entry presents itself perfectly.  But in 1.6.5, it is mangled. 

I will send you the URLs privately.

P.S. to Robin: I usually use the EE pm code to upload and place image files.  I’m not sure that makes a difference though.

Thanks for your patience, Deltajo.  The transformation of the image was a bug, for which a fix is now in.  I’ll drop you an email with some details.

As for the font- that’s expected behavior now.  Basically, EE has a list of elements it will treat as ‘inline’ for xhtml processing (in core.typography.php it’s $inline_elements).  Tags that were deprecated with HTML 4.01 aren’t included, thus EE isn’t treating them as ‘special inline elements’.  Hence the difference.