Closed (fixed)
Project:
Bible
Version:
6.x-1.2-rc9
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Reporter:
Created:
28 Oct 2008 at 17:06 UTC
Updated:
28 Mar 2011 at 03:01 UTC
Jump to comment: Most recent file
Parse error: syntax error, unexpected T_OBJECT_OPERATOR in /home/xxxxxxxx/public_html/modules/bible/bible.module on line 951
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | bible.zip | 38.56 KB | MikeLee_Birdy |
Comments
Comment #1
MikeLee_Birdy commentedDear Sir:
I don't encounter this problem. Can you tell me when/how will this problem happend?
MikeLee
Comment #2
dbt102 commentedI get the same/similar error when trying to update from module "Bible 6.x-1.0-rc5"... to "6.x-1.2-rc2"
"Parse error: syntax error, unexpected T_OBJECT_OPERATOR in /home/mysite/public_html/sites/all/modules/bible/bible.module on line 971"
Here's what I did...
1. I downloaded 6.x-1.2-rc2 (2008-Oct-29) from drupal modules site then uploaded it to sites/all/modules directory on production web server.
2. I moved the old bible module directory off to an 'old_module' backup directory
3. I extracted the new bible module to the sites/all/modules directory
4. I refreshed browser to check if the update was successful by clicking the link 'admin/reports/available_updates'
5. the refresh gave me the white screen with the parse error message. It completely crashed everything on the site, nothing worked.
6. I've been working with Bible module since about July 08 . It took me a few weeks, working in my spare time, to get it running correctly, and I was new to Drubal (using D6.6 presently) at that time too. However your documentation was really good and the issues I was having at the time were already experienced and documented by others, so I just did what they did.
7. My 'fix' was to delete the new "Bible" module folder created during extract and then copy the old Bible module I had saved off-site back into the 'site/all/modules' folder
8. My site works now just like it did before. The above steps only took me about five minutes, so it was really no big deal that it didn't work. However, I am fairly compulsive about keeping drupal modules up to date and would like to figure out what I'm doing wrong. I had tried an earlier update as well and it didn't work for me either, but I didn't mess with it much, just reverted to back-up. I suspect maybe I have to first need to disable the module under 'Home › Administer › Site building' before doing update?
9. But... before I try fix as described in #8 above... I have a question...Once I do the update, and it works right, will I have to reload all the bible DBs again?
Comment #3
MikeLee_Birdy commentedDear Sir:
Thanks for your detail description. I've put my latest on developing module in attach. Please try and see will this problem still happen?
MikeLee
Comment #4
dbt102 commentedThank you very much for you efforts and the response, but sorry to say the same issue occurs, here is the exact message I get...
Parse error: syntax error, unexpected T_OBJECT_OPERATOR in /home/mysite/public_html/sites/all/modules/bible/bible.module on line 1003
...again it completely 'hosed the whole site' ...meaning...it made everthing fail... I mean everything...even www.mysite.com/user
however... it was easy to restore by simply deleting the new bible module directory and copying the old one (which I saved off-site) back into the site/all/modules directory
Comment #5
MikeLee_Birdy commentedDear Sir:
Line 1003 should be
if ($domXPath->query('//bibledata/'. $li)->length > 0) {. I'm not so sure which php version will support XML function. So, please check php so that I can trace down.MikeLee
Comment #6
dbt102 commentedHi,
Thanks again for the reply, I really like this module, and would like to be able to take advantage of any improvements since Bible 6.x-1.0-rc5, but I just can't seem to get the newer version(s) to work...
My hosting service is using PHP version 4.4.9 (and MySQL version 5.0.67-community-log) and I just updated to Drupal 6.8
I also just tried the newest Bible v6.x.1.2-rc3 and it continues to disable my whole site similar to the earlier attempts I've documented above.
This most recent attempt here is what I did...
1. I first disabled the bible module before the update
2. and deleted the old module from the sites/all/modules directory.
3. Then I extracted v6.x.1.2-rc3 into the same directory.
4. I ran update.php
5. and then enabled the Bible module.
6. When I clicked on the save button (mysite.com/admin/build/modules)...
7. ... the result was the white screen with the error message similar to the earlier messages.
I have some time over the next week to trouble shoot this in more detail. I think I will try a fresh install on a new hosted production site and see if it will work there...
Comment #7
MikeLee_Birdy commentedDear Sir:
Thanks for detail reply. Could you tell me on the step 7. what error message is? I need to know where the error happen.
I'm not so sure if this is an error cause from php4. My environment is php5. Please let me know this line. Or, maybe you can switch to a platform with php5 to see if this error will gone?
MikeLee
Comment #8
dbt102 commentedDear MikeLee,
I updated from PHP 4.4.9 to PHP5 (FastCGI), and I no longer get the error message described above. I updated to 6.x-1.2-rc3 and it seems to work pretty good. Thanks for your consideration to the problems I was experiencing.
Best Regards
Comment #10
dejan commentedPlease help
I've added bible-6.x-1.2-rc9 on d6.12 in directory httpdocs/sites/all/modules/. When I clicked refresh shows me the message "Parse error: syntax error, unexpected T_OBJECT_OPERATOR in / var / www / vhosts / mysite.org / subdomains / dejan / httpdocs / sites / all / modules / bible / bible.module on line 682".
When I delete directory bible, site works great.
My provider allows only php 4.4.4-8 + etch4 and mysql 5.0.32 and does not offer the possibility of upgrades.
best regards
Comment #11
MikeLee_Birdy commentedDear Sir:
This should be php version problem. Please refer http://drupalbible.mikelee.idv.tw/?q=node/25678 for more instruction.
MikeLee
Comment #12
Kriss-dupe commentedBeen here too long, changing status for efficiency.