bitofgrace

The issue is not with Pro.. its with NextGen Gallery
I purchased Pro hoping it would resolve the issues.. but it does not.
ALSO : despite having purchased just days ago, that account link says I dont exist.

Hi there,
Didnt realize i had been replying to a noreply email : /

Where can i send info for help with this ??
i have credentials for the dev site that has been prepped – issue persists on original site, a second client site and the cloned staging site as well.
Purchased and installed Pro but made no difference.

Prefer not to post the staging site publicly.

-grace

I can’t keep it live on the site, since it affects customer emails. : /
I don’t have this on a staging site yet – but if thats the only way, i can set it up.

SPECTACULAR! thank you ??

Hi Sormano.. sure anytime you need.

Works smoothly in Chrome.

awesome -thanks!
… and yes, i’m attempting on Safari ??
Will try it on Chrome too.

Hey, hi ??

Having the same problem (3.9.2)
If you could share any possible solution here that would be appreciated
-grace

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.

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.

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.

Feel kinda bad for your extension support team . If you thought they were swamped before – can just imagine the hell they’ll be in now.

Your own update conflicts with a number of your extensions – leaving us ignorant folk to go pressure them for a fix or update. Guess they didn’t read your beta notes!

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!

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!

Thank you Coen… but i do expect your team to shed some light on these new Warnings and errors. PLEASE .

For me it was right away : Errors on expected arrays for Woo Price Filter.
When i hid the messages i started getting Woo-messages posted for every step of determining shipping (had not had this before at all) There is no longer any logical link to where the shipping info is coming from so I’m stumped temporarily on that one.

Then there are at least 2 of my Woo extensions that are no longer compatible with this update : Product Swatches & Photos and the Stamps.com extension.

So – sure i have to hide the warnings for now… but I do hope the team that created these updates/breaks can be of some help in fixing them!

answered my own shiz:

// Turn debugging on
define(‘WP_DEBUG’, true);
// Tell WordPress to log everything to /wp-content/debug.log
define(‘WP_DEBUG_LOG’, true);
// Turn off the display of error messages on your site
define(‘WP_DEBUG_DISPLAY’, false);
// For good measure, you can also add the follow code, which will hide errors from being displayed on-screen
@ini_set(‘display_errors’, 0);

Warnings hidden .. for me to tend to without visitors getting nuts. ??