Paged_archive addon and XHTML compliance

[puzzled]

Hope someone can help. I've searched the forum, but only found posts that were much older related to the validation issue. Since I have the latest version of the Pixelpost installation, I assume the included addons are updated since those older posts.

Am I doing something wrong or is there a problem with the paged_archive addon and XHTML? There are two problems I've found:

(1) If I use either of the tags with the drop-down box (<BROWSE_CATEGORIES_PAGED> or <BROWSE_MONTHLY_ARCHIVE_PAGED>), the validation error is always: there is no attribute "onChange".

(2) Apostrophes in any image title cause validation problems. I'm not sure if this is for specific tags or for all of them in the paged_archive addon.


***************************************
From my General Information page in admin:
You are running Pixelpost version: 1.6.0 (in the right direction) - April 2007
Host Info:
URL http://www.archerfoto.com/photoblog/admin/index.php
PHP-version 4.4.4 (Pixelpost's min requirement: PHP version: 4.3.0 )
Session save path /tmp
MySQL version 4.1.22-standard (Pixelpost's min requirement: MySQL: 3.23.58 )
GD-lib bundled (2.0.28 compatible) with JPEG support
File Uploads to Pixelpost site are possible.
Server Software Apache/1.3.37 (Unix) FrontPage/5.0.2.2635.SR1.2 mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 PHP/4.4.4 mod_ssl/2.8.28 OpenSSL/0.9.7a
EXIF Pixelpost is using exifer v1.5 for EXIF-information.

[Dennis]

Open the paged_archive addon file, look for the line that says

//from the thumbnail row. This could be build by tables too."

right after this line:
$title = pullout($title);
put this:
$title = htmlspecialchars($title,ENT_QUOTES);

[puzzled]

Thanks, Dennis! Even using the paged_archive addon, the browse page now validates as good XHTML.

Summary:
1. The "onchange" problem was solved by changing all five instances of "onChange" to "onchange" in paged_archive.php.
2. The apostrophe in titles problem was solved by editing paged_archive.php as you described in the post just above this one.

I really thought that these problems would've been solved by this final 1.6 version of Pixelpost, since the problem with onchange was mentioned in the forum a long time ago, and since the addon is included with v. 1.6. Anyway, I'm happy now that everything works great!

Please accept my humble request to have these changes fixed in version 1.7, or at least with some reference to this post in the instructions for using paged_archive.

[GeoS]

It was fixed in 1.7 a while ago. New version should be free from this bugs.

As it looks like clear now/solved then Im closing this topic.