Closed (fixed)
Project:
Content Templates (Contemplate)
Version:
5.x-1.7
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
20 Sep 2007 at 07:27 UTC
Updated:
16 Mar 2008 at 05:33 UTC
Just installed the new upgrade and received this error message (which appears now on the front page of my site):
user warning: Table 'femrich_drupal.contemplate_files' doesn't exist query: SELECT data FROM contemplate_files WHERE site = 'sites/default' in /home/femrich/public_html/includes/database.mysql.inc on line 172.
Not sure what this means. Any thoughts?
Comments
Comment #1
jonathanwinn commentedIs this on your install of 1.5 or 1.6? I got a similar error on the install of 1.6.
Error from update.php:
BLOB/TEXT column 'site' used in key specification without a key length query: CREATE TABLE contemplate_files ( site varchar(256) NOT NULL, data longblob NOT NULL, UNIQUE KEY site (site) ) /*!40100 DEFAULT CHARACTER SET utf8 */; in /home/play7com/public_html/includes/database.mysql.inc on line 172.
Error from pages using contemplate:
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.
I tried to go back to 1.5, but I still get the errors. Obviously, I'm not an expert in PHP or MySql. If the developers could please help find a solution--and put it to me in laymen's terms, I'd appreciate it. I have taken my site offline until I can figure this out.
Comment #2
femrich commentedThis was on install of 1.5. I was previously on 1.3, and reverting to 1.3 solved the issue. Now I will wait to upgrade until the module seems actually stable.
As a non-expert, sort of post-newbie user, I've found that sometimes upgrades of modules get a bit ahead of themselves, and that the upgrades are promoted to "recommended" status in the available updates module too, too quickly. A quick succession of upgrades to a module seems to indicate there are still bugs in the system. Those bugs should be worked out *before* a module upgrade is promoted to "recommended" status. And a "recommended" module should never require patching to perform its intended tasks.
Comment #3
jonathanwinn commentedcheck out the thread at http://drupal.org/node/177112/. Discussion of a similar issue is there, and may be of use.
Comment #4
vegeneric commentedI'm getting this same error on a fresh install of contemplate 5.x.1.7.... doesn't seem the problem has been fixed
Comment #5
jrglasgow commentedI'm a new co-maintainer, I just installed 5.x-1.8 and have had no problems with the install. Is anyone having problems still?
Comment #6
femrich commentedI previously reported problems in this thread (actually, I began the thread). Now I am running 5.x-1.8 and have no problems. Stupidly, I did not report back here at what point my problems were resolved (and cannot now recall) so can't add any more information than that at this point.
Comment #7
jrglasgow commentedComment #8
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.