Forgive me for making my first post a request for help (and I hope this is in the right forum). With that said, I'd be hugely grateful for any advice.
My .htaccess file is causing a conflict which causes an internal server error and prevents the site from displaying. It was fine until yesterday, and between now and then the only site change was a server-side software update by my hosting company, Rochen.
Now, enabling (i.e. correctly naming) my .htaccess file causes the server error. Disabling (renaming) it causes the site to run perfectly, but without SEF URLS (which resuire mod_rewrite and a functioning .htaccess file).
I believe one of the server changes was an upgrade from Apache 2.0xxx to the Apache 2.2xxx tree, and a bit of Google searching suggests mod_rewrite and Apache 2.2 have some conflicts. But I can't work out how to resolve it, if this is the case.
Originally Posted by http://httpd.apache.org/docs/2.2/mod/core.html#ifmodule
Syntax: <IfModule [!]module-file|module-identifier> ... </IfModule>
The <IfModule test>...</IfModule> section is used to mark directives that are conditional on the presence of a specific module. The directives within an <IfModule> section are only processed if the test is true. If test is false, everything between the start and end markers is ignored.
The test in the <IfModule> section directive can be one of two forms:
In the former case, the directives between the start and end markers are only processed if the module named module is included in Apache -- either compiled in or dynamically loaded using LoadModule. The second format reverses the test, and only processes the directives if module is not included.
The module argument can be either the module identifier or the file name of the module, at the time it was compiled. For example, rewrite_module is the identifier and mod_rewrite.c is the file name. If a module consists of several source files, use the name of the file containing the string STANDARD20_MODULE_STUFF.