markscarts

Sorry, that does not work. I proposed it, but it was just some brainstorming that went nowhere. The multiple downloads per single purchase need has neve been adequately met to my knowledge as of today's date. There is a similar mod (commercial) for adding downloadable digital options to a product, but it is not the same and doesn't answer the need for many people.

2nd q: Open the file includes/ini.inc.php with a text editor. Near the end of this file, you will see the following comment: // Pages that should be server under SSL (if enabled) Just below that is a line of code, that begins like this: $sslPages = array("unsubscribe" => 1,"login" => 1,"logout" => 1, etc. Add the following code to that line: $sslPages = array("unsubscribe" => 1,"viewDoc" => 1,"login" => 1,"logout" => 1, 1st q: The very best way of dealing with this is by installing a feature-rich commercial mod, try searching google for show-hide-order site docs cubecart The free and easy way to hide one is to exclude it from database query manually, just determine the doc ID number, then open includes/boxes/siteDocs.inc.php and look for this: $results = $db->select("SELECT doc_id, doc_name FROM ".$glob['dbprefix']."CubeCart_docs ORDER BY doc_name ASC"); Change it like this: $results = $db->select("SELECT doc_id, doc_name FROM ".$glob['dbprefix']."CubeCart_docs WHERE doc_id != 5 ORDER BY doc_name ASC"); But use the correct docId instead of 5 Disclaimer: Only You are responsible to any damage done to your store by modifying the code, any advice given here is without any warranty of any kind.

I like the design for your very first store. Kind of neat and clean.

Have you heard of YouTube? I do understand all the coding behind embedding windows media player, etc. etc. but to be honest, the easiest way for you to do this in a user friendly manner would be to learn how to upload your video files to YouTube.com Open an account there and upload your videos there. You can then play them on the web, link to them from anywhere, and they will provide a custom embed code for each of your videos, so that you can just paste it into CubeCart. Check out this CubeCart store in development, it is not finished but it does have YouTube videos on the site. Look for bowling balls that have a little video icon, and click it . . . http://www.allstarbowling.com/devStore/

OK, well there is more to the story then. I have no idea where you are trying to put this code etc. etc. Since you are talking about mods and can't give full info, I would suggest you not post here. Use a third-party forum, or contact the mod author. If this were a line in the correct php file, for instance, the lang.inc.php file, the code I gave you should work just fine.

give a link to your site, please, if possible

Can anyone please check this site in IE6 to see if the products are displaying on all the view category pages? They're displaying fine now here, I'd like to have someone double-check please, http://sendsocks.co.uk/index.php?act=viewCat&catId=3

No, html and js can be used there, but of course you cannot use a double quote unless you comment it, otherwise the script thinks it has hit the end-of-string marker which is a double quote. Something like this should be fine: $lang['front']['viewProd']['variant_out_of_stock'] = "Cette catégorie du STOCK est actuellement épuisée. Veuillez vérifier les autres qualités ou <a href=\"mailto: [email protected]\">NOUS CONTACTER</a> "; Do note that stock CubeCart uses an XHTML 1.0 transitional doctype declaration, and for the code to be valid your html tags need to be lowercase not uppercase. escape inside double quotes with \ like \"

