This plugin suddenly expanded, and I'm going to have to make changes to the database structure. It shouldn't affect any import, but "special" features, if any, may not work, or will have to be reenabled.

The database structure, with only a little change, can be used to set up any sort of list.

The admin can configure a database with fields of any sort, which can be a list for a user.

For example, rather than hard-coding the FavLinks table in, make it flexible, and set up several tables.

That way it can be used for a wish list, a contact list, an address book, a fav links, or anything else.

There are a few ways to do this, and I'm not sure which one I'm going to do. I'm not sure which is more flexible, and logical to code.

One way is to actually create separate lists, and manage them.

Or, to make one list manager, but use a "category" type structure.

Which I pick has more to do with coding ease, than anything else, since I want to get this out ASAP.

Actually, what might happen, is I'll finish this plugin as is, leaving it as a dedicated MyFavLinks and get it out, then create a more flexible version, later.

The "wishlist" feature would be much more valuable for sales sites, books, videos, etc.


PUGDOG� Enterprises, Inc.

The best way to contact me is to NOT use Email.
Please leave a PM here.