hello
 
Can you please convert the complete cart to 100% XHTML Complaint.
 
Presently it gives " Failed validation, 139 Errors" on the Demo Cart at "http://www.viart.com/php-shopping-cart-demo/"
 
The Doctype is not even entered.
 
Check here:
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.viart.com%2Fphp-shopping-cart-demo%2F&charset=%28detect+automatically%29& doctype=Inline&group=0

Hello,
 
We are currently working on W3C compliance issue and we are hoping that we will present the doctype statement for our shopping cart very shortly and make our shop W3C compliant.
 
As soon as it is done, we will make an announcement.
 
With kind regards,
ViArt Support Team

Hello Anjula
 
This is great news. Thanks alot for replying and informing the community on the status of moving Viart to a true 100% XHTML and tableless design.
 
I really cant wait for the update, I am beginning to think that I finally will go ahead with ViArt.
 
now only the Developer's API guide is left

Great news indeed!

Hello Anjula,
Could you give us some idea of what 'shortly' means? A week, a month, 6 months? Just roughly please.
Thanks

Hello
 
I think it will take some time as it is not a small feat to convert the present cart to 100% XHTML/CSS complaint.

This is the only thing putting me off right now because its a nightmare trying to customise something that is riddled with so many tables

Did Anjula or another dev mention tableless design elsewhere? All he promised here was W3C compliance, an obvious must for any page. However they might not be planning tableless design.
 
Our developers currently use ViArt, integrating it within the many site templates we designers pass along. Attempting to mix good code with tables has given them nothing but trouble. Forcing us to consider competing open source alternatives that offer better front end code. This is a real headache, and an issue that needs to be resolved quickly.

Hi,
 
Brook: > Forcing us to consider competing open source alternatives that offer better front end code
 
What would those competing open source options be? The only I can think of are OS Commerce which I don't consider anywhere close to what I see here with Viart, I want the ability to code myself, but also a company willing to lead the direction of the cart.
 
OS Commerce is a tangled nightmare of updates/edits (Hacks I would call them).
 
What else is out there?
-Brett

Magento is looking very impressive indeed but does not allow digital downloads and after sending an email to their development team im still waiting for a response a week later so here i am looking at Viart again. Sadly though its the templates and the difficulty in modifying them that puts me on the fence

Just wondering why you so complaining about tables. Sometime ago for one site I try the both ways:
1. first it was mainly tables structure
2. and later only divs structure
and I can say that for me tables structure sometime much much better then just divs.
 
And my opinion will be that it should be a good balance between using divs and tables rather than just saying that everything should be done with divs.

Monk, its all about the latest buzz of W3C Complaint sites.

Still can't understand - but what the problems with tables, as you still can be w3c complaint with tables.
 
Have I missed something?

Hi Guys,
I'm trying to sort out the validation issues with Viart HTML using Dreamweaver. I don't want customers seeing the "Done but with errors on page" in Internet Explorers status bar.
In Dreamweaver when u test HTML code u get 3 forms of error ie red => informational error, yellow= bad error and white=> future code change related error (eg font type)
Does the "Done but with errors on page" error relate to all 3 or just the yellow error ie what type of errors does Internet Explorer's "Done but with errors on page" pick up? I have also checked using W3C
Would love advice on how best to bug as issues such as {image_height) and such tags cause errors in dreamweaver MX 2008 & V8.
Thanks

Although I have customized my ViArt templates to be at least mostly css based, I have yet to come across a business client who was concerned about complete W3C compliance (or even heard of the W3C for that matter lol) - they are way more concerned about the profit potential of the cart. The W3C compliance issue more about minimizing the developer/designer's headaches when it comes to cross-browser compatibility and future browser releases IMO.

I am using Dreamweaver CS3 and have no problems with Viart.
 
However, I am an end user rather than a programmer and am not in the slightest concerned about things like W3C - as dani says - I am only doing this to make a profit and Viart does that for me handsomely

I am concerned about W3C CSS/XHTML compliance, and so are my clients. Our concern is not just a compliance issue, but also a customization issue. I'm assuming/hoping/praying that when Viart goes to full compliance, they address the issue of having code and templates separated to the extent that customization becomes a breeze.
 
I was just thinking wistfully of jshop, and how easy customization is. I chose Viart for the feature package. It was a hard decision, but one I'd like to make a no-brainer when Viart gets compliant.

Hello Anjula
 
Any updates on the implementation of XHTML complaincy ?
 
Its been 2 years now.

In the new version of ViArt shop we will provide W3C CSS/HTML 4.0 compliance.

Ohh, what a silent hard work You do in the background. Great!

It has been a very long time sisce your last update Viart...We are all looking for better seo friendly cardy including validiation, seo friendly images and so on...

They have said that in the new version.
 
I hope its the new release which would be in the beginning months of 2010