[Resolved] Multisite Domain Name Mapping Side effects
Please bear with me, for all of the programming I have done, I have absolutely no experience with A/C records.
I was hoping an old-hat expert could speak with me about the implications of the plugin http://wordpress.org/extend/plugins/wordpress-mu-domain-mapping/.
I was expecting to use the subfolder multisite option of WordPress, and then to direct traffic for additional domain names set the root folder at the host for that domain name. i.e. server_path/account_root/wordpress/blog_name.
Turns out I had a little case of under-research and being under-informed. I mucked it all up now, lol.
So, I swear all I did was point a different domain at the imaginary new blog folder http://www.widgets.com/newblog/.
I found out it didn’t work, so I set the root folder for that domain back to what it was originally. Now, the old site is working again, but the multisite blog, at http://www.widgets.com/newblog/ doesn’t work, displays “no index file”. However, oddly, the http://www.widgets.com/newblog/wp-admin/ DOES work….?!?
I am at a loss for words. I have no problem reinstalling everything, this is just a test anyway, but I am unsure of what is the best way to accomplish what I am after in a shared hosting platform.
– Multiple Domain names pointing at multiple multisite blogs.
– The redirect to this multisite blog needs to be completely private.
I am worried that using a method such as this plugin, using CNAME records will make the fact that the blog is a multisite blog clearly discoverable. Aren’t CName and A records public…?
WEll, enough ranting, any ideas to help or thoughts on how to go about doing this?
- The topic ‘[Resolved] Multisite Domain Name Mapping Side effects’ is closed to new replies.