Leaderboard

I am thinking your Foundation skin is not current (shipped with CC642). From your screengrab, the Topbar is v5.5.1, while CC642's is v5.5.2. There is also: var back_text = $('#val_lang_back').text(); if(!back_text) { back_text = 'Back'; } Foundation.libs.topbar = { name : 'topbar', version : '5.5.2', settings : { index : 0, start_offset : 0, sticky_class : 'sticky', custom_back_text : true, back_text : back_text, mobile_show_parent_link : false, This finds the language string (which we did earlier), and uses it if

Excellent sleuthing! In the Foundation template main.php, make sure this is there: Near line 59: <div class="row small-collapse"> <div class="small-12 columns"> {include file='templates/box.navigation.php'} <div class="hide" id="val_lang_back">{$LANG.common.back}</div> </div> </div> This is necessary for one of the two approaches to work. The first approach would be this: In box.navigation.php, find: <nav class="top-bar category-nav" data-topba

If making changes to the language phrases, regardless where or how, be sure to clear CubeCart's cache. CubeCart first loads definitions.xml and caches two variations of it (the details not important). CubeCart then loads the targeted language file (for example en-US.xml). Same-key phrases are overwritten. For example, the key 'mobile' has US English "Cell Phone" as what gets displayed. Also, 'postcode' is displayed as "Zip Code". An entire language pack will overwrite whatever same-keys exist in that pack, while missing keys will cause CubeCart to use those default phrases. Usin

Originally the Click and Drop integration was only in beta and RM would only open it up to a few selected accounts and would only allow it to work with integrations they had written themselves. As the answer on 20th November shows, this has now changed ------------------------------------------------------------- Hi all and thank you for your feedback. Following our successful trial of the Click & Drop API integration, we have now activated this integration for all accounts. You can find it in your Settings > Integrations. Thanks to everyone who took part in the beta program

Admin Console -> Advanced -> Request Log Anything showing up in red?

For what it is worth - I still use the Standard, because I want people to create an account on our store. I do not have any issues with 6.4.3. There are other posts here of problems with payment, so I would suggest you search for PayPal and read through some of those threads.

We recommend not changing foundation.css. There are multiple sections that look similar but are within 'media-queries'. That might cause some confusion as changing a rule in a media-query might not show because the browser is displaying another media-query. But, the browser's Developer's Tools do get it right, but only for the current media-query. So, instead add new rules to cubecart.default.css. This file gets loaded after foundation.css and as such, take priority. We have a <div class="panel">. But we do not want all panels. There are two solutions: <div class="panel

Hi @radman420 That slider is just a basic bxslider banner slider set in the document content for the homepage which you modify via your admin panel. Firstly create your banners and upload them to your site, for example (images > source > slide_001.png) Banners should be of equal size Then, go to your admin panel and in the left-hand menu go to File Manager > Documents Then, select the document for the homepage OR create a new document On the document content section click the "source" button in the left corner and create a slider box

Please confirm that there are more than one image associated with a product being tested.

FYI: If any module was installed using the lightning bolt code number (as opposed manual upload), CubeCart will (should) inform you that a newer version is available.

Ah, you're hosted by Haven? Wasn't aware, cheers. Hope you will get this sorted soon.

Hi Tony, To put PayPal Commerce in Sandbox mode you'll need to disconnect your account via its settings page. You then need to edit two files; modules/plugins/paypal_commerce/admin/index.inc.php Change: define('SANDBOX', false); to; define('SANDBOX', true); modules/plugins/paypal_commerce/paypal.class.php Change: private $_sandbox = false; // Set to false for live!! to; private $_sandbox = true; // Set to false for live!! You can then reconnect using a developer Sandbox account from https://developer.paypal.com and test with their test or live ca

In order to add custom condition words, we need to make a few core code edits, then we can use a Code Snippet to actually add the custom words. I will have instructions soon.

When you add/edit a product, it's on there (well, it is on my v6.4.2 install)