Comments for Ernie Leseberg :: Software Developer http://ernieleseberg.com Creating Quality Software for the Web Fri, 17 Feb 2012 13:05:43 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Comment on WooCommerce – No Thanks by Dan Thornton http://ernieleseberg.com/woocommerce-no-thanks/#comment-920 Dan Thornton Fri, 17 Feb 2012 13:05:43 +0000 http://ernieleseberg.com/?p=936#comment-920 Hi, I just wanted to update everyone on what's been happening at Jigoshop as there have obviously been some changes since the original post and some of the comments were made. Jigoshop itself only launched 8 months ago, and obviously any changes to the team straight after launch were going to cause some disruption, although we've minimised it as much as possible, and invested in a growing development team and a growing support team. We've also spent a lot of time rebuilding several sections of Jigoshop from the ground up to make it more stable, more reliable, and easier to build on, and that's been a major focus to give us a great base to work from - hence why we're 'only' on version 1.1 right now - the version number isn't an indication of how mature the product is, or how much work has been done. We've also had a Jaquith security audit and launched a new support system on top of reworking areas such as products to add better UI and easier administration on top of more efficient code (This isn't to knock the original code of Jigoshop, but when you've had 50,000+ downloads and feedback you get a great understanding of what needs to be improved). Our release schedule was originally planned to have less frequent updates to allow more stability for end users, but if that gives the impression that we're not moving quickly, then maybe we need to look at that again! Certainly we've committed a large amount of resource, both financially and in terms of manpower, to continuing to improve Jigoshop with the aim of making it the best possible WordPress eCommerce solution, and we'll continue to focus on that. Hi,
I just wanted to update everyone on what’s been happening at Jigoshop as there have obviously been some changes since the original post and some of the comments were made.
Jigoshop itself only launched 8 months ago, and obviously any changes to the team straight after launch were going to cause some disruption, although we’ve minimised it as much as possible, and invested in a growing development team and a growing support team.
We’ve also spent a lot of time rebuilding several sections of Jigoshop from the ground up to make it more stable, more reliable, and easier to build on, and that’s been a major focus to give us a great base to work from – hence why we’re ‘only’ on version 1.1 right now – the version number isn’t an indication of how mature the product is, or how much work has been done.
We’ve also had a Jaquith security audit and launched a new support system on top of reworking areas such as products to add better UI and easier administration on top of more efficient code (This isn’t to knock the original code of Jigoshop, but when you’ve had 50,000+ downloads and feedback you get a great understanding of what needs to be improved).
Our release schedule was originally planned to have less frequent updates to allow more stability for end users, but if that gives the impression that we’re not moving quickly, then maybe we need to look at that again!
Certainly we’ve committed a large amount of resource, both financially and in terms of manpower, to continuing to improve Jigoshop with the aim of making it the best possible WordPress eCommerce solution, and we’ll continue to focus on that.

]]> Comment on Jigoshop v1.0 beware by Dan Thornton http://ernieleseberg.com/jigoshop-v1-0-beware/#comment-917 Dan Thornton Mon, 13 Feb 2012 11:08:44 +0000 http://ernieleseberg.com/?p=969#comment-917 Hi Ernie, Many apologies that you've encountered problems with your client site - we did test Jigoshop V1.0 both internally and as a beta release, but dealing with over 50,000 downloads now there's a lot of variations in server setup, themes, and customisation around. The good news is that V1.1 should be released later today (Feb 13th), and the issues you've listed are all being taken care of in this release. We'd also encourage anyone running a store or particularly producing extensions or client sites to get in touch and be included on the beta testing list to get earlier access and be able to check pre-release versions to minimise problems and also help us to iron out any issues before launch. Please do send me an email to be added to the list as we're improving our beta testing plans for any future releases... Hi Ernie,
Many apologies that you’ve encountered problems with your client site – we did test Jigoshop V1.0 both internally and as a beta release, but dealing with over 50,000 downloads now there’s a lot of variations in server setup, themes, and customisation around.

