http://omeka.org/forums/ Forums Tag: troubleshooting en Thu, 21 Aug 2008 23:11:40 +0000 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/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/clemson-library-installation#post-249 Tue, 18 Mar 2008 16:00:09 +0000 DaveLester 249@http://omeka.org/forums/ <p>Good catch alexan6. Thanks. </p> http://omeka.org/forums/topic/clemson-library-installation#post-245 Sun, 16 Mar 2008 20:44:16 +0000 alexan6 245@http://omeka.org/forums/ <p>Installing Omeka 0.9.0 a small Gentoo test server we did encounter the whitescreen mentioned in the troubleshooting section, but the error wasn't caused by the <code>AllowOverides All</code> directive. Our PHP installation, version 5.2.5, was not compiled with the mysqli extensions which caused the blank page. It took me a little to trace the cause down to the failing Db.php class. A quick recompile fixed our problems and the rest installed cleanly, but do you think it would be possible/useful for Omeka to check for this in the future? Or at least print something useful if you are missing a function? </p> <p>A simple<br /> <code><br /> if (!function_exists('mysqli_connect')) {<br /> throw new Zend_Config_Exception('PHP missing required MySQL improved extensions.');<br /> }<br /> </code><br /> would have made the debugging a little easier.</p> <p>And thanks to MrDys for <a href="http://omeka.org/forums/topic/non-root-installation-rewrite-rules?replies=1">this thread</a> about the RewriteBase information. </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/install-errors#post-72 Mon, 24 Dec 2007 03:34:08 +0000 KrisKelly 72@http://omeka.org/forums/ <p>Thanks for catching that. We'll be sure to fix that in the next release, and I will push for setting up svn access after the holiday break, so that you and the other active testers can have consistent access to bug fixes.</p> <p>W/r/t to the .htaccess, display_errors and zip.output_compression can both be taken out without any break in functionality, though the 'register_globals' is a bit trickier, it shouldn't break anything but having it set to 'on' has been known to create security holes. For now I'd say remove all the lines that are causing breakage, and we'll fix it in an upcoming version. </p> http://omeka.org/forums/topic/install-errors#post-70 Sun, 23 Dec 2007 23:26:49 +0000 kerim 70@http://omeka.org/forums/ <p>Same is true for the "admin" .htaccess file.</p> <p>By simply removing these lines, rather than modifying them in some way, do I break any functionality? </p> http://omeka.org/forums/topic/install-errors#post-69 Sun, 23 Dec 2007 23:20:39 +0000 kerim 69@http://omeka.org/forums/ <p>Problem solved - and it explains both the errors and the lack of an error log:</p> <p>"the most common case for a 500 error is a broken .htaccess file, which basically prevents Apache from doing *anything* (including outputting any useful hint into the error log). You have two php_value and two php_flag lines in .htaccess and those are only valid for PHP that is served via mod_php. We do not use mod_php, but rather the more powerful mod_fcgid approach, and the lines you have there are thus evaluated as 'invalid'. Just remove them."</p> <p>(NOTE: <code>&lt;blockquote&gt;</code> does not seem to work in these forums.) </p> http://omeka.org/forums/topic/install-errors#post-67 Sun, 23 Dec 2007 14:32:36 +0000 kerim 67@http://omeka.org/forums/ <p>Thanks for getting back to me. I turned on error reporting on my server, but when I open the log it is blank. I'll submit a ticket to my webhost to see if I can get this working better. </p> http://omeka.org/forums/topic/install-errors#post-66 Sat, 22 Dec 2007 20:05:26 +0000 DaveLester 66@http://omeka.org/forums/ <p>There have been some internal discussions about SVN access, and I know your email sent directly omeka.support has been receieved. I'll double check that some got back to you, although I know many of us are on vacation (myself included) for the holiday break.</p> <p>In regard to the 500 error you've experienced, an error log should be written to whenever a request is made to your server with a 500 error message. If you could tell us the specific errors being reported, then it'd be easier to help out. </p> http://omeka.org/forums/topic/install-errors#post-65 Sat, 22 Dec 2007 03:01:20 +0000 kerim 65@http://omeka.org/forums/ <p>I tried again with the final release of RC4, but I'm still getting 500 errors. </p> <p>Seem to be talking to myself ... </p> http://omeka.org/forums/topic/install-errors#post-62 Mon, 17 Dec 2007 15:47:41 +0000 kerim 62@http://omeka.org/forums/ <p>UPDATE: Nothing new, except that I deleted the install linked above, hoping to install from SVN, as per the Codex - but was unable to do so without an SVN password, so I wrote the developers asking if I could get one. </p> http://omeka.org/forums/topic/install-errors#post-61 Mon, 17 Dec 2007 04:04:48 +0000 kerim 61@http://omeka.org/forums/ <p>Strange, I'm trying to install Omeka, but I'm getting 500 errors:</p> <p><a href="http://kerim.joyeurs.com/omeka/" rel="nofollow">http://kerim.joyeurs.com/omeka/</a></p> <p>I changed the default permissions for all files to 755 and for the archives folder to 777.<br /> I checked the database settings 3 times.<br /> I double checked that invisible files had all uploaded.<br /> I checked that I'm running the right versions of PHP and mysql.</p> <p>Its likely that I still missed something, but I'm wondering if there is an easy way to tell whats going wrong?</p> <p>Thanks.</p> <p>Here are my server's PHP settings:</p> <p><a href="http://wiki.joyent.com/facebook:kb:swphp" rel="nofollow">http://wiki.joyent.com/facebook:kb:swphp</a> </p>