Aaron Brazell

Hi @foldeistudio-

Only one of these warnings is from the Bonsai plugin (the first). The other 4 are definitely Cookiebot. Looks like possibly they are redeclaring the PHP-DI library, but I’m not sure.

Thanks for the report!

Nevermind, though the docs are still outdated with little developer direction.

Doug-

I just installed it. It’s really straightforward. You don’t have to modify the theme at all. No new form. No new anything. All the integration is behind the scenes.

/edited… nevermind

Testing confirms. We’ve removed the plugin from the blacklist. Thanks!

Thanks, we’ll test it.

“Well, yes, until you go out and tell people my stuff doesn’t work before getting a reply.”

I have no idea what you’re on about. Really very confused. As far as I know, Mark posted that one post above… and that’s it until you responded today. So I’d highly recommend you actually email me before causing a scene. You have my contact info.

That’s what a support forum is for. ??

No, Joost. That’s not how it works. W3TC is modular and you can load all or some of it.

Yes the function_exists() verifes that the plugin is active, but the pgcache, dbcache, minify and objectcache stuff can all be turned on or off selectively.

Sounds like you’re on a shared host and MySQL isn’t tuned very well. We can make this configurable in a future release, but what happens if you edit yolink-search.php and on line 42, set $this->throttle_rate = 10;?

You should be aware that the obfuscation not only doesn’t solve the problem of it being a secret, but the way it is written causes problems in some setups. Break it into two lines… the base64_decode() returned to a string. The string then eval()’d.

This works in our environment where the current way does not. I know it’s weird. But trust me…

We’ll publicly release at some point in the future. Sorry for the confusion.

Are there any errors in the Javascript error log to speak of? It sounds like we’ve got a JS collision somewhere.

It works (8.8) mostly. It breaks the new galleries feature (all images displayed at full res, as opposed to the designated size).

Okay, everyone cool down. We need a few things here. WP 2.2 may have adjusted the code, but the problem is WP 2.1 and _that_ is what is available for public consumption and support.

So, let’s get this:

1) Plugins installed and versions
2) Theme used
3) Firefox extensions used, perhaps
4) Platform info… Windows? Mac?
5) Can you reproduce on a different computer?

After that, disable ALL plugins – particularly ANY plugin that MIGHT have javascript in use. Does this solve this problem (Note: it will probably create errors on the template because now plugin functions aren’t available – don’t worry when you reactivate those things will be fixed).

If that fixes the issue, take the divide and conquer approach and reactivate half your plugins (that you were using). Does the problem come back? If no, activate half of what’s left. Repeat and rinse.

If you activate plugins and the problem does return, focus on that group of plugins. Deactivate half of them and check for the problem. Does it occur? Yes? No? And so on until you find the culprit.

If none of this solves the issue, kick your theme over to Kubrick (though I doubt this is a theme related issue since the error is in wp-admin but for due diligence, follow through and check it out).

I am 99.999% sure you will find the culprit.

Be methodical. Provide detailed info on how to reproduce.

And for God’s sake, smoke a cigarette or drink a beer and everyone cool the tempers.

??