Hi hexangel,
I was able to reproduce the error, but I’m not sure why it’s happening. Could you try disabling all of your plugins other than Jetpack, and check if you still have the same error? If you don’t, then please activate your plugins one by one until you find the culprit.
If it doesn’t appear to be caused by a plugin conflict, try switching your theme temporarily to the default TwentyTen or TwentyEleven themes, to see if it’s a theme conflict.
If neither of those troubleshooting steps solves the issue, please let me know!
Thanks, Richard.
I did go through a round of plugin-disabling earlier, and it seemed to have no effect. But I’ll be ruthless with plugins and theme this time.
>:-)
Hi Richard,
All plugins but Jetpack disabled.
Activated 2010 theme.
Unfortunately, problem persisted. 🙁
I’ll have to get back to you about this one, I’ll let you know when I have something!
Thanks, Richard.
And do let me know if there’s anything I can do to help troubleshoot… I don’t mind digging into code to help the debug process.
Hi hexangel,
So, I think it’s because you are using relative links to your images, rather than the full URL to the images. The WordPress media manager inserts full links to your images, so maybe you inserted them by hand, or through another plugin? Try modifying the URLs of the images to include your site’s root domain, so that they look like
http://www.GodBeautyPerfectionLove.com/wp-content/uploads/2010/08/secondTao.jpg
rather than
/wp-content/uploads/2010/08/secondTao.jpg
And let me know if that fixes it!
Hey Richard!
Good catch! That’s a funky bug. 🙂
Momma taught me to use relative URLs whenever possible. 😉
So, the “Full URL” in the Media Settings page was set to the relative path (/wp-content/uploads/) rather than left blank, the default.
http://www.GodBeautyPerfectionLove.com/wp-content/uploads/2013/03/Media-Settings-‹-God-Beauty-Perfection-Love-Synonyms-—-WordPress.png
Anytime WP created a URL, it created a relative one.
I’ve reset that to the default. Fortunately, I’ve set a featured image for every post, and that URL gets generated on the fly, so they’re now working. At least folks pinning a page will be offered an image. However, images which have been inserted into posts and pages all have relative paths. I don’t relish the thought of repairing that by hand…
Do you think this is a bug that will be fixed in an upcoming revision? Or is there a simple code change I can make to repair it?
The REALLY funky thing? Now that I’ve reset it to the default, blank — that ‘uploading files’ set of options no longer appears on the Media Settings page. It’s reverted back to the ‘standard’ page shown here: http://codex.wordpress.org/Settings_Media_Screen
Thanks,
Patrick.
Momma taught me to use relative URLs whenever possible. 😉
Oh yeah, it totally makes sense and I agree with you! But since it goes into the DB, if you ever switch the root domain, it can be changed across the board easily. 🙂
Do you think this is a bug that will be fixed in an upcoming revision? Or is there a simple code change I can make to repair it?
It’s definitely something we’re aware of, but I can’t give you a timeline for a fix at this moment.
Now that I’ve reset it to the default, blank — that ‘uploading files’ set of options no longer appears on the Media Settings page
Those options were there before, but were removed in WordPress 3.5. When you removed your custom setting, it reverted to the new default, which means that it doesn’t show it anymore.
Hope that clears things up for you!
Yep. Thanks. Let’s call this one ‘resolved’. 🙂
But since it goes into the DB, if you ever switch the root domain, it can be changed across the board easily. 🙂
Just outta curiosity… how would I make such an across the board change ‘easily’?
Hi!
Have a look here:
http://codex.wordpress.org/Moving_WordPress
It looks daunting, but it’s normally relatively easy. Of course, you’d want to take a full backup (and maybe 2) of your site before doing that, just in case. 🙂
Ahhhhh…. of course there’s a script for database search and replace! 🙂
I was thinking there would be a date with phpMyAdmin. <shivers>
