Dev Board => cpg1.4 Testing/Bugs => cpg1.4 Testing/Bugs: FIXED/CLOSED => Topic started by: jriba on January 26, 2005, 03:13:18 am

Title: Re: Change Metas
Post by: jriba on January 26, 2005, 03:13:18 am
I'm not asking for support on CPG 1.4, I just want to point something out that is related to this thread.

I downloaded CPG1.40 from this thread:, as per this thread:

and on CPG 1.40 (BETA), on the HARDWIRED theme, the {META} tag on template.html was 'outside' of the <head> </head> tags.  Here's a copy/paste from template.html:

Code: [Select]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<meta http-equiv="content-type" content="text/html; charset={charset}">
<meta http-equiv="Pragma" content="no-cache">
<link href="themes/hardwired/style.css" rel="stylesheet">
<script src="scripts.js" type="text/javascript"></script><!--
$Id: template.html,v 1.11 2004/08/25 19:57:35 gaugau Exp $
<table cellspacing="0" cellpadding="0" width="778" align="center" border="0">

As per everything discussed on this thread, the {META} tag is supposed to be 'inside' the <head> </head> tags.

I have not downloaded the latest stable version of CPG 1.3.2 from SF, but if CPG 1.4 looks like this, then more than likely, template.html for Hardwired in CPG 1.3.2 will be the same.

What's going on?
Title: Re: Change Metas
Post by: donnoman on January 26, 2005, 03:50:35 am
The alpha that you downloaded from gaugau's post is NOT the most recent CVS version

Actually it's quite old as far as the development version goes. Notice that in your code listing it's still using HTML 4.01 Transitional.

The current CVS version of Hardwired is XHTML 1.0 Transitional and META's are in the right place.

Code: [Select]
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "">

<html dir="{LANG_DIR}">
<meta http-equiv="Content-Type" content="text/html; charset={CHARSET}" />
<meta http-equiv="Pragma" content="no-cache" />
<link rel="stylesheet" href="themes/hardwired/style.css" />
<script type="text/javascript" src="scripts.js"></script>
<!-- $Id: template.html,v 1.14 2004/12/31 05:38:20 donnoman Exp $ -->

If you seriously want to test 1.4 use a REAL cvs client, don't mess with the packaged releases unless they are VERY current.
Title: Re: Change Metas
Post by: Joachim Müller on January 26, 2005, 07:09:07 am
As development continues, you may find that the packages are outdated pretty soon - when encountering errors or possible bugs, you will have to make sure that you're using the most recent version of the files in the devel branch of the cvs.
Instead of using the development snapshot packages you're encouraged to check out the cvs anonymously; it will provide you with the most recent versions that exist

I think I have found a bug:
Please make sure you're using the most recent version of the file, [...]

Check for updates
The package will most probably not contain the most recent versions of all files (as development and bug fixing continues), that's why you should use the new version check tool (to be found in the "admin tools") to compare your local file versions with the repository on the webspace. Even the repository isn't up to date all the times though, but it should give you an idea what file versions to update - to get the most recent versions, you should check out the devel branch of the cvs.