Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 01/20/2018 in all areas

  1. 2 points
    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.
  2. 1 point
    CC620 has adopted the attitude that clearing the cache as often as all prior versions of CC5/6 was doing was incredibly aggressive. Now, the admin is to make all changes - adding inventory, creating categories, editing documents, etc, etc - then click the "Clear Cache" button (should now be lit) seen at the upper-right corner of the admin page. The cache holds SQL queries and their results to lessen the load on shared database servers. If you are not concerned about the load on the database while setting up your store, then in admin, Store Settings, Advanced tab, switch off Caching.
  3. 1 point
    Hey Claudia - you probably want to edit your post to get your actual admin_XXXX.php name out of public view. As for the database warning you're getting, it's being discussed in GitHub.
  4. 1 point
    Much better - advertising was extremely intrusive but best is that many features that havent been working for a while are now back working
  5. 1 point
    Ok, will try and restore a backup file. Thanks
  6. 1 point
    We are excited announce the release of CubeCart 6.2 which sports a number of fabulous new features. Maintenance release 6.1.15 is also available for those who are not ready or are not keen to make use of the new features. Massive thanks to all those who have tested and reported any 6.2 bugs. What's New in 6.2? Incremental order numbers (with dynamic prefix/suffix). #636 Tools to help with GDPR. #1892, #354 * Automatically minified and compressed HTML, CSS & JS. #1905 * Checkout state/county can be required, optional or disabled. #1870 * Invoice template editor tool. #1904 Caching improvements. #1536 Product category added to Google Analytics for eCommerce. #1859 * Order summary to show "guide" currency used. #1913 Ability to show hide site document titles. #1907 * Email log to show fail reason. #1899 Email configuration test to work prior to save. #1894 reCaptcha added to newsletter signup. #1891 * Colours added to admin control panel order statuses. #1888 Introduction of "Safe Mode". #892 Product dimensions (width, height & depth). #828 * Changed admin URL emailed on setup (if changed). #1314 "Continue Shopping" added to cart at all times. #1381 * Search redirect to product detail page for single result. #1427 Auto delete captured card details when order status changes from pending. #1886 Upgrade Instructions: https://support.cubecart.com/Knowledgebase/Article/View/228/43/how-do-i-upgrade-from-cubecart-v6-to-latest-v6 Download: CubeCart-6.2.0.zip Download: CubeCart-6.1.15.zip 6.2 Release Notes - Please Read!! * These features will require skin updates if you do not use the default "Foundation" skin from the 6.2 release. This release has a clear cache on demand tool which significantly optimises the caching system and lowers server load. This means that inventory or configuration changes made in the admin control panel will not be reflected on the front end of the store until the "Clear Cache" button is clicked. This can be found at the top right hand side of every page of the admin control panel. We very much appreciate that this may be seen as an unwelcome new feature but the technical significance is worthy. Unless you have a critical change to make we suggest clearing the cache habitually at the end of each admin session. If the cache is not cleared it may take up to 24 hours for your changes to show. To help comply with GDPR CubeCart 6.2 now has "double opt-in" for email marketing signup and a tool to create a report of all customer data based on an email address. This can be found in the "Customer" section of the admin control panel under the "GDPR Report" tab. A customer can be "forgotten" by deleting their account, newsletter subscription, review(s) and any orders they may have placed. Please note that it may be a legal obligation to keep their order data on file if you have an existing financial contract. The GDPR report can be disclosed to your customer printed or saved as a PDF and/or used to help remove their data from the system. To be GDPR compliant please be sure to have a suitable privacy policy which should contain other such information such as what each site cookie does. Further information and support may be available from your local "Information Commissioner" such as the ICO (in the UK). GDPR is still a very confused and misunderstood subject of which there is no one solution for every business. We will prioritise further development to help compliance based on your feedback if merchants feel they still need extra tools.
  7. 1 point
    Yes we can do that for you and make sure the PHP configuration is compatible (ZipArchive, mbstring etc)... Done this many, many, many times. Look forward to working with you soon.
  8. 1 point
    There is no need to do this but it should be covered in your Privacy Policy. Having any consent pre-selected will not be allowed under GDPR. You were part of a previous discussion where I summarised the basic points - see It will from technical point of view but the main area of work is down to each customer to update their Privacy Policy and Terms and Conditions based on the decisions taken as to data use and retention.
  9. 1 point
    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.
  10. 1 point
    We've found what we needed! Thanks for the assistance
  11. 1 point
    I see extra lines in 2.cubecart.js: Lines 542-545: if(Foundation.utils.is_medium_up()) { $('.product_list').removeClass('small-block-grid-1'); $('.product_list').addClass('small-block-grid-3'); } Change to: if(Foundation.utils.is_medium_up()) { $('.product_list').addClass('medium-block-grid-3'); } Near lines 567-568: $('.product_list').removeClass('small-block-grid-3'); $('.product_list').addClass('small-block-grid-1'); Change to: $('.product_list').removeClass('medium-block-grid-3');
  12. 1 point
    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; }
  13. 1 point
    Ok, I see that you have the friendly names of the database columns as the CSV headers. I hope you can change those headers. I suggest using the database table actual column names: 'available','status','name','image','product_code','cat_id','description', 'description_short','manufacturer','price','sale_price','cost_price', etc You can see the complete list of table column names in the admin /sources/products.import.inc.php file, lines 299-333. If you cannot change the CSV headers, then try using this: In the admin skin template products.import.php Find near line 68: {foreach from=$COLUMNS item=column}<option value="{$column.column}">{$column.title}</option>{/foreach} Change to: {foreach from=$COLUMNS item=column}<option value="{$column.column}"{if $map.example eq $column.title} selected="selected"{/if}>{$column.title}</option>{/foreach} Note we are looking now to compare example with title.
  14. 1 point
    There will be some major work involved to make the BXSlider "viewport" take a specific height and then allow for the images to scale accordingly - and not make things messy. For example, a collection of 1000x300px images shown in a max-height 200px viewport will have the bottom 100px not visible. To then scale the images (reduce the width and height) so that the height fits, the width will also be reduced to 666px. That will really mess up the overall display of the slider. The BXSlider javascript scans through the collection of images and finds: if horizontal slides, the height of the tallest image if adaptiveHeight is true, dynamically changes the height of the viewport if vertical slides, the combined height of all images (see adaptiveHeight) I see two possible solutions: make all your images no taller than the max-height, or use a different slider.
  15. 1 point
    Yes it's a bug we intentionally created to drive support sales... or so some have suggested. Great for your image!!!!
  16. 1 point
    In the folder /js/styles/, do you have two copies of jquery.bxslider.css -- perhaps one being named something like orig_jquery.bxslider.css? If so, then styles.php is picking up both copies, with the original taking precedence over the edited. I am also not finding the file /js/styles/images/bx_slider_controls.png.
  17. 1 point
    In the file /js/styles/jquery.bxslider.css, you must replace controls.png with bx_slider_controls.png. Line numbers affected are: 106, 114, 143, 157
  18. 1 point
    Somewhere, you have this: $('.bxslider').bxSlider({auto:true,captions:true}); Change to: $('.bxslider').bxSlider({autoStart:false,auto:false,captions:true});
  19. 1 point
    The problem with the left/right arrow buttons is that the file of the controls sprite belongs to a different effect. Suggest that you edit the /js/styles/jquery.bxslider.css so that the controls.png file called would be bx_slider_controls.png, then copy the controls.png from the Foundation skin, renaming it bx_slider_controls.png. Then force the browser to reload the page's resources.
  20. 1 point
    What does the syntax error say is wrong? I'm wondering if PHP is not liking the variables. Try this: 'content_html' => $_POST['title'] . " " . $_POST['first_name'] . " " . $_POST['last_name'] . ",<br>\n Thank you for registering with " . $GLOBALS['config']->get('config', 'store_name') . ".", 'content_text' => $_POST['title'] . " " . $_POST['first_name'] . " " . $_POST['last_name'] . "\nThank you for registering with " . $GLOBALS['config']->get('config', 'store_name') . ".",
  21. 1 point
    Welcome kwickcut! Glad to see you made it to the forums. CubeCart uses the PHPMailer library (https://github.com/PHPMailer/PHPMailer) for all email transportation. PHPMailer is told to use SMTP, or to use PHP's mail() functions that relate to the connection to whatever service is defined in the PHP.INI file, which generally is a server on localhost. So, when you say 'phpmail', do you mean PHP's mail() family of functions, or the PHPMailer library? If in admin, Store Settings, Advanced tab, Sending Method is PHP 's mail() functions, then you do not enter anything relating to SMTP details, as the connection details to postfix (or whatever) should already be in the PHP.INI file.
  22. 1 point
    Yeah, that does the trick, thanks, as always bsmither you are a font of problem solving. On using it more, it's doing some weird things, but it's workable, for some reason it keeps hard forcing a linebreak like a <br> but not visable anywhere. I looked for solutions on ckeditor forums, but they seem to really break it hard and it just spams every blank space with the <i class
  23. 1 point
    Please note that the template rendering engine (Smarty) builds the page before the web browser gets it. Putting HTML comment tags around the Smarty commands does not stop Smarty from replacing those {commands-in-braces} with the intended content. That intended content could also have HTML comment tags. That results in nested comment tags. Look for those statements in the template as mentioned earlier, but change them to look like this: {* include file='templates/box.newsletter.php' *} and {* include file='templates/box.popular.php' *} The brace-asterisk-space sequence is Smarty's comment tag. Thus, the content will not appear in the rendered page sent out to the browser.
  24. 1 point
    I've added another version of this skin, which uses the same layout but a different look. You never know: someone may be interested one day!
  25. 1 point
    Welcome Carlos Martins! Glad to see you made it to the forums. Only two or three database columns store a date as a SQL DATE/TIME value. The other 'time'-related columns are "UNIX timestamps" - the number of seconds since Jan1,1970. There are PHP functions that take this number, and a "pattern", as arguments, and give back a phrase. The phrase can be 'fuzzy' (Yesterday, two weeks ago, etc) or absolute (4 Feb, 2018).


  • Newsletter

    Want to keep up to date with all our latest news and information?

    Sign Up
×