New plugin avaiable, dbfile

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

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

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.

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).

My question is, why would someone like to store images on the filesystem? ??

Umm, because it puts a massive load on the db server as well as the web servers?

A file system is just that – a system for storing files.

But whatever floats your boat.

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.

“I have decided to drop the development of the dbfiles plugin, since WordPress 2.0 handles file uploads smoothly with meta data and such”

I’m sorry to read this (but I understand that there are better things to do in life than maintaining old plugins…).

The file system based access control (usually apache rw-) does not allow one to keep members-only files available for download. This db_files combined with “page restriction” would have been a good and reasonably safe solution. Unfortunately, initial configuration fails due to some bug…

Some people really don’t want more readers.