Hello all,
I've been searching for a few days and can't find what I am doing wrong. Here's my specs:
windows xp, apache 2.2 locally served on my own computer, php 5, mysql 5.0.18, drupal 4.7.2
What I did:
enabled taxonomy (no problem)
downloaded tac_lite 4.7.0
open with WinZip
extracted tac_lite under modules folder (directory)
according to some directions that's all i need to do
went to site, logged in, clicked admin/modules and the tac_lite didn't show up
Then I:
Logged into mysql and tried this at the mysql prompt
C:\apache2triad\htdocs\drupal\modules\tac_lite\tac_lite.mysql;
Error 1064 (42000) syntax error
Then I read on the handbooks to upload the modules via ftp after they're opened. So I acquired Filezilla and Filezilla server but couldn't figure out how it worked.
Then I tried the same thing with the audio module with the sam results.
If anybody can point me in the right direction that would be great.
Thanks,
VeeBee
p.s. July 14, 2006 15:38
Comments
Charset problem?
Just some suggestions, from my experience of similar problems:
What character set does your database have?
(If you are using phpMyAdmin you should be able to see this by entering the database and clicking the "structure"-tab (or something alike, I have the Swedish version...) and then look in a column named "collation".)
I have had some problems with charsets when moving database-dumps (sql-files) between servers (problems to figure out the right charset to use for the mirror-database when using another version mySQL, phpMyAdmin et.c.). some version of utf8 should be the safest (I'm using utf8_swedish_ci), but maybe someone can give more advice on this? I never had problems with the sql-files provided with the modules though, only my own exported sql-dumps,
Another possible reason is some changes made in the JOIN syntax (especially LEFT JOIN) in later versions of mySQL. (I've heard of people getting probs when moving from 4.1 to 5.0: http://www.codingforums.com/showthread.php?t=71431).
If this is the case the following links contain some relevant info and links:
http://mysqldatabaseadministration.blogspot.com/2005/12/what-could-be-ca...
http://gallery.menalto.com/node/36886 (Same problem showing up in 4.1, not 4.0)
(mySQL Reference on the JOIN Syntax: http://dev.mysql.com/doc/refman/5.0/en/join.html)
Our solution to the JOIN syntax problem
Forgot to mention about our solution to this latter problem...
For us, since we are using xampplite (http://www.apachefriends.org/en/xampp.html) locally, we were to find the xampp/xampplite version with the latest version of mySQL which has the old JOIN syntax. mySQL versions later than 4.1.14 were constantly causing problems, so the choice turned out to be:
ApacheFriends XAMPP Lite version 1.4.16 (For windows), which consists of:
+ Apache 2.0.54
+ MySQL 4.1.14
+ PHP 5.0.5 + PEAR (basis package)
+ eAccelerator 0.9.3
+ XAMPP Control Version 2.1 from www.nat32.com
+ XAMPP Security 1.0
+ SQLite 2.8.15
+ OpenSSL 0.9.8
+ phpMyAdmin 2.6.4-pl1
+ Webalizer 2.01-10
+ Zend Optimizer 2.5.10a
With this version of xampp we have been running Taxonomy Access Control without problems. Hope this will help!
module install problem
Hey Samuel, Thanks for replying.
Here are my collation settings:
collation connection utf8_general_ci latin1_swedish_ci
collation database latin1_swedish_ci latin1_swedish_ci
collation server latin1_swedish_ci latin1_swedish_ci
Do you think downgrading mysql 5.0.18 to 4.1.x will solve this problem.
I read somewhere (forums or handbooks) that the php settings might not be set high enough. I would like to try raising this setting but I dont know how. php.settings file?
This plan of attack makes sense to me because adding modules means adding more php programming which needs more memeory to run. I think.
OK I don't think it's a join
OK I don't think it's a join syntax problem because I get a 1064 NOT a 1054.
I adjusted the php memory from default to 24M
I changed session.save_handler:USER
These didn't work. Sucks to be a newbie.
Any suggestions would be helpful.
Maybe it's the command I typed in at the mysql prompt. That's probably wrong.
Maybe it's the roles I assigned to myself or the login.
I'm off to the mysql manual to see what the 1064 is about.