The good news is that V1.1 should be released later today (Feb 13th), and the issues you’ve listed are all being taken care of in this release.

We’d also encourage anyone running a store or particularly producing extensions or client sites to get in touch and be included on the beta testing list to get earlier access and be able to check pre-release versions to minimise problems and also help us to iron out any issues before launch. Please do send me an email to be added to the list as we’re improving our beta testing plans for any future releases…

]]> Comment on 5 Free Software PHP Issue Trackers by Gunnar Wrobel http://ernieleseberg.com/5-free-software-php-issue-trackers/#comment-913 Gunnar Wrobel Mon, 06 Feb 2012 19:41:44 +0000 http://devreview.com/?p=584#comment-913 Just wanted to note that "Whups" from http://www.horde.org reached version 2.0.0 last year in April and got a nice set of new features. Whups uses "queues" as it can handle incoming requests via e-mail - pretty much like OTRS. We successfully use it within the Horde LLC to handle incoming customer requests. Just wanted to note that “Whups” from http://www.horde.org reached version 2.0.0 last year in April and got a nice set of new features.

Whups uses “queues” as it can handle incoming requests via e-mail – pretty much like OTRS.

We successfully use it within the Horde LLC to handle incoming customer requests.

]]> Comment on The Big List of PHP Frameworks by mekele http://ernieleseberg.com/big-list-of-php-frameworks/#comment-910 mekele Wed, 01 Feb 2012 08:53:17 +0000 http://devreview.com/?p=441#comment-910 Nette v2.0RC2 just released. English documentation, finally. http://nette.org/ Nette v2.0RC2 just released. English documentation, finally.
http://nette.org/

]]> Comment on WooCommerce – No Thanks by Ernie Leseberg http://ernieleseberg.com/woocommerce-no-thanks/#comment-904 Ernie Leseberg Sun, 22 Jan 2012 12:29:57 +0000 http://ernieleseberg.com/?p=936#comment-904 The one site I migrated, most of the product content went without trouble. The missing area was around product attributes. Of course as time goes on the changes are likely to be greater and migration harder. The one site I migrated, most of the product content went without trouble. The missing area was around product attributes. Of course as time goes on the changes are likely to be greater and migration harder.

]]> Comment on WooCommerce – No Thanks by Peter Cunningham http://ernieleseberg.com/woocommerce-no-thanks/#comment-895 Peter Cunningham Tue, 20 Dec 2011 22:00:12 +0000 http://ernieleseberg.com/?p=936#comment-895 Very interesting thanks. I was thinking of using a template that uses Jigoshop. Could someone tell me that if I do this and add products etc, later will I be able to use woocommerce plugin without having to re-input all my products? Very interesting thanks. I was thinking of using a template that uses Jigoshop. Could someone tell me that if I do this and add products etc, later will I be able to use woocommerce plugin without having to re-input all my products?

]]> Comment on WooCommerce – No Thanks by Ernie Leseberg http://ernieleseberg.com/woocommerce-no-thanks/#comment-888 Ernie Leseberg Tue, 06 Dec 2011 10:52:42 +0000 http://ernieleseberg.com/?p=936#comment-888 Of the 2 sites I originally set up on Jigoshop, 1 has already switched and the other will probably move as well. The last 2 releases have had a number of problems around variations and attributes. So I am already eating my original words. I must agree WooCommerce is leaving jigoshop behind. Woocommerce and Mike who seems to be doing nearly all the dev, do need to be careful with their releases as they are coming thick and fast (3 in 2 days 1.22 to 1.24). Thankfully any small issues have been fixed very fast. Of the 2 sites I originally set up on Jigoshop, 1 has already switched and the other will probably move as well. The last 2 releases have had a number of problems around variations and attributes. So I am already eating my original words.
I must agree WooCommerce is leaving jigoshop behind. Woocommerce and Mike who seems to be doing nearly all the dev, do need to be careful with their releases as they are coming thick and fast (3 in 2 days 1.22 to 1.24). Thankfully any small issues have been fixed very fast.

]]> Comment on WooCommerce – No Thanks by John http://ernieleseberg.com/woocommerce-no-thanks/#comment-886 John Mon, 05 Dec 2011 22:39:33 +0000 http://ernieleseberg.com/?p=936#comment-886 I went with Jigoshop because i didn't really like the whole "fork" thing. (plus the creators are in the same town as me, so it was nice to support a local company) Now however, i have just switched the site over to Woocommerce, simply because there are issues with the Jigo version and support/fixes just don't seem to be happening. It's a bit sad, but i have to be realistic - despite rooting for the underdog, functionality support and stability are what matters - and i think Woo are striding ahead of the Jigo team. I went with Jigoshop because i didn’t really like the whole “fork” thing. (plus the creators are in the same town as me, so it was nice to support a local company)
Now however, i have just switched the site over to Woocommerce, simply because there are issues with the Jigo version and support/fixes just don’t seem to be happening.
It’s a bit sad, but i have to be realistic – despite rooting for the underdog, functionality support and stability are what matters – and i think Woo are striding ahead of the Jigo team.

]]> Comment on WooCommerce – No Thanks by MacyMyDay http://ernieleseberg.com/woocommerce-no-thanks/#comment-884 MacyMyDay Thu, 01 Dec 2011 19:36:11 +0000 http://ernieleseberg.com/?p=936#comment-884 I started with Jigoshop on a new site project in September. at the time JS was v.9.8; I had plenty of issues with the content wrapping to get it to work with a Theme my client had chosen. Since the forking and questionable behavior of the Woo management, I've been keeping an eye out; rooting for the underdog, hoping for a major score by the JS team. Today JS is v.9.9.3 -- not even an official/final release. Woo has made steady improvements, and today has released v 1.3 -- the 13th release since launch in September. JS has maybe 4. Perhaps the resources scoffed by Woo have crippled the development team and therefore they still after more than 4 months don't have a 'real' release. I'm rooting for them. But I have a client to serve. And it appears that Woo has committed significant resources to the project, for good reason. I'm trying to stay with JS, but if I read between the lines -- of code and otherwise -- Woo appears to be advancing what ultimately JS should've and could've been doing, at a much more rapid rate. As for the requirement of an email address; come on! I know you've used a stale or proxy email in the past. You coulda simply done that! thanks for sharing! I started with Jigoshop on a new site project in September. at the time JS was v.9.8; I had plenty of issues with the content wrapping to get it to work with a Theme my client had chosen.

