Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 06/03/2019 in Posts

  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. Ok in that case try 1.9.7 (just released): https://www.cubecart.com/extensions/plugins/paypal-commerce
    1 point
  4. Hey everyone, I recently discovered a fantastic way to elevate your gift-giving game: custom gift packaging! Whether it's for birthdays, weddings, or any special occasion, adding a personal touch to the packaging can make your gift stand out. I've been experimenting with different materials, designs, and embellishments, and it's been so much fun! Not only does it make the recipient feel extra special, but it also shows that you've put thought and effort into the presentation. Do you have any creative packaging ideas or tips to share? Let's inspire each other to spread joy through beautifully wrapped gifts!
    1 point
  5. Yes please use SagePay-1.0.13.zip. It should be fine with PHP 7.2 but 7.4 would be safer.
    1 point
  6. Please try: https://cubecart.zendesk.com/hc/en-gb/articles/360003831497-How-can-I-create-a-plugin-using-the-code-hooks-system
    1 point
  7. 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
  8. 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
  9. That makes sense. I think I'll keep making the change instead of changing the rate rule. Thanks!
    1 point
  10. Please reload this forum conversation. I made a mistake on the last line of the new code.
    1 point
  11. I'm only running All in One Shipping v 1.0.24, Card Capture v 1.0.12, and Google Base v 1.0.3. So far, so good, but I'll keep an eye on them.
    1 point
  12. During the running of 'setup', CubeCart makes some tests: certain folders must exist and be writable, and key PHP extensions must be initialized. For CubeCart 6.5+, PHP 7.4+ (8.2 recommended but will probably be required for CC652+), the extensions include: MySQLi, GD Image library, Simple XML parser, cURL, ZipArchive, and the MultiByte String library. The test during setup is reported as a list of Pass/Fail line items on the second page shown. Setup will not proceed to the third page if any item shows as failed. CubeCart continuously checks to make sure the version of PHP is compatible, so should PHP change versions (7.4 downgrade to 7.3, for example), CubeCart will make complaints. However, CubeCart does not do continuous compliance checks for the presence of required extensions.
    1 point
  13. Please post a PM with your email address and I will send a ZIP file having the "Previous Purchase" plugin.
    1 point
  14. 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
  15. 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
  16. Please create the error log: https://forums.cubecart.com/topic/51550-how-to-create-the-error-log/ There may be clues to what is happening.
    1 point
  17. Yes. That data item is found in {$PRODUCT.use_stock_level}. The code sequence: {if $PRODUCT.use_stock_level}Extra language{/if} will need to be in template code (as opposed to the "Description" content of the product's data).
    1 point
  18. On my development system, I am trying Amzin 1.05 on CC647 running under PHP8.1. (Found a bug in a template.) But the links appear correct. I have not yet installed CC649. But analyzing code differences between CC647 and CC649 shows no likely source of this situation.
    1 point
  19. 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
  20. 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
  21. 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
  22. 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
  23. As per Al's comments on the github issue you raised, this is almost certainly down to a faulty or partially completed upgrade
    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. If there is a blank page, then there could be error messages in admin, System Error Log.
    1 point
  26. In Catalogue Mode, customers are not even able to add items to a shopping basket. So, there is no way for CubeCart to log what the customer wanted. The admin can try to not enable any Payment Gateways. A shopping basket should be created and an Order Summary created, which the store owner can review and amend in CubeCart's administrative backend. But there will be no means for the customer to actually pay for the items via CubeCart.
    1 point
  27. 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
  28. Experiments have shown that making these two edits will resolve this issue.
    1 point
  29. 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
    1 point
  30. Sorry to hear this Rosemary. Best of luck achieving what you want. I'm not sure I have any valuable input.
    1 point
  31. Attached is a follow-on report for more edits needed to make CC645 run under PHP 8.1 - attempting to eliminate (at least minimize) the numerous error messages that PHP logs. Some of these edits assume that the edits and file replacements found in the prior report have already been made. PHP8.1_Changes2.txt.zip
    1 point
  32. Hi, I just tried this again with with PayPal Commerce 1.6.2 and still no joy, therefore I downloaded the 1.6.2 code to get a better look .. And this is what I found - /** * CubeCart v6 * ======================================== * CubeCart is a registered trade mark of CubeCart Limited * Copyright CubeCart Limited 2019. All rights reserved. * UK Private Limited Company No. 5323904 * ======================================== * Web: http://www.cubecart.com * Email: [email protected] * License: GPL-3.0 http://opensource.org/licenses/GPL-3.0 */ function ppcp_body_js($tpl_output, Smarty_Internal_Template $template) { $skins = $GLOBALS['gui']->getSkinData()['info']; // $skin = $GLOBALS['gui']->getSkinData(); if (($pp_config = $GLOBALS['cache']->read('pp_config.'.$skins['name'])) === false) { if(file_exists('modules/plugins/paypal_commerce/config.custom.json')) { $pp_config = file_get_contents('modules/plugins/paypal_commerce/config.custom.json'); } else if(file_exists('modules/plugins/paypal_commerce/config.'.$skins['name'].'.json')) { $pp_config = file_get_contents('modules/plugins/paypal_commerce/config.'.$skins['name'].'.json'); } else { $pp_config = file_get_contents('modules/plugins/paypal_commerce/config.foundation.json'); } $GLOBALS['cache']->write($pp_config, 'pp_config.'.$skins['name']); } if(isset($GLOBALS['cart']->basket['total']) && $GLOBALS['cart']->basket['total'] > 0) { $pp_amount = $GLOBALS['cart']->basket['total']; } else { $pp_amount = "null"; } return preg_replace('/\<\/body\>/i','<script id="pp_config" type="application/json">'.$pp_config.'</script><script> var pp_config = JSON.parse(document.getElementById(\'pp_config\').textContent) var pp_amount = '.$pp_amount.';</script></body>', $tpl_output); return $tpl_output; } $GLOBALS['smarty']->registerFilter("output","ppcp_body_js"); On about the third line of code you can see I have replaced a line. Now the thing is that this was never going to work the variable '$skin' is never referenced in the code so its clearly in error. The question is why did nobody else experience the same ? Its probably because, and this is just a guess, many other skins are strongly based upon the foundation skin, but as I say that's only a guess .. Anyway it seems to be working now but no production test yet.. Chris.
    1 point
  33. PHP 7.2 stopped even receiving critical security updates over 1 1/2 years ago so running any site on this version is 100% not advised. You would be much better contacting @Noodleman directly via his website and simply asking for a 7.4 encoded version of them and ensuring you stay on the latest supported version of PHP Ian
    1 point
  34. The All in One Shipping module has a Debug setting. Choose to see a Very Verbose explanation. The debug analysis will show why there were no shipping rates found to satisfy the required conditions.
    1 point
  35. 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
  36. Amazing! Thank you that is so helpful. I will take a look.
    1 point
  37. Determine if the following statement already exists in the templates 'main.php' and 'main.checkout.php': <link href="{$ROOT_PATH}favicon.ico" rel="shortcut icon" type="image/x-icon"> If it is not there, add it just before the </head> tag. Next, acquire a square image you want to use. Upload it to a free online ICO file maker, such as: https://www.icoconverter.com/ Place the .ico file in CubeCart's main folder.
    1 point
  38. We need to find out why they aren't 'sticking'. My experience tells me to first look at those settings that could possibly make the aggregate amount of content larger than 64KiB. Those settings are the Offline Message and Copyright Text. Then second, look at the error log.
    1 point
  39. 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
  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. Hey @radman420 In that case it would appear to be some sort of data issue then if it doesn't show in both Amzin or the foundation skin.
    1 point
  44. I would be quite careful for several reasons : 1) The plugin hasnt been updated in over two years - while this doesnt necessarily mean anything by itself, CubeCart has moved on a lot in 2 years 2) It isnt just the demo site that is suspended, the whole website is suspended - this again could be a temporary oversight and may be back online any time soon or may mean a lot more. 3) There have been numerous complaints over quite a long period of time from users and many posts on these forums about not hearing back from this developer both for paid development work and also support
    1 point
  45. Hey, I can't offer any guarantees as i don't have access to the plugin and the developers demo site has been suspended (not sure if hes still active with cubecart). Looking at the plugin info and screenshots the only compatibility issues i predict is layout issues on the customer side. Providing the template side of things for the plugin are not encrypted this can be overcome by converting it over to bootstrap layout and adding any additional styling no problem.
    1 point
  46. Hey, By default the google analytics js is conditional to cookies been accepted so if you don't use the cookies notice or haven't accepted cookies then the code won't run. If you want to run google analytics regardless of if cookies have been accepted then you'll need to remove the conditional statement by skins > amzin > templates > element.google_analytics.php and remove line 1 and 13 like noted below: {if isset($smarty.cookies.accept_cookies) && $smarty.cookies.accept_cookies=='true'} <<< REMOVE THIS LINE {literal} <script> (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){ (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m) })(window,document,'script','//www.google-analytics.com/analytics.js','ga'); ga('create', '{/literal}{$ANALYTICS}{literal}', 'auto'); ga('set', 'anonymizeIp', true); ga('send', 'pageview'); </script> {/literal} {/if} <<< REMOVE THIS LINE
    1 point
  47. 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
  48. Please make this edit: In the module's file /skin/admin/index.tpl, near line 57, find: {$MODULE_ZONES} <div class="form_control"> <input type="submit" name="save" value="{$LANG.common.save}" /> </div> </form> Change to: {$MODULE_ZONES} <div class="form_control"> <input type="submit" name="save" value="{$LANG.common.save}" /> </div> <input type="hidden" name="token" value="{$SESSION_TOKEN}" /> </form>
    1 point
  49. I found it! was in navigation.ss and .top-bar-section! I am so rusty on this kind of work! Thanks for the help
    1 point
×
×
  • Create New...