jpresley23

I ran into the same issue. The line number I got was 176 although I got some other line numbers within the same method. My theory is that it’s due to the key $key not defined in the array $get. Setting defaults for the get_option calls may help or holding off on assigning the keys unless there’s a value.

I’m still looking into it because we may use it on our site. If we find a fix, is there a way to submit a patch?

The error can be fixed by changing line 296 in cloudinary.php to
$wanted = isset($sizes[$size]) ? $sizes[$size] : ["crop" => false];

If there is a github repo I can submit a PR.

I upgraded to the latest version since I received this error as well. The latest version did not resolve the issue. Is there a github repo that we can submit fixes to?

I’ve seen that as a solution but it seems to be the wrong way to go. Increasing the max nesting level only obscures a problem with the code.

Fair enough. We ended up asking our sysadmin to enable the mbstring php module.

I have the same issue as the original poster. I tried switching to the Twenty Thirteen theme and the issue remains. The only difference is I had updated to WordPress version 3.9.2 since installing the plugin.

If it’s helpful, it looks like HTML Minify was the culprit for the error. It looks like another plugin is responsible for the memory leak issue. From other posts about the “Call to a member function…” error that seems to be caused by trying to use methods in the cache object after it is destroyed.

Yes it does. Thank you.

Thank you for your quick reply. 1 and 2 sounds good. To answer your question regarding 3, we were planning on the editors going into the post on Blog B to manually make whatever changes are necessary.

Thank you!

Ooops. Forgot to tick of the resolved box.

I’m going to mark this as resolved. It turns out that getting /blog to work was not a result of forking the domain-mu-mapping plugin. Simply upgrading to WordPress version 3.9.2 did the trick. This is just in case anyone else needs to know the answer.

I was able to get this to work. It was a side effect of forking the domain-mu-mapping plugin to allow complete site url mapping, e.g. https://www.domain.com/foobar/ maps to https://www.foobar.com/foo. I haven’t yet tested how well all the options for the plugin works, but it works for our use case.

Fair enough. Thank you.

This was answered in an email to AddThis support. I was told that AddThis does not support the new Google Share button at this time.