mattjt83

@Dutch1 OK, so you are trying to use the beta version of some software, which has already been described as not ready for production use, and then instead of listening to others advice and using 2.3.4BS you continue to run into issues with the beta version and come here to bitch about osCommerce being terrible. If the software is that bad why don't you contribute something that will fix the errors that you seem to keep having? This software is free to use and there is no one forcing you to do so. The developers involved often receive no compensation for their time and also have real jobs that need their attention. osCommerce 2.3.4BS works very well and many shop owners including myself are using it to run successful online shops.

I've been working on this for a while now but real life has been getting in the way. The difference with mine is just that you don't have to create an account first. Yes, eventually the person will have to enter the data regardless but it's how they perceive the task that matters. I think it's very important to understand your customers and design your site/checkout experience around that. If most of your customers are one-off sort of things than a guest checkout can make a lot of sense.

Here's a good article: https://www.smashingmagazine.com/2017/05/better-form-design-one-thing-per-page/ I might actually rework my checkout with this in mind.

I had a one page checkout on my site and it led to all sorts of issues. It was inherently glitchy and confused customers. After that I decided to code and sell Better Checkout. I still use it on my site but I do not sell it anymore because I don't like all the changes required to make payment modules work properly. Basically, your customers can checkout with or without an account and it's seamless. It splits the checkout up into manageable chunks for customers and is easier to maintain code-wise. You are welcome to check it out on my site and see what you think maybe just to get some ideas. Mine is highly customized. The more that I read on the topic it seems that people in general do better with small simple checkout pages and don't mind having to complete 3 or 4 SIMPLE steps (pages).

All of the meta tags you are wanting to include will be included via header_tags. I'm assuming (hoping) you are using the latest 2.3.4BS version of osC, which should include those header_tag modules. There are some old page cache modules but it opens up all sorts of issues. osC runs pretty efficiently out of the gate these days so it shouldn't bog your server down. That is unless you have a super high traffic site and/or are using shared hosting, which tends to be slower anyway.

I just wanted to add a bit to this thread. I have implemented Apple Pay on my osC site and it works well. I used stripe for my integration as it was the least headache inducing of the options I found. I would share code but my integration is extremely customized for my shop. Basically it consists of the following: A new payment module that outputs on the cart page. a page in the ext/modules/payment folder to handle call backs The stripe PHP API code Most of the code can be found on the stripe website but of course implementing the various aspects of the code has to be done by you (shipping modules, order totals, etc...) I'm glad to answer any questions you have about the integration. It makes checking out extremely streamlined and simple!

@@hyperweb Glad you got your issue sorted out for your client. Best of luck on your project!

I still use my version of this and have not had that error come up.

I have been using the key system for a few weeks now and I am very happy with it so far. I have added some hooks to automate most of the processes, changed the email to an html email with admin configuration options for altering the looks of the email, and I have added a cron job to run the review emails automatically for me based on configuration options set in the admin. Finally I can get away from the mailbeez review system.

It could be manipulated by the end user but I would say it's few and far between that a user knows how to do this and wants to take the time to do it. You could use javascript to manipulate the html and add in @@burt code to make the field required.

@@burt @@mcmannehan You could do a lot of this, probably all of it, via javascript in a header tag module instead of hacking apart these core files. Also what's up with this part: if ( tep_output_string($values[$i]['id']) != 1384 && tep_output_string($values[$i]['id']) != 1411 ) {

I believe if you are using the PayPal App and are up to date with it you should be fine.

Thank you for the update to fix the alignment @@Harald Ponce de Leon

@@Harald Ponce de Leon That corrects the alignment issue for me :)

@@greasemonkey You can float the span that holds the iframe right but then you have to clear the float. I'd rather not try and code around the issue though since it is a pain and will likely get overwritten soon anyway.