Impossible to enable bibliography module on Drupal 6.14
| Project: | Bibliography Module |
| Version: | 6.x-1.7 |
| Component: | Code |
| Category: | support request |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Hello,
I am building a page where a number of scholars should enter their publications so as to make them easily searchable. This module seems perfect for my needs. Unfortunately I have tried to install it locally all day but I couldn't make it.
The first time these messages showed up:
Fatal error: Maximum execution time of 120 seconds exceeded in C:\Programmi\Apache Software Foundation\Apache2.2\htdocs\drupal-6.14\includes\database.mysql.inc on line 108
Fatal error: Maximum execution time of 120 seconds exceeded in C:\Programmi\Apache Software Foundation\Apache2.2\htdocs\drupal-6.14\includes\session.inc on line 56
Fatal error: Maximum execution time of 120 seconds exceeded in C:\Programmi\Apache Software Foundation\Apache2.2\htdocs\drupal-6.14\includes\session.inc on line 14
I modified the php.ini file (both execution time and memory limit) and started enabling the module again. I got a long list of warnings which said the tables already existed. I clicked Administer and all the Administration panel had changed: the links Modules and Menus did not exist anymore (maybe other links too had disappeared) and "Create content" didn't work any more. Drupal had gone.
I had to disinstall Drupal, erase the database and start everything again (I had no backup).
Though I had modified the php.ini, I got the same messages once again, then the same list of warnings. I managed to use the address bar and go to the modules page: I disinstalled the module and eliminated the tables in the database. Since the module page was still working I started the installation again, I got the same three lines of fatal errors and now I have just got into the same problem: the Administer page has been altered during the installation of the module, the same links in the Administration page have disappeared and nothing works any more.
Do you have any suggestions?
Thank you for any help,
Calimera
#1
Yikes! this is bad news indeed.
You will have to take my word for it when I say that to the best of my knowledge this has never happened before. I have seen issues around lack of memory, but usually if your php.ini is giving at least 16M it should be alright, although I currently have my own set to 64M.
What version (5.2, 5.3) of PHP are you using and on what platform (I'm guessing Windows based on the above message). Is error logging turned on in your php.ini file and if not you should turn it on and make sure a logging file is defined, then check this log for further clues as to what might be happening.
Ron.
#2
Thank you for your reply.
I have Apache 2.2, PHP 5.2, MySql 5.0, phpmyadmin 3.2.2.1. Yes, it is Windows based locally. The current limits in my php.ini file are: memory limit: 128M; execution time: 120 sec. Also, I have just turned on the error logging.
I have tried once again to install the Bibliography Module and the tables in the database got messed up. Finally, I have downloaded the previous version of this module (1.6). I could install it and modify a few entries and permissions. Unfortunately when I log out from my administrator account and test the module by using an authenticated user's account (all permissions double checked), the form with the fields is not displayed.
Do you think I should try with Drupal 6.13 and see what happens?
Thanks,
Calimera
#3
I just want to add that I installed Drupal 6.13 and the Bibliography Module 1.7. It's perfect, everything works properly! Just as others said, there must be some kind of incompatibility with Drupal 6.14.
Anyway, it's a great module. Thank you for all this work.
Calimera
#4
I'm glad to hear you found a solution.
Your right, there do seem to be some issues around Drupal 6.14, but strangely, I can't reproduce this incompatibility. My production site is running 6.14 & 1.7. Although now that I've said that, I don't think I've ever tried a clean installation, it was upgraded from previous versions
Ron.