onebrowncow

@bsmither you are correct, updating the API in the Stripe dashboard does make a difference. However many of the available fields in the stripe reports are not populated with data from Cubecart. Of those that would be most useful are the customer_name headed column. The customer name does appear in the dashboard but not in any of the downloadable reports, and the Cubecart invoice number which did appear if using the previous plugin, but not in the latest 3.0.7 version, I think this information should now appear under the invoice_id column

Thanks for pointing me in the right direction @bsmithermuch appreciated. I will take a look and report back.

Just noticed on our monthly Stripe report from Stripe that the field for description which is normally populated with the 'order for payment number' followed by the actual customer order number is now completely blank after updating the plugin to version 3.0.8 Wondered if anyone else has seen the same issue after updating before I report it as a bug. Thanks

I've pushed on with the development of a site on 6.4.1 but now taken the decision to give up. Regardless of what I do including manually inputting my SEO url, when I come back to the site the following day it has added back in the first level category to every product url duplicating that category in the SEO url, if a sub category is also used that is often duplicated too. I can't figure out if it is a bug or my VDS settings but it's too frustrating to continue with at this time.

That might be a better way to word it. It seems to have been stable overnight and any SEO paths I have manually input on the product page search engine tab seem to be ok but products I haven't edited yet have paths like this example: https://www.domain.com/home-and-interior/home-and-interior/candles-and-room-fragrance/home-and-interior/candles-and-room-fragrance/lily-flame-candles/spring-time-scented-candle-by-lily-flame the correct path should be: https://www.domain.com/home-and-interior/candles-and-room-fragrance/lily-flame-candles/spring-time-scented-candle-by-lily-flame

Just upgraded a CC6 store to version 6.4.1 but I'm getting some weird automatically generated SEO URLs with it adding sub categories multiple times to products formatted like this https://www.domain.com/category-2/category-2/sub-cat-1/sub-cat-1/product sometimes it will add the same category or sub category multiple times. Store settings for SEO are: Add category to product URL path? Top level and all sub categories Add subcategories to category URL path? Yes SEO URL Extension None (recommended) running on PHP5.6 I just can't figure out what is causing it to continually add to the SEO URL or if it is just because of the old version of php I'm running CC6 on and that php7 or higher is required for this new SEO feature to work correctly. Thanks in advance

If you are running V4 currently and using the built in SagePay Form gateway which uses the V2 protocol, then we have a gateway module that uses the Server InFrame integration method and is fully V3 compliant. Ian Yes, I'm aware of the mod Ian, you installed it, but we never managed to get it working without breaking out of frame or returning an error so we gave up on it and changed direction with our development and decided to try a move to CC6 The SagePay Server InFrame payment gateway module for V4 has been working perfectly for a while now (as with most things there were a few teething issues when you tried it) and it is installed and working on quite a number of sites. However, the move to V6 has got to be the best way forward for everyone ! Ian Many thanks to Ian at Havenswift-Hosting who has assisted me to resolve my particular issue with the inFrame mod. I can report that thanks to his continuing help the problem I was encountering has been fully resolved and subject to a few final tweeks we will be using his iframe Sagepay mod shortly.

Regarding removing the horizontal categories bar you would need to customise the main.php template. Doing so requires a full understanding of how the Foundation grid works and would require that the following code was retained somewhere within your new grid. <div class="row"> <div class="the foundation classes entered here would change depending on changes made"> {include file='templates/box.navigation.php'} </div> </div>In the location from where you removed this in main.php you could, for example, insert a link to a custom smarty template for a new documents only navigation bar Whatever you do to change the layout of the main.php template you must retain the code include file='templates/box.navigation.php' otherwise your category navigation won't appear. My best advice for anyone looking to make major skin changes to CC6 is to learn and understand how Foundation works first and then move forward. All the documentation for Foundation is available online.

I haven't seen how the Semperfi navigation uses foundation but it should automatically disappear and become a mobile friendly menu below a certain screen size and I would be very surprised if they haven't worked this in to their mod. In fact I've just visited their demo store and their vertical navigation mod does just that, on a small screen or mobile device the navigation disappears and becomes a horizontal menu displaying the catergories which is exactly how responsive design should work when using foundation

Just been doing some testing on GTMetrix and noticed that the waterfall chart is returning a 406 for GET jquery.cookie.min.js and the response is: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>406 Not Acceptable</title> </head><body> <h1>Not Acceptable</h1> <p>An appropriate representation of the requested resource /skins/foundation/js/vendor/jquery.cookie .min.js could not be found on this server.</p> <p>Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.</p> </body></html>Clearly the js file is on the server, I've checked! This is happening with the default Foundation skin so it is not my custom skin that is causing the error and alternatively disabling the EU cookie control makes no difference. Standard response or bug?

Thanks for the info Ian. Our host is usually very helpful so it had crossed my mind to ask for a temporary increase in resources to accommodate the upgrade. I think I will drop them a line.

Will the upgrade process run as normal from V4 to V6.0.6 if the image folder exists but is empty? I would assume it would run fine, just no images would link to products or will I end up with a database full of dead product image link data? My reason for asking, we have a huge image folder and on a test run of an upgrade we timed-out (to be expected) thanks to the image folder. Also we use two different sized images on our current site, not a requirement for V6 so we are thinking of manually adding product images after the upgrade to spring clean our image folders. Or does anyone know how much or how to calculate how much server memory is needed to upgrade successfully with a large store with a huge image folder?

This small code hack will add a continue shopping button (or text in mobile view) to the basket view page after the customer has used the empty basket button. <!--content.checkout.php--> <!--near the bottom of this template find: --> {/if} {else} <h2>{$LANG.checkout.your_basket}</h2> <p class="thickpad-top">{$LANG.basket.basket_is_empty}</p> {/if} <!--add additional <div> content as shown below : --> {/if} {else} <h2>{$LANG.checkout.your_basket}</h2> <p class="thickpad-top">{$LANG.basket.basket_is_empty}</p> <div class="row"> <div class="button secondary small-3 columns show-for-medium-up"><a href="{$STORE_URL}" target="_self">Continue Shopping</a></div> <div class="small-12 columns show-for-small-only pad-bottom"><a href="{$STORE_URL}" target="_self"><i class="fa fa-arrow-circle-left"></i> Continue Shopping</a></div> </div> {/if}Seems to work fine but still testing. If anyone else fancies trying it and seeing if it breaks anything I'd appreciate the feedback

started a new thread for a continue shopping button https://forums.cubecart.com/topic/50065-continue-shopping-button-in-view-basket/

Following on from comments from Dirty Butter in another thread I have added a very simple Continue Shopping button to the basket pages which appears alongside the grand total line in larger views and as a single bar across the screen in a mobile view. It just redirects back to the home page which is fine but if you proceed from index.php?_a=basket to index.php?_a=confirm and use the continue shopping link any data added in the customer information fields will be lost. So the solution I am after is a way of hiding the button on any pages other than the _a=basket page. I'm not great with php but is it possible to wrap the button div in an {if} {/if} statement using the _a=basket to identify the page you need the button to appear on and to control the pages on which the div would not appear on? The following code was added to content.checkout.medium-up.php (a slight variation added to content.checkout.php for the button to appear on the small screen) <div class="button secondary small-7 columns show-for-medium-up"><a href="{$STORE_URL}" target="_self"> Continue Shopping</a></div>