jehosophat

Hmmm…. “Oma Beate” has not posted to the Woo forums in wp.org at all…

Take a look at JigoShop’s response to #NortonAsp here:
https://www.ads-software.com/support/topic/they-are-good

“I have been made aware of your recent comments on our competitor’s wordpress page and therefore I would rather prefer to answer your questions offline. However, I would like to bring to your attention the fact that your comments are not accurate.”

Mr N,

It’s the word ‘all’ that is global …

Search for how to get images on a product:
https://www.google.com/search?q=wp+e-commerce+product+gallery&oq=wp+e-commerce+product+gallery&sourceid=chrome&es_sm=93&ie=UTF-8

Search for wordpress backup:
https://www.google.com/search?q=back+up+wordpress&oq=back+up+wordpress&sourceid=chrome&es_sm=93&ie=UTF-8

Mr N,
I’m usually the first to criticize the customer support, coding and general design of wp e-commerce. However in this case, it seems clear that there is a different rock in the stream of progress.

You demand support and education, yet you don’t respond to WPEC Support’s many requests for access to your site, to help and debug.

That’s fine, but you then can’t come back and say that they aren’t doing their job in this case.

Asking for a list of what programs are incompatible with your site’s profile, is a neverending research project WPEC could never fulfill.

Your current issue seems to be one of research and education, on how WordPress and WPEC work singly and together,along with other plugins.

Rather than making extravagant and global demands, why not research the issues and learn all that you can from the excellent educational resources available with a simple search. Then you might be able to ask more precise, answerable questions.

Try searching for

woocommerce+blockUI

in www.ads-software.com.

Not really a woo update issue. It’s an old bug discussed in the 1st one in the list…

Once again, I think you’re conflating separate things.

You seem to feel that ‘ease of use’ should equal ‘ease of plugin adaptation in theme development’, when these are two entirely different, if related, areas. The first is a user-level attribute, the other is coder-level.

In your decision-chain back 4 days ago, you decided to undertake a serious developer task, which was overly challenging (due to documentation, skills or whatever). My point was not to say ‘nyah nyah’, but to point out that this decision was the immediate reason for your lost time …

Also, you seem to lump the WPML plugin authors with the authors of WOO… If you look at the list, you’ll see that they are entirely different groups of people.

All in all, the point I’m making is that while Woo could absolutely devote more energy to its documentation, it seems that on balance you could recover your task and move forward by using a theme which tests out as compatible with woo, and apply your design skills to spiffing up that theme.

Hmmmm…. If you’re a non-developer, why attempt a developer’s task?

It seems that the root of your unhappiness, is that woo hasn’t made, in your opinion, sufficient effort to fully explain the highly complex task of adapting a theme to Woo.

If you look at the 3 leading ecommerce plugins in WP (woo, wpec and jigo), the task of adapting a theme to any of them is daunting at best.

If someone is not a developer, it seems only logical to seek a theme substrate which will provide good compatibility with the chosen ecommmerce package, rather than try to create a compatible theme oneself…

So let me get this straight.

You’ve tried 3 themes which say they are compatible with Woo, and were unable to get them to work with Woo, and therefore it’s Woo’s fault.

You weren’t successful in following Woo’s documentation to adapt a theme to Woo, and therefore it’s Woo’s fault.

Wow.

If you had searched, for example, for “free woocommerce theme”, you would have found all sorts of them – some even from woo themselves, and much more likely to actually be compatible with woocommerce…

@mike,
great product. don’t give in to the desire to give as good as you get. conversations come and go, but flame wars last forever. keep up the great work and great comments.

@vk011,
“there is nothing either good or bad, but thinking makes it so” – as far as i know, all of the major wordpress e-commerce plugins (woo, wpec, jigo) work the same way. There’s a lovely free theme over at splashing pixels – “mio” (https://splashingpixels.com/themes/mio/) for woo. Check it out, spend some time with it and woo, then perhaps you’ll rethink your rating…

Hi all,
@mike, you can just put in any dummy password to auto create an account on the website, which I did. the situation is indeed as @hoops states, there’s no direct way on the screen to select payment via cc without having a paypal account.

That said, I believe that @mike has the preponderance of evidence on his side. Imagine how many thousands of complaints there would have been to date, if what @hoops asserts is actually true.

So @hoops, assume for a moment that your experience is an anomaly due to a setup issue – either a paypal shop config setup, or a paypal account setup issue.

@doug,
Notwithstanding @ignitewoo’s innaccuracy regarding the WooCommerce Packing Slips php license, do you expect that all purchased software be GPL?

JJC –
What I mean is that NOTHING should be updated because a nag tells you a new version is available.

That’s not a reason to go through all of the immense trouble you should take when updating – full backups, update and complete testing FIRST in a test environment, then and only then apply any update to your production environment.

Have an important reason to go to this trouble – a **clear** security issue important to your site, a fix to a functional failure, etc…

Just because WP or another plugin says ‘New and Improved!” or ‘Spiffy!’, that’s not a reason to update.

@learn-wp,
I’d be grateful if you could please post the code to pastebin, and put the URL here….
Thanks

@asap –
You’ve missed the three cardinal rules of website programming, and they’ve bitten you in the posterior.

Rule Number One
Take backups of your site often, both database and full code (especially before any installs). Automatic DB backups delivered to you via email are great.

Rule Number Two
Once you have a stable store, never, ever update any module – not a plugin, not wordpress, nothing.

Rule Number Three
If you are dragged, kicking and screaming, into having to update your site’s modules (massive security problem, dysfunctional, etc…), never, ever update your live site. Always test exhaustively in a Test environment . Only after the update has proven itself in your test environment, does the update get moved into the production environment.