Leaderboard

Can you believe that CubeCart has been around since 2003? What started out as a small project has snowballed powering thousands of stores globally. If you have a success story you would allow us to publish we would be truly very grateful if you could share it with us. We need new merchants to realise the potential they have using CubeCart. This will help contribute to further growth, new features and an all round brighter future for everyone. Please feel free to email me personally at [email protected] with your company name, store URL and short success story of upto say 300 words. Many thanks to you all for your support.

Contacted now - thanks

In the skin's config.xml, find the <image reference="category">. It is set for 800 pixels on the longest dimension. Change this to 900. It will auto-scale down to fit the container (which is 848 px wide). Next, you will need to find the CSS rule (I do not know where it would be.): .cat-hdr-img img { margin: 0px auto 5px; } Change to: .cat-hdr-img img { margin: 0 0 5px; } This CSS change will remove the margin that the browser adds to either side of the image, in equal part, to center the image in the slightly wider container. Be sure to clear Cubecart's cache.

The developer will probably / should be releasing a new version of the skin to take account of all of the skin changes included in this recent version. However, if you are using a modified version, then that update will not automatically apply to your store and you should chat to the developer about this. If you dont make all the front end skin changes then you wont be able to take advantage of any fixes / new functionality that has been added - you may say that you dont need this functionality but it is always best to stay fully up to date because the situation simply gets worse and worse with each upgrade that is released - this is the problem with having custom changes

Try this: In includes/ckeditor/config.js, at the bottom, find: config.allowedContent = true; }; Change to: config.allowedContent = true; config.coreStyles_italic = {element : 'em'}; config.extraAllowedContent = 'i[*]{*}(*)'; }; CKEDITOR.dtd.$removeEmpty = '{i: 0}'; The same added statements can be used for other HTML tags used in unorthodox ways.

Email routing will automatically be set to "Automatic" or sometimes "Local Mail Exchanger" which in 99.99% of cases will be the same thing. You only need to set it to Remote if you are using external MX records pointing away from your hosting company which is effectively what Godaddy are forcing you to do by closing email ports. Some people choose to use gmail or other email service providers, but why should you have to ? Disabling php mail() is standard practice now for security reasons (WHM built in security advisor flags this as a high security risk if it is enabled !) and SMTP should always be used and configured to use SSL / TLS. Email sent via SMTP is much more secure, more likely to be delivered and not rejected or put into spam and isnt complicated to use. So much so, I would recommend that php mail() is removed as an option in CubeCart as it is very likely to disappear as an option in the near future Ian

For anyone that uses git with CubeCart (or any other packages for that matter), cPanel have been adding a huge amount of functionality which will be included in V68 - see https://features.cpanel.net/topic/allow-users-to-install-websites-from-version-control V68 is already in Edge release status so most people will not have access to it yet, but V68 should be into general release in a few months (V66 has just been released in the last week) Ian

This is the first time using this cart. Like it a lot, easy to work with and the CMS feature is excellent, my previous cart didn't have that. Didn't customize too much but happy with the way it came out. Don's Vintage Audio Feedback welcome!

The 'top menu' is the "Navigation" bar (or sometimes "Shop by Category" box). The menu is built from all the categories (enabled and unhidden) there are. There are also three special items: Home, Sale Items, and Gift Certificates. To add any other links to this group would require editing the skin template "box.navigation.php".

There will be some problems with PHP 8.0+. There are several incompatible changes compared to earlier PHP version families. PHP 7.3 is in the same situation as PHP 5 - end of life. I think PHP 7.4 would work without too much trouble for CC642, - again, end of life.

I understand. Thanks!

Name: Dillion (Bootstrap Responsive Skin) Price: Free Category: Skins Homepage: https://www.cubecart.com/extensions/skins/dillion-bootstrap-responsive-skin

For version 1.05, there is a bug in the template box.template.php, near line 17: From: {if count($POPULAR > 1)} To: {if count($POPULAR) gt 1}

