XHTML 1.0 Strict

**Hostboard** · 12-22-2010, 11:34 AM

I was going to post this in osCMax Projects Discussion forum but seems I do not have the proper permissions

I figured I would take a shot and start converting some of the files to pass XHTML 1.0 Strict validation and wanted the coders blessing in my format as my goal will be to start converting files so they pass validation and hand them back off to the OSCMax project.

slideshow.php

Code:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="XHTML namespace"> 
<head>
<title></title>
</head>
<body>
<?php
/*
$Id: quick_links.php 3 2010-03-31 user pgm
  osCMax Power E-Commerce
  osCMax - osCommerce Maximized | osCmax shopping cart software
  Copyright 2010 osCMax
  Released under the GNU General Public License
*/
define('HEADING_TITLE', 'Slideshow');
define('TABLE_HEADING_SLIDESHOW_ID', 'ID');
define('TABLE_HEADING_SLIDESHOW_IMAGE', 'Slide Image');
define('TABLE_HEADING_SLIDESHOW_TITLE', 'Slide Title');
define('TABLE_HEADING_SLIDESHOW_LINK', 'Link');
define('TABLE_HEADING_SLIDESHOW_TARGET', 'Target');
define('TABLE_HEADING_SLIDESHOW_SORT_ORDER', 'Sort Order');
define('TEXT_SLIDESHOW_INSERT_INTRO', 'Please insert a new slide:');
define('TEXT_SLIDESHOW_TITLE', 'Slide Title'); 
define('TEXT_SLIDESHOW_IMAGE', 'Slide Image');
define('TEXT_SLIDESHOW_LINK', 'Slide Link');
define('TEXT_SLIDESHOW_TARGET', 'Target');
define('TEXT_SLIDESHOW_SORT_ORDER', 'Sort Order');
define('TEXT_SLIDESHOW_DATE_ADDED', 'Added: ');
define('TEXT_SLIDESHOW_LAST_MODIFIED', 'Modified: ');
define('TEXT_SLIDESHOW_DELETE_INTRO', 'Are you sure you want to delete this Slide Image? ');
define('TEXT_INFO_HEADING_NEW_SLIDESHOW', 'New Slide Image');
define('TEXT_INFO_HEADING_EDIT_SLIDESHOW', 'Edit Slide Image');
define('TEXT_INFO_HEADING_DELETE_SLIDESHOW', 'Delete Slide Image');
define('TEXT_INFO_EDIT_INTRO', 'Please edit slide details below:');
define('HEADING_NO_SLIDESHOW', 'No Slideshow available');
define('TEXT_NO_SLIDESHOW', 'Please click <b>Insert</b> to create a new slide for your slideshow. <br /><br /> Please also make sure you have set the slideshow settings <b>before</b> creating your slides to ensure that the images are the correct size for your store layout.');
?>
</body>
</html>

**michael_s** · 12-22-2010, 12:54 PM

Direct posting not allowed in the projects forum. You first have to create a project here:
http://www.oscmax.com/node/add/project-project

Once approved, the project gets a discussion thread in the forum.

As far as getting our blessing, you have mine. Most likely your formatting will be accepted as-is (from looking at the above example). I will have the others have a look as well, just for discussion. Hold off on going to work on this until the others have added their input to avoid any re-working.

**Hostboard** · 12-22-2010, 02:03 PM

Seems I do not have permission to start a project.
Access denied

You are not authorized to access this page.

Will wait to hear back...

**ridexbuilder** · 12-22-2010, 02:11 PM

This is currently outwith my area of knowledge, though thank you for bringing something to the community.
[Way back, it took me a few attempts to get a Project going.]

**michael_s** · 12-22-2010, 02:29 PM

Originally Posted by Hostboard

Seems I do not have permission to start a project.
Access denied

You are not authorized to access this page.

Will wait to hear back...

This problems seems to be part of the upgrade... we used to run vbdrupal which automatically integrated access to projects with your post count. Now that both drupal and vb are separate, there is not a shared login anymore.

Be sure you login to the drupal front end before trying to access that page. Once you login to the drupal site, you will see the Create Content links in the menu.

