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 Development / 
  3. XOOPS Core Hacks 
  4.  / Let's make XOOPS valid xhtml1.0 transitional!
Register
21
Herko
Re: Let's make XOOPS valid xhtml1.0 transitional!

  • 2005/4/5 17:04

  • Herko

  • XOOPS is my life!

  • Posts: 4238

  • Since: 2002/2/4 1


Wanikoo has indeed shown a lot of initiative and skills in helping Mithrandir (and others) out, his PM hack is one of the things that is on the list to be added to XOOPS 2.1/2.2.

Again, not disqualifying Wanikoo but giving more information on our policy, one of the citeria we have for the Core Development Team is the ability to work as part of a team. I suggest Wanikoo joins as a virtual member so we can examine his team player qualities as well as his programming skills Then who knows, if Wanikoo still wants to work with us loonies he might become a core developer.

Herko
22
artigas
Re: Let's make XOOPS valid xhtml1.0 transitional!

  • 2005/4/5 20:34

  • artigas

  • Quite a regular

  • Posts: 208

  • Since: 2004/12/21


Greetings -

Would that mean that the index.html that is used as a place holder in directories would be changed

from
<script>history.go(-1);script>

to
<script type='text/javascript'>history.go(-1);script>

or would there be some additional changes needed to make it fully compliant to strict?

Thanks In Advance.
23
artigas
Re: Let's make XOOPS valid xhtml1.0 transitional!

  • 2005/4/5 21:11

  • artigas

  • Quite a regular

  • Posts: 208

  • Since: 2004/12/21


Greetings -

I actually answered my own question. Here is what I found goes through the validator.

DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> 
<html><head><title>Go Backtitle>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<script type="text/javascript">history.go(-1);script>
head><body>body>html>

Hope That Helps.
24
wanikoo
Re: Let's make XOOPS valid xhtml1.0 transitional!

  • 2005/4/6 7:13

  • wanikoo

  • Not too shy to talk

  • Posts: 129

  • Since: 2003/12/27


Quote:

artigas wrote:
Hope That Helps.

Thanks a lot!!
Quote:

Gambero wrote:
Why isn't wanikoo in XOOPS Core development Team ?
......
And like you said he just need to ask. So, wanikoo: ASK!

Gambero, you are so generous!
but...my answer is "NO...more exactly NOT YET"
because I don't have enough skill and experience yet.
but
I will continue to develop myself more and more....for D-day(--;;)

Umm..
Anyway..
It's off the topic^^;;
25
Shine
Re: Let's make XOOPS valid xhtml1.0 transitional!

  • 2005/4/6 8:06

  • Shine

  • Just can't stay away

  • Posts: 822

  • Since: 2002/7/22


Quote:

wanikoo wrote:
Quote:

Gambero wrote:
Why isn't wanikoo in XOOPS Core development Team ?
And like you said he just need to ask. So, wanikoo: ASK!

Gambero, you are so generous!
but...my answer is "NO...more exactly NOT YET"
because I don't have enough skill and experience yet.
but
I will continue to develop myself more and more....for D-day(--;;)


I understand your hesitation about becoming one of the core developpers. But, looking at your input..... how about the suggestion Herko made at you Wanikoo?
Quote:
I suggest Wanikoo joins as a virtual member so we can examine his team player qualities as well as his programming skills

I think this would be a nice 'in between step' for you! Sometimes people underestimate their own skills and experiences. By becoming a virtual coremember the devteam can examine your skills, experiences and teamplay. By following this roadmap you continue your personal development also

Grtz., Shine
26
MrWiseman
Re: Let's make XOOPS valid xhtml1.0 transitional!

  • 2005/4/6 8:30

  • MrWiseman

  • Just popping in

  • Posts: 3

  • Since: 2005/4/1 8


Um... excuse me. Why do you need to make it XHTML compilant? What users need when browsing a site is not the latest, furious standard compilance, but a fast, minimalist, non-bloated HTML. Ever noticed how Google is so blazingly-fast? Take a look at the HTML you're receiving - this is one of the reasons. XOOPS could implement a filter to optimized HTML by replacing all these
by
, remove , , etc., get rid of double spaces (CR and LF are also spaces), and so on, if you want it to be faster.
27
wanikoo
Re: Let's make XOOPS valid xhtml1.0 transitional!

  • 2005/4/6 8:47

  • wanikoo

  • Not too shy to talk

  • Posts: 129

  • Since: 2003/12/27


