Hello folks. I seem to have run across a problem. I consistently get this error on various pages in the admin interface and have checked the mysql db and verified it doesn't exist:

user warning: Table 'newsprouts.cache_swftools' doesn't exist query: SELECT data, created, headers, expire, serialized FROM cache_swftools WHERE cid = 'swf:36b450b6fa923b412c8e3b60a8271da0' in /home/content/13/3900913/html/includes/cache.inc on line 26.
user warning: Table 'newsprouts.cache_swftools' doesn't exist query: UPDATE cache_swftools SET data = '

If you can see this text instead of an animation then JavaScript insertion failed. Check that your browser has JavaScript enabled, and if it does check your SWF Tools settings.

', created = 1299161147, expire = 0, headers = '', serialized = 0 WHERE cid = 'swf:36b450b6fa923b412c8e3b60a8271da0' in /home/content/13/3900913/html/includes/cache.inc on line 109.

Has anyone come across this before? Any ideas on how I can get this table in there?

Comments

Stuart Greenfield’s picture

Stuart Greenfield commented

Did you run update.php if you came from an earlier version of SWF Tools? The cache table is new and would not be installed by earlier versions.

If you installed from scratch can you let me know what, if anything, you did out of the ordinary as it means the module didn't create the table properly.

You can create the table manually by copying the schema from swftools.install and looking for swftools_scheme().

ko_chin’s picture

ko_chin commented

Hi,

I did install it from scratch but didn't do anything out of the ordinary. Copied the files over, enabled the module and got the error. Not quite sure why or for what reason. But thanks for the info, I'll create the table by hand then. Thanks!

ronline’s picture

ronline commented

The same here.
Installed from scratch and found the same error.
update.php fixed all

vm’s picture

vm commented
Status: Active » Postponed (maintainer needs more info)

I can't reproduce the reported issue 6.x-3.0 beta 5 or the 3.x-dev

@#3 which version did you install? as this report was filed against 3.0-beta4 and the latest release is 3.0-beta5 and you didn't shift the version. If installing beta 4, then I'd suggest using the latest release and testing on a fresh drupal install.

This reads a bit like the module was implemented at one time, then removed, then added back in.

ronline’s picture

ronline commented

@VM the module is 6.x-3.0-beta5.
Yes it has been implemented, then removed, then added back in

vm’s picture

vm commented

Yes it has been implemented, then removed, then added back in

That is likely why update.php had to be run to force the new table to be created in the DB.