X-Cart forums

[Steel]

Hello,

I have searched and studied the posts that seemed to be relevant, and gained some knowledge (as always). As the industry evolves, it seems that it renders old code obsolete.

I have HTML pages that have been created using FrontPage 2002. I am integrating many of these pages into X-Cart, or perhaps X-Cart into these pages. A test at the W3C Markup Validation Service site ( http://validator.w3.org/ ) yields many errors.

What are the best software tools to use to generate HTML pages? Dreamweaver? Will Dreamweaver facilitate correction of existing code, or is it better to start from scratch and compare the newly generated code?

Is the HTML Tidy cleanup generated code useable? It seems that it generates many reference lines near the head of the page. Is there a better option? Will UltraEdit (http://www.ultraedit.com/products/ultraedit/ultraedit_tour.html) help perform this task?

What is the best way to approach the code cleanup process?

Is XHTML, or some other code better to integrate with X-Cart?

Is there a best doctype to use?

I figure I might as well consider all my options before I finish the task. Any and all suggestions are welcome.

Thanks.

[balinor]

Start completely from scratch. Frontpage was an absolute DISASTER...fixing it will take you longer than starting over. Before you go too far though, why not just use the built-in embedded static pages to create all of your html pages?

[Steel]

Hello Balinor,

I have spent a lot of time considering using the various X-Cart formats, and modifying the format to suit our needs.

After much consideration, and trying several layouts we made the decision to stay with our existing format.

The issues were (1) that we wanted to have one picture and description for a product on the main price page, but then include line item price and order button listings for, say ... various finishes. I realize that this is possible, but it would be a challenge for me code wise. (2) Our existing layout for items on the main price page would vary, where some items would have the picture to the right of the description, while others would have the picture centered and above. (3) The load times for the X-Cart PHP pages seemed to average anywhere from 3 to 15 seconds. The initial site page load seemed to take longer, and time of day seemed to be a factor. I have studied the message board posts on this issue and realize that there are settings and code that can be helpful, but the HTML pages would load in a second, and I suspect that the host that our test site is on is as much a factor as any. I figure I▓ll set-up with a new host and then deal with this issue. (4) The X-Cart item listing order arrangement also did not suit our liking (instead of listing a, b, c, d, or d, c, b, a, I might want them listed d, a, b, c). From your question, I suspect that I could generate the HTML pages and rearrange the items as needed. Perhaps I need to give this more consideration (have different coding for different item layouts, and then mix and match as desired?). (5) We had considered having the drop-down options on the detail page, but decided that this was more complicated than necessary for a customer; and our detail pages needed to have a lot of information, in various formats, that did not seem to fit one X-Cart format without a lot of work. (6) Search engine preference for HTML code pages.

There were other considerations, but I can▓t remember them all.

As prompted by your question, I think I▓ll have a look at the code on one of the X-Cart generated HTML pages for ideas. Perhaps I can mix and match the bits and pieces.

If you generate an HTML catalog, do you also convert the customer back-end pages to HTML, or can I have a mix of HTML and PHP pages?

Thanks for your input.

[balinor]

I'm not suggesting using the html catalog at all...I'm suggesting using the full php version of the cart with a Dynamic URL add-on. All of the points addressed above can fairly easily be accomplished with X-Cart - I really think you are creating 10x more work than necessary. To address each specific point:

1. This can be done with this module: http://phpsitesolutions.com/x-cart_variant_chart.htm

2. You can easily create different layouts for different categories or even different products using {if} statements.

3. If you are on an X-Cart compatible host such as EWD Hosting or Hands On Web Hosting, load times are not a problem.

4. You can control the listing order within a category to whatever you want using the POS values.

5. See #1 above.

6. If you use one of these modules, there is no difference between an html page and a php page: http://forum.x-cart.com/showthread.php?t=40783

Creating html pages for everything is a TON of extra work, and each time you change something (including quantities, a minor layout tweak etc) you end up having to make the change on ALL the pages. Using X-Cart's default skins, you change it once and you are done. Creating new pages is as simple as using the WYSIWYG editor to add your content.

[Steel]

Thanks again for your input.

I am aware of your suggestions, but in our situation, the shortest distance to being operational is to complete the HTML pages.

So, back to the original questions:

What are the best software tools to use to generate HTML pages? Dreamweaver? Will Dreamweaver facilitate correction of existing code, or is it better to start from scratch and compare the newly generated code?

Is the HTML Tidy cleanup generated code useable? It seems that it generates many reference lines near the head of the page. Is there a better option? Will UltraEdit (http://www.ultraedit.com/products/ul...edit_tour.html) help perform this task?

What is the best way to approach the code cleanup process?

Is XHTML, or some other code better to integrate with X-Cart?

Is there a best doctype to use?

[balinor]

If you do not know how to write html, yes, you'll need a WYSIWYG editor. The latest version of Dreamweaver writes pretty good code, although you will need to do a little tweaking here and there. Ultraedit only helps if you know how to write HTML, it is not a WYSIWYG interface. Yes, Tidy does some good code cleanup, as do the tools inside Dreamweaver.

[Steel]

I know some of the basics of HTML, but I can not write it from scratch.

I get the hang of what Tidy is doing, and given that there are many common errors, code clean-up may not be that difficult.

Dreamweaver looks to be a good tool to have, and I am under the impression that it is also helpful with smarty and CSS.

After I get the cart functing, and have some time, I'm thinking that I'll give it a try to implimeny some of your suggestions concerning the use of the X-Cart PHP format.

Thanks again for your input.

[balinor]

I have never been able to get DW to read Smarty, that is the problem - pulling smarty variables from your site's database. DW works great for straight html pages, or to view the formatting of the templates, but not to actually edit templates from X-Cart.

[carpeperdiem]

Steel,

With ALL the respect intended, you really should re-read the quote in your signature.

UNLESS you are an html expert, I wouldn't touch the html catalog with a 200 foot pole.

See post #4 from Padraic.

A novice html coder should not be asking about validation. That will come in time.

YOUR #1 PRIORITY is to get your head around variants, and some basic smarty if statements.
Learn to use the data import functions.

Get a basic hosting acct. with a qualified host, then move once you're comfortable to your own server as your business needs demand it.

The forum can be your best friend if you let the community help you. There are VERY few forum members trying to sell anything. And those who do (99% of the time) are really here to contribute, not sell. Trust the guidance from the forum. It helped me immeasurably.

[paul@dimoda.com.au]

If you want a site that validates I'd receommend 1) Clean Install of v4.1.10 2) Cart Labs CSS Skin 3) CDSEO Pro 4) Tela Firm Static Page Categories Mod 5) The easiest way for a novice like me to create thier desired changes is with firefox and the firebug addon - make yuor changes on screen then copy ot the relevent tamplate / style sheet