please move style call to header

[durangod]

So far with several tests this has worked fine when i moved this to the header instead of in the orderforms tpl file. It really needs to go in the header tpl file to pass w3c standards.

 

<link rel="stylesheet" type="text/css" href="templates/orderforms/{$carttpl}/style.css" />

<link rel="stylesheet" type="text/css" href="templates/orderforms/{$carttpl}/uistyle.css" />

 

$carttpl is alive and well in the header load..

 

if i find any issue where it does not work and needs to stay in the tpl file i will let you know but please work with us to pass w3c, it is important.

 

might i also suggest that you add to your testing phase the process of running the pages thru the w3c validator to save us some work..

 

ps, im not trying to be a smarty pants here or mean or sarcastic or anything here so dont take it that way please, im just stating a fact thats all But please dont reply with "we are redoing the whole userside template deal" honestly i have heard that for almost 3 years now and to this day i am still having to change the view cart form, from percent to size on the inputs because it is wacked out of the box.

 

I assume that you are working on stuff and i can appreciate that. However all you have to do is load the view final cart (final order page, where they can register as well) in portal to see how wacked out it looks because the inputs wrap the page. Its because you set them at 80% and then i go in and set them to size 25 or size 30 every time i upgrade and remove the 80% and they are fine. lol

 

But aside from that all we are asking is that you work with us to help us all pass w3c....

 

Thanks so much.

Edited July 16, 2014 by durangod

[durangod]

list of files i changed and moved link style to header and works fine

 

orderforms/comparison/products.tpl

orderforms/comparison/configuredomains.tpl

orderforms/comparison/domainrenewals.tpl

orderforms/comparison/viewcart.tpl

orderforms/comparison/configureproductdomain.tpl

orderforms/comparison/complete.tpl

orderforms/comparison/configureproduct.tpl

orderforms/comparison/addons.tpl

orderforms/comparison/adddomain.tpl

orderforms/comparison/login.tpl

orderforms/comparison/error.tpl

orderforms/comparison/fraudcheck.tpl

 

the main reason we have headers is the same reason we now use css, so we do not over duplicate calls or process.

Edited July 16, 2014 by durangod

[Infopro]

Suggestions on making the product better, belong on the Feature Requests site.

 

...please work with us to pass w3c, it is important.

 

Not so much, really. WHMCS isn't plain HTML and CSS like your old site was.

 

Show us how you're validating and finding the errors you mention.

[durangod]

http://validator.w3.org/

 

I agree it is not, but the same basic standards still apply. When i see basic stuff and basic standards that have not changed even with the evolution of coding, it still applies just as it does regardless of what kind of car you love, the wheels are still always on the bottom lmao hee hee..

 

The header file is there to do basically one thing, to load all the stuff you need (outside of the page content itself) for the page parse so why not put it where it belongs lol

 

The main reason that we are having to code for three different browsers or more is because it was never standardized in the first place. So i do believe that w3c is very important for all of us.

 

It actually does not go in the feature requests IMO, technically its a bug and should go in the bug reports.

Edited July 16, 2014 by durangod