How can I import an existing local Joomla site into a new WebMatrix i...
Re: How can I import an existing local Joomla site into a new WebMatr...
Dec 03, 2010 05:01 PM|F/X|LINK
Thanks so much for your rapid response! And man, you've hit the point on first trial :-)
That means: I didn't even had the option "Use Apache mod_rewrite" in use. But once I turned off the option "Search Engine Friendly URLs" (set it to No), my site works perfectly! I can easily reproduce the issue now,
i.e. if I set "Search Engine Friendly URLs" to Yes, the issue reappears, if I set this option to No, the issue vanishes.
In order to find out, if that just happens to my specific site, I installed another Joomla site (with sample data) in my WebMatrix installation, and bingo! - I can repro the issue there as well. So it's not specific to my site...
Well, now the following interesting questions remain:
1. Why can I use the option "Search Engine Friendly URLs" = Yes on my Apache-based (XAMPP) installation on my Windows Server 2008 computer, but can't use it on my Windows 7 machine using WebMatrix?
2. What can I do to be able to use SEO-friendly URLs when running my site in WebMatrix, and later at my hosting provider once my site will be ready to be published?
One idea, out of my brain (after studying many files within my site) - could this issue being related to the rewrite-rules in web.config (which partially look to me like an IIS replacement for the rules specified in htaccess.txt resp. the .htaccess file
in a PHP environment)? Or ist there some other file/place where such rewrite rules are in place that I don't know, which cause this problem?
At least I can continue developing my site in WebMatrix now, as long as I leave "Search Engine Friendly URLs" = No, until the issue has been identified and a solution or workaround can be applied.
I really hope you have another great answer at hand for me to finally solve this issue :-). And if it turns out to be a bug in WebMatrix, IIS 7.5 Express, or the PHP implementation therein, I hope you can address this to the dev team and hope they'll fix
it before RTM.
Thanks a lot,