You can create html pages in Dreamweaver or whatever, then code the templates into CubeCart. To be very successful at it, you should know the basics of writing and editing html and css directly. For this type of site, it would help to be a little familiar with javascript too. I really like the concept of the site. When you look at barijay.com/salon.php it is analogous to looking at a customized cubecart viewCat page. The large image on the left could represent the CubeCart random image (featured product) showing full-size rather than thumb photo, or it could represent a static category image, either way easily done by modding cubecart code a little. The "slidestrip" represents the product list that appears on viewCat pages in cubecart, the prod list is simply coded as a filmstrip rather than a tabled list, using only product images with alt and title tags that are linked to the viewProd pages. The effect on this site is great, as it gives the appearance of browsing through a wardrobe closet. Following is some information I posted in another forum once about coding the html templates into cubecart, perhaps you may find it helpful. Question Answer Hi Scott! You are correct in principle, I'll give you the whole picture to the best of my ability. First, the global/index.tpl will be the basic cubecart equivalent of your html page. This template is a straightforward HTML page, with two notable exceptions, explained below. Open yours and study along. • Like any valid HTML or XHTML page, it starts with a DOCTYPE declaration. <!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> • As with all HTML pages, the "code proper" begins and ends with the html tag: <html> . . . </html> <html xmlns="http://www.w3.org/1999/xhtml"> and at the bottom of the page </html> • The opening HTML tag is followed by a head section: <head> . . . </head> This section, like any normal html document, contains META tags and links to external scripts and stylesheets, etc. <head> <meta http-equiv="Content-Type" content="text/html; charset={VAL_ISO}" /> <title>{META_TITLE} <meta name="description" content="{META_DESC}" /> <meta name="keywords" content="{META_KEYWORDS}" /> <link href="skins/{VAL_SKIN}/styleSheets/layout.css" rel="stylesheet" type="text/css" /> <link href="skins/{VAL_SKIN}/styleSheets/style.css" rel="stylesheet" type="text/css" /> <script language="javascript" src="js/jslibrary.js" type="text/javascript"> </head> • Following the head section comes the body section: <body> . . . </body> This section contains the code behind what you actually see on the webpage; i.e., the body of the webpage. It contains block-level tags or elements like <div> and <p> and <ul> and <form>, and line-level tags or elements like <span>, <strong>, <li>, etc. --------------------------------------- The page you create in your wysiwyg editor should contain all these elements! --------------------------------------- The two notable exceptions ~ First, note the <!-- BEGIN: special_name --> and <!-- END: special_name --> These look like any old html comments, but they are special markers for telling php where to parse active content from the php includes files. It is important to retain these markers, and to be sure they are in the correct file and in the right place. Certain content must remain between each specific set of markers, and certain content should be kept out from between these markers. Second, note the {SPECIAL_NAME} tags. These are content markers or variables that place php-generated content on the page, and in the global/index.tpl file they represent other .tpl files found in styleTemplates/boxes and styleTemplates/content. If you look at these other non-global .tpl files, you will see that they, too are html with the same two exceptions, but these files do not have doctype declarations, <html> tag, nor head nor body tags. These represent html snippets that are "pasted" into the body section of your xhtml document by use of the above mentioned {SPECIAL_NAME} tags. --------------------------------------- A basic understanding of the above is essential to doing what you wish to do, successfully. With that in mind, here is your general recipe: 1. Create your document using dreamweaver or some other creation program in the XHTML 1.0 format. 2. Copy and replace the doctype declaration and the <html> tag from stock cubecart skin text (recommended) 3. Place the <!-- BEGIN: body --> and <!-- END: body --> markers at beginning and end of page, respectively. 4. "Cut" the code snippets for boxes out of your created page and paste them into the correct styleTemplates/boxes .tpl files. • NOTE: You must re-code these snippets for active content using the php cues in each file appropriately, analogous to the original files ~ 5. Use the correct {SPECIAL_NAME} tags in place of the snippets you cut for pasting in the other files. 6. Likewise, "cut" the main content code and place it in styleTemplates/content/index.tpl, and again you must re-code this snippet for active content using the php cues appropriately, analogous to the original styleTemplates/content/index.tpl -------------------------------------- All of this can be a piece of cake if you are very familiar with coding, or it could be like a difficult birthing for the novice, but in any case it represents work. -------------------------------------- I hope this overview has been helpful; any feedback is appreciated. :D