------------------------------------------
pages which gives us "already defined ID error"
------------------------------------------
Quote:

An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hock for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).


ex)
XOOPS 2.0.10 RC
----------------page start
~~~
form1(with token1)
form2(with token2)
form3(with token3)
~~~
form#(with token#)
~~~
-----------------page end

rendered like this
----------------page start
~~~~









~~



~~~~
----------------page end

same name, same id
so
this kind of page gives us some error message during validation check!

error message:
ID "XOOPS_TOKEN_REQUEST" already defined

ex) edituser.php in case of ($op == 'avatarform')

$form = new XoopsThemeForm(_US_UPLOADMYAVATAR, 'uploadavatar', 'edituser.php', 'post', true);

$form2 = new XoopsThemeForm(_US_CHOOSEAVT, 'uploadavatar', 'edituser.php', 'post', true);

rendered like this
$form:

$form2:


same name and same id!!

error message:
ID "uploadavatar" already defined

Umm...
as you know,
when rendering,
id is determined like this.
-------
name='".$this->getName()."' id='".$this->getName()."'
------
I mean XOOPS form classes do have member variable,$_name but don't have member variable,$_id !!
in most case, it's OK!
but in some case mentioned above, it can cause error when validation check!!
Umm..
To avoid this trouble,
(At my first thought)
we may..need new variable, $_id and and new member function, getID()
because if we have them, we can designate different ID value to each case.
(especially in the case that $_id is not empty....)

------------------------------
After this modification,
we can get this message, "This Page Is Valid XHTML 1.0 Transitional!" from W3 validator.


-------------To be continued-----------
28
giba
Re: Let's make XOOPS valid xhtml1.0 transitional!

  • 2005/4/6 9:25

  • giba

  • Just can't stay away

  • Posts: 638

  • Since: 2003/4/26


@hello wanikoo
One off for you, rss

Quote:

------------------------------
After this modification,
we can get this message, "This Page Is Valid XHTML 1.0 Transitional!" from W3 validator.
-------------To be continued-----------


I am following daily this topic.
Every day already I come fast here to see if we have more new features.
It is certain of that we are using to advantage to correct many things nivel of validations therefore these its tips had opened our eyes for much thing that can and must be modified with urgency.

Thanks

in portuguese for my people.

Estou acompanhando diariamente este tópico.
Todos os dias já venho rapidinho aqui para ver se temos mais novidades.
Tenha certeza de que estamos aproveitando para corrigir muitas coisas a nivel de valida??es pois estas suas dicas abriram nossos olhos para muita coisa que pode e deve ser modificada com urgência.

Obrigado
29
wanikoo
Re: Let's make XOOPS valid xhtml1.0 transitional!

  • 2005/4/6 19:56

  • wanikoo

  • Not too shy to talk

  • Posts: 129

  • Since: 2003/12/27


----------------------------------------------------
pages which give us "Error:required attribute not specified"
----------------------------------------------------
Quote:

In an attribute declaration, #REQUIRED means that the attribute must always be provided, #IMPLIED that no default value is provided. [Definition: If the declaration is neither #REQUIRED nor #IMPLIED, then the AttValue value contains the declared default value; the #FIXED keyword states that the attribute must always have the default value. If a default value is declared, when an XML processor encounters an omitted attribute, it is to behave as though the attribute were present with the declared default value.

Refer to this page:
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd
( Just search/find with keyword, "#REQUIRED"

ex)
1) required attribute "alt" not specified
----------------------------

%attrs;
src %URI; #REQUIRED
alt %Text; #REQUIRED
name NMTOKEN #IMPLIED
longdesc %URI; #IMPLIED
height %Length; #IMPLIED
width %Length; #IMPLIED
usemap %URI; #IMPLIED
ismap (ismap) #IMPLIED
align %ImgAlign; #IMPLIED
border %Length; #IMPLIED
hspace %Pixels; #IMPLIED
vspace %Pixels; #IMPLIED
>
--------------------------

