Closed (fixed)
Project:
Content Templates (Contemplate)
Version:
5.x-1.6
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
20 Sep 2007 at 01:39 UTC
Updated:
5 Oct 2007 at 13:01 UTC
Jump to comment: Most recent file
Comments
Comment #1
cog.rusty commentedI got the same error using version 1.6 on MySQL 4.1.21
I solved it by adding the 256 length in the unique key clause too in contemplate.install, and then re-running update 2.
Comment #2
jonathanwinn commentedCan you please explain this in detail for laypersons?
And will this patch do the same thing?
Comment #3
jonathanwinn commentedokay, I changed the code in the contemplate.install patch as you described, and overwrote the old one on my server. I then did update.php without incident, but I still get the following error on pages that use contemplate:
user warning: Table 'play7com_Drupal5.contemplate_files' doesn't exist query: SELECT data FROM contemplate_files WHERE site = 'sites/default' in /home/play7com/public_html/includes/database.mysql.inc on line 172.What is involved in "re-running update 2"?
thanks,
jw
Comment #4
Hunabku commentedI get the same error - i just replaced the new contemplate version with the old one (overwrote the contemplate folder with the old folder) and the problem went away. I wait till this gets figured out before installing the new version.
Comment #5
jonathanwinn commentedLucky you. I tried the same thing, but the error message didn't go away. :-(
Comment #6
jonathanwinn commentedokay, I think I figured out that "re-running update 2" is going to update.php, expanding the "select versions" link, and selecting "2" from the pull-down list next to "contemplate module." So I did all this and I still get this error on my contemplate pages:
I am on Drupal 5.2 with MySQL 4.1.22 and PHP 4.4.7
trying to install Contemplate 1.6
Comment #7
jonathanwinn commentedJust wondering if anyone can answer this in the meantime. Is it safe to take my site live while this is happening? I noticed the error and took it offline immediately. I'd rather not have the error message on all my contemplate nodes, but I can't really afford the downtime. Will it damage the database to keep executing queries on a nonexistent table?
Comment #8
benjackson commentedMany thanks, the combination of the change suggested by cog.rusty and the info about update2 from jonathanwinn fixed it for me.
I'm running Drupal 5.2 with MySQL 5.0.38 and PHP 5.2.1
Comment #9
jonathanwinn commentedbenjackson,
thanks for posting your experience. I went back and tried again, but my update still failed to create the table. I thought I might have committed a typing error, so I pasted cog.rusty's code exactly as below (
data longblob NOT NULL,was'data' longblob NOT NULL,in the module.install file I downloaded, so I took away the single quotes around data). Can I simply create this table manually from phpMyAdmin? Can anyone tell me how?Comment #10
jonathanwinn commentedOkay I think I fixed it. There was another place I needed to enter the 256 number at the bottom of the file:
All back to normal now. Thanks everybody for their input!!
Comment #11
satori1984 commentedWorking fine on MySQL 4.1.11
After patching, re-run update 2 (see comment #6)
Comment #12
jjeff commentedPatch applied and committed. Release 1.7 created.
Sorry for the chaos. Hope this fixes it.
Yes, re-run update 2 if you've had this problem.
Comment #13
(not verified) commented