Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Noodleman

  1. seems valid. One thing that can cause oddities is the session data not being stored correctly. check your web server error log and see if you have warnings about sessions in there. it may offer some clues.
  2. snap aww, smilies are still broken
  3. weird. seems to have worked OK for me. it's a bit slow, you've got a bad reference to a CSS file, and also an image file. I'm testing in Chrome. FireFox also working correctly. Check your cookie domain is set correctly in store settings, review the error log and check if you have anything being reported.
  4. unsure without seeing the error first hand. can you share a link?
  5. probably a javascript issue. open your dev console (F12) and check for messages/errors when reproducing the issue.
  6. there may be some other considerations. Why pay for SSL? you can (in most cases) use Lets Encrypt at no cost, however some hosting providers don't allow you to use this. If you are using any tracking codes / conversion codes they may need to be updated to reflect the domain change (google analytics etc) If you use any live chat software, chances are the domain needs to be updated in config Some commercial modules are domain locked by license, you may need to have these migrated in store settings, under SSL tab change the domain to reflect the new domain A
  7. Sounds expected. the upgrade from v4 will rename images to make them more URL friendly, so spaces are replaced with underscores etc. If you have any direct linked images in descriptions they will need to be revised. You may find that after the upgrade, going to the "File Manager" in the admin area shows a 500 error. if it does, keep refreshing until it goes away. it will take a while to build the image cache, and the error means it timed our doing a "batch" of images. should be a one time thing after upgrade unless you clear the image cache manually. CubeCart_image_index should be p
  8. status off will remove the item from the store front available for purchase off and status on, will keep the item visible on the store front, but not allow it to be purchased.
  9. Before you make ANY change using a bulk utility, take a database backup. this is in case it goes wrong and you need to rollback the changes. I've seen it happen countless times.. please backup! You may not need the module I offer, it's there for a very specific purpose. I've not checked into this feature for you as I am pushed for time at the moment, just wanted to share a warning about the backup to potentially save you a headache later.
  10. Do you have English UK installed? if not, try installing that. there is a dependency on it, even if your using other languages. if not, cross reference your store default language in store settings, and validate that actually exists. another possible glitch from an earlier version.
  11. did you generate one yet? Store Admin -> Maintenance it will then be here: https://testvalleymodels.co.uk/sitemap.xml.gz
  12. Perhaps this may be a problem that can be addressed with product filters? you can setup filters for colours/brands/shades etc, whatever you require and let customers filter to those items of interest, then have each single paint tin/product you keep on shelf as a product in the store, easier for inventory control. Not a cheap solution, but its a really powerful, mature filter system https://www.cubecart.com/extensions/plugins/product-filters-filter-categories-and-build-menus-dynamically-using-product-metadata
  13. There isn't a limit, however consider the usability from a customer perspective, at some point it becomes painful to select the colours you want. if it were I, I would consider 1 item per colour, with the shades as options.
  14. copy/paste into new directory (or, download via FTP, and upload to new location) set permissions update global file with new database details backup/restore database into new DB set new store URL in store settings done..
  15. Morning Check you are using the latest version of the skin from here: https://www.cubecart.com/extensions/skins/noodleman-co-uk-store-theme and, if you are still facing an issue I'll check into it if you can share a link to an example?
  16. This module was created to solve these kind of issues. https://www.cubecart.com/extensions/plugins/product-addons-easily-purchase-related-products Essentially, each item would be managed as a single product,. and associated via addons. A more simple solution is to use a price tier https://www.cubecart.com/extensions/plugins/discount-price-tiers-plugin This may, or may not be suitable depending on the inventory.
  17. not as easy as you would think. might be easier to just write a cron job, run it once a minute and if it finds things that match your criteria, update the category as required.
  18. This is about as close as I can get without making any module changes. https://www.cubecart.com/extensions/plugins/dynamic-category-content-auto-populate-categories It's based on a keyword search / product Id's, but might be able to be modified to also support stock levels in some way
  19. Open a request to have it added here: https://github.com/cubecart/v6/issues here's an example of one I requested: https://github.com/cubecart/v6/issues/2209
  20. Works fine,it's pretty simple and could do with some refinement in the future to make the UI a little nicer and add additional features such as an API so those of us with a larger catalogue can setup automated order processing (for licenses etc). PayPal do also take a fee on top of the CubeCart fee.
  21. just delete all the "content" of cache and don't sync it to the new server. it will get rebuilt by the new server and will save you a lot of time.
  22. Hide the option with a default value, dont remove it. Css class "hide", or input type = hidden
  23. it's probably a module, encoded for an earlier version of PHP, list the modules you have installed that are not free/supplied by CubeCart directly.
  24. Acces.... *shudder*... the error I am guessing you are getting will relate to MySQL strict mode. you can disable it if needed
  • Create New...