Thanks, I managed to fix everything that I could. There’s nothing I can do about the fact that the save functions now operate within the dashboard theme instead of before it. It’s basically now a notice for other authors that this will be the most frustrating fix to deal with. The ability to redirect after a form submission to safely and smartly hide POST data has most definitely been removed as all of their forms have been adjusted for this. It’s disappointing, but if they went through all that work (for whatever unknown reason), they’re not planning to undo it.
Everything else I was experiencing are legit bugs with WooCommerce and I’ve submitted them through their GitHub. Thanks for your responses though
The global variable might be set, but it’s not working for me. I still see the notice when submitting a function through AJAX. Oh well, I can probably just set it myself.
Most importantly, I don’t like that the code now executes inside the dashboard theme. It used to run beforehand so you could use the ‘redirect’ function after submitting the form data. Now, after you enter data into a form and submit it, there is no redirect, so if you were to push refresh, you would get the prompt asking you to resubmit your data. And now with my plugins, I get the php error ‘could not resend headers, headers already sent by…’. I just wish they hadn’t removed this. It’s better to use it than not to.
Sorry, it’s WC(). For me at least many things did not work, but redefining the variable was easy. It’s the structure changes that don’t make any sense to me and it has the least amount of documentation. Most of the links are for theme developers, not plugin developers so its not entirely helpful.
Thanks for the links. Perhaps I missed it, but I haven’t seen much in regards to the one thing that is causing me the most grief as a developer and as a user. They seem to have nixed the use of wp_safe_redirect. Everything happens within the dashboard now, so if you press refresh after submitting a form, you’ll get the familiar warning popup about re-sending your form data. Plus as a developer, my plugins all function this way because safe redirect is just smart and much more user friendly. I don’t understand why they would ever want to get rid of it except for laziness. It’s easier to program this way, but it’s not a good, and now I have to undo all of this for my plugins that utilize a tab on the settings page. I just don’t understand why they have done all of these foolish updates like changing names and now this. Seems like a step backwards if you ask me.
This is a fantastic start and step in the right direction, but now that I’ve had the chance to use it for a little while, I have a couple suggestions.
Firstly, I agree that feedback is a nice addition so we know why they’re upset when its a bad, the problem is that there is nothing we can do about it. The most frustrating part of receiving a 1-star rating, or any poor rating for that matter, is that we cannot reach out to the customer. In my experience, once you receive a 1-star rating, it sticks because the customer surely isn’t using your plugin anymore. It would be nice to reach out to them and try to earn a better rating once you have changed the bug that upsets them.
Secondly, I think that reviews should be public. A rating is a brief overall description of how the customer feels, but I think that customers should be able to gauge those ratings for themselves. Find out why it received the given rating because while something might upset one person, it doesn’t necessarily upset them all. Authors are only as good as their reputation, so there’s nothing to keep secret here.
Unfortunately I didn’t have as much free time this way around and I didn’t think they would alter the core as much as they did. Most of it was minor, but I don’t understand why my ajax function stopped working. If you have WP_DEBUG disabled you’ll be fine, but after the function executes, it prints a notice and then cannot redirect. This is the notice I get:
Notice: Undefined index: hook_suffix in wp-admin/includes/screen.php on line 355
I have spent hours trying to figure it out. I’m sure it’s something stupidly simple, but can anyone point me in the right direction and tell me why the global variable isn’t set?
So today WooCommerce has officially launched 2.1 and I’m incredibly frustrated. None of my extensions work anymore. Is anyone else having this problem or is it just me? My users are complaining that they no longer ‘have permission to view the settings pages’ and I’ve also noticed that the global variable $woocommerce has changed to woocommerce().
Maybe I didn’t code it correctly before, but this upgrade has become quite the hassle. Has this update affected your extensions?
I would be interested. It’s a feature I use on a lot of online shops, and I love creating new extensions for WooCommerce. I’ve compiled a list of functions I would use and possible fields for the settings page, but if there’s anything in particular you need out of this plugin I would love to hear about it. I can compare it to my list and see what’s possible. I think there are many out there who would like this functionality so thank you for the idea!
FINALLY! big big big thank you, I love it! It was such a pleasant surprise to receive an email this morning with a rating notification. This wasn’t even a must-have for me but it’s a really nice addition. excellent job! It’s nice to know envato cares so much about their authors and listens to requests