Jump to content

burt

Team
  • Content count

    15,299
  • Joined

  • Last visited

  • Days Won

    633

Everything posted by burt

  1. Phoenix 1.0.1.4 Couple of language changes that are mistakes so here are the two commits to bring you from 1.0.1.3 to 1.0.1.4; https://github.com/gburton/CE-Phoenix/pull/772/commits/ffc96cf13c4992058c0c14a5680968bb87d97e38 https://github.com/gburton/CE-Phoenix/pull/772/commits/b9b88c9376fe010818f692883f712a44fe8cb266 Make sure you are on 1.0.1.3 before performing these two changes. Many thanks @raiwa for the heads up. @cupidare for your attention. Apologies to all for dumb mistake.
  2. Phoenix 1.0.1.3 How to update Find out what version you are on now; admin > tools > version checker, then perform the necessary manual 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 EG, if you are on 1.0.1.0, you must perform the 1.0.1.1 & 1.0.1.2 hotifxes, then; Apply the 1.0.1.3 changes -> 1.0.1.3.zip You could also simply download & install the latest v1.0.1.3 https://github.com/gburton/Responsive-osCommerce/tree/1.0.1.3 and install it. You could make commit by commit changes 1.0.1.2 to 1.0.1.3: https://github.com/gburton/CE-Phoenix/compare/1.0.1.2...1.0.1.3 I suggest the simplest way (assuming you are on 1.0.1.2) is to grab the 1.0.1.3 zip, unzip it, and upload the files. Special Thanks to forum members for their constructive feedback and bug hunting to ruden, scottcwilson, scro0303 for minor code updates to @raiwa for Spanish Language Fileset (linked in README) Install New Modules There are no NEW modules to install Reinstall Existing Modules Completely TURN OFF (uninstall) and THEN TURN ON (reinstall) the following module(s); Admin > Modules > Content > Navigation > Navbar Delete Obsolete File includes/languages/english/product_reviews_info.php Enjoy! Notes for Language Maintainers @cupidare DE @raiwa ES /includes/languages/english.php /includes/languages/english/advanced_search.php /includes/languages/english/modules/boxes/bm_specials.php /includes/languages/english/modules/boxes/bm_whats_new.php
  3. Uninstall the module and then re-install the module.
  4. burt

    Vendor Login

    What is a "vendor login"? What is it for, who would use it. Etc. Your post is quite cryptic...it might be useful to shine a light so that others can more clearly see what you are proposing to make.
  5. burt

    Stop Google adding bogus names

    So...what steps have you taken so far other than; deleting out names after they've been added contacting your clueless techy guy Have you installed (eg) Capcha Honeypot Action Recorder What version of osCommerce are you using?
  6. burt

    Creating an extra Order_Total Field

    You do not need an order total module. You simply need to force the checkout to AUD. So, make a header_tag or hook for checkout_shipping (or any other page prior to where the buyer goes off to pay) that; checks if the selected currency is AUD and if it is not AUD reload the page with AUD selected and put out a messageStack message to let the buyer know that you only accept AUD for payment. That is simplest. Playing with order_totals is far from simple.
  7. As of 24 July, BSv3 is EOL with no more security updates etc https://blog.getbootstrap.com/2019/07/24/lts-plan/ This news should nudge you to at least look 👀 at Phoenix (BSv4 Shop Side) if you have not already done so.
  8. Taken from a totally separate piece of ecommerce software called Ecwid. But it does show possibilities.
  9. You've already seen the problem. What if someone else wants; Top Left Right Left Middle Right Left Bottom And then someone else wants Left Right Full Full Left RIght Full Put simply; The overall controlling module would need to be able to be changed to any layout needed. Then the modules would need to dynamically pick up available slots. Good Luck with that!
  10. Idea: Chop up the product_info page and make modules installable per chopped section. Like the navbar is done (home, left, right). That adds in different problems but may be a solution that works. Would take some hardcore coding though.
  11. You'll notice none of those examples show an output like the image posted earlier. They are all in standard rows.
  12. BSv4 uses Flexbox and does not have a "masonry" style capability at the moment. This approach that can be used in BSv3 cannot be used in BSv4.
  13. Install the relevant JSON-LD module. admin > modules > header tags > {install} More at https://forums.oscommerce.com/topic/493728-turn-on-the-json-ld-modules/
  14. Two discussions merged. Please don't create multiple discussions about the same thing, thx.
  15. burt

    Unable to login to Admin

    local xampp does not need https redirects. remove them.
  16. Things do generally seem more positive since the release of Phoenix. It's solved some of the points that some people liked to regularly quibble about; lack of "official" acceptance lack of versioning ease of updating Joined the Phoenix Club?
  17. Cheers. wasn't my decision decision was made in 2014 or maybe earlier - 5 *years* ago at least - I know I was on my holidays when the first argument about it got out of hand announcement was made years ago in forum work has been ongoing ever since to get osc updated, work has not yet started in admin area hardly - waiting on more shopowners, developers, conultants and businesses to actively support forward movement. <blunt>addon compatibility, that's up to addon makers</blunt> Maybe your focus is elsewhere - which is 110% cool - hence why you haven't come across this in the past 5 years ?
  18. Avoid core code changes...you could instead use a Hook... Try it in Phoenix with one of the pre-placed sitewide hooks
  19. Yes. That'd take...a minute or two ? In this instance...who runs osCommerce with prefixes? 1 in 1000 shopowners? I get what you're saying, but to do positive things...sometimes means a perceived negative thing has to be lived with. I did actually have a branch with full pre-fixing capability - but there was very little interest in it, so it got deleted.
  20. You'd need to search for them, they date back to 2014 or earlier. Who cares about pre-fixes? Databases are cheap.
  21. To allow the ethos of "no core code changes". Already covered in depth, multiple times, over the years - there's some threads you can read more buried in the forum. Note also that FILENAME_* are gone too...
  22. burt

    Dutch Translation for Phoenix

    Before you do anything else, please rename your admin folder, and change the admin configuration file to reflect the new name. I have just removed a number of links to your admin area...which means that anyone (and everyone) now knows the location of your admin area. Please be more careful when copy/pasting to this forum - I have found that the best way is to paste to text (eg notepad++), then copy from that and re-paste into this forum. Again: change your admin folder name...now.
  23. burt

    Email queuing system

    It is still on very limited release due to a couple of bugs to iron out etc.
  24. Phoenix 1.0.1.2 How to update 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 Apply the 1.0.1.2 changes -> 1.0.1.2.zip You could also simply download & install the latest v1.0.1.2 https://github.com/gburton/Responsive-osCommerce/tree/1.0.1.2 and install it. You could make commit by commit changes 1.0.1.1 to 1.0.1.2: https://github.com/gburton/Responsive-osCommerce/compare/1.0.1.1...1.0.1.2 I suggest the simplest way (assuming you are on 1.0.1.1) is to grab the 1.0.1.2 zip, unzip it, and upload the files. Special Thanks to forum members for their constructive feedback and bug hunting to @cupidare for German Language Fileset (linked in README) Install New Modules Admin > Modules > Header Tags > {install} > Canonical Links Completely TURN OFF (uninstall) Modules (these payment methods are stale) Admin > Modules > Payment > Moneybookers (all) Admin > Modules > Payment > Sofortueberweisung Admin > Modules > Payment > Chronopay Admin > Modules > Payment > Inpay Admin > Modules > Payment > iPayment Delete Files (AFTER having turned off the modules above) /includes/modules/payment/moneybookers_*.php /includes/languages/english/modules/payment/moneybookers_*.php /admin/ext/modules/payment/moneybookers/ (folder and all files inside) /includes/modules/payment/sofortueberweisung_direct.php /includes/languages/english/modules/payment/sofortueberweisung_direct.php /admin/ext/modules/payment/sofortueberweisung/ (folder and all files inside) /includes/modules/payment/chronopay.php /includes/languages/english/modules/payment/chronopay.php /admin/ext/modules/payment/chronopay/ (folder and all files inside) /includes/modules/payment/inpay.php /includes/languages/english/modules/payment/inpay.php /admin/ext/modules/payment/inpay/ (folder and all files inside) /includes/modules/payment/ipayment.php /includes/languages/english/modules/payment/ipayment.php /admin/ext/modules/payment/ipayment/ (folder and all files inside) Enjoy.
  25. You can do anything you like...that's the beauty of the open codebase. Go to it! Do note that I have plans to overhaul and simplify the code in the product_listing module at some point in the near future.
×