in case of admin.php

From:

To:


To fix this,
open /html/include/cp_functions.php,
and add attribute "alt"

2) required attribute "action" not specified
-----------------------------

%attrs;
action %URI; #REQUIRED
method (get|post) "get"
name NMTOKEN #IMPLIED
enctype %ContentType; "application/x-www-form-urlencoded"
onsubmit %Script; #IMPLIED
onreset %Script; #IMPLIED
accept %ContentTypes; #IMPLIED
accept-charset %Charsets; #IMPLIED
target %FrameTarget; #IMPLIED
>
---------------------------

/html/misc.php
line 86

To:



--------To be continued---------------
Quote:

Giba wrote:
I am following daily this topic.

^^;; What a pressure!!
30
wanikoo
Re: Let's make XOOPS valid xhtml1.0 transitional!

  • 2005/4/11 15:35

  • wanikoo

  • Not too shy to talk

  • Posts: 129

  • Since: 2003/12/27


XHTML 1.0 Transitional or XHTML 1.0 Strict ??
( or XHTML 1.1.....lol )

Umm...
I think lots of modification needed to make XOOPS valid xhtml1.0 Strict !

Quote:

from:
http://www.zvon.org/xxl/xhtmlReference/Output/comparison.html

Following transitional elements were removed from the Strict XHTML:
applet, basefont, center, dir, font, iframe, isindex, menu, noframes, s, strike, u.
--------------------------------------------------------------------------------
Following attributes were removed from the Strict XHTML:
Attribute alink is forbidden on body.
Attribute background is forbidden on body.
Attribute bgcolor is forbidden on body, table, td, th, tr.
Attribute border is forbidden on img, object, it can be used on table.
Attribute clear is forbidden on br.
Attribute language is forbidden on script.
Attribute link is forbidden on body.
Attribute name is forbidden on form, img, it can be used on a, button, input, map, meta, object, param, select, textarea.
Attribute noshade is forbidden on hr.
Attribute nowrap is forbidden on td, th.
Attribute start is forbidden on ol.
Attribute target is forbidden on a, area, base, form, link.
Attribute text is forbidden on body.
Attribute type is forbidden on li, ol, ul, it can be used on a, button, input, link, object, param, script, style.
Attribute value is forbidden on li, it can be used on button, input, option, param.
Attribute vlink is forbidden on body.


mambo : XHTML 1.0 Transitional
xml version="1.0" encoding="iso-8859-1"?>



Official Demonstration Site - Home




    
    



xoops : XHTML 1.0 Transitional
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="en" lang="en">
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1" />
<meta http-equiv="content-language" content="en" />
<meta name="robots" content="index,follow" />
<meta name="keywords" content="XOOPS, news, technology, headlines, xoops, xoop, nuke, myphpnuke, myphp-nuke, phpnuke, SE, geek, geeks, hacker, hackers, linux, software, download, downloads, free, community, mp3, forum, forums, bulletin, board, boards, bbs, php, survey, poll, polls, kernel, comment, comments, portal, odp, open, source, opensource, FreeSoftware, gnu, gpl, license, Unix, *nix, mysql, sql, database, databases, web site, weblog, guru, module, modules, theme, themes, cms, content management" />
<meta name="description" content="XOOPS is an extensible, OO (Object Oriented), easy to use dynamic web content management system written in PHP. XOOPS is the ideal tool for developing small to large dynamic community websites, intra company portals, corporate portals, weblogs and much more." />
<meta name="rating" content="general" />
<meta name="author" content="XOOPS" />
<meta name="copyright" content="Copyright ?2001-2004, the XOOPS.org Project" />
<meta name="generator" content="XOOPS" />
<title>Official XOOPS Website - Powered by You!title>
<link href="https://xoops.org/favicon.ico" rel="SHORTCUT ICON" />
<link rel="stylesheet" type="text/css" media="all" href="https://xoops.org/xoops.css" />
<link rel="stylesheet" type="text/css" media="all" href="https://xoops.org/themes/default/style.css" />
<link rel="alternate" type="application/rss+xml" title="RSS" href="https://xoops.org/backend.php" />


