Jump to content

burt

Team
  • Content count

    14,125
  • Joined

  • Last visited

  • Days Won

    555

Everything posted by burt

  1. I do get your point, but it's outside the scope of the storage of the Data... 🤷‍♂️
  2. burt

    Strong Consumer Authentication (SCA)

    https://www.fca.org.uk/news/press-releases/fca-agrees-plan-phased-implementation-strong-customer-authentication
  3. The box/tray/pallet would (almost certainly) have a different Identifier than the individual items inside.
  4. 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/
  5. https://github.com/gburton/CE-Phoenix/blob/master/admin/categories.php#L229 Pads it out to 14.
  6. 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?
  7. Q: Is it possible that some confusion arises because you are maybe working with a script that does not "follow the rules" ?
  8. I do agree that MPN is something else entirely...unrelated to GTIN aka UPC aka EAN.
  9. 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.
  10. 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" ?
  11. 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.
  12. 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?
  13. CE Phoenix Phoenix is the Master Community Version of osCommerce https://github.com/gburton/Responsive-osCommerce/releases https://www.oscommerce.com/Products Demo Site https://template.me.uk/phoenix/index.php External Libraries https://github.com/gburton/Responsive-osCommerce/wiki/External-Libraries PHP Version Minimum Maximum 7.0 7.1.x Image Credits Images in the default installation are copyright their respective owners; Image Owner osCommerce Logo osCommerce Phoenix Logo G Burton Oranges Eelffica from Pixabay Lemons Eelffica from Pixabay Pears Eelffica from Pixabay Apples Eelffica from Pixabay Tomatoes Rocky_H from Pixabay Heart Gerhard Gellinger from Pixabay Thank You To all shopowners, developers, consultants and business owners who have supported the project over the years. Beer Tokens "Beer Tokens" are not used to purchase beer - they are used to give time into the Project. I am hopeful that enough shopowners, developers, consultants and businesses ... will join the Phoenix Club to allow two professional developers to work on the code on an ad-hoc basis. Join the Phoenix Club If you wish to sponsor ongoing and future development, please consider joining the club https://forums.oscommerce.com/clubs/1-phoenix/
  14. 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!
  15. 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)
  16. Affects nothing so far as I recall. You can input a sort order number but they remain sorted by name (I think). I was going to change it to have sort ordering, but that task was removed in favour of more important things.
  17. burt

    Phoenix installation issues

    Although the databases are fairly similar...you can't just use a CE database for a new installation of Phoenix. So, when you come across errors like this, it is because your (old) DB does not contain required data. In this exact instance, turn off (uninstall) and then turn on (reinstall) the Navigation Bar module: Admin > Modules > Content Have you have played with a brand new Phoenix running its own database? Just to get a feel of how and what Phoenix is before you start to try to integrate your products etc.
  18. burt

    Site Counter

    IIRC, site counter was removed a very long time ago (years, perhaps 4 or 5 years ago). The questions I asked prior to its removal; what use is that count to the shop owner what use is that count to a site visitor Concluded (crowd-sourced) answers were "useless" and "useless". To re-instate it in Phoenix, a way to do it would be to build out a footer_suffix module for it or maybe it could be done by a siteWide hook.
  19. I introduced this Bug in 1.0.2.0 👎 I've pushed a fix in 1.0.2.1 👍 As an easy todo, here and now, fix...do exactly as @René H4 states; uninstall the module and then re-install the module.
  20. Loads of posts got nuked when someone went on a bit of a rampage. It's gone.
  21. Or, if you are looking to use the zip files I provide for updating...just follow the relevant instructions, then at the end of the instructions... admin > tools > security checks
  22. Install 1.0.1.0 using the /install/ folder. Once installed, the first thing you do is admin > tools > security checks and fix any "insecurities", one of which will tell you about /install/
  23. Now you mention it I do (vaguely) recall writing a post explaining how to (fairly) easily add a category image to the Title Module, which was then taken further in the codebase ready for people to start using... https://github.com/gburton/CE-Phoenix/blob/master/includes/modules/content/index_nested/cm_in_title.php#L41 I don't remember a core-code separate category image Module though...I could very well be mistaken on that though.
×