cabgfx

Would you mind sharing how you fixed it? Thanks ??

I’m seeing a lot of those as well when upgrading to 3.8.
When activating it, I even get a notification about the plugin exceeding 1000 PHP warnings & notices.

@danieliser – did you get rid of those in your patch?

I had the same issue – editor shown correctly on WooCommerce taxonomy/product-page, but the text was gone when I reloaded the page.

I’ve found this plugin to work: Rich Tax Description Editor using WP 3.6.1 and WooCommerce 2.0.14

Nice, thanks!
I should note that I’m not 100% certain whether this is a one-size-fits-all solution, but it seems safe enough to add it to the plugin.

According to the docs, it should work fine. Note that the option was added in 2.8, in case you aim to support older WP versions.

Thanks again for a great plugin.

I found a solution for my scenario.
It was related to how the plugin fetches the images from Instagram.

If I set the decompress option to false in the call to wp_remote_request in the Photonic_Instagram_Processor class, it works fine.

I guess it’s related to the configuration of the server on my (shared) host.

So, if anyone is feeling adventurous, go edit the file here /extensions/Photonic_Instagram_Processor.php and change the code starting at line 233 from this:

$response = wp_remote_request($query, array(
  'sslverify' => false,
));

to this:

$response = wp_remote_request($query, array(
  'sslverify' => false,
  'decompress' => false
));

You will have to do this anytime you update the plugin.

Would be nice if the plugin author could chime in, and tell us if this could/should be added permanently to the plugin (I’ll gladly submit a Pull Request on GitHub!).

Same issue here.
The photos are shown just fine, when I work locally. However, on my test server they never render (not even occasionally).

I’ve tried to change the redirect URI in the Instagram app setup, but to no avail.

I do see the photos on your site, @thestoryshop.

Hmm, seems like the core team is aware of it – Trac ticket. Milestone is 3.1.4.

For anyone else having this problem:
You can hide this warning with a flag in your .htaccess to suppress warnings & errors:
php_flag display_errors off

Note: you probably want to keep this on in your development environment, but on your live site you should hide errors for security measures.

I get that exact same error as well, just upgraded to 3.1.3.

Will follow along here, and post if I find any solution that doesn’t involve touching the core.

I’ve ran into the same issue, max. 16 menu items.
I pulled up a phpinfo() and my host (shared) had the default suhosin.post.max_vars set to 200.

Put this in your .htacces file, and you’ll hopefully be good to go:

php_value suhosin.post.max_vars 2048
php_value suhosin.request.max_vars 2048

This obviously requires your host to allow changing the values in your .htaccess, and the value of 2048 might not be enough for you.

It worked for me, so I’m posting it here in hopes of helping others get unstuck and closer to launching ??

I’ve ran into the same issue, max. 16 menu items.
I pulled up a phpinfo() and my host (shared) had the default suhosin.post.max_vars set to 200.

Put this in your .htacces file, and you’ll hopefully be good to go:

php_value suhosin.post.max_vars 2048
php_value suhosin.request.max_vars 2048

This obviously requires your host to allow changing the values in your .htaccess, and the value of 2048 might not be enough for you.

It worked for me, so I’m posting it here in hopes of helping others get unstuck and closer to launching ??

I’ve ran into the same issue, max. 16 menu items.
I pulled up a phpinfo() and my host (shared) had the default suhosin.post.max_vars set to 200.

Put this in your .htacces file, and you’ll hopefully be good to go:

php_value suhosin.post.max_vars 2048
php_value suhosin.request.max_vars 2048

This obviously requires your host to allow changing the values in your .htaccess, and the value of 2048 might not be enough for you.

It worked for me, so I’m posting it here in hopes of helping others get unstuck and closer to launching ??

Thank you so much, Samuel! It works again!

Damn, this is bad news.
As far as I know, Shorten2Ping is the only plugin that successfully enables me to notify facebook+twitter, when I publish new posts.

@samuel; What exactly should I ask of Seesmic? That they approve your API key request, or..?

Thanks for your awesome work on this plugin!

^bump

‘K, thx for checking for it anyway ??