Installation of version 2.3.1 results in an error 'mod_rewrite is not enabled' notwithstanding that mod_rewrite is up and running on my system.
The following are key attributes of the operating environment:
| Operating System | Arch Linux (fully updated) |
| Apache Version | 2.4.27 |
| php Version | 5.6.15 |
| Linux Kernel | 4.2.5-1 Arch |
The mod_rewrite service is known to be running by viewing a file localhost/index.php consisting of the next eight lines of code.
<?php phpinfo(); ?>
The following describes key attributes of the file /etc/httpd/conf/httpd.conf
LoadModule rewrite_module modules/mod_rewrite.so is enabled. This line appears around line 184.
There are two directory sections of interest:
Appearing around line 238 is
Require all denied
Located immediately below a documentRoot "/srv/http" follows the next Directory entry (line 251) which reads, in essence:
Options Indexes FollowSymLinks
Require all granted
I have also experimented with adding a new Directory entry, pointing to /srv/http/omeka-2.3.1.
I have also worked on the ./.htaccess file modifying the 'base directory' as described on line 25.
I have tried every known permutation of the options for AllowOverwride, Require and Satisfy directives as well as different settings in ./.htaccess all to no avail. Generally if both AllowOverride are set to "all" attempting to open localhost/test.php or the omeka installer results in 'not found' or 'forbidden' messages.
Needless to say, every modification to the http.conf is followed by a shutdown and restart of the Apache server. Interestingly, some of the permutations cause Apache to take up to 2 minutes to shut down. With others, Apache shuts down promptly when sending the shutdown signal.
Omeka-2.3.1 is known to work on an external server where we have hosting.
The copious blogs and internet entries on the subject of mod_rewrite suggest there is a serious problem in the Omeka coding that has involved a lot of minor modifications to this mod_rewrite business on the part of a lot of hard working individuals. Unfortunately, that there is again an incompatibility, this time with some versions of the latest (version 2.4) Apache server.
Any help, or suggestions for other tests would be appreciated.