| Post |
|
David M - Guest
5:39 am - March 25, 2008
|
| |
|
Please replace the ??? with your data!
- Your URL: http://???
- The browser used: Firefox Mac V1.05
- cforms version: 8.02
- Your Wordpress version: 2.2.1
[desc]:
_
Hi and thanks for developing such a useful plugin.
I noticed, in another message, the mention of file uploads being renamed to avoid the problem of duplicate file names. However I'm not sure how this works or if I need to do something to enable the feature.
In testing I see that files are named "noid-filename.xxx". I tried uploading duplicates but the second file didn't appear, in the uploads directory.
Is there something I need to enable?
Regards
David M
|
|
|
Oliver
- Admin
7:40 am - March 25, 2008
posts 3909 |
| |
|
Yes, can you try and enable cforms DB tracking under the Global Settings page. This will enable proper data collection and thus numbering the uploads.
|
|
|
David M - Guest
8:45 am - March 25, 2008
|
| |
|
Thanks for the quick reply. I tried turning on DB tracking but got the following Wordpress Error message:
WordPress database error: [You have an error in your SQL syntax. Check the manual that
corresponds to your MySQL server version for the right syntax to use
near 'DEFAULT CHARSET=utf8' at line 7] CREATE TABLE wp_cformssubmissions (
id int(11) unsigned auto_increment,
form_id varchar(3) default '',
sub_date timestamp,
email varchar(40) default '',
ip varchar(15) default '',
PRIMARY KEY (id) ) ENGINE=MyISAM DEFAULT CHARSET=utf8
WordPress database error: [You have an error in your SQL syntax. Check the manual that
corresponds to your MySQL server version for the right syntax to use
near 'DEFAULT CHARSET=utf8' at line 5] CREATE TABLE wp_cformsdata (
f_id int(11) unsigned auto_increment primary key,
sub_id int(11) unsigned NOT NULL,
field_name varchar(100) NOT NULL default '',
field_val text) ENGINE=MyISAM DEFAULT CHARSET=ut
It's late in the day, here in Sydney, so I'll look into this when I get home later this evening.
Regards
David
|
|
|
Oliver
- Admin
7:07 pm - March 25, 2008
posts 3909 |
| |
|
It seems that your provider put some limitations around the use of MySQL. You can go into the code and remove the 'DEFAULT CHARSET=utf8' part and see if you can create the tables then.
|
|
|
David M - Guest
10:36 pm - March 25, 2008
|
| |
|
Oliver
Thanks for the advice. I'm hosted with GoDaddy and found some information on their help pages
Some MySQL database features are not enabled on our shared hosting servers. Below is a comprehensive list of disabled features.
- bdb_shared_data
- flush
- have_openssl
- innodb_fast_shutdown
- innodb_log_archive
- locked_in_memory
- log
- log_slave_updates
- log_slow_queries
- log_update
- low_priority_updates
- lower_case_file_system
- myisam_recover_options
- new
- query_cache_wlock_invalidate
- skip_networking
- skip_show_database
I don't know much about this but could the problem be to do with the 'ENGINE=MyISAM' line when creating the database entries
Regards
David
|
|
|
Oliver
- Admin
10:40 pm - March 25, 2008
posts 3909 |
| |
|
You can try removing that part, too. In fact, you could even try to setup the two tables using the GoDaddy MySQL admin interface.
|
|
|
David M - Guest
10:54 pm - March 25, 2008
|
| |
|
Oliver
Looks like you were right all along. I just found the following on a coding forum:
"DEFAULT CHARSET" table option is not supported by MySQL 4.0. You
should try "CHARSET=latin1" or "CHARACTER SET=latin1" instead.
"ENGINE=MyISAM" option supported by MySQL 4.0
Do you think I shouold just ut out the "DEFAULT CHARSET" or replace it as indicated above?
Regards
David
|
|
|
David M - Guest
12:56 am - March 26, 2008
|
| |
|
In case anyone else has this problem I can confirm that I was able to create the databases in MySQL 4.0 by:
Changed PRIMARY KEY (id) ) ENGINE=MyISAM DEFAULT CHARSET=utf8;"; To PRIMARY KEY (id) ) ENGINE=MyISAM;";
and
Changed field_val text) ENGINE=MyISAM DEFAULT CHARSET=utf8;"; To field_val text) ENGINE=MyISAM;";
in the file 'cforms-global-settings.php'
Regards
David
|
|
|
Oliver
- Admin
6:39 am - March 26, 2008
posts 3909 |
| |
|
Sure, that should do the trick. There is little that can go wrong, you can always delete the tables if they don't seem to work afterwards.
|
|