http://omeka.org/forums/ Forums Tag: .htaccess en Fri, 05 Sep 2008 17:49:16 +0000 http://omeka.org/forums/topic/still-getting-404s-and-whitepages-with-install#post-581 Fri, 08 Aug 2008 16:48:30 +0000 Fritz 581@http://omeka.org/forums/ <p>I'm getting a 500 error that says &lt;Directory not allowed in the .htaccess file. Is there another way to get those commands into the file without putting it into the directory tag? </p> http://omeka.org/forums/topic/still-getting-404s-and-whitepages-with-install#post-580 Fri, 08 Aug 2008 16:07:04 +0000 ammon 580@http://omeka.org/forums/ <p>Fritz,</p> <p>Try adding this to the bottom of your .htaccess file.<br /> <code><br /> &lt;Directory /home/web/manchester-press.com/data&gt;<br /> Options -MultiViews -Includes -FollowSymLinks -Indexes<br /> Order Deny,Allow<br /> Allow from all<br /> &lt;/Directory&gt;<br /> </code></p> <p>This will disable the options set in the apache conf file. This might be necessary because MultiViews, if it can't find a file or directory, kind of makes one up. You'll also want to disable Indexes, so that the directory structure is not visible. Includes (server side includes) are pretty insecure, so it's also best to disable those. You probably won't have any symbolic links to worry about, so it's safe to disable that as well.</p> <p>Let us know if that works or does not. </p> http://omeka.org/forums/topic/still-getting-404s-and-whitepages-with-install#post-575 Thu, 07 Aug 2008 15:13:00 +0000 Fritz 575@http://omeka.org/forums/ <pre><code>&lt;Directory &quot;/home/web/manchester-press.com/data&quot;&gt; Options Indexes FollowSymLinks MultiViews Includes AllowOverride All Order allow,deny Allow from all &lt;/Directory&gt;</code></pre> <p>My sysadmin reports that the above is my entry in the .conf file. Is there anything in this that could be killing the omeka install? </p> http://omeka.org/forums/topic/still-getting-404s-and-whitepages-with-install#post-563 Mon, 28 Jul 2008 23:49:31 +0000 KrisKelly 563@http://omeka.org/forums/ <p>I googled that apache error, and it may have something to do with your server settings not allowing access to that directory. I'm still not sure what would be wrong, but you could try adding something like this to your httpd.conf file:</p> <pre><code>&lt;directory /home/web/manchester-press.com/data&gt; allow from all &lt;/directory&gt;</code></pre> http://omeka.org/forums/topic/still-getting-404s-and-whitepages-with-install#post-562 Thu, 24 Jul 2008 20:11:30 +0000 Fritz 562@http://omeka.org/forums/ <p>Kris:</p> <p>Thanks so much for the quick reply.</p> <p>I commented the FilesMatch section, and that got test.php to work with .htaccess present, but other than that, nothing has changed. I commented the zlib lines out, and I am still hitting a plain white page. I am not getting errors on screen, or in the logs.</p> <p>And yes, php_value display_errors 1 is in my .htaccess file.</p> <p>I am stuck.</p> <p>-Fritz </p> http://omeka.org/forums/topic/still-getting-404s-and-whitepages-with-install#post-561 Thu, 24 Jul 2008 15:28:49 +0000 KrisKelly 561@http://omeka.org/forums/ <p>Is this the line you have in your .htaccess to display errors?</p> <p><code>php_value display_errors 1</code></p> <p>Also, the .htaccess file for Omeka won't let you access scripts other than index.php, since the entire application is routed through that. To get around that in order to try loading a test.php file, you should comment out the following:</p> <pre><code>&lt;FilesMatch &quot;\.(php|ini)$&quot;&gt; Order Allow,Deny Deny from all &lt;/FilesMatch&gt;</code></pre> <p>Be sure to uncomment it again after you get Omeka working.</p> <p>One other thing I can think of is, try taking out the lines with <code>php_flag zlib</code> in them. Let me know if any of that helps. </p> http://omeka.org/forums/topic/still-getting-404s-and-whitepages-with-install#post-558 Wed, 23 Jul 2008 22:18:49 +0000 Fritz 558@http://omeka.org/forums/ <p>My sysadmin has set AllowOverrides ALL in httpd.conf, and I have checked that mod-rewrite is installed in my PHP config (http://www.manchester-press.com/test.php), but when I have the .htaccess file in my root folder, then nothing works: the omeka php files just give me the whitepage, and even test.php which I introduced doesn't work.</p> <p>Basically, I have the server configured as asked, and when I place the .htaccess file into the root folder, all of the php goes dead. </p> <p>I've also made sure that the .htaccess has the code telling php to give me error messages, but that does nothing at this point.</p> <p>what else can I ask my sysadmin to do? I check the error logs and all I get is stuff like this (only when .htaccess is present):</p> <p>[Tue Jul 22 18:57:28 2008] [error] [client 76.232.149.226] client denied by server configuration: /home/web/manchester-press.com/data/test.php </p> http://omeka.org/forums/topic/bluehost-hosting-and-issues-with-pdo_mysql-htaccess-and-phpini#post-543 Fri, 18 Jul 2008 16:30:03 +0000 TemporaryLogin 543@http://omeka.org/forums/ <p>The script you need to propagate php.ini through Bluehost (and probably a zillion other ISPs) is this:</p> <p><code><br /> '&lt;?php system("find * -type d|xargs -i cp --verbose php.ini {}/."); ?&gt;'<br /> </code></p> <p>(Not certain if I actually have the correct 'backtick' character. Copy and paste from the left '&lt;' to the right '&gt;' and you'll be fine. The allowed markup of <code></code> should have it covered, so I am confused about the need to use the backticks at all. Perhaps this page is interpreted and this is a safety check to make certain that 'live code' doesn't run accidentally?)</p> <p>Place it on a text page all by itself and give it a name that ends in "php", such as "somename.php". Give it, and php.ini file attributes of 755 on a Unix-based server.</p> <p>Then, surf to that page with your browser. </p> <p>Your screen should fill up with all the zillions of places the php.ini file has been copied to.</p> <p>You should be able to drop to 700 for "somename.php" after execution, but php.ini needs to remain executable.</p> <p>I ran into the identical problem while installing "Magento" (e-commerce software rumored to be quite good). I traded the pdo_mysql error message for a blank screen. Ah well, onward and upward!</p> <p>My copy of .htaccess does not have a line about php_value in it at all. So I would ask the original poster to download a copy of the php.ini file and the .htaccess file he is using and, using a text editor, perform a search for the php_value string. It would bring him great glory and honor and international acclaim if he would close the loop he has opened by reporting the full resolution. </p> http://omeka.org/forums/topic/omeka-090-installation-and-troubleshooting-tips-gsu-library-case#post-478 Wed, 11 Jun 2008 04:58:11 +0000 anarchivist 478@http://omeka.org/forums/ <p>The issue is point 3.3 - I'll post to the dev list. </p> http://omeka.org/forums/topic/omeka-090-installation-and-troubleshooting-tips-gsu-library-case#post-477 Tue, 10 Jun 2008 22:48:31 +0000 KrisKelly 477@http://omeka.org/forums/ <p>I'm not sure which part of this list needs to be fixed. Maybe you could give a bit more info? We haven't run into any of these errors on our server (except the email bug, which was fixed in the stable-0.9 branch). What sort of problems are you having? If we can't replicate it, maybe you could help us out and try patching it and posting that to the dev list? Thanks. </p> http://omeka.org/forums/topic/omeka-090-installation-and-troubleshooting-tips-gsu-library-case#post-476 Tue, 10 Jun 2008 21:20:57 +0000 anarchivist 476@http://omeka.org/forums/ <p>Please, please, PLEASE fix this in stable-0.9 if not 0.9.1.1 - this is a blocker. </p> http://omeka.org/forums/topic/bluehost-hosting-and-issues-with-pdo_mysql-htaccess-and-phpini#post-437 Thu, 29 May 2008 13:33:54 +0000 KrisKelly 437@http://omeka.org/forums/ <p>That error means that you need to enter the correct MySQL login credentials into your db.ini file. An access denied error only happens when the username/password/host doesn't authenticate properly. </p> http://omeka.org/forums/topic/bluehost-hosting-and-issues-with-pdo_mysql-htaccess-and-phpini#post-435 Tue, 27 May 2008 21:38:52 +0000 mpwakeford 435@http://omeka.org/forums/ <p>So I think I've installed things correctly, on Bluehost, but when I hit the install link I"m getting this:</p> <p>MySQL connection error: [1045]</p> <p>Access denied for user <a href="mailto:MYUSERNAME@'box363.bluehost.com'">MYUSERNAME@'box363.bluehost.com'</a> (using password: YES)</p> <p>Please refer to Omeka documentation for help.</p> <p>Am I missing something simple? </p> http://omeka.org/forums/topic/bluehost-hosting-and-issues-with-pdo_mysql-htaccess-and-phpini#post-413 Mon, 12 May 2008 02:18:38 +0000 SheilaBrennan 413@http://omeka.org/forums/ <p>Chris G.<br /> Glad to hear all is working well with the newest version.<br /> Sheila </p> http://omeka.org/forums/topic/bluehost-hosting-and-issues-with-pdo_mysql-htaccess-and-phpini#post-412 Sun, 11 May 2008 17:45:23 +0000 ChrisG 412@http://omeka.org/forums/ <p>I attempted a clean install of Omeka 0.9.1.1 this morning on Bluehost and everything is up and running without problem. I tried, unsuccessfully, a couple months ago to install on Bluehost and encountered the same problems as described in previous postings. Not sure if this release resolved the issues or if Bluehost made server adjustments. Either way the install went smoothly and without error. </p> http://omeka.org/forums/topic/omeka-090-installation-and-troubleshooting-tips-gsu-library-case#post-393 Sat, 26 Apr 2008 15:31:39 +0000 jgreenberg 393@http://omeka.org/forums/ <p>Just a data point - I needed to do 3.3 in a new installation of 0.9.1.1 in order to get file uploading working as well... </p> http://omeka.org/forums/topic/funny-characters-without-editing-the-htaccess#post-355 Tue, 15 Apr 2008 12:08:53 +0000 Martinis 355@http://omeka.org/forums/ <p>Okay, that's great. </p> http://omeka.org/forums/topic/500-internal-server-error#post-343 Sat, 12 Apr 2008 18:25:05 +0000 veehikle 343@http://omeka.org/forums/ <p>Thanks. Wiped clean and started over with the new .9.1.1 version. Now we get a new error.</p> <p>The install part of the process was fine. When I go to the admin portion of the configuration I type <a href="http://www.historicalsocietyofsomersethills.org/omeka/admin" rel="nofollow">http://www.historicalsocietyofsomersethills.org/omeka/admin</a></p> <p>It brings me to <a href="http://www.historicalsocietyofsomersethills.org/omeka/admin/users/login" rel="nofollow">http://www.historicalsocietyofsomersethills.org/omeka/admin/users/login</a></p> <p>instead and then tells me that the page is not found.</p> <p>The host is on Godaddy.com and I have all the proper sql and php.</p> <p>Any idea? My install is off the root directory in a directory called omeka. Is that a problem for the .htacess files? </p> http://omeka.org/forums/topic/funny-characters-without-editing-the-htaccess#post-327 Thu, 10 Apr 2008 18:34:31 +0000 KrisKelly 327@http://omeka.org/forums/ <p>Thanks for the heads up. That must happen if PHP doesn't have the zlib extension enabled. That is not a life or death thing that Omeka needs to have enabled, so it would be better if that was left out of the .htaccess file and checked elsewhere. I've got a ticket on Trac so we can take care of that for the next release. </p> http://omeka.org/forums/topic/funny-characters-without-editing-the-htaccess#post-320 Tue, 08 Apr 2008 09:43:16 +0000 Martinis 320@http://omeka.org/forums/ <p>I had to uncomment the two lines in .htaccess within mod_php5.c "...zlib.output_compression..."</p> <p>Otherwise the pages gave some funny output on the screen with "random" chars.</p> <p>Dunno if this issue could help someone else or if this is just the mistake of my serverconfiguration.</p> <p>Regards<br /> Martinis </p> http://omeka.org/forums/topic/500-internal-server-error#post-311 Fri, 04 Apr 2008 16:51:45 +0000 KrisKelly 311@http://omeka.org/forums/ <p>Hi, sorry for the delayed response, but could you upgrade your Omeka installation to the latest version (0.9.1)? We've fixed some of the issues with the .htaccess file and it may no longer cause problems for you. Thanks! </p> http://omeka.org/forums/topic/500-internal-server-error#post-241 Sat, 15 Mar 2008 04:54:57 +0000 veehikle 241@http://omeka.org/forums/ <p>Tried logging in a bunch of times to the admin module....</p> <p><a href="http://www.historicalsocietyofsomersethills.org/omeka/admin/" rel="nofollow">http://www.historicalsocietyofsomersethills.org/omeka/admin/</a></p> <p>This is what I'm getting....HELP</p> <p>[Fri Mar 14 17:41:32 2008] [error] [client 69.249.59.157] File does not exist: /var/chroot/home/content/v/e/e/veehikle1/html/events_news/spacer.gif<br /> [Fri Mar 14 17:58:33 2008] [alert] [client 68.192.188.165] /var/chroot/home/content/v/e/e/veehikle1/html/omeka/admin/.htaccess: Invalid command 'php_value', perhaps mis-spelled or defined by a module not included in the server configuration<br /> [Fri Mar 14 17:58:36 2008] [alert] [client 68.192.188.165] /var/chroot/home/content/v/e/e/veehikle1/html/omeka/admin/.htaccess: Invalid command 'php_value', perhaps mis-spelled or defined by a module not included in the server configuration<br /> [Fri Mar 14 17:58:42 2008] [alert] [client 68.192.188.165] /var/chroot/home/content/v/e/e/veehikle1/html/omeka/admin/.htaccess: Invalid command 'php_value', perhaps mis-spelled or defined by a module not included in the server configuration<br /> [Fri Mar 14 18:00:22 2008] [error] [client 74.6.18.164] Directory index forbidden by rule: /var/chroot/home/content/v/e/e/veehikle1/html/Images/photoarchive/<br /> [Fri Mar 14 18:24:01 2008] [error] [client 74.6.18.138] Directory index forbidden by rule: /var/chroot/home/content/v/e/e/veehikle1/html/Images/photoarchive/<br /> SoftException in Application.cpp:624: Could not execute script "/home/content/v/e/e/veehikle1/html/cgi/discus"<br /> Caused by SystemException in API_Linux.cpp:430: execve() for program "/home/content/v/e/e/veehikle1/html/cgi/discus" failed: Permission denied<br /> [Fri Mar 14 18:51:02 2008] [error] [client 74.6.18.154] Premature end of script headers: /var/chroot/home/content/v/e/e/veehikle1/html/cgi/discus<br /> [Fri Mar 14 19:09:25 2008] [error] [client 65.55.104.14] File does not exist: /var/chroot/home/content/v/e/e/veehikle1/html/drafts/bb.php<br /> [Fri Mar 14 19:12:28 2008] [error] [client 74.6.23.217] Directory index forbidden by rule: /var/chroot/home/content/v/e/e/veehikle1/html/Images/photoarchive/<br /> [Fri Mar 14 21:46:59 2008] [alert] [client 68.192.188.165] /var/chroot/home/content/v/e/e/veehikle1/html/omeka/admin/.htaccess: Invalid command 'php_value', perhaps mis-spelled or defined by a module not included in the server configuration<br /> [Fri Mar 14 21:47:06 2008] [alert] [client 68.192.188.165] /var/chroot/home/content/v/e/e/veehikle1/html/omeka/admin/.htaccess: Invalid command 'php_value', perhaps mis-spelled or defined by a module not included in the server configuration<br /> [Fri Mar 14 21:48:31 2008] [alert] [client 68.192.188.165] /var/chroot/home/content/v/e/e/veehikle1/html/omeka/admin/.htaccess: Invalid command 'php_value', perhaps mis-spelled or defined by a module not included in the server configuration<br /> [Fri Mar 14 21:48:38 2008] [alert] [client 68.192.188.165] /var/chroot/home/content/v/e/e/veehikle1/html/omeka/admin/.htaccess: Invalid command 'php_value', perhaps mis-spelled or defined by a module not included in the server configuration </p> http://omeka.org/forums/topic/omeka-090-installation-and-troubleshooting-tips-gsu-library-case#post-231 Mon, 10 Mar 2008 18:19:11 +0000 jackeyhong 231@http://omeka.org/forums/ <p>A copy of this post can also be found at <a href="http://www.library.gsu.edu/pages/pages.asp?ldID=111&#38;guideID=0&#38;ID=5410" rel="nofollow">http://www.library.gsu.edu/pages/pages.asp?ldID=111&#38;guideID=0&#38;ID=5410</a></p> <p>GSU System Settings:<br /> Linux Suse Enterprise v10<br /> Apache 2.2.3<br /> MySQL 5.0<br /> PHP 5.2.5<br /> ImageMagick (with libjpeg library installed)</p> <p>Installation/Troubleshooting Tips<br /> Since the Omeka installation is pretty straightforward, we will only concentrate on the problems we met during installation and testing.<br /> 1. Upgrading PHP from 4.3 to 5.2.5<br /> 1.1 in Suse Linux, use yast2 facility to do the upgrade<br /> 1.2 again, using yast2 to enable with enable exif functions (in yast2, search for PHP and enable exif). Exif function is used by FileImages.php (/omeka/application/models/FileImages.php, exif_read_data() etc..). Exif function is used to read meta data from pictures by digital camera.</p> <p> 2. .htaccess file is a headache. It depends on apache server setting. The .htaccess files come with Omeka are perfect, but we have to add the following code in our apacke config file to make it work with Omeka .htaccess files. </p> <p>In GSU apache config file, we add the followings:<br /> &lt;Directory "/srv/www/htdocs/omeka"&gt;<br /> Options All<br /> AllowOverride All<br /> Order allow,deny<br /> Allow from all<br /> &lt;/Directory&gt;</p> <p> 3. After installation, we found the following problems in our testing.<br /> 3.1 Error in adding a new user (blank page)<br /> This was caused by the micortime() function in /omeka/application/models/UsersActivations.php. This function is only available on operating systems that support the gettimeofday() system call. We changed it to date('YmdHis'), and troule resolved.</p> <p> 3.2 Error in sending activation email to new user.<br /> This is a known issue in Omeka 0.9.0 and to be resolved in next release. A temporary workaround was posted by us in Omeka forum (http://omeka.org/forums/topic/user-activation-issue-temporary-workaround?replies=2). Basically, just add one line of code as a quick fix.<br /> in file: /application/controller/UsersController.php line 122. After<br /> =====================================<br /> try {<br /> if($user-&gt;saveForm($_POST)) {<br /> =====================================<br /> Add:<br /> $user-&gt;email = $_POST['email'];</p> <p> 3.3 Error in adding new item to an archive (here we tested adding a new still image). If we leave the field Compression blank, it will cause a database insert error. We changed the database table field files.compression to NULL. </p> <p> 3.4 Error in uploading images. Omeka returns blank page after uploading an image. It was caused by Exif functions set are not available. Please refer to step 2.2 to learn how to install PHP Exif support. </p> http://omeka.org/forums/topic/installation-trouble-on-debian-etch#post-205 Wed, 05 Mar 2008 22:05:39 +0000 rubinsta 205@http://omeka.org/forums/ <p>That was it! Thanks a lot, jonlesser. </p> http://omeka.org/forums/topic/installation-trouble-on-debian-etch#post-204 Wed, 05 Mar 2008 19:51:15 +0000 jonlesser 204@http://omeka.org/forums/ <p>rubinsta, Is your httpd.conf file on your Debian server allowing htaccess overrides? This can often be off by default. You'd want to look for the AllowOverrides directive. </p> http://omeka.org/forums/topic/installation-trouble-on-debian-etch#post-202 Wed, 05 Mar 2008 01:36:27 +0000 rubinsta 202@http://omeka.org/forums/ <p>Thanks for the response...</p> <p>I've ftp'd via a few different clients and even copied the files from a working install to the debian server, all with the same results. Here are the contents of my index.php file in the omeka root directory:</p> <pre><code>&lt;?php // Ladies and Gentlemen, start your timers define(&#39;APP_START&#39;, microtime(true)); require_once &#39;paths.php&#39;; define(&#39;ADMIN_THEME_DIR&#39;, BASE_DIR.DIRECTORY_SEPARATOR.&#39;admin&#39;.DIRECTORY_SEPARATOR.&#39;themes&#39;); define(&#39;THEME_DIR&#39;, BASE_DIR.DIRECTORY_SEPARATOR.&#39;themes&#39;); require_once &#39;Omeka/Core.php&#39;; $core = new Omeka_Core; $core-&gt;initialize(); // Call the dispatcher which echos the response object automatically $core-&gt;dispatch(); if ((boolean) $config-&gt;debug-&gt;timer) { echo microtime(true) - APP_START; } // We&#39;re done here. ?&gt;</code></pre> <p>This matches the index.php on my working installs (I've since installed successfully on a debian desktop). The only installation step specific to my web server that I can think of is that I used unzip to uncompress omeka. I used Archive Manager on the Debian desktop and Stuffit on the Mac. Probably a red herring but I thought I'd through it into the mix. </p> http://omeka.org/forums/topic/installation-trouble-on-debian-etch#post-201 Tue, 04 Mar 2008 20:39:49 +0000 DaveLester 201@http://omeka.org/forums/ <p>My gut feeling is that these two problems are unrelated, but I could be wrong</p> <p>@rubinsta: Can you check to see that you've properly FTP'd the files to your server? If the htaccess file is properly routing then it should be sending requests through your index.php file - is this file empty?</p> <p>@asnagy: Is this Andrew from code4lib? If so, greetings! </p> <p>I looked at line 23 of the install file; is an exception being thrown, or how else are you seeing an error on that line? In any case line 23 executes the SHOW TABLES command on mysql, which could be handled differently if you're running a version of mysql that's below mySQL5 which Omeka requires to run by default. What version of mySQL are you running? </p> http://omeka.org/forums/topic/installation-trouble-on-debian-etch#post-199 Tue, 04 Mar 2008 17:48:06 +0000 asnagy 199@http://omeka.org/forums/ <p>I am experiencing the exact same problem. I was able to narrow it down to issues with the database (I think). However my mysql database is setup correctly.</p> <p>I was able to narrow it down to line 23 in install/install.php</p> <p>I will keep digging </p> http://omeka.org/forums/topic/installation-trouble-on-debian-etch#post-191 Sun, 02 Mar 2008 21:02:26 +0000 rubinsta 191@http://omeka.org/forums/ <p>I'm having some trouble installing Omeka on Debian Etch running PHP5.2 and Apache 2.x. </p> <p>When I navigate to omeka in my browser the page loads blank and neither PHP or Apache logs an error. mod_rewrite is enabled and I have .htaccess files in /admin and in Omeka's root directory. I've also tested PHP and PHP's error reporting and everything seems to check out. </p> <p>I've been able to successfully install Omeka on my Mac's MAMP stack but no luck on the Debian web server. Here are the contents of my .htaccess files (if this is any help):</p> <p>omeka root:</p> <pre><code>IfModule mod_php5.c&gt; php_value display_errors 1 php_flag zlib.output_compression On php_flag register_globals off php_value zlib.output_compression_level 5 &lt;/IfModule&gt; RewriteEngine on RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d [OR] RewriteCond %{REQUEST_URI} .+\/archive\/ RewriteRule !\.(js|ico|gif|jpg|png|css)$ index.php &lt;FilesMatch &quot;\.(php|ini)$&quot;&gt; Order Allow,Deny Deny from all &lt;/FilesMatch&gt;</code></pre> <p>/admin:</p> <pre><code>php_value display_errors 1 php_flag zlib.output_compression On php_value zlib.output_compression_level 5 RewriteEngine on RewriteRule !\.(js|ico|gif|jpg|png|css)$ index.php</code></pre> <p>This matches the .htaccess files on my successful MAMP stack install. I wish I had more information to give but this is all rather perplexing!</p> <p>Thanks so much! </p> http://omeka.org/forums/topic/bluehost-hosting-and-issues-with-pdo_mysql-htaccess-and-phpini#post-184 Sun, 02 Mar 2008 03:35:29 +0000 DaveLester 184@http://omeka.org/forums/ <p>Patrick -- Sure, I'll take a look at it to see what they did. If you zip it up and send it as an email attachment to <a href="mailto:omeka.dev@gmail.com">omeka.dev@gmail.com</a> that'd be great. Also - could you send along the script that Bluehost gave you to copy the php.ini file to all subdirectories? I'd be interested in looking at it, and eventually adding this information all to the codex for future users. </p>