Domain Mapping plugin causing broken images

I am working on a new site for a client built on their Wp Network install. I have the Domain Mapping plugin installed to handle custom domains.

The site is ready to launch, everything is perfect when the domain is {sub}.{mainsite}.com. When I apply the new domain through the domain mapping plugin, then reload the site with the new domain active, all the site images are broken, not displaying. It is worth noting, the broken images are not just related to images uploaded through the Media Library. Images loaded through the Child Theme are also not displaying. The CSS is completely intact, minus the images.

When I remove the custom domain, and reload using just the subdomain, then all the images reappear.

Also worth noting...when the base install was initially built, I had to build it at {mainsite}.us, as the .com address was applied to the old site. I used the Domain Mapping plugin to apply the .com domain to the mainsite and that works fine. It appears that the Domain Mapping is breaking the images for the additional sites built off the WP Network.

I have the most current Domain Mapping plugin in place. Additionally, I just ran the WP updates, so it is the most current WP install.

I need to get this remedied as soon as I can. I really can't afford to go live Monday with broken images. I would love any thoughts and help possible.
Thanks
Matt

I actually did test the site, this morning, against the base TwentyEleven and got the same result. The images were broken when loading TwentyEleven.

With the circuitcellar domains, yes. I used circuitcellar.us as the dev domain since I needed to build this site while the old site was still active. Knowing that we were building more sites on it, I set WP up as a network. I probably jumped the gun on that, probably could have set the network up after, but since I already had, I used the domain mapping plugin to apply circuitcellar.com when I set that site live.

Never had any issues with that. From what I've read, anyone having issues like this always have them on the child blogs/sites, never on the main blog/site.

There are a load of plugins, so I will have to disable parts tonight, as anything I disable will probably effect the main site. Any suggestions on what to focus on disabling?

Related to the conflict, would the conflict only appear after I applied the new domain? I have all the same plugins, all the same code. Everything works properly as audio.circuitcellar.com, just not as audioamateur.com, after the domain is added.

I probably jumped the gun on that, probably could have set the network up after, but since I already had, I used the domain mapping plugin to apply circuitcellar.com when I set that site live.

So if you removed that mapping on the main site does the subsite work then?

Related to the conflict, would the conflict only appear after I applied the new domain? I have all the same plugins, all the same code. Everything works properly as audio.circuitcellar.com, just not as audioamateur.com, after the domain is added.

I'm still thinking some kind of path issue perhaps caused by the plugin.

Any suggestions on what to focus on disabling?

Quickest way to test is rename the /plugins/ folder to something else. Move over the domain mapping plugin and then go to site and test. This affectively deactivates the plugins. Also ensure the default theme is on on then.

You can then rename it back afterwards to reactivate them all (providing you didn't load the plugin admin area).

I renamed the plugin folder, replacing it with a plugin folder containing only the domain mapping plugin. Went to the AudioAmateur.com homepage, and the issue was still persistant. I have since replaced all the plugins.

It has something to do wirh the sunrise.php file. I was questioning the file I have in there, so I downloaded a new copy of this plugin and swapped the current sunrise.php and it broke all the images on circuitcellar.com. Broke everything just like AudioAmateur.com is currently broken.

Hi Timothy,
I have done everything I can think of to try and remedy this 403 with no fix.

-tried to edit my wpconfig, and bypass the plugin, couldn't get that to work.
-tried to enable hotlinking, to avoid the 403, didn't work
-tried reinstalling the entire plugin, and that didn't work. That actually threw me an error, like my sunrise.php was missing
-tried a different plugin, and that was a fail.

FIXED! I turned off the Rewrite on the server, and set allowances in the htaccess to allow the domain to hotlink from the root domain and it worked. It elimitated the 403. Probably unorthodox, but it works, and I'm going to bed.

I disabled the rewrite because it appeared to be throwing the 403 as a block to Hotlinking. As far as I can see it, the server was blocking the new domain only because it wasn't a sub of the main domain anymore. I placed a rewrite exclution in the htaccess to allow the hotlinking and everything worked.

Is there anything I should fear by doing this, besides someone linking to a file?

The mod_rewrite module uses a rule-based rewriting engine, based on a PCRE regular-expression parser, to rewrite requested URLs on the fly. By default, mod_rewrite maps a URL to a filesystem path. However, it can also be used to redirect one URL to another URL, or to invoke an internal proxy fetch.

I will admit, it started turning a little greek to me, but one of the examples I found on a forum suggested thar hotlinking may be an issue. Through Webmin, I found a section on the server that noted a rewrite for hotlinking, so I turned that rewrite engine off, but only in Webmin. I did not remove anything or turn anything off in the .htaccess, because frankly the htaccess scares me. I only added an a rewrite condition: RewriteCond %{HTTP_REFERER} !^ , and a rewrite rule to allow the images to be pulled from the domain in question.

For me still don't work. It's been a month now since 2 of my sub-sites have been never launched because of this issue that is related to the DOMAIN MAPING wpmu plugin. I dont know if this issue is because of the domain mapping plugin or my .htacces file or anything else. But what is strange to me is that all images for all subsites that I create are having this path:

Make sure you select the site that is having the issue too and if you would like to speed up the process then you can send us your FTP and wp-admin as we will likely need that to troubleshoot further :slight_smile:

If you send that in then just mention in your new ticket that you have sent your credentials to Tyler Postle. I'm not sure if it will be me that gets your ticket or not so that way they will be aware and no time will be wasted :slight_smile:

Cheers,
Tyler

PS. As this thread is 5 years old I'm going to go ahead and close it to avoid any confusion, we'll continue with your issue on your new thread.

Thanks for viewing this post but this topic has been closed to new replies.

How do you rate me?

Thank you for rating your experience!

We’re thrilled to hear you had a great experience with . Would you like to leave a comment about your experience?
Thanks for voting on your experience with , we’d love to get some feedback please.
Ohh no! We’re really sorry to hear you didn’t have a pleasant experience with , we’re always looking at how we can improve and would appreciate you provide some further feedback here please.
Type your feedback here

it's great that you had a positive one. Based on your experience in this ticket would you please be kind enough to rate us externally on: