-
AuthorPosts
-
January 28, 2015 at 1:07 am #193203
chasemcdonald626ParticipantHaving the same issue. Fixed by changing woocommerce/cart/cart.php as suggested.
January 28, 2015 at 6:57 am #193377
harharjuhaParticipantHaving a same issue after updating 3.2.1. Not possible to downgrade (X), I suppose? And we certainly don’t want to use beta woocommerce for production site.
January 28, 2015 at 5:36 pm #193880
ttbrownParticipantOMG I was so embarrassed, a customer emailed us and told us they couldn’t buy anything from our site. I’m not sure how many sales we lost out on. 🙁
January 28, 2015 at 5:38 pm #193881
RadModerator@Chase,
Glad it’s okay now too.
@Harhar,
You can follow Lambert’s suggestion, you will be working with FTP or cpanel’s file manager to do this.
Thanks!
January 29, 2015 at 1:54 am #194118
TonyBearParticipantYou are brilliant!
January 29, 2015 at 4:36 pm #194732
KoryKeymasterHey everyone,
It should be noted that the proceed to checkout button is not missing in the new templates, it has simply been moved in v2.3 of WooCommerce. You can read this from their notes here:
The ‘Proceed to checkout’ button on the cart has been moved and is now located beneath the cart totals. Obviously this is a crucial design element so if your theme overwrites any cart template files please double check this. We’ve tried to make this change as backwards compatible as possible, though.
As mentioned in our release notes, we have updated the most recent version of X to be compatible with v2.3 of WooCommerce, so if you have updated X, simply update your WooCommerce plugin to the beta version as mentioned in our release notes, or you can wait to update the theme until after the official WooCommerce release is available.
Please let it be known that this is not an error in the theme and is simply a compatibility update due to changes in the WooCommerce plugin itself, so if you might run into problems updating the theme templates. Please either update the theme and WooCommerce to it’s current beta version, or wait until the official WooCommerce release is out and then update your theme and shortcode plugin.
We certainly understand that this is a unique situation and apologize for any issues this might have caused for our customers who didn’t happen to see the release notes. It is always recommended that the release notes be read, even if you have automatic updates enabled just to be sure nothing you’ve customized or are using has been altered (for situations like this specifically). Unfortunately, the WooCommerce update came at a unique time in our development cycle and since they do not release a definitive timeline on when to expect the official release, we had to make the call to prepare for the official release beforehand due to a variety of factors. We certainly appreciate the specific nature of this situation and apologize for any inconvenience this might have caused.
Hopefully this helps to alleviate any confusion on this matter moving forward, thanks!
January 30, 2015 at 12:05 am #194934
germanParticipantHave the same problem….My ” proceed to checkout’ button” is missing.
It was not a big deal since I’m still building the site, so I decided to wait for the new WooCommerce Plugin update.
Today ( 1/29/2015) I installed the new update Version 2.2.11 from WooCommerce and still don’t see the checkout button.
I thought the new X 3.2.1 update was gonna be compatible with this latest version of WooCommerce.
Need Help.January 30, 2015 at 10:33 am #195326
AlexanderKeymasterHi there,
As mentioned in our release notes for version 3.2, we’re now supporting the template changes required for WooCommerce 2.3. They changed quite a bit, and required theme developers to rewrite several template files. We opted to release X early, as we’re not given the exact release date for WooCommerce 2.3. That way there’s no lapse of compatibility. You could try installing the latest WooCommerce beta which is pretty close to what it will be for the final release.
January 30, 2015 at 10:43 am #195333
AdendumParticipantI also agree that you should not EVER release anything that is dependant on beta software. I have only just been told by a client that the checkout button has gone missing…..worse they are wondering why their orders dried up just after Christmas!
Not happy guys – plus I now need to track down the beta version of Woo and see what that does!
January 30, 2015 at 10:54 am #195341
AdendumParticipantBeta version installed and CHECKOUT button is back however I also see a message from Woo saying the them has outdated bundled something or other.
January 30, 2015 at 12:15 pm #195406
germanParticipantHello.. Does anyone have a link to the WooCommerce Beta ? having a hard time finding it on their website
January 30, 2015 at 3:57 pm #195582
AlexanderKeymasterHi there,
The reason we chose to release something that was tied to the beta is because WooCommerce could not give a date on the 2.3 release date. It could be at any time, so we decided to release early to avoid a lapse in compatibility. WooCommerce put theme developers in a tough position with this one because: 1. So many template changes were needed. 2. There’s no official scheduled release date.
You can find their beta here.
http://develop.woothemes.com/woocommerce/February 6, 2015 at 8:53 am #200496
Maju VParticipantHi there,
Well said timtimd… Thanks a lot Lambert T
I’m still struggling with this so called update for beta-users of WooCommerce 2.3… I’m so angry I can slap these guys in the face!
However, now I have the problem with the actual cart page… there is no order or payment button!
Help!!!!
MajuFebruary 6, 2015 at 4:16 pm #200772
RadModeratorHi Maju,
You can revert back to stable version and follow the fix mentioned here for missing checkout button. Or start a new thread will all possible information about your issue, plus admin and ftp login credentials so we could check this.
Thanks.
February 11, 2015 at 1:40 am #203785
JosBloParticipantThank you, this solved my problem!!
Best regards, Jos
-
AuthorPosts
- <script> jQuery(function($){ $("#no-reply-188859 .bbp-template-notice, .bbp-no-topic .bbp-template-notice").removeClass('bbp-template-notice'); }); </script>
