To Do List > Talk

We are using MySQL's FULL-TEXT index for this search, which makes for a very efficient search with the ability to show relevancy...

• I'd like to search to place a higher importance on the `title` of the file.

More information here

http://www.xmlrpc.com/weblogsCom

When To Ping

Initially, my thoughts were that the ping would be done when a file is Posted (this happens when a file is first created, and can be done again manually to an older file via Options).. however, file creation in WikyBlog is closer to wiki's than blogs in that anyone can create new files... The problem here being we wouldn't want to ping a service if a random user created a meaningless file.

To just get the ATOM feed going, someone just needs to copy the rss feed script and change the arrangement so it fits the ATOM format... I'd already worked on it a bit, but was unable to get it to verify at http://feedvalidator.org

So my thought for interbliki are a little different that what someone who is familiar with interwiki links might expect... and well, might not be a good idea at all because of security, but here goes..

InterBliki links would be links to other sites that could be loaded via AJAX and added to the users current document.

I really like this idea, but my biggest concern is security.. In no way should we store uploaded php files in a folder! This is going to require another table in the database and an efficient way of serving these files stored in the database.

You could use some of the zipping libraries and just zip all attachments upon uploading. Dump the zip files into a folder with a unique ID as their file name and when someone requests that file, the backend would send them a zip file... The option to include passwords on the zip files could always be used as well.

The `flag` field in the `all_files` is a set including the value "redirect"..

What we need is a way to set this flag to "redirect" and we need a way to know where the redirection is going. I'm thinking this is going to result in a database modification of some sort. Do we need another field in the table to store the permaLink? It could then be used for other things.. we could implement a "duplicate entry" flag...

The plugin system is currently in Beta, so it works but will be going through some changes... What's needed most is work on the plugin management scripts (installing/updating/removing of plugins).

The biggest problem I see with the implementation, is that so much depends on the folder name of the plugin. A folder name of /skeleton means the url of all skeletons will begin with "/skeleton"... the wiki will look for a $lang['skeleton'] value... the class in /skeleton/class.php has to be "class skeleton"...

LOL. I feel funny suggesting this but you could actually add a "To-do" feature to your WikyBlog... I am suggesting this feature after getting inspired by Pimki. It's a Wiki-based PIM. Get more details here.

Yeah, I was thinking the same thing.. It's not a big priority for me at the moment though, maybe a little down the road. Main 16:34, Aug 17, 2006

Yep, seems better suited for a PIM anyway. I don't think it's a necessary feature for a blog+wiki. If you wanted a To-do list, you could simply have a Wiki page dedicated for that. -- King