**pgmarshall** · 12-22-2010, 03:09 PM

I am delighted if you would like to help contribute to the osCmax code base. I have been putting quite a bit of work into squashing E_NOTICE issues and if you check the bugtracker you will see me trying to get all the pages in both admin and catalog to pass the W3C validator (although only for the less strict HTML).

My only concern would be mixing the XHTML and HTML formats within the store/admin ... but very happy otherwise. You should checkout the developers link as you will need to get yourself SVN access with posting rights.

Welcome on board.

Regards,

**michael_s** · 12-22-2010, 03:32 PM

Originally Posted by pgmarshall

I am delighted if you would like to help contribute to the osCmax code base. I have been putting quite a bit of work into squashing E_NOTICE issues and if you check the bugtracker you will see me trying to get all the pages in both admin and catalog to pass the W3C validator (although only for the less strict HTML).

My only concern would be mixing the XHTML and HTML formats within the store/admin ... but very happy otherwise. You should checkout the developers link as you will need to get yourself SVN access with posting rights.

Welcome on board.

Regards,

He will be working on a separate project, that when finished, we can incorporate into the core. Sorry I wasn't clear on that. This is a big project that I want to review and test carefully before committing to the repo, since it touches basically every file. It will serve everyone better if it is a separate project at the moment.

**met00** · 12-22-2010, 03:52 PM

while I am all for meeting standards, please understand that the way this beast is "built" is by a user making mods to the osCmax deliverable. While it would be great to say that 100% of all needs can be met by the core and that a user should only have to adjust the templates, that is generally the exception, not the rule. So, while I'm all for the deliverable meeting the xhtml standards, and I think that would be a good thing, I also think we should acknowledge that the reality of how open source is used (users modifying the code base at will) that just because we deliver xhtml complaint code doesn't mean it will ever really run that way, and we shouldn't lock the user community into a requirement of xhtml compliance.

Best of luck on the project.

**michael_s** · 12-22-2010, 05:26 PM

What the end user does is their business, and if they do not care that their site validates so be it. But I think it is important that we demonstrate our commitment to standards compliance by producing a core package that validates. This is no small task, I agree. It is however a worthwhile endeavor.

The logic here is that we do not want our core code to be the problem preventing validation/compliance. We want to promote good practices, and emphasize that we think clean compliant markup is important.

One major thing that this does is let the design community at large know we are serious about producing a package that is easy to work with and will not make them cringe when they look under the hood. It will encourage new, better template developers to start creating osCmax templates (which this community seriously needs). It is also a way to stand out in a crowd of non-validating osC-derived projects. osCmax will only benefit from this distinction.

**met00** · 12-22-2010, 08:30 PM

just because we deliver xhtml complaint code doesn't mean it will ever really run that way, and we shouldn't lock the user community into a requirement of xhtml compliance.

Michael, please note that my concern is "locking in the user community", not what WE do. As long as what we do doesn't in any way enforce a system on outside developers that they must follow to have a functioning application, I have no problem or concern with Hostboard's efforts. If it in any way enforces the standard on osCmax users/developers, then I would have a problem with that. I would hate to see osCmax lose good contribution development because the potential developer didn't code (or want to code) to strict xhtml compliance.

You said...

Hold off on going to work on this until the others have added their input to avoid any re-working

So, there is my input. Go forward, but don't lock out potential contributions or do anything that would enforce xhtml compliance that would turn a good idea for a contribution away.

XHTML 1.0 Strict

LinkBack

Thread Tools

XHTML 1.0 Strict

Re: XHTML 1.0 Strict

Re: XHTML 1.0 Strict

Re: XHTML 1.0 Strict

Re: XHTML 1.0 Strict

Re: XHTML 1.0 Strict

Re: XHTML 1.0 Strict

Re: XHTML 1.0 Strict

Re: XHTML 1.0 Strict

Re: XHTML 1.0 Strict

Similar Threads

oscommerce-2.2ms2 to XHTML

valid XHTML Catalog Side 2.3---is this mod compatible with--

Bookmarks

Bookmarks

Posting Permissions