Price Filter causing array error on Category pages

I have exactly the same problem and have no clue what to do with it, please help someone.

https://www.innervy.com/

The function ‘woocommerce_price_filter’ does not exist. Your theme or a plugin should no longer be calling it, and needs to be updated by the author for 2.1 compatibility.

Mike do you have any solution to the problem? if you fix it for me I give you bag for free ?? innervy.com just let me know – thank you so much

Suggestion to the Woo Team: Maybe consider putting ratings at the top of your future changelings, along the line of:
**** Requires developmental theme updates to be compatible -advanced level
***May require theme re-styling after update – Moderate experience recommended **Tweaks and fixes -backup as precaution
* Easy update

Could be weeks before theme devs roll out their updates – so to us laymen a warning that’s understandable would be most helpful!

@bitofgrace I don’t know why a theme would need to call that manually – we cannot anticipate all usage. Thats why listening to our beta announcements is so important!

Problem there Mike is that a large percentage of your users are NOT developers.. reading beta announcements is a full time job – that many of us cannot take on — so when a stable release is posted within our dashboards we are given the impression that it is necessary. But the reality is that if we do give in to the demand to update – we are not equipped with any tools for picking up the mess in its wake.

You can’t tell me that you’re really ok with wiping your hands of that, are ya?
Thousands of theme developers have to bend to the will of your changes. No, you can’t anticipate everything.. but obviously you CAN anticipate that a percentage of devs used the available tool – that you have now eliminated.

So in fairness.. don’t expect lay users to read your novel-thick history of beta geek-speak – instead DO warn lay users when you’ve flown the kite into the trees overhead and they’ll need a ladder or even the fire department to go fetch it!

wow such an exchange ??

lol innervy ??

i love WOO i just hate being the toddler put in the hockey rink with the big boys without warning. Had i known that devs had such a full plate to tend to in this update i wouldn’t have run the update.

well tell me about it – i don’t like it either that the customers who are trying to buy a product are telling me that they can’t – it drives me crazy to wake up today after an woo update

You can’t tell me that you’re really ok with wiping your hands of that, are ya?

Why should a plugin developer be considered responsible for a non-official hack to your theme?

Thousands of theme developers have to bend to the will of your changes.

If they are going to start throwing in their own hacks, yes. Welcome to the joys of running a web site. It’s an ongoing responsibility that’s all yours as the site owner.

@innervy: If you require assistance then, as per the Forum Welcome, please post your own topic.

esmi – isn’t the point of having an open system for devs to expand on it?

But beside the point since we’re talking about using the very tools that WOO created and supplied, and now has eliminated.

I appreciate their moving forward. I love it. but its a bit of arrogance on their part to expect everyone using their product to be as skilled at development as they are.

There are hundreds of levels of users – its the beauty of the Woo product- just asking that they be more considerate of the non-geeks that rely on their system day in and day out too.

sorry than

but its a bit of arrogance on their part to expect everyone using their product to be as skilled at development as they are.

If you are using a customised theme that is heavily dependant upon a specific plugin, then you either need to start brushing up your developer skills or you need to employ a professional to assist you. It’s is not the plugin dev’s fault if you do not (or will not) read beta announcements.

Esmi – you may want to go back and read what this thread was even about..
My statement was a suggestion to warn non-dev folks like me more clearly on updates so intense as this one so that we can be AWARE that we’ll need dev help BEFORE clicking Update.