http://omeka.org/forums/ Forums Tag: bluehost en Thu, 21 Aug 2008 22:35:34 +0000 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/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/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> http://omeka.org/forums/topic/bluehost-hosting-and-issues-with-pdo_mysql-htaccess-and-phpini#post-164 Wed, 27 Feb 2008 14:50:29 +0000 patrickgmj 164@http://omeka.org/forums/ <p>Sorry I haven't had a chance to get back here....</p> <p>Bluehost does say that php.ini should be copied to all directories. They have a script that they will give you to automatically copy it to all subdirectories, so that speeds things up nicely.</p> <p>The current ones going are the beta (0.9.0). All I can say is that so far everything is working okay. I don't think that items are going into it yet (there are four installations of it for use by students in a digital history class taught by Jeff McClurken).</p> <p>But here's something I forgot in my first post (sorry). Many of the file permissions had to be changed to 755 before everything was going okay.</p> <p>Once I got an installation working, I immediately zipped it all up so that I'd have a copy of what was working. Is there I way I should try to pass that on to you? </p> http://omeka.org/forums/topic/bluehost-hosting-and-issues-with-pdo_mysql-htaccess-and-phpini#post-151 Sun, 24 Feb 2008 07:18:49 +0000 DaveLester 151@http://omeka.org/forums/ <p>Hey gspurloc, in the future it's best to open separate threads for these problems.</p> <p>I just tried setting up Omeka 0.9.0 on a LunarPages account we have to test Omeka and it's compatible with LunarPages. There are a few ideas that come to mind of why this isn't working:</p> <p>You said you've uploaded the htaccess file - have you also included the one in Omeka's base directory? There's one there in addition to /admin/</p> <p>Going over the easiest ways for Omeka not to work, I wonder if you have PHP5 turned on. In cPanel, LunarPages offers the easy option to turn this on and off - when I tried turning it off with my test account all heck broke loose. With that said, I received a parse error and not what you're seeing. If it's none of these then we'll have to brainstorm further.</p> <p>Maybe Kris has some thoughts/ideas? </p> http://omeka.org/forums/topic/bluehost-hosting-and-issues-with-pdo_mysql-htaccess-and-phpini#post-148 Sat, 23 Feb 2008 19:07:47 +0000 gspurloc 148@http://omeka.org/forums/ <p>I checked and I have the file.</p> <p>This is the line from my errorlog</p> <p>[Sat Feb 23 10:50:56 2008] [alert] [client 71.31.112.55] /home/south150/public_html/colquitt/colquitt/admin/.htaccess: Invalid command 'php_value', perhaps mis-spelled or defined by a module not included in the server configuration</p> <p>This is from the htaccess file</p> <p>&lt;IfModule mod_php5.c&gt;<br /> php_value display_errors 1<br /> php_flag zlib.output_compression On<br /> php_flag register_globals off<br /> php_value zlib.output_compression_level 5<br /> &lt;/IfModule&gt; </p> http://omeka.org/forums/topic/bluehost-hosting-and-issues-with-pdo_mysql-htaccess-and-phpini#post-147 Sat, 23 Feb 2008 15:17:06 +0000 DaveLester 147@http://omeka.org/forums/ <p>As Kris indicated in his comment above, did you sure you copy the htaccess file that's included in the /admin/ directory? Failure to do so will result in an error message. </p> http://omeka.org/forums/topic/bluehost-hosting-and-issues-with-pdo_mysql-htaccess-and-phpini#post-146 Sat, 23 Feb 2008 07:36:21 +0000 gspurloc 146@http://omeka.org/forums/ <p>I installed the site on lunarpages and am having the same problem. The install site worked,but I can not get into the administrative part. </p> http://omeka.org/forums/topic/bluehost-hosting-and-issues-with-pdo_mysql-htaccess-and-phpini#post-145 Fri, 22 Feb 2008 20:58:47 +0000 KrisKelly 145@http://omeka.org/forums/ <p>Hi, Patrick. Good to hear that you got Omeka to work in Bluehost. I had tried to work with them to see what was wrong, but I got brushed off by their support staff. I'm curious as to which version of Omeka you were running when you encountered these problems. We still have problems getting Omeka to work on Bluehost, but in the latest release of Omeka we have fixed one of the problems you reported.</p> <p>Namely, Omeka no longer requires pdo_mysql to connect to the database. Instead it uses the mysqli extension, which is installed by default with PHP 5.2.x. </p> <p>When you say that Omeka works on Bluehost, do you mean that everything works properly? I have been able to get it to install correctly, and the home page loads properly, but none of the links work, nor does the administrative interface. I had thought it was related to the .htaccess directives somehow. Moving the php_value directives out from the .htaccess to the php.ini file does not seem to fix that part, but maybe it has something to do with having the php.ini file in every directory.</p> <p>With regards to putting the php.ini file in subdirectories, do they mean to say that it should be in *all* subdirectories of the application? Many web applications have a complicated directory structure, and copying the file manually would probably take a long time. Is this something that Bluehost will do for users if you ask them?</p> <p>If you get a chance, could you let me know whether your Omeka install is fully working, and what version you had installed? Thanks. </p> http://omeka.org/forums/topic/bluehost-hosting-and-issues-with-pdo_mysql-htaccess-and-phpini#post-144 Fri, 22 Feb 2008 17:46:43 +0000 patrickgmj 144@http://omeka.org/forums/ <p>Thought I'd share this in case anyone is using Bluehost and trying to get Omeka up and running.</p> <p>I had lots of difficulties, and it took a few rounds with tech. support to find someone who could nail down the issue. Once found, it seemed to be all good. Here's a run-down.</p> <p>1. Though they're on PHP 5.2, their configuration doesn't have pdo_mysql active. That needs to be done in the php.ini file in all directories. Start with the php.ini file they provide in the root directory and add this under the list of extensions. </p> <p><code>extension=pdo.so</code><br /> <code>extension=pdo_mysql.so</code></p> <p>Make sure you copy the php.ini file into all the subdirectories</p> <p>2. I'm fuzzier about this one--maybe someone in the forum with deeper knowledge of Apache can help me out. They said that the php_value command in the .htacces file needs to be moved into the php.ini file. Their tech. support did this for me and all is good, but I didn't think ahead enough to ask them for a line # to see what exactly they did--bad and silly me. </p> <p>Without those, I was getting errors that php_value was not defined, couldn't be found, or couldn't be initialized. I would also get this Apache error: [an error occurred while processing this directive].</p> <p>Upshot: if you're using bluehost, these are some things to watch for. And, don't let their tech. support go in circles by telling you repeatedly to make sure php.ini is copied into all the directories. Ask about the php_value command in .htaccess that needs to be moved to php.ini.</p> <p>Good luck! </p> http://omeka.org/forums/topic/glitch-on-installation#post-83 Thu, 03 Jan 2008 09:10:53 +0000 DaveLester 83@http://omeka.org/forums/ <p>Did you upgrade to RC4? I know that niceoutfit found the bugs he was experiencing were cleared up with the newest release with Omeka's codebase being much lighter and manageable.</p> <p>I visited the URL you previously gave to Dayton Stories, and it appears from the outside that Omeka is working properly. Could you try populating it with items and see how far you get? I realize there's bound to be some errors related to the .htaccess modifications Bluehost is making. </p> <p>We know that Omeka works out of the box with Dreamhost, which is why we recommend them. Our goal is to make Omeka an easy to use platform, so we'll continue to make changes that make it easier to install for everyone. With that said, Bluehost has constrictive server settings out that significantly vary from comparable and other professional shared hosting services. I hope that helps answer your question.</p> <p>About Jeff's question and image processing - Bluehost and almost all servers that run PHP also run ImageMagick, which Omeka uses to create all its derivative images. When you installed Omeka, it asked for the location of this; in the case of Bluehost its <code>/usr/bin/convert</code> You can modify this in the admin panel under the Settings tab. </p> http://omeka.org/forums/topic/glitch-on-installation#post-80 Sat, 29 Dec 2007 19:05:59 +0000 MarjorieMcLellan 80@http://omeka.org/forums/ <p>Jeff writes: I just looked at the .htaccess file and it still has the first four<br /> directives disabled with the server-written comments, which makes me wonder<br /> if everything is going to function correctly. The latest system requirements<br /> mentioned an image processing application. But I'm not sure how that needs<br /> to be installed to work with Omeka. Have you seen anything about that in the<br /> documentation? </p> http://omeka.org/forums/topic/glitch-on-installation#post-79 Sat, 29 Dec 2007 16:46:08 +0000 MarjorieMcLellan 79@http://omeka.org/forums/ <p>I wrote to Bluehost explaining the program and inquiring about possibly closing my account and moving to Dreamhost service. So far, I haven't received a reply. However, I can suddenly now log in to the administrator page. Perhaps your conversations with them had the desired effect? The bluehost server is still running php 5.16 -- Should I assume that its better to move to a different host still?</p> <p><a href="http://daytonstories.org/phpinfo.php" rel="nofollow">http://daytonstories.org/phpinfo.php</a></p> <p>Margie </p> http://omeka.org/forums/topic/glitch-on-installation#post-68 Sun, 23 Dec 2007 20:04:33 +0000 DaveLester 68@http://omeka.org/forums/ <p>Part of the problem is that Bluehost actually modifies any htaccess files you upload, based upon their own server settings. This is unconventional, and an unforseen problem. We've spoken with their support about ways to get around this, after after returning after the new year we'll reexamine solutions to handle this.</p> <p>At this time we're highly recommending Dreamhost as a stable webhost that provides the standard features utilized by Omeka, although we're still making an effort to get newer versions of Omeka running on Bluehost if possible. </p> http://omeka.org/forums/topic/glitch-on-installation#post-60 Sat, 15 Dec 2007 17:53:34 +0000 MarjorieMcLellan 60@http://omeka.org/forums/ <p>Thank you for asking this question. We did realize this might be a factor and we went back and installed it and then installed omeka with the.htaccess file a second time as well. Neither strategy resolved the problem. </p> <p>Margie </p> http://omeka.org/forums/topic/glitch-on-installation#post-59 Fri, 14 Dec 2007 20:02:34 +0000 niceoutfit 59@http://omeka.org/forums/ <p>Did you upload the .htaccess files? They are hidden/invisible in some ftp programs by default and are needed for the directory paths to work properly. Usually you can click something in the prefrences like "show hidden/invisible files".</p> <p>I know I forgot to do so on my first installation and could see others doing the same. </p> http://omeka.org/forums/topic/glitch-on-installation#post-58 Tue, 11 Dec 2007 21:26:53 +0000 MarjorieMcLellan 58@http://omeka.org/forums/ <p>We got past the Parse Error problem that I reported on earlier. We have Omeka installed on our Bluehost account and <a href="http://www.daytonstories.org/omeka/" rel="nofollow">http://www.daytonstories.org/omeka/</a> takes us to the Dayton Stories page. However, we cannot access the administration login page. We have tried installing Omeka twice and we get stalled at the same point. The message we see (http://www.daytonstories.org/omeka2/admin/) is:</p> <p>"Welcome to Omeka! It looks like you have not installed Omeka. Begin the installation process."</p> <p>We have already installed Omeka, of course. However, when we click to once again "Begin the installation process" -- the message is:</p> <p>"could not find driver<br /> Please refer to Omeka documentation for help."</p> <p>Marjorie McLellan </p> http://omeka.org/forums/topic/parse-error#post-48 Mon, 26 Nov 2007 16:47:50 +0000 DaveLester 48@http://omeka.org/forums/ <p>Great to see this has been resolved. When I had a similar upgrade, Bluehost didn’t edit my php.ini file for me, so I had to manually make the following revisions:</p> <p>Replace: extension_dir = "./" with extension_dir = "/usr/lib/php/extensions/no-debug-non-zts-20050922/"<br /> Add: extension=pdo.so<br /> Add: extension=pdo_mysql.so</p> <p>Users who still see the parse error should double check they're using PHP5 -- earlier versions will spit out that error in RC3; we'll be adding in a check for this in future releases. </p> http://omeka.org/forums/topic/parse-error#post-47 Mon, 26 Nov 2007 13:30:54 +0000 MarjorieMcLellan 47@http://omeka.org/forums/ <p>From Bluehost:<br /> This is now working. The extensions are not installed by default and they were not installed on the server so I installed them and edited your php.ini file accordingly. </p> <p>Brett<br /> Technical Support Specialist Level 3<br /> BlueHost.com<br /> 888.401.4678</p> <p>Most questions can be answered by articles in our forum, knowledgebase, and video tutorials:<br /> Forum: <a href="http://www.bluehostforum.com" rel="nofollow">http://www.bluehostforum.com</a><br /> Knowledgebase: <a href="http://helpdesk.bluehost.com/kb/" rel="nofollow">http://helpdesk.bluehost.com/kb/</a><br /> Tutorials: <a href="http://www.bluehost.com/tutorials/" rel="nofollow">http://www.bluehost.com/tutorials/</a><br /> Server Status: <a href="http://serverstatus.bluehost.com/" rel="nofollow">http://serverstatus.bluehost.com/</a><br /> When you have a new questions or issue, please open a new support ticket. </p> http://omeka.org/forums/topic/parse-error#post-46 Sun, 25 Nov 2007 22:32:53 +0000 DaveLester 46@http://omeka.org/forums/ <p>Thanks for directly pasting your exchanges with Bluehost into the forum, I hope it will clarify this for others in the future.</p> <p>We currently list PHP 5.2.x as a system requirement, however we’re working on an overhaul of our database connections in the core code which will lower that requirement to 5.1.4 once completed – possibly by next month. Omeka should work on earlier versions, but there may be some bugs that may otherwise pop up. Our test environments have primarily been on 5.2.x, so it’d be helpful to hear from a variety of users who use PHP 5 but 5.1.x.</p> <p>The PHPinfo file is perfect – the first place I should have directed you. Other users who want to see a similar page should create a new php text file, with the following code:</p> <p><code>&lt;?php phpinfo(); ?&gt;</code></p> <p>You have PHP version 5 installed, however only the sqlite2 driver is listed as enabled. Omeka requires that the mysql driver be enabled. When contacting support, you can ask them to install the PDO_MySQL module. <a href="http://pecl.php.net/package/PDO_MYSQL" rel="nofollow">http://pecl.php.net/package/PDO_MYSQL</a></p> <p>Good luck! </p> http://omeka.org/forums/topic/parse-error#post-45 Sun, 25 Nov 2007 04:15:14 +0000 MarjorieMcLellan 45@http://omeka.org/forums/ <p>I checked with our web designer. I've pasted his feedback below. I did read the omeka server requirements to a bluehost tech before setting up the account and he said that they were ok. </p> <p>Margie</p> <p>I put a file in your site that gives a list<br /> of everything you'd want to know about the version and configuration of php<br /> and related apps. Go here:</p> <p><a href="http://daytonstories.org/phpinfo.php" rel="nofollow">http://daytonstories.org/phpinfo.php</a></p> <p>You'll see at the top that you now have php version 5.1.6. That may be the<br /> problem right there since the system requirements for Omeka call for version<br /> 5.2.x or greater. The good news is that if you scroll down the page a bit,<br /> you will see that PDO is enabled. Also, the version of MySQL is up to snuff.</p> <p>So, my question for Omeka would be whether php version 5.1.6 could be the<br /> culprit. My question for Bluehost is whether they can host your site with<br /> php 5.2.x.</p> <p>By the way, php version 5.2.1 was released in February and the latest<br /> version is 5.2.5. The Bluehost guy said that upgrading the php version<br /> sometimes causes old scripts to break. So I wouldn't be surprised if they<br /> balk. But I sure hope they can accommodate you. </p> http://omeka.org/forums/topic/parse-error#post-44 Sat, 24 Nov 2007 23:33:14 +0000 MarjorieMcLellan 44@http://omeka.org/forums/ <p>OK. I received this message from bluehost:<br /> Your account has been migrated to a server running PHP 5/ MySQL 5.</p> <p>Now, when I go to the page, <a href="http://www.daytonstories.org/omeka," rel="nofollow">http://www.daytonstories.org/omeka,</a><br /> It invites me to proceed with installing Omeka. However, the next screen says:</p> <p>"could not find driver"</p> <p>Margie </p> http://omeka.org/forums/topic/parse-error#post-43 Sat, 24 Nov 2007 20:38:02 +0000 MarjorieMcLellan 43@http://omeka.org/forums/ <p>Dave,</p> <p>Thanks for the quick reply. I got an interesting response to my help ticket inquiry. As you read this, keep in mind that my bluehost account was set up only 2 weeks ago and that the omeka application was the first thing that I tried to set up on it. I've backed it all up and ok'd migrating my account as proposed below. I thought you would like to have this information; I'll let you know how it goes.</p> <p>Margie<br /> ___________</p> <p>Marjorie,</p> <p>I have a different take on this issue. The reason you don't have PDO is because you've been with us so long that you still have a PHP4 server. All newer PHP5 servers come with PDO built-in. To confirm this, I just had an administrator try installing PDO, and he got this error:</p> <p> pecl/PDO requires PHP (version &gt;= 5.0.3), installed version is 4.4.7</p> <p>We don't arbitrarily upgrade PHP4 servers to PHP5 because some older scripts are not compatible with PHP5. If you would like to try PHP5, we will move your account to a server with PHP 5 installed. Your site will be down up to 24 hours for DNS propagation. Also before we proceed with the move we want to make sure you have a backup of all your files because there is a small chance of data corruption with a server move. To proceed, please respond with the time to initiate the migration, as well as the password for your account OR the last 4 digits of your credit card, for verification purposes. </p> <p>Thank you,</p> <p>Roger Brown </p> http://omeka.org/forums/topic/parse-error#post-42 Sat, 24 Nov 2007 07:58:25 +0000 DaveLester 42@http://omeka.org/forums/ <p>Hi Marjorie,</p> <p>Thanks for posting this question on the forums. I’ve had my personal website hosted by Bluehost for several years, so I can hopefully point you in the right direction.</p> <p>Omeka uses PDO, which provides a data-access abstraction layer packaged with PHP and enabled by default. We need this to make the necessary database connections, edits, and additions. For some reason, Bluehost has a policy of disabling PDO on all their servers by default, but is willing to change the setting for users who need this functionality. At this time, Omeka requires PDO to run smoothly.</p> <p>It’s likely that you don’t PDO enabled already for your Bluehost account. To double check or make such a request, visit the Bluehost Helpdesk (http://helpdesk.bluehost.com/help) and open a ticket. Based upon my research, most if not all other shared hosts including Dreamhost keep PDO enabled; Bluehost remains an odd exception.</p> <p>The parse error you’re experiencing in the core file is related to the PDO connection, so I’d start troubleshooting there. However, without PDO a message should appear that says "could not find driver," rather than giving a fatal error. Is it possible you also edited the core file by accident, or removed one of the necessary quotes from the db.ini file? There shouldn’t be a parsing error, and I can’t replicate it. If it persists, we’ll have to dig a little deeper. </p> http://omeka.org/forums/topic/parse-error#post-41 Thu, 22 Nov 2007 18:21:47 +0000 MarjorieMcLellan 41@http://omeka.org/forums/ <p>Hi,</p> <p>We've just installed omeka on our server, but we're getting a parse error that says:</p> <p>"Parse error: syntax error, unexpected '{' in /home/daytonst/public_html/omeka/core.php on line 21"</p> <p>So far we've installed the omeka folder on our bluehost webserver and setup an empty database with a username and password and entered that information into the db.ini file. I checked to make sure mod_rewrite was enabled and it is. Also, all of the Omeka files have permissions set to either 0755 or 0644.</p> <p>Thank you for assistance with this.</p> <p>Marjorie McLellan </p>