XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk
  1. Board index / 
  2. XOOPS Community Support forums / 
  3. 2.4.x Support 
  4.  / Theme problem when upgrade to 2.4.4
Register
1
OldWen
Theme problem when upgrade to 2.4.4

  • 2010/1/27 17:12

  • OldWen

  • Just popping in

  • Posts: 5

  • Since: 2010/1/27


Hi,all...

When upgrade my site from 2.3.3 to 2.4.4,I find some css classes take no effect both in ie6 and firefox 3.6. The generated html source is ok, but when check the dom in Microsoft Expression Web 3 SuperPreview for Internet Explorer and Firebug,I find all meta tags,link tags and script tags go into part of the generated html file. In 2.3.3, everything goes well.

Does any one can help me? thanks!

Sorry for my poor english.
2
aph3x
Re: Theme problem when upgrade to 2.4.4

  • 2010/1/27 17:30

  • aph3x

  • Theme Designer

  • Posts: 834

  • Since: 2004/12/26


Let me see if i get this right...before upgrade, all meta, scripts and stuff were correctly in the head area...after the upgrade they were somehow moved into the body area?!

Its unlikely for that to happen because when you upgrade XOOPS (And any cms for that matter), it doesn't affects how your theme is coded unless its/or has same name with one of the default themes contained by the package so if your theme was a 3rd party one and NOT one distributed with the core, the upgrade process doesn't replaces files in your theme.

Long story short..unless its a default theme included in the upgrade package and files were rewritten on upgrade then it can't happen
3
OldWen
Re: Theme problem when upgrade to 2.4.4

  • 2010/1/27 17:47

  • OldWen

  • Just popping in

  • Posts: 5

  • Since: 2010/1/27


Thanks. I found a fresh install also has the same problem. The generated html sources seem ok,but same css classes no effect. When check the file dom in firefox firebug, metas ok but links and scripts moved to body area. In ie SuperPreview,all metas,links and scripts moved to body area.
4
aph3x
Re: Theme problem when upgrade to 2.4.4

  • 2010/1/27 17:55

  • aph3x

  • Theme Designer

  • Posts: 834

  • Since: 2004/12/26


If you can provide us with a link and even some screenshots of your code outputs it will be great
5
OldWen
Re: Theme problem when upgrade to 2.4.4

  • 2010/1/27 18:45

  • OldWen

  • Just popping in

  • Posts: 5

  • Since: 2010/1/27


For fresh install, the generated source:
?DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Transitional//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd'>
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="zh-CN" lang="zh-CN">
<head>
     
    
    
    
    <meta http-equiv="content-type" content="text/html; charset=UTF-8" />
<title>My Sitetitle>
<meta name="robots" content="index,follow" />
<meta name="keywords" content="service" />
<meta name="description" content="" />
<meta name="rating" content="general" />
<meta name="author" content="WEIXIN" />
<meta name="copyright" content="" />
<meta name="generator" content="XOOPS" />

<link rel="alternate" type="application/rss+xml" title="THEME_RSS" href="http://192.168.1.6/backend.php" />
<link rel="shortcut icon" type="image/ico" href="http://192.168.1.6/themes/zetagenesis/icons/favicon.ico" />
<link rel="icon" type="image/png" href="http://192.168.1.6/themes/zetagenesis/icons/icon.png" />
<link rel="stylesheet" type="text/css" media="screen" href="http://192.168.1.6/xoops.css" />
<link rel="stylesheet" type="text/css" media="all" href="http://192.168.1.6/themes/zetagenesis/css/layout-soup.css" />
<link rel="stylesheet" type="text/css" media="all" title="Color" href="http://192.168.1.6/themes/zetagenesis/css/style.css" />

<script src="http://192.168.1.6/include/xoops.js" type="text/javascript">script>
<link rel="stylesheet" href="http://192.168.1.6/language/schinese_utf8/style.css" type="text/css" />

    
    head>
<body id="system" class="zh-CN">
<div id="xo-wrapper" class="system">
...

It seems ok. But in firebug, dom structure looks like:
firebug output screenshot

If the link does not go to the screenshot,pls copy "http://dl.javaeye.com/upload/picture/pic/53869/fada0555-4210-3350-9f57-7f9d1aa9ee03.gif" to your browser address box.
6
aph3x
Re: Theme problem when upgrade to 2.4.4

  • 2010/1/27 19:14

  • aph3x

  • Theme Designer

  • Posts: 834

  • Since: 2004/12/26


I see what you mean, i just checked a zetagenesis "out of the box" version in firebug and all seems fine from my end and it is an upgraded version of system for many times since the 2.0.14 up till current version so umm i'd say at least 3 upgrades
7
bjuti
Re: Theme problem when upgrade to 2.4.4

  • 2010/1/27 19:15

  • bjuti

  • Just can't stay away

  • Posts: 871

  • Since: 2009/1/7 2


I see there url-s pointing at local host...

In screenshot i see that is under the body tag. Delete the theme, and try again.

under the closed tag must be tag.
8
aph3x
Re: Theme problem when upgrade to 2.4.4

  • 2010/1/27 19:18

  • aph3x

  • Theme Designer

  • Posts: 834

  • Since: 2004/12/26


Resized Image


And here's my screenshot
9
OldWen
Re: Theme problem when upgrade to 2.4.4

  • 2010/1/27 19:27

  • OldWen

  • Just popping in

  • Posts: 5

  • Since: 2010/1/27


It seems yours ok.It's strange!I made a new install and use theme zetagenesis(no modifications) ,when check it in firebug or ms superpreview,links and scripts moved to body area that make some css classes take no effect.

for ms superpreview:

http://dl.javaeye.com/upload/picture/pic/53871/448e1c7a-d935-39cb-936f-6e6c3555351b.gif

for firebug:

http://oldwen.javaeye.com/upload/picture/pic/53869/fada0555-4210-3350-9f57-7f9d1aa9ee03.gif


sorry. links does not work, copy the address to you browser and go...
10
ghia
Re: Theme problem when upgrade to 2.4.4

  • 2010/1/27 19:33

  • ghia

  • Community Support Member

  • Posts: 4953

  • Since: 2008/7/3 1


?DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Transitional//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd'>
In your first line there is a ? at the start.
Is that correct?
It should not be there. Possibility is that some (theme?) files are UTF-8 with BOM. Should be without!

Did you run the file check (see release notes)?
(1) 2 »

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

308 user(s) are online (199 user(s) are browsing Support Forums)

Members: 0

Guests: 308

more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Nov 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits