Recent Updates Toggle Comment Threads | Keyboard Shortcuts

  • jameskoster 5:04 pm on November 19, 2014 Permalink | Reply
    Tags:   

    Attention theme authors. Frontend changes ahead in WooCommerce 2.3. 

    The Handsome Hippo is strutting along nicely and the release is beginning to take shape. As the name suggests the main focus for this release is UI and UX beautification which will result in some significant changes to the frontend design.

    Depending on how your theme integrates with WooCommerce, this could have a big impact on your product so we strongly recommend that you begin testing/playing with the bleeding WooCommerce version ASAP.

    In this post I’ll list many of the changes we’re making, but keep in mind that it’s not final. More things might change before release so please keep up to date. Check early and check often!

    For themes that provide a deep integration with WooCommerce (IE remove our CSS in favour of enqueueing their own) things will be simpler. But you may still wish to add some styles for new / tweaked elements.

    For themes that simply overwrite our bundled CSS (please stop doing this, guys) and/or template files, things could be more complicated. You will need to work through your theme accordingly paying close attention to all details.

    The list

    • All design elements now feature a ‘flat’ design ensuring WooCommerce provides a modern aesthetic that blends nicely with many theme styles. Check:
      • Messages
      • Buttons
      • Tabs
      • Demo store notice
      • Sale flashes
      • Price Slider widget
      • Payment box at checkout
    • Frontend style settings (allowing folks to change button colors etc) have been removed in favour of a separate plugin. If your theme interacted or relied on these settings keep an eye out for the upcoming plugin.
    • The increment and decrement buttons attached to quantity inputs have been removed now that support of input type="number" is more widespread. A separate plugin will be released for folks who want to add this back in.
    • 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.
    • In the cart widget, it is now possible to remove products.
    • WooCommerce now loads dashicons for the animated loading graphic used by blockUI. Feel free to utilise this without enqueueing it separately.
    • Some tables have been made responsive such as the orders table on the my-account page. If you want to add style for this to your theme, activate Twenty Twelve and check the core CSS used to achieve responsive tables. The class .shop_table_responsive has been added for this purpose.

    Hopefully this gives you guys a heads up on what’s happening on the frontend of WooCommerce 2.3. I highly recommend that any theme authors start looking at this as early as possible, even before we enter the beta stage.

    As I said earlier, themes that simply overwrite our own CSS will be most affected by these changes. To re-iterate, this is a bad practise that we do not recommend. Why not make the switch and do things properly now? :-)

     
    • Rafael Angeline 9:54 pm on November 19, 2014 Permalink | Reply

      Hi!

      Do you guys have an estimative of when will it be avaliable to public download?! This way I can alocate my team properly to migrate to this new version.

      Kind Regards.

    • Bryce 1:25 am on November 20, 2014 Permalink | Reply

      Hey Rafael. You’d be able to download the latest working copy here – https://github.com/woothemes/woocommerce

      When the Beta Release is ready, we’ll post about it here.

      • Rafael Angeline 4:28 am on November 20, 2014 Permalink | Reply

        Thank you Bryce!

        Well, it’s better already prepare to do some work hehehe

        Kind Regards.

    • Haris 12:32 pm on November 20, 2014 Permalink | Reply

      Hey Bryce,

      Any timeframe for the final release ?

      • jameskoster 5:49 pm on November 20, 2014 Permalink | Reply

        Nothing definitive. We’ll say Q1 2015 for now :-)

    • Brian Krogsgard 10:07 pm on November 20, 2014 Permalink | Reply

      WooCommerce now loads dashicons for the animated loading graphic used by blockUI

      Can you explain this further or screenshot what you mean? Is this the only Dashicon used? And it’s front-end? Seems a wasted font load if so. I’d think SVG would be better if possible. unless I’m thinking of the wrong thing.

    • Janae 4:50 pm on November 22, 2014 Permalink | Reply

      I have a question regarding your statement:

      “As I said earlier, themes that simply overwrite our own CSS will be most affected by these changes. To re-iterate, this is a bad practise that we do not recommend. Why not make the switch and do things properly now?”

      I’ve only built a single theme, based on the design for my husband’s website. It was my first crack at it, and I’m not sure I did everything properly.

      For the CSS styles, I essentially copied the entire contents of the woocommerce.css file and pasted it at the end of my own styles.css file and just made adjustments as necessary to fit my overall theme design. Is that the bad practice you speak of? :) If so, how can I fix it?

      I’ve also copied certain template files and placed them in a ‘woocommerce’ folder in my theme folder to overwrite woocommerce plugin template files, again, to better fit my theme design. Is this also bad practice?

      I don’t pretend to be the best at theme development, or even code, but I do want to be sure I’m doing the best I can at doing it properly.

  • claudiosmweb 3:00 pm on October 29, 2014 Permalink  

    WooCommerce 2.2.8 Fix/Security Release Now Available 

    The WooCommerce 2.2.8 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 nonce check in form handler. Read more about the fixes in the changelog. A total of 25 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.)

     
  • patrick 8:00 am on October 23, 2014 Permalink | Reply
    Tags:   

    WC 2.3 Email Class Refactor and Enhancements 

    WooCommerce 2.3 is still a ways out, but one of the things we’ve been working on is a better email class system in core. Primarily, we’ve refactored how emails are sent through WooCommerce. Any extension can send a WC branded email by loading the mailer and calling the send method. Like so:

    // set subject
    $subject = 'WC Send Mail Test';
    
    // load the mailer
    $mailer = WC()->mailer();
    $mailer->send( get_option( 'admin_email' ), $subject, $mailer->wrap_message( $subject, 'a test message' ), '', '' );
    

     

    WooCommerce Test Email

    An email sent via the refactored send() method

    The wrap_message() function wraps the email in the WooCommerce branding. If you want to send an email without any WooCommerce branding you can do so by not using the wrap_message() function.

    WooCommerce Email Without Branding

    An email without any WooCommerce branding

    A CSS Inliner for Prettier Email

    If you’ve ever spent time customizing an email template you know how awful it is to work with different email clients and how none of them support regular CSS. This is a pain for developers and really confusing for end users. After refactoring the send methods we were able to add a CSS inliner. This will take regular CSS and rewrite it so that each element has the styles written inline. This prevents a lot of problems with email clients.

    A New Way to Customize Email CSS

    We used to have all of the CSS in the email-header.php template which was convenient programmatically but a bit confusing for users. We took all of this CSS and put it into it’s own template. An end user can now override the email-styles.php template.

    A New Way to Customize Email CSS for Developers

    Overriding templates is great for end users but it’s not great for developers. If you want to write a plugin that changes the email styles you can use the new woocommerce_email_styles filter. I’ve made an example plugin that shows how to use this filter.

    If you want to test this new functionality yourself it’s merged into the master branch of WooCommerce on GitHub.

    Happy emailing!

     
  • Mike Jolley 12:23 pm on October 22, 2014 Permalink
    Tags:   

    WooCommerce 2.2.7 Fix/Security Release Now Available 

    The WooCommerce 2.2.7 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 when using product notes. Read more about the fixes in the changelog. A total of 58 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 8:53 pm on October 8, 2014 Permalink
    Tags:   

    WooCommerce 2.2.6 Fix Release Available 

    The WooCommerce 2.2.6 release is now available via WordPress.org or automatic update in your administration panel. This fixes a few small notices and a bug around editing order addresses in the backend.

    You can read more about the changes in the changelog. A total of 10 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 4:39 pm on October 7, 2014 Permalink
    Tags:   

    WooCommerce 2.2.5 fix release is now available 

    The WooCommerce 2.2.5 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 130 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 2:02 pm on October 7, 2014 Permalink  

    Roadmapping Core via Trello 

    Up until now ideas and roadmapping in general have been spread out across several places; todo lists, a GitHub Wiki page, within old GitHub issues, an ideas board, even private Google docs. As you can imagine, this was a nightmare to manage, let alone do any useful planning.

    In an attempt to rectify this, we’ve decided to unify our Roadmap into a single Trello board; the WooCommerce roadmap.

    The WooCommerce Roadmap

    The WooCommerce Roadmap

    Inspired by this post on the Trello blog, the board is public with voting enabled and can be used by anyone. Log ideas, comment, and vote on everything.

    So what will we use this Roadmap for? Many things!

    • Getting feedback from devs and power users
    • Prioritising things developers need via card voting
    • Interacting with the community
    • Submitting ideas to core
    • Giving brave developers some hardcore issues to work on, or think about which are not planned in the short term
    • Organising ideas into future milestones
    • Separating add-on ideas from core-worthy ideas

    How does this fit in with Github you ask? Well, Github should be used for issues we definitely need or want to work on short term. Bugs for example will still go to Github. Feature requests (or larger ideas for the medium to long term) can go to the Roadmap for feedback and voting.

    The Trello board is open now and has been populated with the old roadmap items from the (no defunct) Github wiki. See you there!

     
  • 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.

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