7 replies to this topic

[Dean]

This part of the forum is to request features that you would like to see added to the core of Etomite. Requests may or may not be included in future releases.

When making feature requests, keep in mind that Etomite is a content management system, not a community management system. The idea behind the core of Etomite is to manage basic site content flexibly, powerfully, and well. Therefore, options such as polls, calendars, forums, forms, etc., are not included in the core for that reason. These kinds of things can be included using Snippets and can be written as needed by yourself or, alternatively, you can use snippets written by community members or request a snippet, in the relevant forums.

An example of a core feature request would be to ask that the Manager have a "Save" button at the bottom of the editing page.

Thanks!

[Dean]

We currently are not taking requests for Wishes

[Cris D.]

Not even to add the etomite installation prefix to the system_settings table so that it can be retrieved via the getConfig() API rather than sending a separate db call via $data=$etomite->dbConfig(); $etoPrefix=$data['table_prefix'];
Unless there is another easier way I have overlooked.
[EDIT 15/9/07] There is an easier way...

$GLOBALS['database_server']
$GLOBALS['dbase']
$GLOBALS['database_user']
$GLOBALS['database_prefix']
$GLOBALS['table_prefix']
$GLOBALS['database_password']
$GLOBALS['absolute_base_path']
$GLOBALS['relative_base_path']
$GLOBALS['www_base_path']:

are all available to be accessed directly in the snippet.

Edited by Cris D., 15 September 2007 - 05:22 AM.

[pixelstyle]

I think it's strange that a cms will close their wish list for more than a year. Why would you even do that?

Just tell the users that there is no guarantee that a feature will be implemented. Then, when you've got time for development, read to the list of feature requests and choose the ones you like or the ones that are easy to implement.

I've got a request that's probably very easy to implement:
In the user manager, separate users by role. Then you can see at once who is an admin and who is not in one view. Because admin is the default role and an error in user role can have grave consequences.

[Ralph]

pixelstyle, on Oct 14 2007, 12:02 PM, said:

I think it's strange that a cms will close their wish list for more than a year. Why would you even do that?

Just tell the users that there is no guarantee that a feature will be implemented. Then, when you've got time for development, read to the list of feature requests and choose the ones you like or the ones that are easy to implement.

I've got a request that's probably very easy to implement:
In the user manager, separate users by role. Then you can see at once who is an admin and who is not in one view. Because admin is the default role and an error in user role can have grave consequences.

The reason the wish list is closed is because there will a complete rewrite of Etomite and comparing what you see now to the new version is a moot point... Hence, no need for wishes until you actually see what is coming... We truly already know the short-falls of the existing code base...

[pixelstyle]

Ok, sounds interesting and I can understand your point. Thanks for your reply.

[Cris D.]