{5} Assigned, Active Tickets by Owner (Full Description) (12 matches)

Omega fails if we do use another auxprop plugin but sasldb (and therefore the sasldb files do not exist) because "ispcp-mbox-mngr" alsways tries to update user/pw data through "sasldb_passwd".

There should be an option to disable the sasdlb method for those who do use another auxprop plugin.

Currently VHCS Omega uses a single flat file for the virtual hosts (/etc/apache2/sites-enabled/vhcs2.conf)

Wouldnt it be better to use individual configuration files for each domain. The apache2 configuration file pattern is designed like that.This way we can individually enable or disable a domain (suspending!) by the commands readily available within apache2 .

As an example. If we have a domain name example.com a config file for it will be created like /etc/apache2/sites-available/example.com.conf and once the status of this domain is OK ,a soft link for the file will be created

/etc/apache2/sites-enabled/example.com.conf

This way it is a lot easier to manage the individual configurations rather than dealing with a bulky flat file.

This method is used by the Interworx control panel,and i guess it is much better than a flat file

Having a lok at the problem from here http://www.isp-control.net/forum/errors-after-update-to-latest-trunk-t-766.html I realized that the handling of the mysql selects and results is not very friendly for extensions. Example: add a new column to the domain table, eg. "myflag" defaulting to "no". Now add a new domain/user - in (apache)ispcp.conf and the zonefile of the new domain there will be "no" instead of the IP address. The reason: in ispcp-dmn-mngr (function dmn_mngr_engine) there is a mysql select and the handling of the result (picked out some commands in order):

$sql = "select t1.*, t2.ip_number from domain as t1, server_ips as t2 where ..."
($rs, $rows) = doSQL($sql);
my $entry = @$rows[0];
$rs = dmn_add_data($entry);
# in "dmn_add_data" the argument is given over to other functions
# also to dmn_add_named_db_data:
my ($dmn_data) = @_;
my $dmn_ip = @$dmn_data[21];

ok - the 21st field/column of the first result row is the IP address... not in our case with the new field....!

This really should be changed/improved. You never can rely on the order or the number of columns in a table (at least not if there is no check done if the order and numer still is as assumed) - a very basic database rule..

I put it to release 1.1 - for 1.0 we can write something about not extending the tables but as soon as there are people who want to extend ispcp this will be a bigger problem.

I feel that this "Overview" page could be much more helpful. When i first login as a system administrator, i would like to see a snapshot of whats going on in the system. A lot of things could be helpful here:

-Total users logged into ispcp -# active ftp connections -# active ssh connections -summary of disk usage across the mountpoints -overall server status (like teh serverstatus screen, but only show things that are down). -notification if there are new support tickets that I need to respond to -current ispcp maintenance status (online, maintenance, etc) -some icon to notify if there is a new version of ispCP available -an icon to signify that there are some system errors that need to be addressed (link to ispcp_debugger.php) -if possible try to exact out the status of the last rootkit log, and display a warning message/icon if it found something...

There are a lot of options for what could go on this screen, but i really do think it would be helpful to make it more than just a list of how many of each type of item is in the database. I know this list is long but maybe some of the easier items could be added to the screen for 1.0.0, then work on the others in the future...

Protected areas are not working correctly. If I create some users and try to add them to a protected area (with CTRL- or Shift-Key) only the first user is added. In both, the htaccess- and the htpasswd-file, there is only this one user. I also recognized that sometimes deleted users and groups are left in the htpasswd- and htgroup-file.

php cleanup is in work please be patient

24.04.2008 50 % done