Recent Updates Toggle Comment Threads | Keyboard Shortcuts

  • Mike Jolley 12:56 pm on September 18, 2014 Permalink
    Tags:   

    WooCommerce 2.2.4 fix update is now available 

    The WooCommerce 2.2.4 release is now available via WordPress.org or automatic update in your administration panel. Thanks to all of our contributors who’ve been helping out.

    There were several minor fixes in this release which you can read about inside the changelog. A total of 52 commits made it into this release.

    (As always, the comments on this post are closed because this is not the right platform for support requests.)

     
  • Mike Jolley 1:03 pm on September 16, 2014 Permalink
    Tags:   

    WooCommerce 2.2.3 fix/security update is now available 

    The WooCommerce 2.2.3 release is now available via WordPress.org or automatic update in your administration panel. Thanks to all of our contributors who’ve been helping out.

    There were several fixes in this release, including a minor security fix for an XSS issue in the reports section. Read more about the fixes in the changelog. A total of 78 commits made it into this release.

    (As always, the comments on this post are closed because this is not the right platform for support requests.)

     
  • claudiosmweb 11:30 pm on September 10, 2014 Permalink  

    WooCommerce 2.2.2 fix release is now available 

    The WooCommerce 2.2.2 release is now available via WordPress.org or automatic update in your administration panel. Thanks to all of our contributors who’ve been helping out.

    There are only three changes in this release which can be found in the changelog. A total of 6 commits made it into this fix release.

    (As always, the comments on this post are closed because this is not the right platform for support requests.)

     
    • Francisco 3:51 pm on September 11, 2014 Permalink

      Dear friend
      Just updated to 2.2.2 and i have lost the spanish translation of several pages and boxes ( like chekcout fields, add to cart button… )
      I have check language folder and theres no a spanish .po file
      What can i do to have my spanish text back?
      Thanks a lot!

    • Damian 4:27 pm on September 11, 2014 Permalink

      Claudio,

      I have updated WP + WC to latest versions and tried many fixes both on the template level and WC to allow virtual + variable products to show correctly, but still the ADD TO CART button is not showing up. just the message:

      “Sorry, this product is unavailable. Please choose a different combination.”

      You can see it here: http://thecaboairportshuttle.com/product/private-airport-transfer/

      Tried the jquery cookie fix to no avail… I understand that 2.2.2 release was fixing this issue…

      Any ideas?

      Muito Obrigado !

      D

      • claudiosmweb 4:55 pm on September 11, 2014 Permalink

        Experiment with the WordPress standard theme and see what’s different.

  • claudiosmweb 7:15 pm on September 10, 2014 Permalink
    Tags:   

    WooCommerce 2.2.1 fix release is now available 

    The WooCommerce 2.2.1 release is now available via WordPress.org or automatic update in your administration panel. Thanks to all of our contributors who’ve been helping out.

    There are only three changes in this release which can be found in the changelog. A total of 6 commits made it into this fix release.

    (As always, the comments on this post are closed because this is not the right platform for support requests.)

     
  • Mike Jolley 2:41 pm on September 10, 2014 Permalink | Reply
    Tags:   

    Developers Rejoice: The Pangolin Has Landed 

    Finally we’re proud to announce WC 2.2 (Prowling Pangolin) is live! 2.2 is our 9th major release and has been in development since 2.1 was released back in February.

    WC 2.2

    Some Stats on This Release

    To highlight the work that’s gone into 2.2, since 2.1 I would have loved to have shown more stats from Github, but instead saw this:

    This comparison is big! We’re only showing the most recent 250 commits

    I think that pretty much covers how much work has been done, but from the data I was able to scrape there have been:

    • 47 contributors
    • 1670 commits
    • 553229 additions
    • 972950 deletions

    That’s staggering, so huge props to everyone who has contributed via Github, and also not forgetting the translation teams on Transifex!

    Release Highlights for Developers

    Upgrading to 2.2

    Aside from testing before pushing to live (use a staging site) developers should be aware of the upgrade script which runs in 2.2. The script will:

    1. Update some deprecated options such as woocommerce_ship_to_billing.
    2. Convert the old order statuses (taxonomy) to the new ‘post status’ formats.
    3. Update variations to include new stock meta data.
    4. Add new capabilities to admin users for webhooks.

    Users will be prompted to run this in WP admin after upgrading.

    What Comes Next?

    WC 2.3 has already been scoped out and planned to be a UI focussed release. We’re hoping to speed up our release cycles as of 2.3, so keep an eye on Github and feel free to get involved.

    And for everyone attending our first WooCommerce conference, see you in November!

     
    • Michael L'Ecuyer 3:17 pm on September 10, 2014 Permalink | Reply

      Fatal error: Call to a member function get_settings() on a non-object in /nfs/c02/h08/mnt/42123/domains/roxbur.com/html/wp-content/plugins/woocommerce/includes/class-wc-install.php on line 291

      • Rocco 3:51 pm on September 15, 2014 Permalink | Reply

        Updated to the 2.2 core and the quantity button overlapped the minus button making it so you could not longer see the quantity for a product. To fix i just had to tweak the css a bit to get it to render correctly. This was using the Woo Reatiler theme. The fix was to paste this css into the custom code .woocommerce-page .quantity input.qty {
        position: relative;
        left: 35px;
        }

    • Michael L'Ecuyer 3:33 pm on September 10, 2014 Permalink | Reply

      The above “Fatal error” is consistent amongst several of my WooCommerce sites; anyone seeing a similar error?

      Thanks in advance for thoughts, solutions, etc…

    • Michael L'Ecuyer 3:48 pm on September 10, 2014 Permalink | Reply

      I was able to resolve by doing the following:

      1. In class-wc-install.php, change all occurrences of get_settings() to get_options() as the previous is deprecated.
      2. Change the single occurrence of get_settings_pages() to get_options().
      3. /wp-admin loaded up nicely and I reverted the above back to normal as it was only relevant for the install (I believe).

    • Bogdan 4:13 pm on September 10, 2014 Permalink | Reply

      Is there a way to downgrade it? The admin panel is not loading anymore, and the website is loading slow.

      Any idea why the admin does not load after upgrade?

      Thnaks

      • Mike Jolley 4:15 pm on September 10, 2014 Permalink | Reply

        • Bogdan 4:18 pm on September 10, 2014 Permalink | Reply

          Thanks. I will disable the plugins to see if I can get it fixed.
          Do you know if I can downgrade it? Because I have other issues on frontend, and I can’t fix them now as is night here :)

          • Mike Jolley 4:21 pm on September 10, 2014 Permalink | Reply

            You can grab an old version from the ‘developers’ tab on WordPress.org. If you’ve run the updater some things like order statuses may be wrong though.

            In future, test updates on a dev/staging server. Doing any update on a live store is a bad idea.

            • Bogdan 4:41 pm on September 10, 2014 Permalink

              Thanks for your help. I was able to downgrade it and now the site is working fine. I know that it was stupid to update a live store, but tomorrow I’ll make it work on a test site.

    • nick 5:28 pm on September 10, 2014 Permalink | Reply

      Yep. And entire back office is blank

      • nick 5:30 pm on September 10, 2014 Permalink | Reply

        http://www.firebirdink.com – I have no idea what to do..

        • Claudio Sanches 5:36 pm on September 10, 2014 Permalink | Reply

          Please do not upgrade just the WooCommerce.
          Update all plugins at the same time to avoid these problems:
          http://docs.woothemes.com/document/upgrade-instructions/

          • Diego 5:39 pm on September 10, 2014 Permalink | Reply

            Excellent suggestion, I was about to write the same. Also, it’s always better to update the plugins on TEST sites first, so that nothing breaks on the live site if something goes wrong.

          • nick 5:39 pm on September 10, 2014 Permalink | Reply

            I think I am going to restore the site and do this later. Can’t afford to loos anything now. Woocommerce was the only update I had I believe

            • jameskoster 6:32 pm on September 10, 2014 Permalink

              Please do not perform updates (especially major releases like this one) on a live site. We cannot stress this enough.

    • nick 7:12 pm on September 10, 2014 Permalink | Reply

      I keep a backup of everything on my site in 2 different places and I did a backup locally, before doing the update. I was just hoping it’d go fine. I’ll have to test it out on my test server at another time.

      Thanks for the suggestions everyone

    • Mikkel Cortnum 9:31 am on September 11, 2014 Permalink | Reply

      Is anyone else having trouble with thumbnails not being displayed after updating?

      • Mary Baum 12:57 am on September 14, 2014 Permalink | Reply

        My images aren’t scaling. Even when I regenerate thumbnails.

    • Vincent 4:40 am on September 12, 2014 Permalink | Reply

      Hi,

      For Woocommerce 2.2, how can i add custom fields into variable products? As my previous code to add custom field doesn’t work. It appears in the backend, but when i print the array, the value for product_custom_fields disappeared. Help?

    • Tim Mathews 4:11 pm on September 12, 2014 Permalink | Reply

      We’re having a major issue. Every hour or so, we get a notification that “WooCommerce Data Update Required – We just need to update your install to the latest version”
      We have updated it several times, still keeps occurring.
      A search on G. led me to a post where a guy deleted his .htaccess and put permalinks to default, saved, then back to his custom and the message went away.
      Well, I did that yesterday and I thought I was good. Today, however, I get into the office, log in and I am seeing the notice “WooCommerce Data Update Required – We just need to update your install to the latest version” all over again.
      What can I do to make this go away? Anyone?
      Thank you for your time,
      Tim

  • Mike Jolley 3:53 pm on September 8, 2014 Permalink
    Tags:   

    WC 2.2 RC1 is here 

    whosthatpokemon

    WC 2.2 Release Candidate 1 has today been tagged. If all goes well, the final release will be happening wednesday. You can compare the changes since beta 3 here.

    If you have not tested a theme/plugin yet (what have you been doing?) you have ~48 hours to do so if you want to beat the release of the new version.

    You can download the release candidate here: https://github.com/woothemes/woocommerce/archive/v2.2.0-RC1.zip

    If you are testing plugins and they are not showing up, ensure you name the plugin folder ‘woocommerce’ (removing the -2.2.0-RC1) when moving it into your plugins directory.

    Thanks to everyone who has contributed to this release so far!

     
  • Mike Jolley 2:19 pm on September 4, 2014 Permalink | Reply
    Tags: ,   

    2.2 Prowling Pangolin Beta 3 

    Today we tagged WC 2.2 beta 3 which should be the last beta before release.

    Beta 3 contains mostly bug fixes and an update to the Language Pack Downloader to make it compatible with WP 4.0. You can view a comparison between beta 2 and master here.

    Again, we’re happy to hear your feedback about 2.2 and would appreciate any bug reports going directly to Github.

    Download 2.2 Beta 3

    If you find a bug with the beta, please ensure you prepend the ticket title with [2.2] when submitting the issue to GitHub, or at least mention what version you are using in the ticket description.

    Thanks again.

     
    • Julien 11:12 am on September 5, 2014 Permalink | Reply

      There’s a “bug” in Woocommerce for a while and it havent been changed. When there’s more than 50 variations in a product it takes forever to load the product page. Could you add a navigation in the variations in order to make the page load quicker. That’s a big issue for my client and it makes the admin useless on big product.

      Thank you.

      • Mike Jolley 3:35 pm on September 5, 2014 Permalink | Reply

        Not really a bug, but it’s already logged for a future release.

        • Julien 2:07 pm on September 6, 2014 Permalink | Reply

          ok thanks i’m looking forward :)

    • Jason 2:59 pm on September 5, 2014 Permalink | Reply

      Hi i keep getting WARNING: WooCommerce is not active and WooCommerce Autocomplete Order will not work! even tho both plugins are activated and im also im getting no download link in my emails or on the redirect page, if i refresh the page the download link will apear any help would be great thanks

      • Jason 11:22 am on September 6, 2014 Permalink | Reply

        Still getting this WARNING: WooCommerce is not active and WooCommerce Autocomplete Order will not work! both plug ins are active so i dont understand why im getn this error and also i still cant any download links in my emails or on the redirect page,but if i refresh the page the on my store the download link will apear any help would be great thanks

        • Claudio Sanches 3:56 am on September 7, 2014 Permalink | Reply

          You probably downloaded from github and the name of the directory was as “woocommerce-2.2-beta-3″
          Change to “woocommerce” and probably this will work ;)

    • Gus 12:11 pm on September 11, 2014 Permalink | Reply

      Hi all ! Where can I find Language Pack Downloader in my dashboard? I need to translate my Woocommerce to PT BR. Thanks.

  • Mike Jolley 1:44 pm on August 19, 2014 Permalink | Reply
    Tags: ,   

    2.2 Prowling Pangolin Beta 2 

    Work continues on 2.2 and we’re getting closer to an end-of-month release. Don’t forget to test your extensions and themes!

    Changes since beta 1

    You can view a comparison between beta 1 and master here, but notable changes include:

    • Prefixed get_order() to make wc_get_order()
    • Prefixed get_product() to match – wc_get_product() (soft deprecated)
    • Added info about the refunder in the backend refund system
    • Fixed stock logic for parents and children variations
    • Added some backwards compatibility for the new shop order statuses to prevent old style get_post queries breaking
    • max amount option for coupons
    • Deprecated Mijireh gateway
    • Added Simplify Commerce gateway
    • Added a 3rd parameter on the process_refund() method for $reason
    • Refund API

    Help translate 2.2

    The latest 2.2 POT files have been pushed to Transifex meaning you can get involved in the translations here: https://www.transifex.com/projects/p/woocommerce/

    Thanks to everyone who submits a translation!

    Download the latest beta

    We’re happy to hear your feedback about 2.2 and would appriciate any bug reports going directly to Github.

    Download 2.2 Beta 1

    If you find a bug with the beta, please ensure you prepend the ticket title with [2.2] when submitting the issue to GitHub, or at least mention what version you are using in the ticket description.

    Thanks again.

     
  • Mike Jolley 3:06 pm on August 7, 2014 Permalink | Reply
    Tags:   

    WC 2.2 order statuses: plugin compatibility 

    Orders can have several statuses in WooCommerce; completed, processing, on-hold, pending to name a few.

    In WooCommerce 2.1, statuses were associated with orders via a taxonomy called shop_order_status. The shop_order_status taxonomy is no more in 2.2.

    Instead, 2.2 uses post_status for the order status. In terms of usage, this makes more sense – regular post statuses are of little use for orders (since when did you have a non-published order?). For performance, using post status has several benefits, particulary to queries and reporting which can now contain less table joins.

    How does this affect developers? If you query shop_order posts via a get_posts() function, or DB query, you will need to modify your code to fully support 2.2. Otherwise you’ll either get a notice, or no results.

    If you are calling get_posts() for the shop_order post type

    Here is an example of a 2.1 order query:

    $orders = get_posts( array(
            'post_type'   => 'shop_order',
            'post_status' => 'publish',
            'tax_query'   => array( array(
                    'taxonomy' => 'shop_order_status',
                    'field'           => 'slug',
                    'terms'         => array( 'processing', 'completed' )
            ) )
    ) );

    This query uses shop_order_status which will no longer work in 2.2 without throwing a notice. For 2.2 you’d change this to be:

    $orders = get_posts( array(
            'post_type'   => 'shop_order',
            'post_status' => array( 'wc-processing', 'wc-completed' )
    ) );

    If you wanted to get all orders, of any status, 2.2 has a function wc_get_order_statuses() which returns all registered order statuses:

    $orders = get_posts( array(
            'post_type'   => 'shop_order',
            'post_status' => array_keys( wc_get_order_statuses() )
    ) );

    If you are doing $wpdb queries on shop_order posts

    Like above, you’ll need to change the taxonomy part of your query. Here is an example from 2.1:

    $sales = $wpdb->get_var( "SELECT ID FROM {$wpdb->posts} as posts
                LEFT JOIN {$wpdb->term_relationships} AS rel ON posts.ID=rel.object_ID
                LEFT JOIN {$wpdb->term_taxonomy} AS tax USING( term_taxonomy_id )
                LEFT JOIN {$wpdb->terms} AS term USING( term_id )
                WHERE   posts.post_type     = 'shop_order'
                AND     posts.post_status   = 'publish'
                AND     tax.taxonomy        = 'shop_order_status'
                AND     term.slug           IN ( '" . implode( "','", array( 'completed', 'processing', 'on-hold' ) ) . "' )
            " );

    In 2.2, this becomes:

    $sales = $wpdb->get_var( "SELECT ID FROM {$wpdb->posts} as posts
                WHERE   posts.post_type     = 'shop_order'
                AND     posts.post_status   IN ( '" . implode( "','", array( 'wc-completed', 'wc-processing', 'wc-on-hold' ) ) . "' )
            " );

    Direct queries on the database will need to be updated, or no results will be returned.

     
    • Brent 11:46 pm on August 22, 2014 Permalink | Reply

      Another use case that needs updating – using get_posts() without specifying a post_status.

      The default WP_Query value for post_status is ‘publish’, so when no post_status value is specified, WordPress will fall back to 'publish' and that’s not a valid order status.

    • Aaron 10:40 am on August 29, 2014 Permalink | Reply

      It would be nice to have a helper function to handle the list of new statuses. I assume they will change in the future or plugins will need to add custom ones in the future.

      A helper wc_order_statuses() or similar will make any future changes simpler.

    • David Woodthorpe 9:35 am on September 10, 2014 Permalink | Reply

      Will the update automatically alter previous orders to use the new post status?

    • David Villalpando 3:21 pm on September 13, 2014 Permalink | Reply

      Is it possible to translate this statuses with this new post_status usage? I can’t find where to do that.

  • Mike Jolley 3:55 pm on August 5, 2014 Permalink | Reply
    Tags: refunds, transaction ids,   

    WC 2.2 payment gateways: Adding refund support and transaction IDs 

    Payment Gateways in WC 2.2 can be improved with the introduction of two new features; being able to store a transaction ID in a standardised format, and being able to programatically handle refunds.

    Storing transaction IDs

    Storing transaction IDs is useful because these will appear in the order interface:

    2014-08-05 at 16.41

    If your gateway makes use of the $order->payment_complete() method, storing your transaction ID is a simple process. Simply pass the transaction ID to the method:

    $order->payment_complete( $transaction_id );

    WooCommerce will then store the ID as post meta.

    If you need to do this manually for any reason, you can set it directly using add_post_meta:

    add_post_meta( $order->id, '_transaction_id', $transaction_id, true );

    Turning the transaction ID into a link

    You’ll notice in the screenshot above, the transaction ID is a link – in this case linking the the transaction on the PayPal site. If you want to do this for your gateway, in your constructor set a “view_transaction_url” property, e.g:

    $this->view_transaction_url = 'https://www.paypal.com/cgi-bin/webscr?cmd=_view-a-trans&id=%s';

    WooCommerce will substitute the %s for the transaction ID during output.

    Supporting refunds

    To support refunds you need to create a process_refund() method in your gateway class. Without showing the refund code itself (which you’ll be writing) your method should look something like:

    public function process_refund( $order_id, $amount = null ) {
      // Do your refund here. Refund $amount for the order with ID $order_id
      return true;
    }
    

    This method should return a bool (true or false, if the refund was successfull or unsuccessfull) or a WP_Error object if something went wrong.

    As well as created this method, you need to define support for refunds. To do this, set the “supports” property in your constructor, e.g.:

    $this->supports = array(
      'products',
      'refunds'
    );
    

    This will let WooCommerce know that your gateway can handle refunds.

     
    • Emyr Thomas 9:55 am on August 6, 2014 Permalink | Reply

      This is fantastic – excellent work! I assume the bundled PayPal gateway will be one of the first to support refunds. Will your official Stripe gateway support refunds by the time WC 2.2 is released?

      • Mike Jolley 10:56 am on August 6, 2014 Permalink | Reply

        PayPal has it yes – it does require some extra API details, but once setup it works well.

        I’ll be looking at adding this to Stripe and a few others over the next few weeks.

    • Lee Willis 7:06 pm on August 10, 2014 Permalink | Reply

      Hi Mike,

      I’m just adding support for refunds / transaction IDs to the Paymill gateway – can you confirm what an amount of “null” – means – is it “no refund”, or (As the bundled PayPal gateway code implies) that a “full” refund should be attempted. If so – would it be better if WC core sent the amount needing to be refunded, rather than having the gateways try and work it out?

      • Mike Jolley 9:58 am on September 3, 2014 Permalink | Reply

        Unsure on best handling for this one – the gateways I’ve done so far have all supported doing a ‘full’ refund without defining an amount.

    • Chris 2:55 pm on September 10, 2014 Permalink | Reply

      Awesome! I can’t wait until Authorize.net gets some support for this! Is this something Woo is working on or is this up to the payment gateway and other developers?

c
Compose new post
j
Next post/Next comment
k
Previous post/Previous comment
r
Reply
e
Edit
o
Show/Hide comments
t
Go to top
l
Go to login
h
Show/Hide help
shift + esc
Cancel