Moving Wordpress from Apache to IIS - apache

I've encountered a problem when moving a Wordpress installation from a Linux Apache server to a Windows IIS server. Nearly all pages load blank, including /wp-admin/. I created a php file in the main directory to check phpinfo, and it loads fine.
I've copied the file system over, as well as the database. I've also updated the wp-config.php with the correct credentials.
I think it has something to do with .htaccess, but I'm not sure how to correct it. Any help would be greatly appreciated.

.htaccess is not used on Windows IIS servers.
http://learn.iis.net/page.aspx/557/translate-htaccess-content-to-iis-webconfig/

Sounds like you have a permalink problem, compounded by the fact that permalinks operate differently on IIS than Linux. See: Using Permalinks « WordPress Codex
Try resetting permalinks to default in Dashbord/Settings/Permalinks, if you can get into Admin. If not, you need to go into the database with phpmyadminand manually clear the permalink field in wp_options, usually around option 34.
Update: And, did you change domains? Or just hosting? See this, too: Moving WordPress « WordPress Codex

Related

Contao is redirecting to non existend development subdirectory

Im currently trying to move a website to production that has been designed using contao. The website has been developed in a subdirectory of the current website. Now when I change the DocumentRoot to the contao directory the application automatically forwards me to the /development directory which in that situation does not exist anymore.
I did a database dump and searched it for "/development" to find the variable that is storing this information but I didn't find a match. I then did the same with the configuration files but it didn't show up any results too. How is redirecting handeled in contao?
It sounds like your pathconfig.php is wrong. After deploying/moving a Contao installation, you should always execute and log into the Install Tool under contao/install.php. This will correct your pathconfig.php.
Also make sure the RewriteBase in the .htaccess is set to the correct value (probably / in your case).

HTTP sources with h5ai appear empty in XBMC

I'm having some trouble adding a custom source to my XBMC set up. I've got an Apache2 server up and running that I use to stream movies to my computer and would like to include it as a source in XBMC. I'm no web server expert, but I managed to get h5ai style indexing on my server, which I'd like to keep. The problem is that when h5ai is enabled, XBMC can't locate any of the files. With h5ai disabled I have no issue browsing through my files.
The obvious solution is to keep h5ai off, but since I use my server outside of XBMC, I'd like to find a way to keep it on. I'm very new when it comes to web servers, so it's very possible I'm just doing something wrong. I merely followed the instructions of placing the _h5ai folder in my path and editing .htaccess. If anyone could shed some light on the issue (solution or simply an explanation) I would greatly appreciate it.
Additional info: I'm running XBMC 12.0. My server is a rented seedbox, so I have no root privileges.
Easiest solution is making a subdirectory specifically for XBMC and adding a .htaccess file that keeps h5ai indexing out of it:
DirectoryIndex index.html
Then have the HTTP source include the full path to said subdirectory.
I had the same issue and fixed it by removing "IndexOptions IconsAreLinks" from .htaccess

Wordpress says .htaccess file is unwriteable, but it's definitely writeable

I've just finished moving a Wordpress site to a new server. The domain has not changed, nor has the directory that Wordpress is installed in; the only thing that has changed is the machine it happens to be on.
The only problem I seem to have had as a result is that my permalinks aren't working, and when I go into the permalink settings, it claims that my .htaccess is unwrittable. For testing sake my .htaccess is currently CHMOD777, so it definitely is.
Any suggestions?
I have experienced problems in changing file permissions through FTP sometimes; CPanel always works. So try doing it from your host's control panel.
If that doesn't work, try editing .htaccess file manually. Follow this link to learn how to.
Your files may be 'owned' by a different user, especially if your hosting provider moved the files for you or if you used a script. If you continue to have problems, ask your hosting provider to check if the owner and permissions are set correctly on the files.
The permalinks themselves aren't working, i.e. the rules already in the .htaccess file from the previous server aren't taking effect. Mod rewrite, header and expire weren't installed. If a moderator wants to delete this silly question please feel free.

Updating Files on Apache

I'm having trouble with my Apache Web Server. I have a folder (htdocs\images) where I have a number of images already in place. I can browse them and see them on my web server (and access them via HTML). I added a new image in there today, and went to browse to it, and it can't be found. I double and triple checked the path and everything. I even restarted Apache and that didn't seem to help.
I'm really confused as to what's going on here. Anybody have any suggestions?
Thank you.
Edit I just turned on the ability for the images directory to be listed, browsed to it (http://127.0.0.1/images/) and I was able to see all the previous images that were in the folder, but not the new one.
Turn directory indexes on for htdocs\images, remove (or move out of the way) any index.* files, and point your browser at http://yoursite/images/
That should give you a full listing of files in that directory. If the file you're looking for isn't there, then Apache is looking at a different directory than you think it is. You'll have to search your httpd.conf for clues -- DocumentRoot, Alias, AliasMatch, Redirect, RedirectMatch, RewriteRule -- there are probably dozens of apache directives that could be causing the web server to get its documents from somewhere other than where you think it's looking.
make sure the caSE and spelling are 100% correct.
There is not magic in programming (some may disagree:), so look for silly errors. Wrong server? Case of your letters? Wrong extension?
There's a chance it could be due to the cookies stored on your device. I would delete all cookies to the website you're working on before you refresh again

Issues with FastCGI and links containing index.php? versus index.php

On a Windows 2003 server running IIS 6.0 and FastCGI with an ExpressionEngine-powered website, I've encountered an issue where links containing index.php fail unless a question mark is added.
The basic issue is that if a link points to "index.php/archive/article", the page fails to load (see below) but it will work when "index.php?/archive/article" is used.
What happens when the "index.php" links fail is the URL will change in the browser address bar, but the main page content is still displayed. Append a question mark to "index.php" and the page loads properly.
The site was previously running with ISAPI as the Server API with no issues: the server saw "index.php" and "index.php?" as being synonymous and pages with "index.php" in the path would load as expected.
How would I configure setting somewhere which would tell FastCGI to treat "index.php" and "index.php?" the same way?
I am a bit green when it comes to Windows servers; my experience is mostly with Apache servers running on Unix boxes.
Any guidance or pointers would be most appreciated.
One option is that you could simply enable EE's force URL query string option.
But, if you don't like having the question mark in the URL, you can try this workaround.
I can't say that I know anything about Windows servers, but this has worked for me on Apache servers when running PHP as CGI. Best of luck!