pugdog
User
Karma: -0 / +1
Apr 20, 2005, 9:38 AM
Post #6 of 6
(10975 views)
Shortcut
Send pugdog a wink
|
|
Re: [loxly] Blogging Software for GT setups
[In reply to]
|
Can't Post
|
|
<G> we do think alike
I may be missing something, but I don't understand why blogs need to ping other blogs? (I know this is a standard blog feature, just don't know why?)
I don't either!!
It's cool, it's funky, it's spamish, it's really, really, confusing and cluttering, and unless you are part of an organized news network, it's really, really wasteful, and pointless, IMHO.
But that's another story :) I just posted an update to the Comments thread, and I really, truly do hope to have that released this week, along with the Search_Logger update, and a few other things.
I hope to have the blogger in it's first incarnation released within 2-3 weeks. It's really just a major modification of the comments plugin.
This first release, and the "lite" version will be an add-on to an existing Links SQL installation. I'd *love* to make it a community add on, but there are issues with that at the moment, that hopefully will eventually be addressed.
Any Links SQL user (who is granted permission) can set up a "blog". It's sort of like a home page. The actual mechanics of that are still being firmed up, as I try to deal with quirks.
But, they will request (or be granted permission if allowed -- this is a pluggable option, so an admin can set up requirements -- such as 100 karma points before allowing it to open. You have to write that, but you can use that to set a users "blog_allowed" field) to set up a blog. Once set up, the system will create the necessary key entries, and set up a "homedir" on the server for the user. I am looking at making this both public and private -- eg: like Links, serve images from the private non-web area, or have them in the www/html tree.
The problem I can't reconcile is how to break up the users in the MySQL database. One huge table seems like it's asking for problems, and one-table-per-user is a file-system disaster. Maybe key it to the first letter of the username??? 26 tables is a lot better than 1000's, and probably much better than 1.
Anyway, the system creates the blog entry, which is the top-level description for the blog. It has public and private fields (such as where data is stored) as well as user preferences, and such.
The blogger script first looks at that to display the home page, or index entry. If that's all a request needs, that's as far as it goes.
If more data is needed, either the script or the template will fetch the required data to fill in the blanks.
A blog owner can "post" to their blog, and posts are entered (hopefully in a flexible manner). Topically or by date.
Visitors can read the posts, and if logged in, comment, rate, review, or otherwise feedback on them.
To my mind, this is all a blog is. it's a stripped down CMS. The more features you add, the more bloated it becomes, and the less of a blog and more of a CMS it becomes.
The "pro" version, will use a modified version of Links SQL, and Links table will be the "blog entry" table. But, it might not be necessary to do that, if this first version works right. (and if GT moves the core engine code into a shared library, then I can potentially hook it up to community).
This is something I've wanted for a long time, but finally had the push to do.
There are about 6 related plugins I've been working on that are coming together in this, as well as about a dozen of our already written ones that need to be rewritten and integrated.
I have so much work.... but I think it will be worth it. I have about 40 sites that could use it, and that alone is probably enough of a "market" even if no one else is interested <G>
|
MAIN
SEARCH
WHO'S 
LOG