Suggestions

[hazer]

(1) The initial account should be a "master admin" type account. It should have the ability to override the settings of any blog on the system.

(2) Every time a new person registers, it takes over the homepage. If someone doesn't know your blog ID they can't get to it unless someone links it on the side. If there's more than one blog on the system the home page should probably be a "directory of blogs" on the system.

(3) Once item 1 is in place, there should be a way to manage users signing up. By default ANYONE can sign up if they know about register.php. If I don't want to let anyone sign up, I have to move the file. If I want to let people ask for blog space, I have to find some external method ATM. The registration process should allow for open reg, closed reg or admin approved reg.

I know these 3 are major items. I'm probably listing things that are already on the road map pending a bug shakedown of the current build.

Everything else is working great so far. I'm very happy with the project and will hopefully have a few hacks/plugins to contribute later.

[phunkphorce]

Hi!

Let's see...

(1) The initial account should be a "master admin" type account. It should have the ability to override the settings of any blog on the system.

That's pending for a 0.1.1 or 0.2 release. There will be some kind of user permissions/user groups so that some special users with "Administrator" permissions can do things like that. It won't be anything too complex but powerful enough, because pLog is a blogging software and not CMS

(2) Every time a new person registers, it takes over the homepage. If someone doesn't know your blog ID they can't get to it unless someone links it on the side. If there's more than one blog on the system the home page should probably be a "directory of blogs" on the system.

Have you tried the summary.php script? It shows a list of the most recent posts in every blog, as well as by default a list with all the blogs registered. It is also based on templates so it is easy to customize. Check it out and let me know if that's what you were looking for.

(3) Once item 1 is in place, there should be a way to manage users signing up. By default ANYONE can sign up if they know about register.php. If I don't want to let anyone sign up, I have to move the file.

I know the system works in a pretty rudimentary way at the moment, but in the end of the installation wizard, it clearly states that you should remove register.php if you don't want to allow public registrations.

If I want to let people ask for blog space, I have to find some external method ATM. The registration process should allow for open reg, closed reg or admin approved reg.

What do you mean by "open reg" and "closed reg". What would be the difference?

I know these 3 are major items. I'm probably listing things that are already on the road map pending a bug shakedown of the current build.

There won't be new features in the 0.1 final version. The RC is just to iron out some of the bugs that haven't been noticed so far. The thing with user permissions and so on has been planned for next release... hopefully

Everything else is working great so far. I'm very happy with the project and will hopefully have a few hacks/plugins to contribute later.

Great! I'm looking forward to seeing them

Oh, and thanks for your feedback!!!

[hazer]

Open Reg: Registration is open to anyone that can click on the link

Closed Reg: No new registrations allowed.

Admin Approved Reg: You can register, but before the blog is made the Admin has to approve it (basically you apply for a blog, and then it's created by an admin later)


And just out of curiousity, shouldn't the summary.php be the main page (ie: index.php)? If it's the page that's doing the summary listings it should be the main site page...

[School]

Ya, I find that i have to change the codec of summary.php...
And I suggest that you can make two environment, one is for admin and the other for blog users, which make the interface more comfortable for users and give them to upload templates ( Yes, upload or online editing, or other ways to give them choices of cusumize their blog. )
It is quite hard to do, or may need a rewrite of admin class, but it is worth to make it as a multiple independent blog system that don't require admin to serve users.

Another thing that can be added, is the function of multiple users to have abity to add posts to one blog. It is already done by other php blog software, it is very good to introduce with the next release. But it also require some major changes of database as well as source code, but I think is is in priority with the account system.

[phunkphorce]

Let's see...

Ya, I find that i have to change the codec of summary.php...

If what you really need is to make summary.php the main page, we have two options: one of them is hack index.php so that it detects if it's been configured as the main page or not and acts accordingly, and the other is to use Apache itself to use another file as the index file.

The mod_dir (http://httpd.apache.org/docs/mod/mod_dir.html) module for Apache (compiled by default, methinks) allows to set another file other than index.html. In our case, we could tell Apache to fetch first summary.php as default instead of index.php if we'd like to show the summary page as the main page. This directive can be specified in an .htaccess file and its content would be something like:

Code: Select all

DirectoryIndex summary.php index.php

This should work and I am sure that any reliable web service provider allows to use .htaccess files to change some of the Apache default behaviours.

And I suggest that you can make two environment, one is for admin and the other for blog users, which make the interface more comfortable for users and give them to upload templates ( Yes, upload or online editing, or other ways to give them choices of cusumize their blog. )

I have already been working on this, but I don't quite see your idea. What I've done so far is that you get the same admin menu, but if you have additional administrative permissions, then you get an additional option where you can add/edit/remove users and blogs, see more detailed statistics of the site and tweak the configuration options (which btw, will be eventually moved to the db)

As soon as I get that somehow working I'll start releasing testing snapshots (much like the old plog-devel-xxx releases) so that people insterested in those features can start testing.

Another thing that can be added, is the function of multiple users to have abity to add posts to one blog. It is already done by other php blog software, it is very good to introduce with the next release. But it also require some major changes of database as well as source code, but I think is is in priority with the account system.

This is already there, but there is unfortunately no clear interface to "invite" or "add" new users to an existing blog. You can add existing users to your blog with just an SQL command... Now we just need to make that possible from within the admin interface Give me sometime, I have already thrown some code for that and it'll be there for the next release.

Regards,

Oscar.

[School]

Sorry, I haven't go through the whole source codes so I don't know which features is there and which feature is not....