Hello all.
We're very excited to give interested developers access to v060 as a beta pre-release. There are _many_ of you that have told us you needed v060 "yesterday" or "last week," and while it's not 100% at this point, you can now turn it on for your stores.
What it has:
The big ones are:
* PayPal Standard
* Debit (non-credit) card support
* True guest checkout (checkout as a guest or create/use an account)
* Display the full checkout on pageload
* Multiple payment options (CC + PO + PayPal or any combo)
* Much better cart functionality wrt detecting changes that would require an update, and improved updating (try changing quantities on the cart)
* XML now has CDATA tags
What you absolutely need to know:
v060 is still undergoing _ACTIVE DEVELOPMENT_, and things _WILL CHANGE_. The wiki upgrade notes are a work in progress. PayPal's sandbox is kind of a pain, and we haven't documented it yet.
We do NOT recommend using v060 on a live store at this point. Really, we're not just saying that. We've done a lot of testing, but there are bound to be issues, so please don't just "set it and forget it". Let us know about any strangeness or room for improvement, and we'll let you know (via this thread) about any changes we made from here out that might impact you.
What's not done yet:
* Ability to select the guest/account options. (Default to guest, default to create an account, only allow one or the other.)
* Subscription improvements.
* Testing Google Analytics as it relates to PayPal Express Checkout.
* More.
Again, DO NOT USE THIS!
You've been warned
UPGRADING:
We recommend no upgrading your live store at this point, but rather creating a new store to test with.
Links of interest:
*
Upgrade notes
* New XML (coming soon; you can grab it yourself if you're interested in the meantime)
brett
FoxyCart Team
What does "true guest checkout" mean?
When do you anticipate active development to cease? I mean it's nice and all that we can test, but not being able to use it in production and rightfully warned against it, doesn't solve the "yesterday" and "last week" issues that we too face.
The entry page (w/sample code) looks okay the first time that it's loaded, but after clicking through to any other pages, it's a full plaintext site, and there's no menu to get to the other admin pages. The template section seems to be missing from the pages-- the page source begins at -- so the whole and header sections are missing.
The forms also appear to not be working: Once you upgrade to 060, you cannot make changes to the template or select a different store version.
Checking on that now. Thanks Oskay. What browser are you using when you're seeing the borkage?Fixing right now.Fixed. Sorry about that. Miscommunication with something between staging and production. Human error.
As far as the development schedule and further changes go: When we call it "ready" will be largely based on how much feedback and bug reports we get from everybody during this testing phase. We've done a lot of testing, but there are many changes, and there are always bugs to be found (even after a true release, as you can see based on the number of improvements and fixes ported back to 050 and 051 in the 060 changelog). If you need the functionality in 060 though the best way to make sure it's ready for production use is to test it and let us know about issues. We'll be fixing them as quickly as we can.
Also, due to the nature of testing PayPal on their sandbox, we won't be able to provide test accounts for PayPal. We'll document this as soon as we can, but for now you have to create your own dev account.
When this message is displayed, the "Email me my password" link is no longer visible.
That's a good question. The "fake" guest mode in 051 and prior didn't actually mark the customer as a guest, and those users do actually have a randomly generated password on their accounts. What might make sense would be to take all your existing customer records and set them as "guests", so that from here out your customers can create accounts or checkout as guests, whichever they desire.
I was going to ask about the randomly generated passwords, but that's a *very* different question, and I thought that I would wait until the first layer of dust settled on 060. BUT, since you bring it up... setting prior customers to "guest" sounds like a great idea. How can I go about this?
@tookings: looking into that one now. I really thought I had removed that from the drop down.
Do you have a rough ETA for when this new version can be deemed "stable"?
@oskay: The changelog should now show up, but keep in mind it will be changing up until we make this version officially launched.
Hmmm.... Not seeing it yet.
Edit: Also, recent transactions don't seem to be showing up in the transaction log.
>but depending on how many customers you have, that might take a while.
I'm looking at the API. I suspect that there may be something amiss with the 060 datafeed/API results-- I can use it to view recent transactions (taken in 060). None of them have the anonymous bit, nor do they have any customer data-- it all looks like this:
"<customer_first_name><![CDATA[]]></customer_first_name>"
Cart contents are there, though, and when I query older transactions that took place under 051, customer information (such as first name) is there... so it looks like a problem of data collection and/or storage, rather than retrieval.
In any case, we do have thousands of customer records that apparently need to be updated....
No rush-- I have the transaction e-mail. Just thought that I should report bugs as I come across them.
Update: We've identified the cause. We'll update again once it is resolved.
Glad this is easily forced. Can you elaborate on the recommended way to do this given the future FC roadmap?
Let's assume you have two types of customers (retail and wholesale) and you only want to have wholesale customers be able to use PO payment methods. Also assume this would be coming out of a MODx-based cart with logged in wholesale users.
BTW, Brett, Luke et al: I'm very appreciative and excited by the 060 release. Thanks for you guys hard work and ongoing improvements.
$(document).ready(function(){ if (fc_json.custom_fields.show_po == 'N') { $('#fc_payment_method_purchase_order_container').hide(); } });Also perhaps worth noting is that you may need to set certain elements to show/hide based on what payment method you want to show, but for just hiding the PO you'll be fine, since the CC is selected by default.
Update on the transaction/API issues: They're resolved now. Please continue to let us know any issues you discover, and thanks for finding everything so far.
Edit: We seem to have found a likely clue: Upon "completing" payment in PayPal, and trying to return to complete the payment, we're actually coming back to:
https://[ourstorname.com]/[redacted, included a dev path that doesn't need to be spidered]?ThisAction=paypal_express_checkout&fcsid=[...]
If it helps to locate the problem, this was observed after clicking the paypal button on the checkout screen, not the one in the cart.
Sorry about the issue. Fixing now... please standby...
Fixed. Thanks for pointing it out. We'd actually known about this but in fixing the other issue we'd neglected to push this fix out along with it.
Seems not to be.
FF catches the error, displays "Error: There was an error processing your payment: (10419 Express Checkout PayerID is missing.) Express Checkout PayerID is missing." on the checkout page, without heading to PayPal to enter information. This generates an error that shows up in the error log.
Safari does not generate that error, and passes through to PayPal to collect data. It's only on return from PayPal that it redirects to the "bad" address that I mentioned earlier. This does not generate an error that shows up in the error log-- it just hangs.
I can't seem to complete a purchase in either case.