Jump to content

burt

Team
  • Content count

    14,558
  • Joined

  • Last visited

  • Days Won

    584

Everything posted by burt

  1. And what does the order (in your admin area) show?
  2. burt

    phoenix 1.0.2.0 version check

    FYI here is the setting for the Phoenix Demo site; Obviously I have blanked out the account username. And here is that location via FTP (shows the cache file for version_check); Yours should be similar.
  3. burt

    phoenix 1.0.2.0 version check

    Make sure that cache directory (a setting in admin) is correct and that it exists within the file structure of your hosting. eg: /tmp/
  4. Anything in the configuration table is "auto loaded" ready to use, so you can just reference the configuration_key directly to get the value of it.
  5. $cashondelivery_cost = CASHONDELIVERY; Don't overthink it
  6. burt

    Sub Categories Bug

    Was fixed in 1.0.2.1 I think; https://github.com/gburton/CE-Phoenix/commit/70438f7581a8b1b0f59f7d570bcdab1970a1444e#diff-6cf84f05b277528edf3e7c81eb26cce0 As you say...turning the module off and on again fixes it.
  7. The only difference you will find is that Phoenix has the ability to choose whether or not to load the sample data (products/categories etc) as part of the installation procedure.
  8. It believe it is you who is misunderstanding the concept. The GTIN site clearly states that storage of GTIN *must* be 14 digits. That you can't code a script to read that, is on you. I found a nice class at phpclasses which you'll find useful. https://www.phpclasses.org/package/8560-PHP-Detect-type-and-check-EAN-and-UPC-barcodes.html
  9. I'll try one more time...taking your pallet example; You buy a pallet of laptops. The pallets identifier is 12345678901234 This means *nothing* to hardly anyone. Who cares about it other than you...the next time you want to buy another pallet. Each Laptop inside has an identifier 0987654321123 In your shop you would sell individual laptops at 199.99 each, and in the GTIN input field you would insert: 0987654321123 That would allow your branded laptops to be sold on Google Shopping by you. Does that make it more clear? I understand that you are struggling to come up with code to plug into a suppliers CSV, but that's outside the scope of oscommerce.
  10. I do get your point, but it's outside the scope of the storage of the Data... 🤷‍♂️
  11. burt

    Strong Consumer Authentication (SCA)

    https://www.fca.org.uk/news/press-releases/fca-agrees-plan-phased-implementation-strong-customer-authentication
  12. The box/tray/pallet would (almost certainly) have a different Identifier than the individual items inside.
  13. It is a requirement to store the GTIN as a 14 digit number. What you (end user) does with that 14 digit number...is outside the scope of the storage. https://www.gtin.info/
  14. https://github.com/gburton/CE-Phoenix/blob/master/admin/categories.php#L229 Pads it out to 14.
  15. Then the company that delivers the CSV's needs a better developer on board! Email them? In osC; GTIN exists - has done since 2015/2016 (ish). That covers EAN and UPC as described above. If MPN is now needed...simple enough to add. It's not required by (eg) Google Shopping, but I realise there are more sites/services than G-shopping out there. Thoughts anyone? MPN needed in Core. SKU is something different again - at the moment osC has no stock checking other than on the main product and I assumed (rightly or wrongly) that most shopowners would be using the "products model" as some type of "SKU" factor?
  16. Q: Is it possible that some confusion arises because you are maybe working with a script that does not "follow the rules" ?
  17. I do agree that MPN is something else entirely...unrelated to GTIN aka UPC aka EAN.
  18. https://www.gtin.info/ The family of data structures (not symbologies) comprising GTIN include: GTIN-12 (UPC-A): this is a 12-digit number used primarily in North America GTIN-8 (EAN/UCC-8): this is an 8-digit number used predominately outside of North America GTIN-13 (EAN/UCC-13): this is a 13-digit number used predominately outside of North America GTIN-14 (EAN/UCC-14 or ITF-14): this is a 14-digit number used to identify trade items at various packaging levels Note that each of these is a GTIN (bolded), but also note their name in Brackets (bolded)...this is taken from the global GTIN site.
  19. Memory hazy so forgive me if incorrect (or out of date!); GTIN is the overall name for UPC and EAN. GTIN's can be 8 or 12 or 13 or 14 digits long. If less than 14 digits, they have to be stored in the DB with preceeding 0's, eg; GTIN/EAN/UPC: 1234567 Has to be stored in DB as 00000001234567 GTIN/EAN/UPC: 123456654321 Has to be stored in DB as 00123456654321 GTIN/EAN/UPC: 1234567891234 Has to be stored in DB as 01234567891234 GTIN/EAN/UPC: 98765432198765 Has to be stored in DB as 98765432198765 What the end user then does with it...is up to them. Shopowner may display it or change it to a barcode. Scripts may read them and do things (eg place products in a feed) and so on. So, boil it down; In the database GTIN aka EAN aka UPC *must* be exact 14 digits it may have zero's to pad it out to 14 That's it... there is nothing more needed...on the storage side. Is it possible that some confusion arises because you are maybe working with a script that does not "follow the rules" ?
  20. GTIN and EAN and UPC are all the same thing... I *think* - recall looking into it quite deep before i coded it into osc, but that was a few years ago so memory hazy.
  21. Note that Google Shopping does require use of GTIN, whereas use of MPN is not mandatory. I suppose we should add a new field specifically for MPN?
  22. Phoenix 1.0.2.1 Join the Phoenix Club https://forums.oscommerce.com/clubs/1-phoenix/ This Update Fixes bug in one of the product listing files - TY @raiwa for heads up Deprecate custom.css - A few HTML changes in some files to accommodate this Fixes bug in data-price in a couple of places - TY @raiwa for heads up Adds RU language fileset link in Readme - TY @Fredi Update FA - To 5.10.1 Fix Sort By Bug in products_new.php - TY @Heatherbell for heads up Modernise Reviews - Deprecate reviews.php - Deprecate product_reviews_info.php - Remove links to the above pages - Prettify and Pre-install Reviews module on product_info.php - Move "write review" into /ext/ - Make stars "gold" Update Version - To 1.0.2.1 Special Thanks to Forum members for constructive feedback and bug hunting to Phoenix Club members for constructive feedback on the new Layout to @cupidare @raiwa @Fredi for maintenance of language filesets Notes for Language Maintainers @cupidare DE @raiwa ES @Fredi RU /includes/languages/english.php /includes/languages/english/modules/boxes/bm_reviews.php /includes/languages/english/modules/content/footer_suffix/cm_footer_extra_copyright.php /includes/languages/english/modules/content/product_info/cm_pi_reviews.php /includes/languages/english/modules/content/reviews/write.php How to update ZIP FILE, easy upload. Find out what version you are on now; admin > tools > version checker, then perform the necessary updates; Make sure you have applied the 1.0.0.1 hotfixes Make sure you have applied the 1.0.0.2 hotfixes Make sure you have applied the 1.0.0.3 hotfixes Make sure you have applied the 1.0.0.4 hotfixes Make sure you have applied the 1.0.1.0 hotfixes Make sure you have applied the 1.0.1.1 hotfixes Make sure you have applied the 1.0.1.2 hotfixes Make sure you have applied the 1.0.1.3 hotfixes Make sure you have applied the 1.0.1.4 hotfixes Make sure you have applied the 1.0.2.0 hotfixes All previous hotfix zips are listed in this thread. EG, if you are on 1.0.1.0, you must perform 1.0.1.1 hotfix to the latest listed hotfix, then; Apply the 1.0.2.1 changes -> 1.0.2.1.zip Read and perform the "if updating an existing phoenix" section DOWNLOAD AND INSTALL FULL VERSION You could simply download & install the latest full v1.0.2.1 https://github.com/gburton/Responsive-osCommerce/tree/1.0.2.1 COMMIT BY COMMIT (MANUAL CHANGES) 1.0.2.0 to 1.0.2.1: https://github.com/gburton/CE-Phoenix/compare/1.0.2.0...1.0.2.1 WHAT IS SIMPLEST I suggest the simplest way (assuming you are on 1.0.2.0) is to grab the 1.0.2.1 zip, unzip it, and upload the files. If Updating an Existing Phoenix Make sure that you have first updated fileset to 1.0.2.1 (by either manual commit, or uploading zip), then, doing this in order; 1. Install New Modules There are no NEW modules to install 2. Uninstall Existing Modules Completely turn off (uninstall), if you have them installed Admin > Modules > Content > Reviews Button Admin > Modules > Navbar Modules > Review Link 3. Reinstall Existing Modules Completely TURN OFF (uninstall) and THEN TURN ON (reinstall) the following module(s); Admin > Modules > Boxes > Reviews aka bm_reviews Admin > Modules > Content > product_info > Reviews aka cm_pi_also_purchased 4. Delete Obsolete Files includes/languages/english/modules/content/product_info/cm_pi_review_button.php includes/languages/english/modules/navbar_modules/nb_reviews.php includes/languages/english/product_reviews.php includes/languages/english/product_reviews_write.php includes/languages/english/reviews.php includes/modules/content/product_info/cm_pi_review_button.php includes/modules/content/product_info/templates/tpl_cm_pi_review_button.php includes/modules/navbar_modules/nb_reviews.php includes/modules/navbar_modules/templates/tpl_nb_reviews.php product_reviews.php product_reviews_write.php reviews.php custom.css 5. Run SQL There is no SQL that needs to be changed. Enjoy!
  23. burt

    Phoenix installation issues

    Don't run before you can walk... Get a new, clean Phoenix set up and have a play with it. There are lots of different things about Phoenix compared to older CE editions, and (most of) that is stored in the two config tables. When happy, then port over your DB but NOT the two config tables (configuration and configuration group)
×