Since the forking and questionable behavior of the Woo management, I’ve been keeping an eye out; rooting for the underdog, hoping for a major score by the JS team.

Today JS is v.9.9.3 — not even an official/final release. Woo has made steady improvements, and today has released v 1.3 — the 13th release since launch in September. JS has maybe 4.

Perhaps the resources scoffed by Woo have crippled the development team and therefore they still after more than 4 months don’t have a ‘real’ release.

I’m rooting for them. But I have a client to serve. And it appears that Woo has committed significant resources to the project, for good reason.

I’m trying to stay with JS, but if I read between the lines — of code and otherwise — Woo appears to be advancing what ultimately JS should’ve and could’ve been doing, at a much more rapid rate.

As for the requirement of an email address; come on! I know you’ve used a stale or proxy email in the past. You coulda simply done that!

thanks for sharing!

]]> Comment on WooCommerce – No Thanks by Andy Eastes http://ernieleseberg.com/woocommerce-no-thanks/#comment-843 Andy Eastes Mon, 10 Oct 2011 15:35:38 +0000 http://ernieleseberg.com/?p=936#comment-843 Went through the whole setup process, then the checkout does not even work. Spent hours trying to fix, cannot even find the calls in the code. Even tried different templates to no avail..... Went through the whole setup process, then the checkout does not even work. Spent hours trying to fix, cannot even find the calls in the code. Even tried different templates to no avail…..

]]>