Getting WordPress to work with my own pages plus additional complications

I am developing a hosted blog service and am intending to use wordpress with it's multisite/network feature. I have been using a subdirectory install.

I have developed an independent (outside of wordpress) set of pages to promote and explain the services I offer. Those pages have their own back-end programming. These are the pages I want to been seen when someone comes to the main URL. eg mycompany.com

However, Wordpress needs to be installed in the root directory for the WordPress MU Domain Mapping plugin to work. The plugin seems to be required if I want to give users their own domains.

The issue is that wordpress requires the root directory to be a blog and also uses the index.php for (seemingly) all it's pages and all the blogs of the network.

I really don't need this root directory blog and prefer my own suite of pages to come up in a visitor's  browser.

At this point, I need to be able to do the domain mapping with wordpress in a directory of it own; or modify wordpress to redirect to my set of pages when the index page is the actual intended destination; Or a new third solution I haven't thought of yet.

I did have a php header redirect set up in the index.php but when I added the domain mapping plugin to wordpress, my code seem to cripple the wordpress functioning.

Any ideas on what I should try or do differently?
LVL 2
CybervanesAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jason C. LevineNo oneCommented:
>> However, Wordpress needs to be installed in the root directory for the WordPress MU Domain Mapping plugin to work. The plugin seems
>> to be required if I want to give users their own domains.

Is that WPMUDev plugin?

>> The issue is that wordpress requires the root directory to be a blog and also uses the index.php for (seemingly) all it's pages and all the
>> blogs of the network.

Correct.

>> . Those pages have their own back-end programming. These are the pages I want to been seen when someone comes to the main URL.
>> eg mycompany.com. Any ideas on what I should try or do differently?

Why not convert these pages into custom page templates, keep the coding more or less intact, and use those to build the top level WP site?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
CybervanesAuthor Commented:
0
Jason C. LevineNo oneCommented:
So I don't see anything in that plugin that requires WordPress to be at the public web root.  In theory you should be able to install it to:

www.yourdomain.com/network

and create

www.yourdomain.com/network/site1
www.yourdomain.com/network/site2
www.yourdomain.com/network/site3

etc.  The trick is the ability to map www.someotherdomain.com to www.yourdomain.com/network/site1 but that's mainly server config issues and not so much WordPress.

If you can pull that off, that leaves www.yourdomain.com available for your custom coded pages.  I still think your life will be easier spending the time to convert your existing custom pages so they will work within WordPress, though.
0
Cloud Class® Course: C++ 11 Fundamentals

This course will introduce you to C++ 11 and teach you about syntax fundamentals.

CybervanesAuthor Commented:
Thanks. I am exploring the details of template building now.

 When I did the wordpress directory install and enabled the plugin, this message comes up in a  variety of places :

The domain mapping plugin only works if the site is installed in /. This is a limitation of how virtual servers work and is very difficult to work around.
0
Jason C. LevineNo oneCommented:
That might be true, but I still think you can work around it with a redirect.  I've never tried it, which is why I keep saying that converting your custom pages to work under wordpress is the better way to go...it avoids the issue completely.
0
Jason C. LevineNo oneCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
WordPress

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.