Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 10/25/2020 in all areas

  1. I am currently working on my website powered by cubecart when i get time after the day job. https://www.bobityboogemcrafts.co.uk/index.php Really please with this great template available from Amzin (Bootstrap Responsive Skin) by Nitefox designs https://www.cubecart.com/extensions/developer/nitefox-designs
    2 points
  2. Thanks for the feedback. I'm keen to add more features. Helpful. I think we need to make it more attractive with a good default skin and work form there.
    2 points
  3. 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
  4. 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.
    2 points
  5. rework global configuration file found in /includes/ with your new database details. setup/restore database to new location. upload all files. adjust permissions of uploaded files. as a basic test, you can validate those permissions by uploading the latest setup directory from the installer and validate they all report OK. test...
    2 points
  6. Well it's been a long week. New ventures meant I needed a more suitable web shop solution than the manual input Wysiwyg web builder I have used for the last three years. I have had 'proper' shopping carts in the past, but the web has moved on a lot in recent times with far more people using mobile devices to access content nowadays. The Wysiwyg web builder meant I had to design different layouts for different screen sizes by hand, which was a total drag. I have lost count of how many shopping cart solutions I have looked at over the last couple of weeks, but found many that no longer had viable download links (never a good start) and discovered many obsolete programs still out there, that are no longer developed and with subsequently no support network. During my forays I found out that my XAMPP server that allows me to test websites locally on my own computer was utter crud after recent 'upgrades', so moved to a WampServer which is wonderful in comparison. Anyway I eventually drew up a list of potential shopping carts. The one feature I wanted above all others, was an easy checkout process. Hesitation, confusion or complexity is no good for quick cash flow. Those in business will tell you, there is no business till you have the customers cash in your hand. The offerings I looked at included Woocommerce, Zen Cart, Opencart, Abantecart and of course Cubecart. All had their plus and minus points and some features which will appeal some some people, but not others. What did surprise me though is the flaws I found with some of the bigger players out there. Woocommerce I just found weird and confusing, Zen Cart still looked very dated and out of touch with its customer base, with many of the free community shared plugins conflicting with each. Most surprisingly of all Opencart seems to have created endless problems with its 'twig' modules in version three. Even the 'fix patch' didn't work and I couldn't even get one compatible skin (theme) to install without a plethora of error messages. Would I really want that on a live server? Answers on a postcard to..... That left it as a direct shoot out between AbanteCart and Cubecart, both of which are good programs with similar features and to their credit neither of them 'fell over' during testing. Looking at the programs on my offline server setup though, AbanteCart had nearly three times the number of operating files to Cubecart and more importantly a footprint of nearly 80mB, compared to Cubecart's sprightly 27.6mB. Where that becomes important, is if like myself you have more than one site on the same server space. Anyway before this turns into a saga, I had to do a lot of research and had a few long computer chained sessions often going beyond midnight these last few days. Making a bad choice with ecommerce software has the potential to make or break a business. I decided to go with Cubecart over everything else, as I found it very easy to work with. I didn't find it a stressful experience as unlike many others, it just worked flawlessly and did what it was supposed to do. I particularly like the fact you get a core program and just add the bits you want instead of being burdened with a pile of stuff you'll never use. From the front end view, the customer has a layout that is easy on the eyes, is straightforward to navigate and the checkout process is trauma free (and quick). That's the whole point with shopping carts though (or should be). Cubecart won't tick everyone's boxes, but having done the endless research, there are a lot of products out there that simply aren't fit for purpose. Been a long week, but time for a cold beer and unwind session....
    2 points
  7. 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
  8. This is an interesting scenario to solve. I am asking for details so that efforts aren't proceeding to a misunderstood, unworkable solution. As it currently sits in my brain, I want to use an otherwise unused product attribute (GTIN code? 'condition' recoded to "big" and "small"). When AIOS iterates across the basket contents, a flag can be set to invalidate certain other possible shipping choices.
    1 point
  9. Looking forward to hearing how you get on.
    1 point
  10. In your Cpanel screens, there should be a section that details the version of PHP you wish to run, along with any extensions you wish to make available to PHP. Check the box for ZIP Archive.
    1 point
  11. We can assume that the mailer-daemon[at]localhost is a system put in place by your hosting provider. So, begin by creating a support ticket with them. There will probably be no indication about what was objectionable in the email's content, so we cannot attempt to "work around" the issue by changing the wordings of the email phrases.
    1 point
  12. I figured it out and it's working like a champ! What I had to do is edit the Order Completed e-mail and on the link to the postal service website it has to read like this: https://tools.usps.com/go/TrackConfirmAction.action?tLabels={$DATA.ship_tracking} Then, when I enter the tracking number in the order screen, the macro automatically inserts the tracking number, and when the order is marked completed, it e-mails out the link to the USPS and it looks like this: https://tools.usps.com/go/TrackConfirmAction.action?tLabels=9400109205568680959749 (That's an old tracking number from earlier this year) So this issue got resolved. I have another one but I will work on that more before I ask for help.
    1 point
  13. This is me new store https://moonshinerlights.com
    1 point
  14. Hi Abraham. Please see https://support.cubecart.com/hc/en-gb/articles/360003793978-How-do-I-create-a-custom-skin-or-template-
    1 point
  15. Currently, no. There used to be a plugin but the publisher has disappeared. CubeCart used to have a "Tell-a-Friend" feature, but has been removed (it was horribly abused). There exists a manner that is cumbersome and definitely not dynamic: Create a new newsletter and select only the email address of the target customer to send it to.
    1 point
  16. They arent known for providing good support and know nothing (and care even less) about your CubeCart store - to be fair, not really any different from most of the other large generic hosting providers out there where you are simply a number - however they are relatively cheap and you get what you pay for with hosting ! CubeCart can often run out of process memory when processing large images but this would have been clearly recorded in the PHP error_log file as would any errors like this. Images would no have been the cause if you were getting this error when doing a search on the front end of the store though. I have not heard of any memory related issues when doing searches though. If they allow you to increase to 512MB then great, but do go into the PHP Info option in admin and check that the "Master" value also says 512 MB - if it is less than 512 MB, then that is what you will actually be allowed to use regardless of what you set it to
    1 point
  17. In the admin skin's javascript file admin.js, somewhere near line 654. This selector starts/ends with: $("textarea.fck").each(function() { // code that determines how to start the editor $(this).ckeditor(t)}) The javascript file that is the CKEditor utility is loaded via the admin skin template main.php. It is available to anything that wants to use it (meaning, it is not buried in the admin folder.
    1 point
  18. Thanks for the prompt update on it.
    1 point
  19. Let's review: $record['bijkomend'] = (isset($_POST['bijkomend'])); The form element with the input name "bijkomend" will get POSTed if the input tag is within the appropriate <form> block. The statement above tests if the form element exists in the POSTed data. But, so far, the answer is either a 'true' or a 'false' logical value. This is the start of a typical test structure called a Tertiary Operator. We can see that with the $_POST['rating']. To finish that statement: $record['bijkomend'] = (isset($_POST['bijkomend'])) ? $_POST['bijkomend'] : ''; The $record array will be saved in the CubeCart_reviews database table, so the new column 'bijkomend' should have been added to that table.
    1 point
  20. No tutorial that I know of. In admin, Product Options, Option Groups tab... Add a new option group for the first type of option: color? style? some defining characteristic? Required? Check the box. Save. Add a second option group for Size. Required? Check the box. Save. On the Option Attributes tab, select the first option group from the drop-down selector. Add a new attribute and click the white-plus-in-green-circle. Add as many new attributes as needed. Select the Size option group from the drop-down selector. Add as many sizes as needed. Be sure to click the white-plus-in-green-circle for each addition. Save. Bring the product up for editing. Options tab. Start selecting the options from the Add New Option from the drop-down selector. Click the white-plus-in-green-circle. Add all the options that apply to this product. Save & Reload. In the list of options now shown, in the Options Matrix column, check all that should contribute to the various combinations of the product. Save & Reload. Now, you will see an Options Matrix table showing all possible combinations, with a stock level field, and other fields, for each combo. Fill out the table and Save.
    1 point
  21. 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
  22. Depending what you have enabled as far as what contributes to the shipping rate (weight, sub-total, quantity, etc), change the conditions so that a rate would be impossible to match. For example, if there is a weight range of 5-25, change it to 50000-250000. Since this row will now never be seen by the customer, you can also change the description by adding "(added 000)" to remind you what the original range was.
    1 point
  23. No that would make sense because the thumbnails are new. GD isn't very clever and will remove the orientation preference. The source image is unchanged and the browser probably does respect the orientation preference.
    1 point
  24. It is a default setting. In the file /setup/index.php, near line 81, is a list of all the initial settings. The "admin_notify_status" is set to "2" (Processing).
    1 point
  25. 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
  26. Oh my... Be back soon.
    1 point
  27. 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 present.
    1 point
  28. Welcome JoJo! Glad to see you made it to the forums. In the skin template element.product.options.php: Find near line 44: <select name="productOptions[{$option.option_id}]" id="option_{$option.option_id}" class="nomarg" {if $option.required}required{/if}> Change to: <select name="productOptions[{$option.option_id}]" id="option_{$option.option_id}" class="" {if $option.required}required{/if}>
    1 point
  29. Use the Print Order form gateway, adapt it as required. this will bypass the payment step and capture the order as needed.
    1 point
  30. I have already found the translations inside the Admin and changed some of the phrases. If, or rather when, this shop goes live I will have to translate quite a bit more and I will gladly supply my translation then if wanted.
    1 point
  31. It is known to be incomplete as it is not maintained - none of the languages are except the main language definition file which is in English and contains every single language string. If you do go through and translate any / all of the missing language strings then I am sure that @Al Brookbanks and other German speakers would be very grateful. If you use the Admin Language option to do the translations, these are stored in the database but it is then possible to export these as a language file which could be sent to Al to be added back as an update
    1 point
  32. CubeCart doesnt have an EPOS system and you need to get that information from your client - nobody here would have a clue what they are using ! There are a number of cases of stores that have developed links to third party external systems and I know several linking into EPOS systems but there is no standard plugin into any as far as I am aware - it has all been custom work
    1 point
  33. Allow me to make a Feature Request in the GitHub.
    1 point
  34. If it works, don't fix it, right? Some general info you might find useful: Windows servers don't use .htaccess. Instead, all meta data regarding your site's behavior (including URL rewrites/redirects) are contained in web.config (as you've already noted.) The syntax is similar: a rule written for .htaccess can be used in web.config by just plugging in the values in the right spots, e.g. RewriteRule ^$ /index.php [L,R=301] equals <rule name="home"> <match url="^$" /> <conditions logicalGrouping="MatchAll" trackAllCaptures="false" /> <action type="Rewrite" url="/index.php" /> </rule> Search up "regular expressions" for more details on how the matching syntax works. Writing web.config by hand isn't fun, per se, but as you've discovered, it can be done.
    1 point
  35. The image needs to be a complete <img> tag. <a href="{$DATA.storeURL}"><img alt="{$DATA.storeName}" border="0" src="https://diffgif.co.uk/images/logos/Diffgif_logo_inc_web_150x150.png" /></a> However, and unfortunately for everyone, it seems the editor here is malfunctioning. See: https://github.com/cubecart/v6/issues/2285 and https://github.com/IGx89/CKEditor-ShowProtected-Plugin/issues/10 If the template has already been corrupted, we will need to make some deep dive fixes.
    1 point
  36. Please verify two things if you are using CC642: Examine the database to determine if all the paths in CubeCart_seo_urls end in .html. In admin, Store Settings, Search Engines tab, "SEO URL Extension", what is the setting?
    1 point
  37. There will be an edit to each of main.php and box.navigation.php. There will also be content added to the otherwise empty file cubecart.default.css. main.php From: <div class="row small-collapse"> <div class="small-12 columns"> {include file='templates/box.navigation.php'} To: <div class="row small-collapse" style="max-width: none;"> <div class="small-12 columns"> {include file='templates/box.navigation.php'} box.navigation.php From: <ul itemscope itemtype="http://www.schema.org/SiteNavigationElement" class="left"> To: <ul itemscope itemtype="http://www.schema.org/SiteNavigationElement"{* class="left" *}> cubecart.default.css Add: @media only screen and (min-width: 58.75em) { .top-bar-section ul { display: block; width: max-content; margin: 0 auto; } } The media directive limits this to the desktop display only. Pads and mobiles should behave as they did originally. Have CubeCart clear its internal cache.
    1 point
  38. What were your findings in admin, Store Settings, Layout tab? Verify that there exists a skin template named box.popular.php.
    1 point
  39. Hi @radman420 Sounds odd, neither the CC6.4.1 update or the skin update would affect the visibility of the popular products section as from my knowledge nothing was changed in relation to that. This behaviour is not occurring on any of my test setups so not sure what the cause would be. Have you tried going to site settings > layout and clicking save , then clear your sites cache ? Also, if you right click on the area the box normally is then click "inspect" or "inspect element" can you any html code in the console panel that relates to the popular products? Thanks, NiteFox
    1 point
  40. I'd probably wait for 6.4.2 as 6.4.1 has a few bugs which have been fixed for 6.4.2 but not sure if the fixes have been applied to the current files for 6.4.1
    1 point
  41. That works thank you Before And after
    1 point
  42. Wasn't to sure where to put this as its not really a CC issue but more of a marketplace suggestion but anyways A couple times i've come across customers who didn't realise they needed to log into their buyers accounts in the marketplace to access updates/previous purchases and get confused when they click the download/install token button to then see its unavailable until purchased. So, was wondering if maybe when they click the update link in the admin panel they should be redirected to the marketplace login page instead of the product page or maybe alter the update url (?update=1) then add a notice to the product page if update=1 advising them to login? It's a minor thing but hey we all love abit of fine tuning.
    1 point
  43. Thanks for this. I was going to make some tweaks tomorrow so I'll add this to the list (or a similar solution).
    1 point
  44. This sounds like you have a mix of old and new files. I expect the admin_xxxx folder has old content. Please make sure the content of the admin gets uploaded into the correct directory. Each CubeCart store has a unique admin folder name.
    1 point
  45. You can see the manual update guide for Amzin at http://nitefox.x10host.com/docs/ManualUpdates/amzinguide.html - The latest update (V1.03) is mainly a compatibility update for CubeCart 6.4.0/6.4.1
    1 point
  46. Didn't meant to offend anyone I love the software it's great really stable. Unfortunately it wont upgrade my data base, the settings all appear to be correct. Temporary Tables are allowed. I do suspect its to do with permissions but I just don't have the time to learn it all right now so im sticking with 6.2.9 until the next update when I will try again. Thanks I think its an issue with the host. Its no big deal to me here, I like the learning bit anyway and besides I will be beginning a new project soon meaning a fresh instal. This will involve digital downloads and if all goes well its going to be run using Cube. If you wanted to look at my data base setting inside my host plan Im happy to give you the credentials privately of course for your own information and so you can see if changes need to made to the build to accommodate this. There is at least one other person who has the same problem. Not asking you to do my work but if you wanted to look its fine by me.
    1 point
  47. We are excited to announce the release of 6.4.0 beta which contains a number of new features. This is a beta release and may not be suitable for production stores. Please do take a moment to read the release notes. We would like to thank all those who have contributed towards the development and testing of this version. What's new? Automatic 301 redirection support for changed SEO URL's and custom 301/302 redirection support with support for removal of ".html" from SEO URL paths. Metadata title and description support for contact us and gift card pages. Built in What3Words integration enabling customers to specify their delivery and billing address to a 3m2 location anywhere globally with just three words. Media player page for streaming of mp3/mp4 type digital downloads with title and description. Significantly improved image file manager with gallery style view, search tool and multiple delete. Option to delete product image during product delete. Improved system error logging with URL, back trace and dashboard count notification. SendGrid support for email delivery. Discount codes can be linked to manufacturer/brand. Discount codes can be restricted by customer. e.g. 1 per customer. GTIN code added to product option matrix. Miscellaneous bug fixes. Download: CubeCart-6.4.0-b1.zip Download: CubeCart-6.4.0-b2.zip Release Notes The setup process will attempt to rewrite part of the root .htaccess file but may fail in some hosting configurations. If you see 404 errors after upgrade please either delete the .htaccess file so that it can automatically be regenerated or find; RewriteRule ^(.*)\.html?$ index.php?seo_path=$1 [L,QSA] and replace with RewriteRule ^(.*)?$ index.php?seo_path=$1 [L,QSA] What3Words will require an API key which can be entered into your stores settings in the "Features" tab. If you are not using the default foundation skin then template code changes will be required.
    1 point
×
×
  • Create New...