Please try this edit: In /classes/language.class.php, line 106: From: if(ADMIN_CP == false && isset($d[$url['host']]) && !empty($d[$url['host']])) { To: if( (!defined('ADMIN_CP') || ADMIN_CP == false) && isset($d[$url['host']]) && !empty($d[$url['host']])) {

This may be related to an open issue: https://github.com/cubecart/v6/issues/3057 If the error was copied from CubeCart's admin, System Error Log, if you hover the mouse over the error, there may be a popup that gives the trace PHP made to get to the code that errored. If that popup appears, try to copy/paste the contents to a reply here.

CubeCart version 6.4.6 is now available. This is a maintenance release with full PHP 8 and 8.1 support. This release is backward compatible to earlier PHP versions so your hosting environment doesn't need PHP 8 or above to run it. What's New? - PHP 8 Support - Miscellaneous bug fixes Download: CubeCart-6.4.6.zip Download: CubeCart-6.4.7.zip

Thanks, I realised it but forgot to hide it!

So, the browser did not find ORDER BY popularity DESC. The next step I would like for you to do is edit the skin template box.popular.php and at the very end of the file, add {debug}. Save the edited file. When you next ask for the Homepage, your browser will want to popup a window. Let it. (You may need to request the Homepage a second time if you need to give permission for the popup.) The popup contains all the variables assigned to the template. Scroll down to near the bottom and find $POPULAR in the left pane. If it is there, is there a value for it as shown in the right pane? It might be an array with 20 elements. (Do not post the array here. Just indicate if it is an array with 20 elements, or if the value is something else.)

What were your findings in admin, Store Settings, Layout tab? Verify that there exists a skin template named box.popular.php.

Hey @radman420 Just checked your site and theres no trace of the missing box so i can only assume that no data is been passed to $POPULAR used for it. Does it reappear if you switch to the foundation skin?

NiteFox beat me to it! But the solution works great. Thanks!!!

Hey, No, you'd go from the one above the version you have installed as any below it will already be done in the skin. So if you installed Amzin V1.02 then you'd only want V1.03 and above updates. If you go to yoursite > skins > amzin > docs > changelog.txt the top entry shows which version of amzin you had when you installed the skin. I'm guessing you have Amzin V1.02 installed so the only one i would say is necessary would be on V1.03 - #23 Prevent Add To Cart Cache Once your store is running CubeCart 6.4.1 then you'll need #16 to #21 (SEO EXT Support) to fix the login/register/search URLs The updates in the guide only cover skin edits to support core features, some of which cover new features added in CubeCart V6.4.1. So to use those features you'd need to upgrade your store to CubeCart V6.4.1 which is entirely separate from skin updates. Just doing skin updates won't update CubeCart's core.

Hey, In relation to my answer to your previous question of "Can the core script be updated manually?" By "modified version of CubeCart" i mean if you have manually edited any of CubeCart's core script files. Using the upgrade option in the admin panel may cause the loss of any custom edits made to the core files. In relation to Extensions such as Skins, if you modify them (Change colours by editing the css files, manually add additional html etc) then it's advisable that you do not use "install tokens" to install new versions of the skin as you will lose any previous edits to the skin. CubeCarts Install Tokens basically pulls the full new version of the extension (skin) from CubeCart servers and extracts it over the existing version (replacing the existing files with new files - restoring the skin back to its default version) but also merges so any extra files are not lost. Which is why i now do a manual update guide for any updates to my skins as most people modify the colour scheme at the least. If that makes sense.

Thanks @bsmither for helping out while i catch some Joys of timezones.

There is a CSS rule that is setting the max-height of the logo. .main-logo img { display: block; max-width: 100%; max-height: 60px; } I can't really determine where this rule is at, but it can be overruled by adding a style attribute to the <img> tag: <div class="col-xs-7 col-sm-3"> <a href="{$ROOT_PATH}" class="main-logo"> <img src="{$STORE_LOGO}" alt="{$CONFIG.store_name}" style="min-height: 120px;"> </a> </div> Edit the main.php and main.checkout.php templates.

Hi @NiteFox Thank you it worked fine. I know what you mean about the "Latest" page, but thats fine, I would rather all product have "From" than non. I have options on some products that are more expensive and got a few questions about why the final proce in the cart was different to what was shown on the home page. As for the "Categories" page, that just perfection. Once again, thank you very much.

Here is what I have from tonight's test: - Order DOES go to "processing" even if the customer bails out after hitting the "Pay" button and doesn't go back to the store by clicking the "Confirm" button on the Auth.net results window. This is great. - Created a copy of the "Default emails" template, called it "Hard-coded emails", replaced the header image and signature macros with hard-coded urls and made it the default. - Under the "Email Contents" tab, I modified Cart: Order Confirmed and Admin: Order Received, replacing the macro {$DATA.link} with a hybrid hard-code / macro combination of https://mystore.com/index.php?_a=vieworder&amp;cart_order_id={$DATA.cart_order_id} (where mystore.com is the actual store domain and the order number is handled by the dynamic macro {$DATA.cart_order_id}). - Have NOT been able to solve the gigantic store title issue on the Auth.net transaction results page. Will have to keep looking or call their support and find out how to get this under control. It looks like all of the information is being sent correctly and the transaction was successful. (NOTE: I only tested auth only since my clients all capture funds when the item ships.). Generally, it works with a few workarounds and the need for a small formatting tweak. I much prefer the new embedded frame and the clean form look and operation to the old SIM. It works well enough for me to put it live in one of my client's stores. We will see how it goes over the next 24 hours of live use.

Congratulations Al, to you and your wife!

While it is faster to upload the zip file and then extract after it has completed, you then need to add the additional steps of ensuring that (if you already have a renamed /admin_xxxxxx directory and admin_yyyyyy.php file), these need to be renamed as you will have a /admin directory and admin.php file from the zip extract and you will end up with multiple copies of both and mixed versions of files as so many on here have done. You also of course still need to run the /setup AFTER completing the rename Ian

An easy way is to add the style attribute to the link itself: <a itemprop="url" href="/my_special_link.html" title="My Special Link" style="background:red;">My Special Link</a>

In Foundation.css .thickpad-top { padding-top: 1.25em; } make it 0em or padding: 0; I'm not sure if it's used in other pages though, so maybe be careful with that, I haven't really come across it in my rebuild yet, but then again, I am on part 5 of 9billion.

I lied, I figured it out. In /foundation/templates/main.php <div class="row"> <div class="small-12 columns small-collapse"> {include file='templates/box.navigation.php'} <div class="hide" id="val_lang_back">{$LANG.common.back}</div> </div> </div> Make it <div class="row row-mod"> <div class="small-12 columns small-collapse"> {include file='templates/box.navigation.php'} <div class="hide" id="val_lang_back">{$LANG.common.back}</div> </div> </div> then go to foundation/css/foundation.css and add .row-mod { max-width: none !important; }

When a customer registers for an account, that registrant could instantly be assigned to a customer group. The group would have been created before-hand, and some or all products would have had a price schedule created for them. There is no percentage difference between one group and any other group (yet). Each group has a distinct and independent price schedule. Still, I reiterate, once a customer registers, even at checkout, but then resumes shopping, the group's price schedule is shown everywhere to that customer. Is this acceptable according to the contract you have with the product supplier? However, I know that someone (Noodleman?) is or has been working on something related. There is a new parameter in the function that gets an item's price, that when true, will return the full retail price regardless of any other consideration. If it was Noodleman who asked for this to be added to the core code, you should drop him a note to ask if he has anything on the shelf ready to install.

There are no tables in the invoice. The code is all proper. I will have to blame it on the latest version(s) of Firefox. In the meantime, maybe Cyberfox or Waterfox (respectable forks of Firefox) will suffice.

Sooo...., if the site administrator has implemented this anti-scrape mechanism, then AJAX exchanges of data may fail if the AJAX package does not send the correct cookie - or may actually fail even with all the correct cookies. I have no experience in this scenario. The template parser (Smarty) does not execute any code other than its own Smarty code. Having PHP code in a template is exactly the same as having any other text. It is just plain text and that plain text will be in the final output that Smarty creates. Also, any code that looks like Smarty code but is not Smarty code in a template could cause PHP to crash. For example: <?php echo "Hello {smiley} World" ?> will cause Smarty to quit parsing the template and stop PHP with a Fatal Error. Please know that you must not think the templates are PHP code scripts just because the filenames end in .php. (The templates can be named anything, and I do not know why the programmers chose '.php' as the filename suffix for the skin templates.)

There is no "transferring over" CubeCart PHP code. An upgrade is "whole cloth". So, you now have a folder named /admin/ and a folder named /admin_hash/. I suggest you determine which folder has this latest update, rename the other one to something completely bogus, then rename the correct folder to the same name that is in the /includes/global.inc.php file. (Yes, I do understand that having implemented a derived name for the admin folder introduced a number of headaches.) Just to make sure, also force your browser to reload the admin page resources (javascript and css - new versions in CC6110 - and images.) This is usually done with CTRL-F5.

A couple of questions: Are you using AIOS? Do you have a country or region set up in AIOS for the countries you ship too? Are you running the following CC6.1.8 with Skin Foundation and AIOS. + various plugins. ie Card capture+paypal express I may not be able to help for here on, but the answers will help others more knowledgeable.

Welcome, @EricClark!

Click on "Air Systems" in the Category Name column. When the new page is displayed, you will see the sub-cats listed.

You'll need to contact the developer using the "Email Developer" link: https://www.cubecart.com/extensions/developer/patrick-bullert

I've created a bug report: https://github.com/cubecart/v6/issues/1607

Hi Niall I have updated the Microdata plugin so two versions are available (for PHP 5.6 and above and another for PHP 5.5 and below) but unfortunately due to some caching issues with the Marketplace (which I have reported to Al), these are not showing. If you would like to register as a client at our site and open a ticket, I can let you have the correct version that way Ian

In the file /classes/order.class.php Near line 483, find: case self::ORDER_DECLINED: // Nothing to do, but leave the option here for hooks & such break; case self::ORDER_FAILED: // Email the customer to explain their order failed fraud review $content = $mailer->loadContent('cart.payment_fraud', $order_summary['lang'], $this->_order_summary); break; case self::ORDER_CANCELLED: // Cancelled $content = $mailer->loadContent('cart.order_cancelled', $order_summary['lang'], $this->_order_summary); break; Change to: case self::ORDER_DECLINED: // Nothing to do, but leave the option here for hooks & such break; case self::ORDER_FAILED: // Email the customer to explain their order failed fraud review $this->assignOrderDetails(); $content = $mailer->loadContent('cart.payment_fraud', $order_summary['lang'], $this->_order_summary); break; case self::ORDER_CANCELLED: // Cancelled $this->assignOrderDetails(); $content = $mailer->loadContent('cart.order_cancelled', $order_summary['lang'], $this->_order_summary); break; The related email templates will need to have the macros added -- you can copy the contents from another template.

A proper solution would be more involved than the following (a proper list item on the Transaction Logs tab, for example), but here is an edit that puts a field on the Billing tab - which I think is more appropriate than Delivery. In the admin template orders.index.php, find near line 264: <fieldset> <legend>{$LANG.account.contact_details}</legend> On a new blabnk line ABOVE that, add: <fieldset> <legend>{$LANG.orders.gateway_name}</legend> <div><label for="sum_gateway">{$LANG.email.macro_gateway}</label><span><input type="text" id="sum_gateway" name="summary[gateway]" value="{$SUMMARY.gateway}" class="textbox"></span></div> </fieldset>

Works for me. But as I said, the pagination urls are different now - so may not be necessary any more. I still have the Disallow in my robots.txt file, though.

The above was developed for AIOSv108. If you are editing index.inc.php, then you are in the /admin/ folder. You should be editing the /skin/admin/index.tpl file.

This is a known issue and will not cause any damage to the store. The programmer's are working on it. CubeCart makes three attempts at searching for a product. 1. Using a complicated (as implemented by the database server) algorithm that searches the database using a 'relevance approach'. The results have a "relevance weighting factor". If nothing found, 2. Using an expression looking for whole words. If nothing found, 3. Looking for the characters entered which may appear anywhere. The problem with the CubeCart code is that the Advanced Search page has a sort selector that defaults to a sort method (Relevance) that is only applicable to method #1. CubeCart is supposed to drop that sort method and default to another, legal sort criteria for #2 or #3, but doesn't. Thus, the error message from the database server. You shouldn't see this error if you choose to sort by something other than Relevance on the Advanced Search page.

The county bounty! Firstly, thank you to the Cubecart developers for making such a great platform. So much more responsive and closer to my needs than so many other systems I have tried, including Magento and oscommerce. I think in nearly all aspects Cubecart are better than the others. It's not perfect, though, and that's what I would like to address here; My biggest gripe is not being able to disable the county field in admin. Users have to search through a long list of counties, which acts as an additional barrier to making that sale. Especially if they live in London or Manchester, since their locations are listed under 'G', and the field is totally unnecessary in the UK in any case. Especially if you are using a postcode lookup system which presumably populates the address correctly. Also, if you are retailing to mostly end users, you may prefer not to ask the user to fill in company name when entering the address, or at least mark it as Optional so the user knows they don't have to worry about it. Again, the option of hiding that field would be useful. I have spent some time trying to kill the county field eventually realising my efforts were being thwarted by additional checks validating the address part way against database tables. So here goes: If the cubecart developers make the next, or next-but-one version have an admin option to not ask for County, I pledge to pay a £50 bounty.

Seems like I got this working now! This is how I made my filemanager.class.php file to look like: class FileManager { private $_directories; private $_mode; private $_manage_cache; private $_manage_dir; private $_manage_root; private $_recently_uploaded = array(); private $_sub_dir; private $_sendfile = false; //private $_max_upload_image_size = 350000; private $_max_upload_image_size = 6291456; // 6MB public $form_fields = false; Thanks!

The phrase won't be in the skin templates. This is an advisory/warning phrase in the language file. In admin, Languages, click the edit icon for the language you want to change. When shown the drop-down, choose Checkout. When shown the list, change the phrase associated with the 'error_shipping' key.