Printable View
Some people have products that are very heavy on attributes
Making pages go own for ever. So having it on its own tab would be much better.
Now I suppose with the coding you could have the best of both worlds right?
Set global to off then code when you need it on?
Set global to on, then if you want the attributes on the first tab for a product,
set the code to turn on attributes for tab one?
I think its made to work for either...
Well as it is now (until I can figure out how to implement ordering)
Tab priority from first to last is:
1. Product Description
1b. Any other custom tabs
2. Attributes
3. Product Details (weight, model #, etc)
4. Add to Cart (with Qty Discount box)
5. Additional Images
6. Customers Also Purchased
7. Cross Sell (if installed)
8. Reviews
With the new code, it will be much easier to move them around and/or merge multiple items together. It will still need to be modified in the code to do it.. but its still a lot easier.
Also, as with the other versions, if there are no items to be displayed on "Zen based" tabs (attribs, product details, add'l images, etc) then the tab will not show up for that product, even if the tab is enabled. The only exception to the rule is the reviews tab. Since that references the real reviews page, it uses its own "There are no reviews" message.
Just thinking about this...
Will there be a way (Globally)
To have either...
Add to Cart on every tab
or
Add to cart on its own tab
Personally I would want it on every tab,
Well Add to Cart is now a global tab of its own. And yes it is possible to have Add to cart on every tab globally if you edit the code a bit. But that seems a bit silly. Why not just leave it off the tabs so you can always see it anyway.Quote:
Originally Posted by milobloom
Ill see how it flows...
I am very new to this contrib.
How long do you estimate the release of the new version?
I'm testing it now with most of the configurations but there are a lot of ways they can be configured between global and manual tags so I'm just doing as many as I can.Quote:
Originally Posted by milobloom
Found & fixed a few bugs already. Zen-Cart uses a lot of id based css.. which seems unnecessary when you could use class instead.. so for each id I find I have to "finagle" it so that it still w3c validates without changing or breaking anything else.
I am also testing it with 1.3.8a.. and it's working fine.
I will release it tomorrow for sure.. as I will be tired of testing it by then :P
You can sneak a peak here:
http://www.unbannable.com/zen138a/in...products_id=36
It won't look like much has changed from the last version but it's a complete rewrite from start to finish.
Hi QHome and other Zenners,
Thanks again for one of my favorite mods.
Question: Is there any impact in using tabbed product lite on search engine postion optimization (SEO for future searchers)? I believe, based on my rudimentary understanding, that it should be ok, as the text and keywords are still included on the page. However, if I am wrong on this, I definintely need to make some changes on how I have done my descriptions.
For this interested, you can take a look at a sample product on my site:
http://www.certifiedbattery.com/cell...5696b-108.html
Normally what I do is put the compatibility information on another tab, as HP is notorious for having thousands of different skus that work with a single model.
If you check the example page I sent, then click compatibility, you will see the various models that the battery works for. Some (or most) of those are never in the front tab of the product description, and I am scared that it might impact SEO results.
Anybody care to comment on the potential impact of TPL and SEO? I would really appreciate it.
Thanks kindly,
Todd
Since you are editing the default template_info_display
Perhaps you could make a slight mod to where the price lays out.
Looks a little off center on my site...
http://www.allforyourwedding.com/~no...oducts_id=1661
I know, I should learn some php programming myself by now...
Since TPL doesn't actually modify any of the meta data or description, there is no impact. TPL just takes the existing page data and manipulates it on the client to look differently. With the upcoming version, this will be even more accurate as now I am using requires of the real zc files instead of creating a subclassed version of them.Quote:
Originally Posted by bifficus
In TPL 3.8, I use a subclassed version of the reviews module, and I copied a lot of DB queries from the real files and cloned them in TPL. In the new version, I call the existing files for the functions so even if the files were to change, it should be transparent to TPL.
So there should be no impact at all on SEO.
Well in the previous versions of TPL, I did a lot of restructuring of the add to cart and stuff using tables because of the way the addtocart was set to "float" in its css properties. This was causing the add to cart button to float off the tab. I also left in some other modifications that I had on my site cuz i thought it looked better than the zc default.Quote:
Originally Posted by milobloom
In efforts to keep it more basic, I removed all the tables. I did however add <fieldset> </fieldset> tags around the add to cart button to keep it on the tab but it should be cleaner and still rely on the rest of its CSS props for alignment. Which on my demo above is right up against the right-side wall where it should be.
In other news...
I finally got all the w3 validation stuff worked out from what I can tell.
I fixed a few more minor bugs
I am working on making the rendered html look cleaner and easier to read (useful for debugging problems)
I also am trying a different method for the sql file. The previous versions seem to cause a lot of people grief, mainly those that had prefixes on their database. I have not yet tested it with a prefixed database.
Other than that I will be updating the Readme file now and get it packaged up for release.
I am going to release the "magic" one first to see how it works for everyone. That one has the least maintenance for bugs and stuff but I am still unsure if using the "magic" will cause any other unforeseen problems.
You guys will be my guinea pigs :) but I will also use it on my live site.
Well I just found the first "semi-major" problem with the "magic" version.
Because of the way the magic works, it basically creates 2 copies of each module and uses javascript to figure out if it exists on the tabs, then hide the real one on the product display template. But it's only hiding it from your browser, the code still loads in the background.
Then i use jscript to set the real divs to be hidden, and change the rendered id of the tabbed version of the modules to have the real id name so that it uses the correct css settings. So its really an optical illusion. The actual source code will show 2 copies, while the rendered page will only show one.
The problem is that this is a form. So while the add to cart button does the send action, i forgot that there are other modifiers.... the attributes and the add to cart qty box.
It works fine for radio buttons. But for textboxes and dropdown boxes, there is a default value already set. So while changing it on the tab, the real version, which loads after the tabbed version, is hidden but still applies its own default value. Which means that the tabbed version gets over written when clicking add to cart. Same with the qty box. If you use the qty box option and enter qty 10.. it will use the default min qty number from the hidden one.
So to fix this I have 2 options.
Option 1.
I can:
- use php to save the actual name value of the tabbed version to a variable.
- Rename the name value to add "_tab" to the name so that when the real one loads they are uniquely named.
- Pass that php variable from step 1 to a jscript variable and match that name to the real one. Then change the real one on the rendered client to be something else.
- Then change the tabbed one to the real one to apply the form action when submitting.
The problem with this one is that I have not yet proven that the form will accept the jscript manipulated name vs the one that is in the code. If it doesn't, then this option is completely out of the water.
Option 2:
I can hybrid with the non-magic one for the add to cart and attributes in the product template. So instead of just 3 lines added to the template, you need to add 2 more IF statements. It would still be less changes than the old versions have needed to date.