[geeklog-devel] Improvement of Installation GUI

[Abhishek Shrivastava]

Hello Dirk,

While installing other CMS like Joomla, I didnt have to do any
shifting/moving stuff like in Geeklog. It would be better if we can
make it more user-friendly. For now, I'd suggest we can skip that part
in which the user has to input the path of "db-config.php". In cases,
where GL is not able to detect that file, this step can give
non-experienced users a headache. So what we can do is to complete the
installation of GL without having to move the public_html folder and
remaining contents anywhere,so that that step can be avoided(bcoz GL
already knows where db-config is!). This is just a suggestion, I'd
like to get your feedback on this (any bad points about doing this?)

Anyways, this is obviously not enough for my GSOC work, it will take
hardly few days. I went through your ideas page list and I have
decided I can work with the "Improvement of Configuration GUI" idea.
Its actually a very good idea and GL will benefit a lot from it.
However, there are few things I want to discuss about each topic :

1) More Fine Grained Access Control
This is a nice idea but there's something that needs to be tackled
first. Suppose I'm a user with permission to create stories and I have
been given access to configurations related to Stories, and there's
another such user like me who changes the common "stories"
configuration to meet his own story needs. This change by the second
user will affect me also and vice-versa as they are indeed "common"
story settings. This is an embarassing situation!

This can be fixed by splitting the "Core" configuration into groups
like "Stories","Polls", etc. and then each group can have different
values for each "admin" user. This can be further optimized by
associating every story_id(uid) or poll_id(pid) etc with a config_id
(cid -> the id of a group of a particular configuration set). This
would require a complete overhaul(or may b a rewrite?) of
config.class.php with lots of added functionalities.

I'd talk about the other topics in this idea in next few mails, for
now I'd love your feedbacks please...

Regards,
Abhishek.


On 3/26/10, Dirk Haun <dirk at haun-online.de> wrote:
> Abhishek Shrivastava wrote:
>
>>Can someone please give me a brief idea about why exactly do I need to
>>separate public_html folder and other contents in separate directories
>>during installation ??
>
> Actually, you do not need to do that. The Geeklog tarball is layed out
> like we recommend Geeklog to be installed on your server, with
> public_html being your webroot directory (it's sometimes called that, or
> "htdocs", or "wwwroot", or similar).
>
> So in most setups, you wouldn't need to move things around at all. And
> if you keep the same basic layout (even when your webroot is called,
> say, "htdocs"), the installer will find things just fine.
>
> I'm probably biased, but is that really such an unusual setup?
>
>
>>To be frank, I really think there is a much scope of improvement.
>
> The above issue alone wouldn't be enough for a GSoC project anyway. So
> what else did you have in mind?
>
> bye, Dirk
>
>
> --
> http://www.geeklog.net/
> http://geeklog.info/
>
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>