parse error
AndriaD - March 14, 2008 - 11:35
| Project: | Book Review |
| Version: | 5.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
After reading the various threads, I tried installing this module; I downloaded the new .install file and used it instead of the one that comes in the original tar file, but everytime I try to install, I get a parse error on line 535 in bookreview.module, unexpected } -- but I looked in that file and on line 535 there is no }, nor even anywhere near line 535, so I have no idea. I can't even go to my regular admin page until I delete the whole bookreview dir from modules via FTP.
And I was so hoping this would be a good solution for book reviews... (sniff)
#1
Well, this is really weird.
I decided to try to install it using the original install file; at first, it gave me the same parse error, line 535 in bookreview.module. So, I tried removing the } which occurs at line 537, after which, it then gave me an error about "premature $end at line 720". So I put the } back on line 537 -- after which, it worked just great, no more parse error.
Weird or what?
At any rate, it now seems to work, so, puzzled as I am, I am grateful. I'm not using table prefixes, so maybe I don't need that new install file anyway?
still scratching head in sheer befuddlement
Andria
#2
Well, scratch all that about it working fine. It doesn't. It seemed to finally get itself installed, and the UI for adding a book review came up fine; except I couldn't get that bit about adding more links and hitting preview to work at all -- but when I hit submit for the review just entered, I get a page full of MySQL gobbledygook about bookreview tables not existing. I don't know enough about MySQL to be able to really decipher what's happening with it, but I went and looked at the db via phpmyadmin, and sure enough, those bookreview tables are not present.
So I guess it's just a bust.
*pft*
Maybe I'll just make forum topics for book reviews.
#3
I removed an apparently extraneous } above the line in question, line 487 according to my editor which immediately took care of the parse error problem. Haven't gotten around to testing the actual module, although I upgraded it rather than new install and the previous version was working fine :)