floregonian
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Featured Images Broken in Back End after 4.4 Update@sdk, I’m sure it does exactly what it’s supposed to do—it’s just that turning off the responsive images feature didn’t solve the problem I had. I was glad to have something to try!
@thefitrv, I rolled my site back to 4.2.5 and everything works again. Interestingly, neither 4.3 nor 4.3.1 worked for me, either. I need to figure out what’s going on, though. Don’t want to have a site stuck in 2015 forever.
Forum: Fixing WordPress
In reply to: Featured Images Broken in Back End after 4.4 Updatesdk, I tried your code—didn’t work for me.
Forum: Fixing WordPress
In reply to: Featured Images Broken in Back End after 4.4 UpdateI’m experiencing the same exact problem on a site I’m working on. The featured images are still linked in the back end, but when I view a post (custom or otherwise) that has a featured image, I just see “Set Featured Image,” and if I try to re-link the featured image, once I close the media manager, nothing happens on the post page. The “Featured Image” box still says “Set Featured Image,” and if I save the post, the link between that post and the featured image is broken.
I’ll probably downgrade at some point here, but here’s to hoping there’s something simple to fix in WP instead.
I just rolled back to 4.2.4 for now . . . I need an actively working site. Everything seems to be working just fine. I’ll keep my eye out for other instances of this problem and whether or not they get solved before upgrading to 4.3.
Thanks!
Jeremy
Also, let me clarify:
the “Warning: trim() expects parameter 1 to be string, array given in /home/onehopenetvps/onehope.net/wp-includes/link-template.php on line 3156” error I’m seeing is happening when I’m in the wordpress admin space, using the wordpress editor. It’s not just on the front end.
Jeremy
Hi, Tara:
We’re using WordPress 4.3. Sorry I didn’t post that right away.
I’ll post my request, including the version of WordPress, in the proper subforum.
In the meantime, don’t you think it’s still appropriate here, as the problem is also showing up across WordPress on every Featured Image, on every post?
Jeremy