Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 01/22/2019 in all areas

  1. 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.
    2 points
  2. 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
    2 points
  3. you are a hero! - Thanks works perfectly under SMTP!
    1 point
  4. Yes please use SagePay-1.0.13.zip. It should be fine with PHP 7.2 but 7.4 would be safer.
    1 point
  5. I am going to ignore the lines that appear to come from an SSL Cert manager. I just wanted to make sure there is an appropriate RewriteBase directive. It will be interesting as to what would be found in the web access logs.
    1 point
  6. Great! Thank you very much. It is working, I used the database credential and host localhost:9200. In the search box, to get the drop down list product, need to use mouse cursor. Can we add keyboard up,down to reach to the downward list instead of mouse cursor. Even after click outside of the search box, ES search dropdown list wont disappear. Need to used ESC key. It would be good idea to add one click functionality to clear search dropdown list like ESC key.
    1 point
  7. Did this transaction pass 3D secure? If so I believe it should be protected and you shouldn't be liable to chargeback fees. Our PayPal integration has much more granular settings. If you want to you can choose to only accept payments that pass 3D secure. With that setting enabled you are never liable to chargeback fees. The square extension could have this feature added.
    1 point
  8. Since upgrading to version 6.5.2 we have the following issue: For reference our shop is located at https://www.airbornesappers.org.uk/shop/index.php We do have products with a Sale price entered, which are less than retail and greater than zero In Store Settings - Features we have Sales Mode set to Per Product, with Number of sale items to display set to 20 I don't know if the upgrade to 6.5.2 has caused this, all I can say is that prior to the upgrade Sale Items were displayed in the Sale Items category I've searched other topics and checked as much as I know what to check but can't fix this error Any help appreciated Thank you
    1 point
  9. A 'throbber' (spinning circle) that does not go away indicates that the javascript that is supposed to cancel the throbber and make the browser proceed to the next step, has crashed, failed to start, or failed to load. Failing to load could be caused by a browser extension that prohibits fetching javascript from non-whitelisted sources. While stuck on the CloudFlare page, examine the browser settings menu for a "Developer" section, then view the browser 'console'. It will indicate the cause of being stuck on the CloudFlare page.
    1 point
  10. Another popular open source cart that brought v4 out recently had also taken PayPal Std out (and a few other things), has found a considerable number of its members have now reverted back to using the earlier v3, which also has a separate branch on Github, where developers have now upgraded it so it will run on PHP 8. Say what you will, but people like to have choices. Interestingly enough, whilst using another cart solution last week and going out to PayPal using Std PayPal on PayPal live site, that also brought up the option to pay later? That certainly not something that has ever shown up on there before. I will contact PayPal myself, to ask why they asking people to agree to an undisclosed partnership 'agreement' when signing up to PayPal Commerce (on any platform), as that just not right. Absolutely no mention of rates, extra charges, changes to seller responsibilities or anything else. Not good.!
    1 point
  11. That makes sense. I think I'll keep making the change instead of changing the rate rule. Thanks!
    1 point
  12. In shipping.class.php: Find near lines 237-240: $this->debug(sprintf('<strong>&gt;&gt;&gt; Shipping zone [ID %s] matches the delivery address! Use this zone for shipping calculations.</strong>', $this->_all_zones[$i]['id'])); if ($this->_settings['multiple_zones'] == 'first') { $this->debug('Looking for first matching zone of best match (instead of searching for all matching zones - see AIOS module settings)'); } else { Change to: $this->debug(sprintf('<strong>&gt;&gt;&gt; Shipping zone [ID %s] matches the delivery address! Use this zone for shipping calculations.</strong>', $this->_all_zones[$i]['id'])); if ($this->_settings['multiple_zones'] == 'first') { $this->debug('Looking for first matching zone of best match (instead of searching for all matching zones - see AIOS module settings)'); $closest_match_zone_id = $this->_all_zones[$i]['id']; break; } else { The above is the exact same edit as was posted earlier, just the line numbers have changed.
    1 point
  13. Please reload this forum conversation. I made a mistake on the last line of the new code.
    1 point
  14. You are getting the address items from the admin, Order Summary page? If so, try the following: In the admin /sources/orders.index.inc.php: Near line 419, find: $overview_summary['country'] = is_numeric($overview_summary['country']) ? getCountryFormat($overview_summary['country'], 'numcode', 'name') : $overview_summary['country']; After that, add: $overview_summary['state_abbrev_d'] = is_numeric($overview_summary['state_d']) ? getStateFormat($overview_summary['state_d'], 'id', 'abbrev') : $overview_summary['state_d']; $overview_summary['state_abbrev'] = is_numeric($overview_summary['state']) ? getStateFormat($overview_summary['state'], 'id', 'abbrev') : $overview_summary['state']; In the admin template orders.index.php: Near lines 163-164, from: {$OVERVIEW_SUMMARY.town_d|upper}<br> {if !empty($OVERVIEW_SUMMARY.state_d)}{$OVERVIEW_SUMMARY.state_d|upper}, {/if}{$OVERVIEW_SUMMARY.postcode_d}<br> To: {$OVERVIEW_SUMMARY.town_d|upper}&nbsp; {if !empty($OVERVIEW_SUMMARY.state_abbrev_d)}{$OVERVIEW_SUMMARY.state_abbrev_d|upper}, {/if}{$OVERVIEW_SUMMARY.postcode_d}<br> Near lines 174-175, from: {$OVERVIEW_SUMMARY.town|upper}<br> {if !empty($OVERVIEW_SUMMARY.state)}{$OVERVIEW_SUMMARY.state|upper}, {/if}{$OVERVIEW_SUMMARY.postcode}<br> To: {$OVERVIEW_SUMMARY.town|upper}&nbsp; {if !empty($OVERVIEW_SUMMARY.state_abbrev)}{$OVERVIEW_SUMMARY.state_abbrev|upper}, {/if}{$OVERVIEW_SUMMARY.postcode}<br>
    1 point
  15. Nice idea! In admin, Maintenance, Rebuild tab, there is a means to "Reset all product view counts". "Views" is one of the choices on what criteria to base a query for "Best Sellers" (aka Popular Products). But resetting Views might be overkill for some. I have in mind a text box next to Store Settings, Layout tab, "Source data for popular products" saying, "Within the past [###] days." This won't be a date range, but will this suffice for your needs?
    1 point
  16. I added more to my post above. Please reload this forum page. There is no urgency in removing the debugging code. It does not affect how CubeCart runs.
    1 point
  17. This is the one I wanted to see: [14] HookLoader::_build_hooks_list:451:Hooks: class.cubecart.display_gateways => Array ( [paypal_commerce] => Array ( [hook_id] => 248 [plugin] => paypal_commerce [hook_name] => Display Gateway or Make Payment [enabled] => 1 [trigger] => class.cubecart.display_gateways [filepath] => [priority] => 0 ) ) More to come.
    1 point
  18. Name: Dillion (Bootstrap Responsive Skin) Price: Free Category: Skins Homepage: https://www.cubecart.com/extensions/skins/dillion-bootstrap-responsive-skin
    1 point
  19. You might be able to set identifier exists = false in the feed rules on Google's end:
    1 point
  20. 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}
    1 point
  21. 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']])) {
    1 point
  22. Did you follow the steps in method 1? https://support.cubecart.com/hc/en-gb/articles/360003794198-How-do-I-upgrade-from-CubeCart-v6-to-latest-v6-
    1 point
  23. We are in the middle of developing a plug-in to cover both these areas of functionality. It is a big job to do it fully so have no release date yet but will be in the first half (hopefully first quarter) of next year. If you want to register as a client at our website and open a support ticket asking about this, we are interested in people’s views on functionality and we can keep you updated regarding progress
    1 point
  24. Currently, no. But, CubeCart has the ability to respect a custom API call that a "cron job" would execute on schedule, as well as hooks that could be used every time that a web page is requested to update if a specified amount of time has elapsed since the last update.
    1 point
  25. Decided to persist with getting the wamp server to work in a ssl mode, so I could use PayPal commerce working offline with CubeCart. Well it has gone 10pm now and after looking at lots of variations on other sites and lots of trial and error, I have FINALLY got the PayPal Commerce extension working fully in wamp, meaning I can develop my sites offline and upload to live servers when completed... Yay.!!! This is the difference with working with outfits like CubeCart, you get help rather than sarcasm and assistance rather than bitter critique. Forwards and onwards..... Thanks Al
    1 point
  26. 1 point
  27. If there is a blank page, then there could be error messages in admin, System Error Log.
    1 point
  28. I think nearly all of the log entries matching the examples shown in the document provided, relate to the parts of the skin template system you have stripped out (Language chooser, Featured box, Sale Items box, Newsletter box, Live Help, Debug, and Skin chooser). Looking at the source HTML delivered to my browser, I see that there is a removed text entry field for the person's phone number. This will cause the form to not even be submitted if the form validation fails. In the file /skins/ho/js/3.cubecart.validate.js, at lines 66-97, there are the rules for the contact form. Remove 92-94: }, 'contact[phone]': { phone: $('#validate_phone').text() Remove 83-85: }, 'contact[phone]': { phone: true What I do not know is this: How smart is the Validator? If the Validator does not find a text entry input field having the name contact['phone'], even with a rule referencing it, will the validator still submit the form? According to this, the Validator does not check non-existing fields (from five years ago): https://forum.jquery.com/topic/jquery-validate-check-that-a-field-exists-before-validating In other words, I do not know if this edit will fix things. FYI: The core code in cubecart.class.php, says only that 'email', 'name', 'subject', 'enquiry' are the only required fields. So maybe an issue will get posted in the Github that compares the Validator rule for the phone being required, but the core code does not.
    1 point
  29. Experiments have shown that making these two edits will resolve this issue.
    1 point
  30. Chaps.. This situation is embarrasing, I'm getting female members of my team telling me that they are receiving explicit messages from one of our contact forms. Can anyone suggest how I get invisible working, failing that I'll have to employ the services of a dev to write something which works.
    1 point
  31. Attached is a report that covers the edits needed to make CC645 run under PHP 8.1. Of course, without a comprehensive testing procedure plan - preferably automated - hitting every feature and function that CubeCart can do is impractical. As such, I advise against running this in a production environment, for now. However, I believe I've found and fixed the Fatal Errors, Warnings, Deprecated Notices, as well as a number of general notices that became visible under PHP 8.1, and made a number of code optimizations, but only in the core code. I have chosen to not make a fork of CC645. For those who want to slog through the edits, I hope they will be able to discern the reasons for each change. Any module encoded with ionCube will need a new version from the publisher. The publisher should also take it upon themselves to test their modules under PHP 8.1. Some additional insights can be found reading the latest Github issues. PHP8.1_Changes.txt.zip
    1 point
  32. It should, however it hasen't been updated since 2017. Which only means that, since it is encoded with ionCube, the encoded files must have been built with a matching version of the encoder for the version of PHP it is running under. Even though the current encoded files are built for "PHP 5.6 and above", this does not mean they will work on any version of PHP7 - which your hosting provider has likely configured your hosted account to use. The publisher, @Noodleman, will need to build encoded files for PHP 7.
    1 point
  33. It is 'responsive', so it works regardless of the device's viewport width.
    1 point
  34. I had issues with SendinBlue. I don't recall the exact scenario, but it went along the lines of them rejecting my mailing campaign half way through sending. I quickly spent my credits and went elsewhere. Moosend is perfect for our requirements, although they are fussy with certain address uploads.
    1 point
  35. Amazing! Thank you that is so helpful. I will take a look.
    1 point
  36. Hi Lyd, If you edit the page/document via the admin panel "status" should be ticked and "Show link to document in storefront?" unticked. This should hide the link in the footer but leave the content accessible by the new nav link. If you are linking to a category, don't create a new page/document as stated in step 1. Simply just do step 2 and use the url for the category for the link. Thanks.
    1 point
  37. Hi Lyd, It is possible to add to the area you mention, however anymore than 3 can cause a layout issue on screens between 768px and 991px (the joys of responsive websites ) you can free up a bit of space by removing the "register" link and just have a login link (theres a register link on the login page and register options during checkout so no biggy) To Add A Page 1) Create a page (Admin > Documents > Create Document) When you create the document a link should appear in the footer of your site. Make a note of the link. 2) Open basix > templates > box.navigation.php Add your link (i've used Affiliates as an example) to the bottom of the list. <li itemprop="name"> <a itemprop="url" href="http://exmaple.com/CubeCart/affiliates">Affiliates</a> </li> and save. NOTE! The navigation file gets cached so you will need to clear your sites cache if you have the cache enabled. (You should have a Clear Cache button in your admin header) Remove Register Link (OPTIONAL - Upto you if you want to) basix > templates > box.session.php Find and remove <li itemprop="name"><a itemprop="url" class="parent-link" href="{$STORE_URL}/register{$CONFIG.seo_ext}">{$LANG.account.register}</a></li>
    1 point
  38. My bad. Replace that other new code with this new code: if (!empty($item['product_options'])) { $product['product_options'] = array(); if (($list = unserialize($item['product_options'])) !== false) { foreach ($list as $value) { $product['product_options'][] = $value; } } else { if(method_exists($order,'unSerializeOptions')) { $options = $order->unSerializeOptions($item['product_options']); } else { if(empty($item['product_options'])) { $options = array(); } else if(($options = cc_unserialize($item['product_options'])) !== false) { } else if (($options = cc_unserialize(base64_decode($item['product_options']))) !== false) { } else { $options = explode("\n", $item['product_options']); } } foreach ($options as $option) { $value = trim($option); if (empty($value)) continue; $product['product_options'][] = $value; } } $product['product_options'] = implode("\n", $product['product_options']); }
    1 point
  39. The POF module prior to 1.2.2 had its own code to email a courtesy email confirming the order was placed. Version 1.2.2 now is supposed to use the established code in CubeCart's core codebase. Looking at 1.2.2 (version 1.3.0 is the same), it seems more work needed was mentioned to the programmers, but didn't get done. So, please make this edit: In the Print Order Form module, gateway.class.php, near line 206, find: if (!empty($item['product_options'])) $product['product_options'] = implode(' ',unserialize($item['product_options'])); Change to: if (!empty($item['product_options'])) { if (($list = unserialize($item['product_options'])) !== false) { foreach ($list as $value) { $item['options'][] = $value; } } else { if(method_exists($order,'unSerializeOptions')) { $options = $order->unSerializeOptions($item['product_options']); } else { if(empty($item['product_options'])) { $options = array(); } else if(($options = cc_unserialize($item['product_options'])) !== false) { } else if (($options = cc_unserialize(base64_decode($item['product_options']))) !== false) { } else { $options = explode("\n", $item['product_options']); } } foreach ($options as $option) { $value = trim($option); if (empty($value)) continue; $item['options'][] = $value; } } }
    1 point
  40. Hey @radman The W3W compatibility notice in the admin panel is cosmetic - Providing you enter your W3W info it will work as intended. It's just in the admin panel it looks for a certain skin file to determine whether or not its compatible, however for the updates i approached it differently so the certain skin file isn't there. As for the other issues, i can only assume something might have been edited incorrectly during your update, i can't seem to load your site (503 Service Unavailable) at the moment so i can't check whats going on.
    1 point
  41. @traylor23 you are very welcome ! One takeaway is that you might want to look into the frequency and accessibility of backups your hosting company is doing. Minimum has to be full off-server backup once per day but even that for busy transactional sites can lead to massive data loss. As an example, we do hourly Continuous Data Protection backups !
    1 point
  42. Please follow along with me. Let's look at /classes/gui.class.php, the private function _displayPopularProducts(). At the bottom of the function, near line 1275, a statement assigns the $content from fetching and rendering a template to $POPULAR_PRODUCTS. So we know the code gets executed down to that point. Just above that statement is where all of the products from the query (in the $vars variable) is assigned to $POPULAR. But $POPULAR isn't in the diagnostics popup. That's crazy. If 'POPULAR_PRODUCTS' got assigned something, then 'POPULAR' must have been assigned something, even if it is null or false. Just above that is a hook. And above that, inside the foreach() loop, is a test that skips the product being examined if it does not have an associated category that has its status enabled. What is still disconcerting to me is that the query isn't showing in the grey debug section. It really should be there, because, with the test near line 1240, if there are no $products from the query, none of what we just discussed gets executed. Assuming the query is listed in the grey debug section, but wasn't correctly found, the only thing that could cause problems is: the test for enabled categories assigned to each product being looked at, or there being a hook that empties $vars. In the grey debug section, near the bottom, are there any messages that indicate problems with any of the queries?
    1 point
  43. 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.)
    1 point
  44. The debug section can be quite lengthy. Your browser has the ability to Find things in the web page. Usually by the keyboard combo CTRL-f. In the small bar that opens (maybe at the bottom of the browser window) enter one of the terms I mentioned above. If not found, find for the other term. Do NOT copy/paste the entire debug section into a forum post.
    1 point
  45. Thanks @bsmither for helping out while i catch some Joys of timezones.
    1 point
  46. In the template main.php: Find: <body> Change to: <body background="https://mybikerleather.com/Banner.jpg"> or <body style="background-image:url('https://mybikerleather.com/Banner.jpg');background-repeat:no-repeat;"> Do the same for the template main.checkout.php.
    1 point
  47. A scenario has been known to happen whenever one mouse-swipes some text to select it, then copies it to the clipboard, and then pastes the clipboard to a text entry field -- that the mouse-swipe inadvertently also includes hidden white-space: a tab character, a space character, a newline character. So, in this scenario, which can and does happen everywhere, extra illegal (invisible) characters was part of the token sent to the Marketplace.
    1 point
  48. In the Noodleman skin template main.php, find: Near line 26: <a href="{$ROOT_PATH}" class="main-logo"><img src="{$STORE_URL}/skins/noodleman_v6/images/noodleman/noodleman-logo.png" alt="{$CONFIG.store_name}"></a> Change to: <a href="{$ROOT_PATH}" class="main-logo"><img src="{$STORE_LOGO}" alt="{$CONFIG.store_name}"></a>
    1 point
  49. 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!
    1 point
×
×
  • Create New...