<script type="text/javascript">

script>
head>


xaraya : XHTML 1.0 Strict
DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<base href="http://www.xaraya.org/ " />
<link rel="stylesheet" type="text/css" href="themes/xe1/style/combined_screen.css" media="screen" />
<script type="text/javascript" src="themes/xe1/scripts/nav.js">script>
<link rel="shortcut icon" href="themes/xe1/images/favicon.ico" type="image/x-icon" />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="Generator" content="Xaraya :: 0.9.11" />
<meta name="Keywords" content="" />
<meta name="Description" content="" />
<meta name="rating" content="General" />

<link rel="alternate" type="application/rss+xml" title="RSS" href="http://www.xaraya.org/?theme=rss" />
<link rel="alternate" type="text/html" title="Print" href="http://www.xaraya.org/?theme=print" />
<link rel="EditURI" type="application/rsd+xml" title="RSD" href="http://www.xaraya.org/index.php?module=xmlrpcserver" />
<link rel="pingback" href="http://www.xaraya.org/ws.php" />
<link rel="Top" type="text/html" href="http://www.xaraya.org/" />
<link rel="Parent" type="text/html" href="http://www.xaraya.org/" />
<link rel="author" href="mailto:info@xaraya.com" />
<link rel="contents" type="text/html" href="http://www.xaraya.org/index.php/articles/map/" />
<link rel="search" type="text/html" href="http://www.xaraya.org/index.php?module=search" />

<title>
Xaraya :: Welcome            title>
<script type="text/javascript" src="http://www.xaraya.org/modules/tinymce/xartemplates/includes/tinymce/jscripts/tiny_mce/tiny_mce.js">script>
<script type="text/javascript">
tinyMCE.init({mode : "specific_textareas",theme : "advanced",document_base_url : "http://xaraya.com/",content_css : "http://xaraya.com/themes/xe1/style/xareditor.css",width : "200%", height : "450px", plugins : "emotions,zoom,preview,ibrowser,advlink,advhr,advimage,searchreplace,print,table", ask : "true",inline_styles : "true", force_p_newlines: "true",theme_advanced_toolbar_location : "top", theme_advanced_path_location: "bottom", theme_advanced_buttons2_add : "preview,zoom,ibrowser,insertdate", theme_advanced_buttons3_add : "emotions,advhr,search,replace,print,tablecontrols", extended_valid_elements : "ul[style|*],li[style|*],ol[style|*],table[float|style|id|name],p[float|style|id|name],dd[*],dl[*],dt[*],code,pre,th[*],blockquote/quote,a[float|style|id|name|href|title|onclick], img[float|style|class|src|border=0|alt|title|h", directionality : "ltr",language : "en" });script>
head>


drupal : XHTML 1.0 Strict
DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<title>drupal.org | Community plumbingtitle>
<meta http-equiv="Content-Style-Type" content="text/css" />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<base href="http://drupal.org/" />
<style type="text/css" media="all">@import "misc/drupal.css";style>
<style type="text/css">@import url(http://drupal.org/modules/codefilter/codefilter.css);
<style type="text/css">@import url(http://drupal.org/modules/project/project.css);
<link rel="alternate" type="application/rss+xml" title="RSS" href="http://drupal.org/rss.xml" />
<style type="text/css" media="all">@import "themes/bluebeach/style.css";style>  
<script type="text/javascript"> script>
head>


for reference:

http://www.7nights.com/asterisk/archive/2004/04/xhtml-10-strict-not-ready-for-prime-time
http://liorean.web-graphics.com/xhtml/comparison.loose-strict.html
http://www.zvon.org/xxl/xhtmlReference/Output/comparison.html
http://www.sitepoint.com/article/standards-compliant-world
http://www.sitepoint.com/article/xhtml-strict-popups
http://www.w3.org/TR/2002/REC-xhtml1-20020801/DTD/xhtml1-strict.dtd
XHTML 1.1:
http://www.w3.org/TR/xhtml11/

PS:
My grandfather died a few days ago.
so...
I'm so depressed now.
« 1 2 (3) 4 5 »

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

232 user(s) are online (133 user(s) are browsing Support Forums)

Members: 0

Guests: 232

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