| 10:39 am on May 16, 2013 (gmt 0)|
I agree with your IT manager ( and his reasoning )..don't do it..put it elsewhere..
| 11:21 am on May 16, 2013 (gmt 0)|
Thanks for the response.
| 4:58 pm on May 16, 2013 (gmt 0)|
I concur. Listen to the IT mgr.
| 8:21 am on May 17, 2013 (gmt 0)|
I was kind of hoping (for specific SEO reasons) to have the Wordpress installation under the main domain, not a subdomain.
As there seems to be a consensus against, and no solution allowing it, I'll take your advice and adjust our plans accordingly.
I'm grateful for the assistance.
| 10:16 am on May 17, 2013 (gmt 0)|
you can still do this on the main domain while hosting the blog elsewhere.
Setting up a Reverse Proxy using IIS, URL Rewrite and ARR : carlosag : The Official Microsoft IIS Site:
| 3:27 am on May 26, 2013 (gmt 0)|
We went through something similar at my work. Our solution was an iRule in the F5 pointing mainsite/blogs to a different server.
You're IT dept is correct in not wanting to introduce new isues to an existing system.
| 5:51 pm on May 26, 2013 (gmt 0)|
I am wondering why WordPress when you obviously have experienced web developers. Sure it has a lot to offer newbie site starters, ie: I was contacted last week by a guy who had 100 web sites and didn't how to upload a file to any one of them.
Take a peak under the hood... view source code of any WordPress site and then ask yourself if you really want to load that overhead on every page. The more plugins means more CSS and .JS includes and they will be loaded even if not being used.
| 8:42 am on May 28, 2013 (gmt 0)|
We do indeed have experienced web devs. Unfortunately they are totally snowed under with projects - new sites and a lot of intranet work.
Wordpress was my first choice mostly because I will have to do most day-to-day admin. It's a platform with which I am familiar. I can customise it and keep it ticking over without needing to run to IT every day, and I know how to use it so it works well for Google.
Installation was a different matter - I couldn't have much input there as I'm used to running it on *nix/Apache/PHP/MySQL. I have no personal experience with running stuff on Microsoft server/script/database platforms.
Anyway, looks as if IT have found a way to install it on the main site in a way that they are happy with. I had accepted the need for a subdomain, but the IT manager told me last week that he's got it working with Microsoft SQL and he's set it up so it won't break or compromise any extant site elements.
Looks like we're good to go.