Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Posts posted by fulluvscents

  1. @@pfrecon


    Yes, I noticed those issues myself, and got them taken care of and uploaded.




    I also fixed the auto refresh when discount codes are entered.




    Yes. I removed the auto-update. If you want to add it back in then do this:


    Find around 752:


     .on('change', 'input[name=shipping]', function(){$.post('checkout.php', 'shipping='+$(this).val()+'&comments='+$('textarea[name=comments]').val(), function(){window.location.href = unescape(window.location.pathname);});})


    Add this before that line:


     .on('change', 'input[name^=cart_quantity]', function(){$('form[name=cart_quantity]').submit();})


    As written now, if a customer enters a new quantity and hits enter, it will automatically submit the change (without that line of code).


    The difference that the extra line of code will make is this: If a customer changes the number and clicks tab, or clicks the mouse anywhere else on the screen directly from the input field, it will also submit the form, the same as if they clicked enter, or clicked the refresh button itself.

  2. @@tapa


    It's PHP 5.3.10


    As far as I know, nobody has run into php compatibility issues. It's just been the browser issues.


    Edited: Going back and reading through, I see that you actually had a php issue. Would you like to test the script before I finalize it for upload?


    Looks like everything is going better with this one, on all browsers, so I'm hoping it will be safe to upload a final version and also the guest checkout package. I'll probably have that done by Tuesday, as long as nobody reports anything. I want to get this uploaded to a couple other servers for testing as well before I finalize it.


    Any takers? Just PM me and I'll get you the files.

  3. I will be uploading another release soon.


    I am asking for browser testing again.


    First, turn off java in your browser, and test it that way. Then, turn java back on and test it with java on. It should work with or without java.


    The guest option will no longer be a part of the checkout itself. I've written a second script for guest checkout which will work in both a stock checkout and Simple Checkout. The second script is a full guest checkout script that will store customer information under a single customer ID no matter how many times they checkout as a guest. It provides the customer with the convenience of a shorter form, and the shop owner with organized records and accurate reports.


    Discount codes will work in this checkout like they would in the stock checkout, but each discount contribution will need to be integrated differently. There is a specific area left free for discount code input fields (to the left of the order totals, below the cart contents). Before I upload the next version, I will install the discount codes for 2.3.1 contribution, so that I can supply instructions. I believe that one is the easiest discount mod to integrate with this.


    I will not upload this until I've received feedback from Safari and IE8> users. After it is confirmed that the script on the test site works in all browsers, with and without java, and poses no functional issues, I will package the two scripts up and release them.

  4. It is difficult to keep up with the test site as now it seems to be back to something other than the newest version. kinda ressembles something seen in past renditions, like OPC or the out of the box stocker... what gives?


    Yeah, sorry about that. Give it a couple days (2 or 3 maybe). There were way too many bugs, and I stripped the entire thing down. Adding it back one piece at a time.

  5. My focus is on the fact that the latest version is not working in all browsers, and I personally like it better than the previous one, as do some others. It works in chrome, mozilla, and IE 9. The issues known exist in IE8 and Safari. At this point, since the updates I made, I've been informed that there are still issues in Safari.


    I'm using an IE tester, but the tester itself is not accurate. None of them are. I'm also testing in IE9 under IE8 mode, but this is also not accurate because IE9 does not imitate IE8's javascript program, which is precisely what I need. My only other resorts are the feedback of others, or using virtual machines which extends beyond anything that I care to do, since I'm not willing to go out and BUY the operating systems that I need to run these browsers. So, it comes down to feedback.


    I'm going to download Safari for PC and test that as well, but I'm not sure how this will compare to safari on mac.




    Thank you for posting that.




    I am not here to debate the semantics of a guest checkout. I already KNOW the points that you've made. I contributed a "single page checkout" with an optional guest checkout feature and made it clear at that time that I did not put a lot of focus in the guest checkout aspect, and I am not up to debating the reasons why. Take it or leave it or make it work the way you want it to, until something better comes along. If I extend the instructions in the next upload for a full fledged guest checkout, then take advantage of that.




    Thank you as well.

  6. There was a comma where there shouldn't have been, and a span without a closing bracket (>)


    The span itself should have destroyed the script in any browser, but it didn't.


    In your local TEST files from the v2.2 contribution, do the following and please post back if that fixes anything that you're experiencing.


    Line 360:


      .on('click', '#submitCreate, #submitGuest', function(){if ($('#NewAccount .required_icon:visible').size() > 0) alert('<?php echo MESSAGE_FIELDS_REQUIRED;?>');else if ($('#NewAccount .error_icon:visible').size() > 0) alert('<?php echo MESSAGE_FIELDS_ERROR;?>');else {$('#NewAccount').find('input, select, textarea').each(function(){if ($(this).val() == $(this).attr('title')) $(this).val('');});$.post(url,'action='+$(this).attr('id')+'&'+$('#NewAccount').find('input, select, textarea').serialize(),function(data){if (data.msg != '') alert(data.msg);if (data.status == 'success'){$('#Account').dialog('destroy');$('#checkout').show().find('#shippingAddress, #billingAddress').trigger('refresh').end().find('#cartContent').parent().load(url +' #cartContent', function(){$('#cartContent').trigger('refresh');});$('#NewAccount').dialog('destroy');}else alert('<?php echo MESSAGE_ACCOUNT_ERROR;?>');}, 'json');}});});},


    Remove the comma from the end of that line.


    Line 426:


        <div class="cartRow6 cartDelete" data-pID="'.$products[$i]['id'].'"><span class="ui-icon ui-icon-trash"</span></div>


    Change to:


        <div class="cartRow6 cartDelete" data-pID="'.$products[$i]['id'].'"><span class="ui-icon ui-icon-trash"></span></div>





    I am running this through an IE tester. I still have two issues from my end. The first is the cart delete button not working. The second is that shipping resets to cheapest method when payment is selected (but my radio buttons stay checked). The first works fine in other browsers that I've tested, but the second is across all browsers.




    I don't think anyone is interested in entertaining bogus workarounds. Let's get this thing fixed. The old OPC for 2.2 is how old now? I can tell you for a fact that the latest contribution STILL has bugs with fixes that have never been publicly posted. This was just contributed a few months ago. I am not about to leave it hanging with bugs and half cocked "fixes" that don't really fix anything.




    Read one of my very first posts about the guest checkout. I wrote it that way and knew that I wrote it that way. When I've dealt with the bugs/browser issues, I will consider providing instructions that take the "guest" checkout a step further. I still say if they come back, they aren't a guest. They are a client. At this point, that is not a bug. It was intentional.

  7. @@surrfman particularly - and anyone with a MAC.


    Please go through the test site in whatever environment you're browsing from, and see if it's working now (http://simplecheckout.oscbyjetta.com/checkout.php).


    Please state your browser, platform (PC or MAC), and any issues that you run into. If I don't respond, it's because I'm gathering information and working on the fixes. Obviously, I can't fix anything if I'm spending all my time responding to each and every question or issue.

  8. @@danut82


    Everything is set to redirect on one condition or another. If the cart is empty, the checkout is set to redirect to the shopping cart. If the customer is not logged in, and goes to a login page, and is redirecting to the checkout with an empty cart, it would just create a mess for the customer. So you'd have to change the entire redirection schema.


    Another solution would be to create a separate page for the login/create account section. Then use an ajax load function to call to that page from the checkout AND the login/create account pages.


    Either way, it could be done. I think if I were to choose between one or the other, I'd choose the second, even though it would probably be a bit more work to put together. I just think it would be cleaner and more efficient.

  9. @@ToneDJ


    If you're using 2.2, then I set up a nifty little line in the script that you can modify to set a default country. I forgot to mention that in the instructions. Skipped my mind.


    Find: $default_country = ''; and set the country number between the quotes (223 is the US in stock osc)


    To eliminate other countries altogether, remove everything from your country list in your admin panel.

  10. An error occured with the USPS shipping calculations.

    If you prefer to use USPS as your shipping method, please contact the store owner.


    Are you sure you're not using the USPS Methods contribution? It's not the same as this one. This one doesn't display errors. Errors are silent.


    In any regard, there is a line that will email you the USPS response. You can un-comment that line, and first find out what response you're getting, before doing anything else to debug.

  11. To elaborate on what @@altoid has said:


    In January, 2011, I knew html. That was the extent of it. My USPS module broke, and there was no available fix. It took me a week of eyeballing and fighting with a language that I knew nothing about and reading the USPS API manual, breaking down the existing script and guessing at what each section did, and struggling to find the piece that wasn't right, and then further struggling to add the bells and whistles that I figured I was entitled to for all the work that I put into it. I shared that work freely. Anybody else could have just as easily put the time and effort into it and probably succeeded, and while some secretly already had their fixes in place, others sat idly by waiting for someone else to do it for them. I needed it done, did it, and I shared it. If it worked for others, then great. If not, then so be it. A year later, for no reason except I felt like it, I decided to rewrite the entire script just to eliminate the mess of code that came with the old one.


    And that is the plain and simple fact with every contribution you see. They are written to work for somebody, to meet somebody's needs. I can take one of two stances. The first is simply this: "If you don't like it, then do it your own damn self like I did". The second is how I look at it. I want these contributions to work for myself. So, of course, I want them to work in general. While I personally am not experiencing any of the bugs that others are experiencing, it does not mean that the bugs don't exist. It simply means that I don't have the means to replicate them, be that lack of platform, lack of browser, etc... Obviously, if I have IE9, then it's going to be tough for me to test on IE8, and likewise, I can have a million PCs but it is NOT going to tell me what's going on with a MAC. My sites run on Apache 2.2.22, PHP 5.3.10, MySQL 5.1.56, and use peering connections for faster speed. So, I am not going to be able to replicate problems with older server software or slower servers. The short of it is that there are so many varying factors that nobody can possibly expect a one size fits all contribution, particularly when you're talking about using such a wide variety of scripting languages and communication methods in one page of a website.


    As online business owners, we have all taken on the responsibility of owning a website and doing whatever it takes to make that website work for us the way we want it to. We can pay others to do the work. We can wait around for others to do it for us. We can take what we can get for free, and tweak it for our own needs. It would probably cost me ten grand or better to get the work done that I want. I decided to do it myself and compromise my own website in the meantime, which is why I'm only doing business on eBay right now. It doesn't matter how we do it. But, one thing we should never allow ourselves to do, is complain about work that others do for us for free, even if it isn't perfect, or even usable at all. Where I, and many others come from, we call that just plain rude.


    Onto the contribution itself, for some people rolling back to the 1.7 version may work best. For others, the 2.2 version may be working perfectly. For others yet, it may not work at all and you may want to go back to the old OPC. Originally, I wasn't even going to use ajax. I was going to let the page refresh on every change to avoid all the bugs that come with these scripts. Getting a custom script that does that may meet more needs than an ajax version. I don't know. But, do what works for you.


    In my personal opinion, unless or until I know this is working on all platforms, and in all browsers, I think that I need to perform a browser/platform check in the script, and turn the checkout off if the site is running in those particular environments. If anyone is up to putting together the code to do that, I'd surely appreciate it. But, as far as immediately investing a lot more time into this, I do have more pressing projects to deal with, which affect my retail business personally. Those MUST come first.


    PS @@altoid - On another note, I ran across the bug in the shipping restrictions and know what it is. Just haven't worked on it yet.

  12. @@jhaugen


    Actually, I hadn't run into it until this very evening while testing something else out with PayPal express. It's a simple fix:




    $http = new httpClient();


    Add this before it:


    if (!class_exists('httpClient')) include('includes/classes/http_client.php');




    Are your php errors turned on? Is this specific to one page or another, or is it sitewide?