Posted by stattler on December 9, 2009 at 8:02pm
Ok, so I have tried everything afresh and this time installation started without any glitch. At the last step of installation, I get the following error:
Configuring OpenPublish
There was an error configuring OpenPublish.
Please continue to the error page
An error occurred. http://my/URL/install.php?locale=&profile=openpublish&id=2&op=do <br /> <b>Fatal error</b>: Cannot redeclare link_install() in <b>/path/to/op/sites/all/modules/link/link.install</b> on line <b>12</b><br /> When clicked on the error page link, it took me to the finish line:
OpenPublish installation complete
Congratulations, OpenPublish has been successfully installed.
You may now visit your new site.
I will update the site as I go along the configuration. In the mean time, please keep your findings/errors/success-story posted.
My VPS configuration:
Debian 64-bit
nginx (http://nginx.com/) With latest php and mysql server
Comments
Error when creating node
I get the following error when I try to create content:
sTattler.com
Errors in Vews
In node type: Blog
Under Homepage Block, Field section has two "Broken/missing handler". Both are related to user profiles, perhaps due to missing fields.
sTattler.com
Your installation did not
Your installation did not complete correctly, so the real problem is the error in the message #1, the rest of the errors are the result of the broken installation.
Any chance you can re-run installation and see if you hit the "Cannot redeclare link_install() " error again?
Thanks
.............................................
http://twitter.com/inadarei
New error with emvideo
I've deleted my old installation and tried a fresh install. Following error has occurred:
An error occurred. http://www.domain.com/install.php?locale=&profile=openpublish&id=1&op=do <br /> <b>Fatal error</b>: Cannot redeclare emvideo_vimeo_info() in <b>/www/dev.stattler.com/sites/all/modules/emfield/contrib/emvideo/providers/vimeo.inc</b> on line <b>24</b><br />sTattler.com
Awesome!
Dear irakli,
After seeing my initial (broken) installation with the said error, I was really really upset with the new look of OP. I thought what happened to the developer that they have made something worse than the previous version! But alas, all what I saw was due to that error!!!
I do not know what made the difference when I tried for the 4th time to install it. It did install smoothly and flawlessly and I've got the fresh new OP similar to the old one with lots of improvements in terms of the theme. A big thank you to all of your team.
What I tried different this time?
1) I untarred the .tgz file same as before
2) It gave me openpublish folder (same as before)
3) I copied the folder to newfolder: cp -r openpublish newfolder (previously I was doing mv openpublish newfolder)
4) I created /sites/default/files folder and chmod to 777 (before running the installation. Previously I started the installation, then created "files")
5) I chmod 777 the settings.php file before running the installation (Previously, I started installation and then changed the permission)
It went flawlessly! Awesome!!
A big thank you!!
I am posting it so that others might be benefited. :)
sTattler.com
Open Publish 1.6 test install problem
Installed in subdirectory (.htaccess suitably altered) in Apache data directory, on FreeBSD 7.2 on local network. Install ok, then directed to go to home page, whereon WSOD appeared. Going to index.php does same.
httpd-error.log line is:
[Thu Dec 10 16:06:12 2009] [error] [client 192.168.1.21] File does not exist: /usr/local/www/apache22/data/admin
Where is admin normally?
I am not sure, but if you
I am not sure, but if you install OP1.6 correctly (without any error message appearing), then it should have the following files and folders:
The terms with .txt or .php are files, while the rest are folders. I do not see any folder called "admin" in my installation root directory.
sTattler.com
There must be some other
There must be some other errors in the log before that.
WSOD mostly appears when you run out of memory. What is memory_limit set in your php.ini, right now? Make sure it is at least 64M, but 128M highly recommended.
.............................................
http://twitter.com/inadarei
Re: There must be some other
Indeed. The problem was more fundamental: /var was too small at FreeBSD installation (a long time ago) leading to disk full error - found on mysql log. I wanted to upgrade the version anyway. It took the db intensiveness of OP to flush out my underestimate. OP now installed on FreeBSD 8.0.