51
ianez
Re: w3c compliance
  • 2008/11/20 19:37

  • ianez

  • Not too shy to talk

  • Posts: 188

  • Since: 2006/1/26


@sailjapan
keeping a community which support XOOPS in Italy, of more than 5000 users, and actvely working in XOOPS code evolution (as far as I can).. so I think at the moment I'm just volunteering enough

@ghia
in the normal XOOPS use that template is used just once... where did you saw it?
things just change if you use the clone feature in XOOPS 2.3.x or if you're using the multimenu blocks which repeat this ID in any default menù block.. as you just said in most cases it's just a problem of module developing.

Ian



52
ianez
Re: w3c compliance
  • 2008/11/20 12:54

  • ianez

  • Not too shy to talk

  • Posts: 188

  • Since: 2006/1/26


I totally agree with ghia..
every site should conform to those universal standard and hopefully every browser should respect them...
the whole web is full of sites showing the w3c compliance icon as a flag of quality... but being validated by w3c don't make a site a good site .

Actually, except some minor details, ALL the xhtml and css generated by XOOPS is valid. More communication efforts should be taken to inform theme developers but above all module developers about standard markups for XOOPS and general lines for xtml+css compliance.
I suggest also, that more clear and rigid rules should be created in order to generate a kind of 'offical repository' containing only modules and themes that have w3c compliance, css templates (or clean table templates), accessibility features, adeguate compliance with XOOPS standards and Smarty.
that way developers will find their way to develop honest code, wich personally I prefer to cool graphics using non-standard or very messed code.

Ian




53
ianez
Re: editing xoops redirect messages
  • 2008/10/17 16:54

  • ianez

  • Not too shy to talk

  • Posts: 188

  • Since: 2006/1/26


it's just a language define...
search for the text string you're searching in the file of these folders folders:
- /language/yourlanguage
- modules/system/language/yourlanguage

Ian



54
ianez
Re: Theme messes up blocks. (could this be a 2.3 bug?)
  • 2008/10/17 7:59

  • ianez

  • Not too shy to talk

  • Posts: 188

  • Since: 2006/1/26


if the problem stays in xoops.css.. it should have been fixed before the 2.3.1 announcement as just suggested earlier..

happy your problem is solved

IAn



55
ianez
Re: Upgrading from 2.2.6 to 2.3 Themes Changes??
  • 2008/10/15 23:37

  • ianez

  • Not too shy to talk

  • Posts: 188

  • Since: 2006/1/26


you should add
display:block;

to your style.css for the ids 'usermenu a' and 'mainmenu a'

Ian



56
ianez
Re: Theme messes up blocks. (could this be a 2.3 bug?)
  • 2008/10/15 22:14

  • ianez

  • Not too shy to talk

  • Posts: 188

  • Since: 2006/1/26


first a question.. does it happen with the default XOOPS theme? and more.. can you peovide a screenshot of how things are messed up?
I suspect is a css problem

Ian



57
ianez
Re: Everything is centered in IE7
  • 2008/9/30 15:06

  • ianez

  • Not too shy to talk

  • Posts: 188

  • Since: 2006/1/26


phpkaox is really an old an not compliant theme..
anyway if you open the theme.html file you'll see plenty of <td> tag with the align="center" attribute.. so it should be enough to remove this attribute from the parent td of the center blocks..

concerning the strange symbol it's probably caused by an unparsed character you have before block titles.. did you hack this part? remember that 2.3 change the charset to utf-8.. so there's a chance to have non recognized character..

Ian



58
ianez
Re: [hack] - How to use Extended Xoops Dhtml Editor as default editor for all Xoops
  • 2008/9/10 23:41

  • ianez

  • Not too shy to talk

  • Posts: 188

  • Since: 2006/1/26


yes mamba,the 2.3 editor it's very good!
I'm actually deeply testing 2.3... the extended editor is great and in a few I'll release a little tutorial about how use the 2.3 powerful editor in 2.0.x installations.

Ian



59
ianez
Re: changing xoops basic editor
  • 2008/9/10 16:33

  • ianez

  • Not too shy to talk

  • Posts: 188

  • Since: 2006/1/26


well I've finally find the solution.
The basic dhtmlext.ph file need some hack to work,
I've made a small tutorial at this link

Ian



60
ianez
[hack] - How to use Extended Xoops Dhtml Editor as default editor for all Xoops
  • 2008/9/10 16:30

  • ianez

  • Not too shy to talk

  • Posts: 188

  • Since: 2006/1/26


This small hack is for using the useful extended dhtml editor as the defautl editor, instead of the normal one which is not very usable and for example don't let you select and then change the code on the fly.

It was not so easy to find the way but in the end, thanx to the big help of Lucio Rota (Thanx man!) I finally made it.

- First step
Download and install last official XoopsEditor class (version 1.21)
Download and install last official Frameworks pack (version 1.22)

Backup the original copies of following files:
/class/xoopseditor/dhtmlext/dxhtmlext.php
/class/xoopsform/formdhtmltextarea.php

- Second step
Open the file /class/xoopsform/formdhtmltextarea.php
Around line 74 change:
var $htmlEditor = array();

with:
var $htmlEditor = array('FormDhtmlExt','/class/xoopseditor/dhtmlext/dhtmlext.php');


This is for telling XOOPS to use that class for the textarea editing

- Third step
Open /class/xoopseditor/dhtmlext/dxhtmlext.php
Around line 37 you have to change this line:
$this->XoopsFormDhtmlTextArea($caption$name$value$rows$cols$hiddentext);

with this one:
$this->XoopsFormTextArea($caption$name$value$rows$cols$hiddentext);


This is for avoiding a server error probabyl caused by a php5 bug... thanx Lucio..

- Fourth step
Open /class/xoopseditor/dhtmlext/dxhtmlext.php
Immediatly after this line:
require_once XOOPS_ROOT_PATH."/class/xoopsform/formdhtmltextarea.php";
+
add the following code:
include_once XOOPS_ROOT_PATH."/class/xoopseditor/dhtmlext/editor_registry.php";

and uncomment this line:
//include_once XOOPS_ROOT_PATH."/Frameworks/textsanitizer/module.textsanitizer.php";

final result should be:
require_once XOOPS_ROOT_PATH."/class/xoopsform/formdhtmltextarea.php";
include_once 
XOOPS_ROOT_PATH."/class/xoopseditor/dhtmlext/editor_registry.php";
include_once 
XOOPS_ROOT_PATH."/Frameworks/textsanitizer/module.textsanitizer.php";


This hack is for having language properly displayed and special buttons as flash or youtube
(don't forget that you need to put your language file in class/xoopseditor/dhtmlext/languages/ if you want the buttons translated)

This should do the trick.
I've tested this on local and remote server whit XOOPS 2.0.18.1 installation with no errors.
Hope this will work for you

Ian




TopTop
« 1 ... 3 4 5 (6) 7 8 9 ... 12 »



Login

Who's Online

233 user(s) are online (156 user(s) are browsing Support Forums)


Members: 0


Guests: 233


more...

Donat-O-Meter

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

Latest GitHub Commits