Jump to content
Latest News: (loading..)

burt

Team
  • Content count

    13,472
  • Joined

  • Last visited

  • Days Won

    516

Everything posted by burt

  1. burt

    Email queuing system

    It's just a template so individual shopowners can easily set it up as they like and tweak it etc. HTML Emails are actually quite difficult as email programs render the output markedly differently. Well, it's certainly close enough to get the updated system out to the two testers to try. Tomorrow chaps.
  2. burt

    Email queuing system

    I now have this working smooth with a Cron - which I have set for every 5 minutes. On a busy shop, you could set it for every 1 minute, on a slow shop you could set it for once a day - you get the idea. Anyway in the test shop as it is set for every 5 minutes, the lonest you'll need to wait (to get the order_success email) is 5 minutes... So, if anyone now wants to test it, please go ahead: https://template.me.uk/outgoing/ All I ask is that you use a REAL EMAIL that you have access to so that you can receive/view the order_success email (which is HTML). The "slug" (aka template) for the order_success email looks like this): <p>Dear {{FNAME}}, thank you for your order #{{OID}}.</p> <p align="center"><img src="https://template.me.uk/outgoing/images/apps/thanks.png"></p> <table cellspacing="0" cellpadding="0" width="100%"> <tr> <td valign="top"><b>Products:</b></td> <td valign="top">{{PRODUCTS}}</td> </tr> <tr> <td colspan="2"><hr></td> </tr> <tr> <td valign="top"><b>Invoice:</b><br>#{{OID}}</td> <td valign="top"><b>Full Invoice:</b><br>https://template.me.uk/outgoing/account_history_info.php?oid={{OID}}</td> </tr> <tr> <td valign="top"><b>Date Ordered:</b><br>{{ORDER_DATE}}</td> <td valign="top"><b>Status:</b><br>{{ORDER_STATUS}}</td> </tr> <tr> <td valign="top"><b>Payment Method:</b><br>{{PAYMENT_METHOD}}</td> <td valign="top"><b>Order Value:</b><br>{{ORDER_VALUE}}</td> </tr> <tr> <td valign="top"><b>Delivery Address</b><br>{{DELIVERY_ADDRESS}}</td> <td valign="top"><b>Billing Address:</b><br>{{BILLING_ADDRESS}}</td> </tr> </table> <p>A big BIG BIG Thank You from all of us here at Burtys Test Shop!</p> As you can see, that is obviously a very basic HTML template - if you look back through this thread you will see @Dan Cole has come up with a much better HTML template for his emails. But read between the lines and you'll see that it you are, pretty much, limited only by your imagination. Feel Free To Test...any feedback is gratefully received.
  3. With a big thanks to @Heatherbell I have a day next week and a day the week after to commence work on; fixing php7.2 warnings and errors translating old x.x (some of which relates to php4!) php code to newer 7.x formatted code In the meantime, if anyone sees any more errors/warnings please reply to this thread stating what the error says and where you found it (eg an URL) or how you made the error appear (eg only happens when pressing edit on XYZ module) and so on. As much details as you can give would be very helpful.
  4. I've a little bit of time in hand and it seems like this is the next necessary thing to solve, the use of php7.2. But I need your help to point out any problematic area so that attention can be given to them. To help...you'll need an installation of CE (any flavour that is Frozen or later) running on php 7.2 - with error reporting dialled right up. To set up error_reporting to show everything that is wrong: includes/application_top.php Find: error_reporting(E_ALL & ~E_NOTICE & ~E_DEPRECATED & ~E_STRICT); Change to: ini_set('display_errors', 1); ini_set('display_startup_errors', 1); error_reporting(E_ALL); admin/includes/application_top.php Find: error_reporting(E_ALL & ~E_NOTICE); if (defined('E_DEPRECATED')) { error_reporting(E_ALL & ~E_NOTICE & ~E_DEPRECATED); } Change to: ini_set('display_errors', 1); ini_set('display_startup_errors', 1); error_reporting(E_ALL); Save both files. Obviously...you DO NOT want to do this on a live shop as it will show errors to your customers, so hopefully a few people have a test shop to play with... Now if you browse your test shop...all warning and errors will appear. Thank you in advance. Please copy/paste the following as a reply: URL: WARNING/ERROR:
  5. burt

    jQuery vulnerability -- upgrade needed

    Admin side is not started. Waiting on more support from individuals and companies using osCommerce, in order to march forward.
  6. burt

    version with php7.2

    Opinions vary & everyone is entitled to their opinion. No need for any apologies from any parties, no need to attempt to start arguments (again). /end
  7. burt

    jQuery vulnerability -- upgrade needed

    Note that CE has been on the 3.x jQuery for over 2.5 years. CE is presently on 3.3.1 (edge) and 3.1.1 (frozen), easy way to check external libraries on the Wiki; https://github.com/gburton/Responsive-osCommerce/wiki/External-Libraries
  8. If you don't like what we're doing in the Community Edition (in your words, "shoving stuff down your throat")...then it is simple; stay on the official osCommerce version. Official version is still useable, just nowhere near as useable as the Community Edition.
  9. burt

    Email queuing system

    Always. Problem is that by thinking of doing one thing different/better...it means coding something else different/better. But, I do now have it working. It also now has an email pre-viewer;
  10. burt

    Email queuing system

    Right now I am working on setting up a Cron system for this system. Having not really played in-depth with Cron before, it's proving to be a PITA. But the system is close to starting the next phase of testing.
  11. burt

    Email queuing system

    nl2br - which is a pain in some circumstances. So I removed it, in favour of user using HTML.
  12. burt

    Email queuing system

    Yep looks good, thanks. Big gap is from my testing (of line breaks, as well as you can see such things as BOLD and Italic etc. Thanks for testing. Here;s the template that created that; Dear {{FNAME}}, thank you for your order #{{OID}}. <b>BOLD</b> <i>Italic</i> Summary ------------------------------------------------------ <table cellspacing="0" cellpadding="0" width="100%"> <tr> <td><b>Order Number:</b></td> <td>{{OID}}</td> </tr> <tr> <td><b>Detailed Invoice:</b></td> <td>https://template.me.uk/outgoing/account_history_info.php?order_id={{OID}}</td> </tr> <tr> <td><b>Date Ordered:</b></td> <td>{{ORDER_DATE}}</td> </tr> <tr> <td><b>Status:</b></td> <td>{{ORDER_STATUS}}</td> </tr> </table> Products ------------------------------------------------------ {{PRODUCTS}} Delivery Address ------------------------------------------------------ {{DELIVERY_ADDRESS}} Billing Address ------------------------------------------------------ {{BILLING_ADDRESS}} Payment Method ------------------------------------------------------ {{PAYMENT_METHOD}} for {{ORDER_VALUE}} A big BIG BIG Thank You from all of us here at Burtys Test Shop!
  13. burt

    Email queuing system

    Create Account Email is not part of the Queued Email system (yet). I had turned off one portion of the system to test something and then forgotten to turn it back on! D'oh. It is now turned on again and so you should have received those two product_purchase emails Also in the Queue for you: Thank you very much for testing!
  14. I believe my answer would be the same as the answer of @Jack_mcs Hooks do not add anything "bad". They allow shopowner and developer to do things easier. Typical example would be the Paypal App as mentioned in previous post, another example would be my recent PDF thing I made that allows shopowner to attach a PDF to an Order. Side Thoughts; Hooks pre-date osCommerce CE osCommerce CE mirrors 2.3.4.1 functionality - there is (to my correctly remembering) nothing in 2.3.4.1 that is not in CE.
  15. burt

    Email queuing system

    This would be why there is a delay on sending emails. Eg for a request_review: 60 days? 30 days? choosable by individual shopowners. Put another way...a pair of trousers straight off the peg might fit a 34" waist, but would be wayyy too small if someone eats too many pies.
  16. burt

    Email queuing system

    I'm still working on this as and when I can - want to get it as "right as possible" before too many people get their hands on it, as outgoing emails are a (very) important part of any shop.
  17. burt

    version with php7.2

    Without getting into too much detail, I have to take time out of my usual schedule to give time to moving osCommerce forward. I've tried to increase that time in a number of ways, but what I've tried hasn't worked out in the way I'd hoped. There's a distinct lack of enthusiasm (amongst most [not all] shopowners), so I am only able to give 5 minutes here and 10 minutes there. I don't blame shopowners - why give cash/time/effort when someone else will - there are some (not many) shopowners who are willing to be the ones keeping the project alive and I thank them for that. I'm aware it's no way to run a project that shopowners depend on, not having regular updates in good time.
  18. burt

    version with php7.2

    7.2 work has not commenced - not enough support in the Community to make it happen in good time.
  19. burt

    Flat Rate Shipping

    If nothing else works, consider getting a pro coder to make it to specification. It's an hours work of coding and testing; Give each product a postage cost maybe in the shipping module as you have so few products? maybe in a new admin page? maybe in the existing admin/categories.php page? In new shipping module look at cart contents and work out cost appropriately
  20. https://github.com/gburton/Responsive-osCommerce/commit/a8e68e5832ecbcbafed279a41a7432432a076469
  21. No reason. HT module would be just as good, if properly coded.
  22. Thank you for the kind words, and thank you for your support over the years.
  23. You'd need to change that script (includes/modules/product_listing.php) to a form along with one button at the bottom. Depending on what version you use, you may also need to create an action for the form. Do these two parts first and get it working to add multiple products/qty into cart. After that is done and working, then think about adding in ajax functionality - which should be fairly straghtforward.
  24. burt

    Index Link Modules

    What do you want to link to, and how do you want to do it? I'd wager everything you can think of has been already made and is available either free or paid-for.
×