Hi Mysty, don't want any misunderstandings, so I will explain myself a little better, hopefully. I just want to be helpful with this . . . What I meant to write was that isolating the peekaboo problem is not that simple when you start modding CubeCart stores. The problem can become layered when you added new floating divisions in modifying the code, or when moving float codes around. This happens all the time. I regularly code new classes and codings into CubeCart stores, and use the float property often enough. When the problem gets layered a lot, there have been times in the past when I've had to remove all the relative positioning and start fresh adding it back by trial and error to find where it needs to be to work properly. The key is not to put relative positioning on every class that uses float in the stylesheets, but putting it in the right place to make IE render the page properly. With stock CubeCart code, that is usually at the .boxContent class in layout.css, the .txtContentTitle class in style.css (though you don't see float on that one in the stylesheets) and in a couple of the template files where the float property is used inline styles. I'm sorry I can't be more specific, but when you've modded the skin files this has to be done by trial and error. The good news is that it works, once you get it in the right place. For the other, you've see how that works already in the other thread. Again, I can't tell you whhere to put it without experimenting with your actual modded code, I have given an example above though. If you read that code, you see that there is one division named background that contains another division. Because of the way it is coded, nesting one division in another, the background division should flow behind the other division to the end. Sometimes this does not render properly though, and in that case you need to add a spatial element, even if it is just a non-breaking space, just before the closing </div> tag of the background division, and when floats are used above, you have to clear them with something like <br clear="all" /> Without actually trying this at your site, my best guess would be that this code: <br clear="all">&nbsp; should be placed just before the closing </div> tag that is used to close the boxContent division.

1. Look in skins/Legend/styleTemplates/content/index.tpl and find code like this: <!-- BEGIN: repeat_prods --> <div style="float: left; text-align: center; width: {VAL_WIDTH}px;"> Replace it with this new code: <!-- BEGIN: repeat_prods --> <div class="latestProds"> 2. Now open skins/Legend/styleSheets/layout.css, and at the very end of that file add this: .lateProds { float: left; text-align: center; width: 150px; height: 150px; margin-top: 10px; margin-left: 10px; } 3. Adjust the mmargin-left amount (10px, in red above) up or down little by little until they are centered properly, then check in multiple browsers.

It has a nice, clean look to it. Check the errors in your code: Result: 15 errors / 0 warnings line 10 column 81 - Error: document type does not allow element "LINK" here line 18 column 60 - Error: there is no attribute "BACKGROUND" line 26 column 102 - Error: there is no attribute "WIDTH" line 26 column 114 - Error: there is no attribute "HEIGHT" line 26 column 126 - Error: there is no attribute "BORDER" line 34 column 101 - Error: there is no attribute "HEIGHT" line 42 column 11 - Error: end tag for element "P" which is not open line 71 column 161 - Error: required attribute "ALT" not specified line 81 column 137 - Error: required attribute "ALT" not specified line 81 column 144 - Error: end tag for element "SPAN" which is not open line 105 column 152 - Error: required attribute "ALT" not specified line 105 column 159 - Error: end tag for element "SPAN" which is not open line 113 column 15 - Error: end tag for element "P" which is not open line 158 column 5 - Error: end tag for "TR" which is not finished line 164 column 9 - Error: end tag for element "P" which is not open Not sure why you are coding as HTML 4.1 but spend a little time cleaning up the doctype declaration and all the other deprecated code, it would be worth the effort. I'm not a fan of tables in the layout, but I have to admit I do it too on occasion. As to your question, check the pinned posts in skins forum.

Very nicely done; a pleasure to view, to read and to navigate. Interesting stuff in the js solutions, thanks for sharing.

What you are asking is not easily answered. The links you added on extra tabs are now hard-coded into the categories.tpl file. In order to have language control, you would have to add this as a special links mod that work through the categories php file and allows editing like the prod desc, site docs and categories does now, for languages. The other language terms would have to be added to the CubeCart_cats_lang table in db and used just like te current category titles are used. This is off the top of my head . . . I am not a php coder, I have learned a little from messing with CubeCart and the few minor mods I have made are usually made to work with CubeCart languages. It can be done using the built-in CubeCart language support. But this is a different enterprise from offering simple hacks and tweaks like hard-coding extra tabs into the templates. If you can't figure out how to do this, try requestinng a developer from one of the third-party stores or forums; perhaps someone would have time to take this on.

I think actually, it is lang.inc.php for the language of your choice :dizzy:

@webicon, I just looked at your site (missed the URL t'other day) OMG, definitely IE peekaboo problem IE6 This is always cause by the IE's freaking out over the FLOAT property. The reason this is a new thing for your sites is because you folk have added the gallery product view, which replaces a tabled list with FLOATING divisions. This can be "cured" by adding a relative positioning to the correct containing element. This type of problem can become layered in the code, so if you have a great deal of trouble pinning it down, it may be necessary to remove any relative positioning you had previously added to the page or pages, and start fresh Peekaboo problem is indicated by: • use of float property • cursor changes to hand over links, though not visible • able to "highlight" the hidden elements by clicking and dragging the cursor This means that the elements are actually coded into the page properly, and IE obviously knows that they are there, but has a rendering bug in this situation. HTH By the way, an absolutely fantastic design there :zorro:

<a href="index?act=viewProd&amp;prodId={VAL_PRODUCT_ID}">

Here are a couple screenshots from IE6 As mentioned in the other post, you have quite a few problemms with this page Mysty, but one of the IE rendering probs that has to be dealt with is tricking it to render the boxContent division all the way. If you ever have a situation like this: <div class="background_area"> <div class="contains_floating_elements_or_table"> content </div> </div> and, you find that the background division seems to be pulling up short, you can usually make IE render it all the way by introducing an element of space like this: <div class="background_area"> <div class="contains_floating_elements_or_table"> content </div> &nbsp; </div> But if you have floating elements above, float: left or float: right, you may well need to clear the floats first, so you code: <div class="background_area"> <div class="contains_floating_elements_or_table"> content </div> <br clear="all" />&nbsp; </div> Instead of a non-breaking space, you could add a paragraph down there or an image, or any other spatial element. I always use the position: relative; trick to clear peekaboo issues - there is more than one way to do it, but that one always works. I have come across problems with peekaboo issue that have taken a few hours to iron out, though. Those problems can become many-layered, and it is often time-consuming to determine which element(s) to put the relative position on, and which not, but in my experience it has always solved the issue when you get it in the right place. Adding paragraph tags before division tags is not a good idea, when the division contains a multitude of block-level elements (other paragraphs, tables, etc.) My developer tool picks up 187 errors on the page right now. Some of these are cascading errors, wherein fixing one bit of code will eliminate several errors each time. Bottom line: Best way to fix this is to clean up the code, get rid of all the errors then use the typical IE tricks to fix the rendering problems if any remain.

Hi guys, sorry I dropped out of the conversation, haven't been available today, but reading with interest. Well, I didn't expect the advice about .boxContent division to be a bum steer, but in my experience with peekaboo bug it is not unusual to have several layers of this problem crop up in CubeCart, where the float property is used so much. The only thing I could be certain of is that it was indeed the IE peekaboo rendering problem I saw. All the elements were there, which was evident by rolling the mouse over, they just weren't rendering. Mysty, I just looked at the site, statues cat, and it wasn't pretty. Maybe you're still working on it now. What I saw is the product list extending far down past the boxContent division that's supposed to contain it - which is probably the result of removing the break code - and the pagination was then stuck up in the right column just below where the boxContent division left off, and this was pushing all the right side boxes down the page. Off to bed now, will be looking tommorrow to see if this was just a fluke of loading the page at the wrong time while you were working on it.

If your code is similar to stock Killer skin, look in styleTemplates/boxes/cartNavi.tpl You'll see code like this: <!-- BEGIN: repeat_region --> <td class="topCatsTabLeft">&nbsp;</td> <td class="topCatsTabMid"><a href="{VAL_LINK}" class="txtCat">{TXT_LINK}</a></td> <td class="topCatsTabRight">&nbsp;</td> <!-- END: repeat_region --> Just after it, you would add this code: <td class="topCatsTabLeft">&nbsp;</td> <td class="topCatsTabMid"><a href="index.php?act=viewCat&amp;catId=1" class="txtCat">Our Products</a></td> <td class="topCatsTabRight">&nbsp;</td>

LOL, not so bad, just IE peekaboo bug there Go to layout.css and position: relative; to the class .boxContent and this may solve the problem

AGTH :)

Well, it shouldn't be inside that box, the stock CubeCart code puts it beneath that box. It is the "Current Category Image" That image is meant to display on the current category page. As I mentioned, in stock CubbeCart, if you have subcats, CC will display them first, then the current cat image below them. Many people elect to move the current cat image to the top, and have subcats display below the current cat image, which seems to make more sense. The fact that your current cat image is moving up into the subcat section rather than displaying beneath it may indicate that you have made an error in customizing your subacat code somewhere. To remove, or move, the current image, you must normally deal with this block of code in styleTemplates/content/viewCat.tpl: <!-- BEGIN: cat_img --> <img src="{IMG_CURENT_CATEGORY}" alt="{TXT_CURENT_CATEGORY}" border="0" title="{TXT_CURENT_CATEGORY}" /> <!-- END: cat_img --> If you want to retain this on the final cat page in a tree, and have it invisible for pages that show subcats, you have to mod the code in includes/content/viewCat.inc.php so that it doesn't parse <!-- BEGIN: cat_img --> when subcats are present. HTH

You need to go back and hash out your code a little better. Some of this looks like some faulty code on my part; the cell containing left column is set to 165px width and the one containing right column is set to 250px width . . . and this is improper in many ways, for one, in a table cell the syntax should be width="165" not width="165px" Need to spend a little time going thrrough and tweaking all your code just a little. Try going to an html validator and run it through, then look to resolve any and all errors. You have it going in a good direction :)

Yes. Haven't you seen the many new versions released since 3.0.0, and often due to security patches because of those exact problems? Your host(s) may require that your carts be upgraded before turning the site on.