alturnwall

Emsi, sorry about that. Yes, I’m on 3.5.1. That’s what I tried previously, but I just tried again for good measure. Same problem.

I then installed the stock Twenty Twelve theme and activated it and don’t get the error message there, so guessed this has something to do with my theme, which is a customization of the underscores starter theme.

Did some more digging and found this line in my functions.php:

wp_enqueue_script( array( 'jquery' ), '20120206', true );

That was an incorrect usage of wp_enqueue_script that I forgot to comment out. I guess the issue didn’t pop up for a few days because the rest of the site had been cached. For reference, this is the correct way to include the WordPress-bundled jQuery:

wp_enqueue_script('jquery');

Still interested to know why the warning only popped up on this particular server and not on localhost or another test server though.

I should also note that this message is not appearing on my local version, and not on a test installation on another server, leading me to believe this may have something to do with the server config.

But, I’m not sure where to start debugging that. Any general thoughts on where to start?

Hi esmi, I’m not—I have the most up to date, that’s also why I just started a new topic for this here.

Apologies for the confusion.

I seem to be getting this same error and have manually re-installed WordPress from a fresh download. I’ve also disabled all of my plugins and still no luck.

The weird thing is this seems to have come out of nowhere—I hadn’t made any code changes to the site in a few days and all of a sudden somebody reported this error.

Any thoughts?

Could this be an issue with the server config?

Edit: The site still isn’t “public”, but here’s a link to the test site…

https://www.bywayswestmass.com/test/

Edit 2: Starting another thread for this here since it’s more of a troubleshooting topic.

Wait a minute. I just tried again and your original code seems to have worked this time.

I added it to a functions file on a parent theme that all of my blogs are children of, then I went to the Network Admin page and updated one of the plugins via the WordPress Updates page and it worked!

Not sure why it didn’t work the first time, but perhaps it has something to do with the Proper Network Activation plugin?

I’ll test a little more…

Changing the first “#_EVENTIMAGE{295,175}” you mean?

Yes, that does change the image size, meaning timthumb is still running.

I averted all of this by writing a custom archive page entirely outside of the plugin, but happy to help you troubleshoot if that’s helpful to you.

Thanks for your help.

I’ve been looking for this also. I haven’t been able to get anything to work yet, but I found this article, which I thought might be useful.

Specifically, it says:

However, there is a fly in the ointment. When we change blogs using set_blog_id, we are only changing the database context. The global $wp_rewrite object remains the same, i.e., it is the $wp_rewrite object of the original blog from where we executed the network activate or deactivate.

Seems like that’s the key, but I can’t figure out the code.

Food for thought.

Hi, I’m not actually using a caching plugin.

The events listing page is here, and I’m using version 5.3.6.1.

I should note that I customized my output by using the ‘format’ option and in that format I’m using the #_EVENTIMAGE{295,175} placeholder to output the image. I also tried simply #_EVENTIMAGE on a prior version, which pulled in the image without cropping it, but did not actually use the WordPress specified thumbnail size.

Is this setting not compatible with using the #_EVENTIMAGE placeholder?

Thanks again for the clarification!

Thank you for the clarification!

Ah, you guys are amazing!

I used @vtxyzzy’s latest pastebin since it was a tad simpler and it works like a charm.

Thank you!

@vtxyzzy, could you possibly paste that code again since it’s been removed? Thanks!

This topic was continued on the ACF forum… the thread is here.

Wow, I was trying to do the same thing and that code worked wonderfully. Thanks for sharing—you saved me a day’s worth of Googling ??

Got it. Thanks.