kanngard

As I suspected. Thanks Beel!

I have decided to drop the development of the dbfiles plugin, since WordPress 2.0 handles file uploads smoothly with meta data and such. If anyone is interested in developing it further, please let me know. The latest source can be found in the Subversion repository:
https://svn.wp-plugins.org/dbfile/

Viper007Bond: I agree, it puts a lot of load on the server, and not all hosts (mine for instance) allow big databases.

Revision 3654 adds a working db_file::listPostFileLinks(), that can be used to retrieve files related to the current post. In a previous revision, I added the ability to relate a dbfile to a post by simply entering the postID when uploading a file. A better UI will be created soon ?? Note that for now, it’s only possible to have one to many relation between posts and file (it’s not possible to relate to the same file from more than one post).

Changes in revision 3537 in the repository (https://svn.wp-plugins.org/dbfile/):
* Added Requirements in readme.txt.
* Install/enabling the plugin now checks if the files table exists before trying to create it.
* SQL changed to be MySQL 4.0x compatible.
* More user friendly maximum upload size error message.

Whenever you find new bugs or have requests for enhancement, please report them to:
https://dev.wp-plugins.org/report/1

FYI: version 1.0 of dbfile is now under Subversion control at:
https://svn.wp-plugins.org/dbfile/

Arlo, I have no plans on doing a meta-data only version of my plugin at the moment. But if the interest is high enough, perhaps there are others who will pursue the matter?

I got my first support mail today. A user running MySQL 4.0.22-standard got an error message when activating the plugin. This is because the SQL used is for 4.1. A workaround that works is to change the dbfile.inc file at row 399 to 409. Change them from:

$sql = “CREATE TABLE ".$table_prefix."files (
id int(11) NOT NULL auto_increment,
name text,
mimeType varchar(30) default NULL,
content blob NOT NULL,
description text,
created datetime NOT NULL default ‘0000-00-00 00:00:00’,
modified timestamp NULL default NULL on update CURRENT_TIMESTAMP,
UNIQUE KEY id (id),
FULLTEXT KEY name (name,description)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 AUTO_INCREMENT=34 ;”;

to:

$sql = “CREATE TABLE ".$table_prefix."files (
id int(11) NOT NULL auto_increment,
name text,
mimeType varchar(30) default NULL,
content blob NOT NULL,
description text,
created datetime NOT NULL default ‘0000-00-00 00:00:00’,
modified timestamp NULL default NULL,
UNIQUE KEY id (id),
FULLTEXT KEY name (name,description)
) TYPE=MyISAM AUTO_INCREMENT=46 ;”;

The diff reads as this:
406c406
< modified timestamp NULL default NULL on update CURRENT_TIMESTAMP,
—
> modified timestamp NULL default NULL,
409c409
< ) ENGINE=MyISAM DEFAULT CHARSET=utf8 AUTO_INCREMENT=34 ;”;
—
> ) TYPE=MyISAM AUTO_INCREMENT=46 ;”;

A better explanation perhaps: if you would like to add a downloadable ZIP-file to a post, you do like this:
* Open “Manage”, “Add Database File”
* Upload the ZIP
* In “Manage”, “Database Files”, right click “View” and select “Copy Link Location”
* Create the post
* Click on the link Quicktag and paste the URL you copied

And for your other question, absolutely. Handling meta data for normal files could be handled, but it’s not anything I am interested in for now.

For now, you have to manually add the URL to the file in for instance an img tag. I will add a tag(s) allowing you to getdb’d files per post or by file id or file name.

I forgot to add the following information in the readme.txt file. It will be added in the next release:

Server side tested with:
Windows XP SP2
Apache httpd 2.0.54
PHP 5.0.4
MySQL 4.1.11-nt
Wordpress 1.5.1.3

graemep: one downside is that the database will grow as you add files.
My plugin does NOT intercept normal file reads/writes, so you could have a combination of both. The actual downloading takes place outside of the plugin architecture, so it will not mess up wp-cache. But perhaps some sort of caching mechanism could be interesting to add in the future. Mind that the current release is my first PHP, MySQL and WordPress project ever, and I’m sure there are several things that could be added ??

I come from the Lotus Domino world. A Domino database consists of everything from the layout of the pages, to “records” of data and files (as attachments). With those databases, I can simply replicate complete applications in just one file. My question is, why would someone like to store images on the filesystem? ??
My idea with dbfiles, is that the files that belong to posts will go into the database. That can be images, code source, archives etc. The normal site images (for themes) etc, would not be e candidate to put in the database.

Thank you! Repost of the files can be found at https://dev.kanngard.net/Permalinks/ID_20050719100140.html

– Johan

Chen, the download is timing out after about 300KB for me (your homepage is slow too). Is it possible for you to repost the file somewhere? If you want, I could add it to my site, if you send it by email…

– Johan
johan@kanngard.net
https://dev.kanngard.net