cms

UABgrid Development using Eclipse IDE

1.)Prerequisites to download:

With YaST use search keywords apache, php5, and mysql, tomcat, phpMyAdmin (individually), install the following packages:

Apache
*apache2
*apache2-doc
*apache2-prefork

PHP5
*php5
*php5-gd
*php5-ldap
*php5-mysql
*php5-openssl
*php5-pear
*php5-session
*php5-zlib

MySQL
*mysql
*mysql-client
*mysql-shared

Tomcat
*latest Tomcat 4.1.x release

phpMyAdmin
*phpmyadmin

From the web, make sure to install:

Drupal

starting phpwebsite:

mysqladmin -u root -p create itacwebdb

mysql -u root -p
mysql> GRANT ALL PRIVILEGES ON itacwebdb.* TO itacwebdba@localhost
IDENTIFIED BY 'somedecentpassword';
mysql> SET PASSWORD FOR admin@localhost=OLD_PASSWORD('thepassword');
mysql> exit

[the database administrator password must be stored in hash format for V3 mysql libraries -- may need to use this if accessed by PHP4 libraries. ]

Some of the PHP debug functions like debug_print_backtrace are only supported in PHP 5 which is not the PHP version with our current configuration. However, Some of other debug functions like debug_backtace, error_log etc are supported in PHP 4.3.0 and above and these functions work with the present configuration setting of PHP and Apache server.

The problem with display in Limbo was, in the config.php file we have to set the URL as https:// instead of http://
the reason being, after index.php is loaded, the requests for certain images to be displayed will be sent to pubcookie server and since Pubcookie requires authentication these requests will not be valid and gets rejected.

also in your .htaccess files you have to add

PubcookieAppID username or anyname

pubcookie application ID is used to give a common cookie name which changes with the directory path.
for more information refer http://pubcookie.org

In the registerExtAuth() function $conn->Execute("INSERT INTO #__users (name,username,email,password,registerDate) VALUES('".dbencode($username)."','".dbencode($username)."','','','$time')" );

There is a plethora of CMS available, I found phpCMS, Guppy and CathDesign CMS to be ideal for our requirements,

http://www.phpcms.de/index.en.html

http://www.freeguppy.org/

http://cms.cathdesign.nl/

here is a link comparing the above three CMS

http://www.opensourcecms.com/index.php?option=com_wrapper&Itemid=139

Based on comparisons Guppy or phpCMS looks good to test (actually guppy has more security features)
but unfortunately guppy is not available in english, it is available in spanish, german, russian, italian languages !!

I will try phpCMS to begin with...

Thanks,

Is this interface still functioning?

there are a ton of elements that make up a good site. the main pages (drupal, phpwebsite), special function services like documentation (latex2html), faq (phpMyFAQ), images (gallery), file store (read-only via apache, read-write via zope or webdav), search, maillist, the list goes on.

it's clear for this little list that in order for the user experience to be uniform across the applications there needs to be a common definition of users, groups for identities and authorizations.

this is nothing new, really. it is worth being explicit about it, though. that helps bring these elements to the fore front of the system. knowing what they are and how they can be accessed within the system.

[phpwiki]
review how to deal with lab-subscribed groups by individuals

a few problems with this: I want a forum block to tie in specific forum to
a project page; don't seem to be able to restrict no comments on such
forums to prevent responses (or posts) from anyone but the gateway, eg.
must post to mailling list not forum; would be nice to just have a web
interface to news groups, eg. don't delete the messages out of a backend
subscribers folder. don't take them to the web, show them on the web.

Had a thought of the nature of various items we need to catagorize in our collaborations.

* A task is the generic unit of work we need to track.
* A todo item is a task that is on the wait queue.
* A bug is a type of task, it reflects the task's origin not its fundamental characteristcs. In some sense a bug is a task deferred: the task was skipped/forgotten while coding and must now be attended to.
* A wishlist/feature request is request to create a task. it might share the structure of a task but is inherently ambigous and might be further broken in to other tasks.