webcollab-users — Mailing list for WebCollab users

[Webcollab-users] Survey as part of my bachelor thesis on the topic of "Diffusion rate of OS business software"

[Rezan K. <rez...@sm...>]

Hello everybody,

in the moment i am writing my bachelor thesis on the topic "Diffusion  
rate of open source business software".

I want to ask you (the Community) who is using and/or supporting the  
Software "WebCollab", if you would conduct the quick survey based on  
the software "WebCollab".

Under the following link, you can start with these:  
https://www.umfrageonline.com/s/8b5eeb1

I would be very grateful, if you could take the time and conduct the survey.

Best regards
(Mrs)
Rezan Kedik

[Webcollab-users] Survey as part of my bachelor thesis on the topic of "Diffusion rate of OS business software"

[Rezan K. <rez...@sm...>]

Hello everybody,

in the moment i am writing my bachelor thesis on the topic "Diffusion  
rate of open source business software".

I want to ask you (the Community) who is using and/or supporting the  
Software "WebCollab", if you would conduct the quick survey based on  
the software "WebCollab".

Under the following link, you can start with these:  
https://www.umfrageonline.com/s/54e5d89

I would be very grateful, if you could take the time and conduct the survey.

Best regards
(Mrs)
Rezan Kedik

[Webcollab-users] WebCollab 3.40 Released

[Andrew S. <and...@pa...>]

Hello all,

I am pleased to announce the release of WebCollab 3.40 (Glenorchy).

This is a bug fix and general upgrade version.

Password security has been improved with new passwords being encrypted with the Blowfish algorithm.
Existing passwords will not be changed until the password is manually changed.  Note that this is
only applicable to versions of PHP 5.3.7 (or higher); since earlier versions of PHP have a buggy
implementation of the Blowfish algorithm.

Uploaded files are now stored with random hash id's instead of the file name.  This increases
security and solves potential problems with non-ascii filenames in filesystems.  Again, this only
applies to new uploaded files, and the code is still backwardly compatible with existing uploaded
files.

The Italian language translation has been updated.

Note that a database upgrade is necessary for earlier versions to implement the new hashed uploaded
file names.

Enjoy!

Andrew Simpson

[Webcollab-users] Webcollab 3.31 Released

[Andrew S. <and...@pa...>]

Hello all,

I am pleased to announce the release of WebCollab 3.31 (Baldy).

This is a bug and security fix version with two changes.

Internet Security Auditors have found a HTTP Response Splitting Vulnerability in the 'help' files
(CVE-2013-2652). This vulnerability would appear to have been present since the first released
version of WebCollab, and is not considered to be high impact.  Nevertheless, all users are
recommended to upgrade. 

As an alternative to upgrading, add the file '[webcollab]/help/help_language.php' from this release
to any earlier release, overwriting the existing file of the same name.

A bug in setting passwords with PHP 5.5+ has been fixed.  An internal function shared a common name
with a new reserved function in PHP 5.5.

I am aware that WebCollab is often vetted and inspected by various organisations looking for
security issues.  However, in over 10 years of WebCollab releases this is only the second time that
a security vulnerability has been reported.

Enjoy!

Andrew

[Webcollab-users] WebCollab 3.30 Released

[Andrew S. <and...@pa...>]

Hello all,

I am pleased to announce the release of WebCollab 3.30 (Aotuhia).  The release was made a few days
ago and seems to have raised no issues.

This version has bugfixes and a minor feature improvement in reparenting.  

Password encryption internally has been changed from MD5 (now considered weak) to either MD5, or
SHA256 encryption. SHA256 is preferred and will be used with versions of PHP 5.3.2, and higher.

There is provision in the code for the blowfish algorithm, but this has not been enabled for
general use, mainly because blowfish in PHP prior to 5.3.8 is reportedly buggy (PHP Manual).  

Password re-encryption for existing installations will occur as users change their passwords, or
new users are created.

Active Directory authentication has been added.  This is considered experimental.  Please file bug
reports as necessary.

Note that for upgrades, setup.php must be run to add and write the small change in the config
file.  See Release Notes for more details.

Enjoy!

Andrew Simpson

[Webcollab-users] WebCollab 3.21 Released

[Andrew S. <and...@pa...>]

Hello all,

I am pleased to announce the release of WebCollab 3.21 (Kaitake):

This version has principally bugfixes of a minor nature as the 3.00 series becomes stabilised. 

Note that in versions 3.00 and 3.10, when a task/project was deleted the uploaded files were not 
physically deleted from the server due to a coding bug.  This was unlike all other versions of 
WebCollab where uploaded files are physically deleted with projects/tasks.  This bug is now fixed, 
and files will be deleted when the task/project is deleted.   

This version 3.21 is a re-release of version 3.20 with WebCollab Bug #3535626 fixed.  This was in
fact not a WebCollab bug, but a database bug present in some versions of PHP.        

Enjoy!

Andrew Simpson 

Re: [Webcollab-users] 3.00 - Tasks not being updated with current date upon completion

[Justin W. <jw...@at...>]

Andrew,

Confirmed, this fixes the bug.  Thanks very much for taking the time to fix this and update git.  

-Justin Winschief

-----Original Message-----
From: Andrew Simpson [mailto:and...@co...] 
Sent: Wednesday, February 29, 2012 11:49 PM
To: web...@li...
Subject: Re: [Webcollab-users] 3.00 - Tasks not being updated with current date upon completion

On Tue, 28 Feb 2012 17:09:38 -0600
Justin Winschief <jw...@at...> wrote:

> Hi Andrew and webcollab users,
> 
> After upgrading to 3.00 recently, we noticed that tasks are not being 
> updated with the current date when they are marked as completed - 
> instead, any task we close seems to have finished_time left set to the same value as created.  Looks like this field is set upon task creation but is no
> longer being updated upon completion.   This might not be a big problem for most users, but we
> wrote some PHP "status" pages for management to track recently-completed tasks/projects, and this
> breaks that.  I verified this is happening in the database and is not just a display issue.   I
> had included some SQL output here but removed it since this should be easy enough to verify.
> 
> The "edited" and "status" columns are being updated but 
> 'finished_time' is not.  The task's webpage shows the same data.  
> Looking at the database documentation I actually don't see 
> finished_time in the list of fields so I'm hoping you haven't removed 
> this for some reason.  I ran some queries and was able to verify that, since our upgrade to 3.00, no tasks have had this field modified.  This is the case for both new and old tasks.
> 
> I tested a bit on the online demo page and it seems to happen there too.   Wondering if you have
> any ideas for a quick fix and if you can reproduce this behavior, as it seems to be new to
> 3.00.   Thanks very much for the help and the great software =)
> 
> -Justin
> 

Justin,

The problem with doing big database engine rewrites is that things get broken. Hopefully this is the last (or nearly last) of the little database bugs.

If you can grab the file webcollab/tasks/task_submit_update.php from the Git Repository, this bug should be fixed now.

Andrew

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Webcollab-users mailing list
Web...@li...
https://lists.sourceforge.net/lists/listinfo/webcollab-users

Re: [Webcollab-users] 3.00 - Tasks not being updated with current date upon completion

[Andrew S. <and...@co...>]

On Tue, 28 Feb 2012 17:09:38 -0600
Justin Winschief <jw...@at...> wrote:

> Hi Andrew and webcollab users,
> 
> After upgrading to 3.00 recently, we noticed that tasks are not being updated with the current
> date when they are marked as completed - instead, any task we close seems to have finished_time
> left set to the same value as created.  Looks like this field is set upon task creation but is no
> longer being updated upon completion.   This might not be a big problem for most users, but we
> wrote some PHP "status" pages for management to track recently-completed tasks/projects, and this
> breaks that.  I verified this is happening in the database and is not just a display issue.   I
> had included some SQL output here but removed it since this should be easy enough to verify.
> 
> The "edited" and "status" columns are being updated but 'finished_time' is not.  The task's
> webpage shows the same data.  Looking at the database documentation I actually don't see
> finished_time in the list of fields so I'm hoping you haven't removed this for some reason.  I
> ran some queries and was able to verify that, since our upgrade to 3.00, no tasks have had this
> field modified.  This is the case for both new and old tasks.
> 
> I tested a bit on the online demo page and it seems to happen there too.   Wondering if you have
> any ideas for a quick fix and if you can reproduce this behavior, as it seems to be new to
> 3.00.   Thanks very much for the help and the great software =)
> 
> -Justin
> 

Justin,

The problem with doing big database engine rewrites is that things get broken. Hopefully this is
the last (or nearly last) of the little database bugs.

If you can grab the file webcollab/tasks/task_submit_update.php from the Git Repository, this bug
should be fixed now.

Andrew

[Webcollab-users] 3.00 - Tasks not being updated with current date upon completion

[Justin W. <jw...@at...>]

Hi Andrew and webcollab users,

After upgrading to 3.00 recently, we noticed that tasks are not being updated with the current date when they are marked as completed - instead, any task we close seems to have finished_time left set to the same value as created.  Looks like this field is set upon task creation but is no longer being updated upon completion.   This might not be a big problem for most users, but we wrote some PHP "status" pages for management to track recently-completed tasks/projects, and this breaks that.  I verified this is happening in the database and is not just a display issue.   I had included some SQL output here but removed it since this should be easy enough to verify.

The "edited" and "status" columns are being updated but 'finished_time' is not.  The task's webpage shows the same data.  Looking at the database documentation I actually don't see finished_time in the list of fields so I'm hoping you haven't removed this for some reason.  I ran some queries and was able to verify that, since our upgrade to 3.00, no tasks have had this field modified.  This is the case for both new and old tasks.

I tested a bit on the online demo page and it seems to happen there too.   Wondering if you have any ideas for a quick fix and if you can reproduce this behavior, as it seems to be new to 3.00.   Thanks very much for the help and the great software =)

-Justin

Re: [Webcollab-users] Active Directory Authentication

[Andrew S. <and...@co...>]

On Sat, 25 Feb 2012 20:44:10 +1300
Andrew Simpson <and...@co...> wrote:

> On Fri, 24 Feb 2012 04:29:15 -0800 (PST)
> jamesoaustin <au...@wr...> wrote:
> 
> > 
> > Is there any progress on this? I am in the same boat as far as management
> > goes!
> > 
> > Thanks!
> > 
> 
> It's slipped my memory completely.  I'll have another look at it.  Active Directory looks to be
> easy to implement, it's just that I have no hardware set up to test it on.
> 
> Andrew
> 

O.K, I have cobbled together a patch here:

https://sourceforge.net/tracker/?func=detail&aid=3495224&group_id=75945&atid=545543

This file replaces the index.php in the main directory and includes code for Active Directory
authentication.  It is experimental, because I don't have Active Directory on my hardware,
so I can't test it.  Testing and improvements by those that do would be welcomed....

I have also taken the opportunity to refactor the code for index.php, and will incorporate this
into the main code base soon.

Andrew

Re: [Webcollab-users] Active Directory Authentication

[Andrew S. <and...@co...>]

On Fri, 24 Feb 2012 04:29:15 -0800 (PST)
jamesoaustin <au...@wr...> wrote:

> 
> Is there any progress on this? I am in the same boat as far as management
> goes!
> 
> Thanks!
> 

It's slipped my memory completely.  I'll have another look at it.  Active Directory looks to be
easy to implement, it's just that I have no hardware set up to test it on.

Andrew

Re: [Webcollab-users] Active Directory Authentication

[jamesoaustin <au...@wr...>]

Is there any progress on this? I am in the same boat as far as management
goes!

Thanks!



-- 
View this message in context: http://old.nabble.com/Active-Directory-Authentication-tp31014643p33384678.html
Sent from the webcollab-users mailing list archive at Nabble.com.

[Webcollab-users] unsubscribe

[Brian B. <bb...@ap...>]

 

 

-- Brian              1.847.278.2100 ext 120

 

Re: [Webcollab-users] unable to connect to database after installation webcollab 3.00

[Bhuvan K. <bh...@sw...>]

Thanks for the input. I realized this error after i posted to the list. 
Now when i try to give the command for creating the schema i get a peer 
auth error which is entirely postgres error. I am trying to fix it. 
Thanks for the help.

Regards,
Bhuvan

On Friday 06 January 2012 12:55 AM, Andrew Simpson wrote:
> On Thu, 05 Jan 2012 16:34:47 +0530
> Bhuvan Krishna<bh...@sw...>  wrote:
>
>> I am attaching the relavent log details from apache, postgresql and
>> webcollab. I enabled debug in the config.php and tried installing. I got
>> this error on the screen.
>>
>> Database server error:
>> SQLSTATE[42P01]: Undefined table: 7 ERROR: relation "site_name" does not
>> exist LINE 1: UPDATE site_name SET manager_name='WebCollab Project
>> Managem... ^
>>
>> check the attachments for more details.
>>
>> Regards,
>> Bhuvan
> Bhuvan,
>
> Thanks.  That's not too hard to fix.
>
> What has happened is that you've created the database manually, but not created the tables from the
> database schema.
>
> This is why WebCollab can connect to the database, but fails to insert data into the
> (non-existent) tables.
>
> The database table schema is in [webcollab]/db and is 'schema-pgsql.sql'.  There are some
> instructions in [webcollab]/docs, but basically something like this will work:
>
> # psql -U 'database_user' -e 'database_name'<  schema-pgsql.sql
>
> I'll add another error trap to the setup program to look for this condition.
>
> Andrew
>
> ------------------------------------------------------------------------------
> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
> infrastructure or vast IT resources to deliver seamless, secure access to
> virtual desktops. With this all-in-one solution, easily deploy virtual
> desktops for less than the cost of PCs and save 60% on VDI infrastructure
> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
> _______________________________________________
> Webcollab-users mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webcollab-users

Re: [Webcollab-users] unable to connect to database after installation webcollab 3.00

[Andrew S. <and...@co...>]

On Thu, 05 Jan 2012 16:34:47 +0530
Bhuvan Krishna <bh...@sw...> wrote:

> I am attaching the relavent log details from apache, postgresql and 
> webcollab. I enabled debug in the config.php and tried installing. I got 
> this error on the screen.
> 
> Database server error:
> SQLSTATE[42P01]: Undefined table: 7 ERROR: relation "site_name" does not 
> exist LINE 1: UPDATE site_name SET manager_name='WebCollab Project 
> Managem... ^
> 
> check the attachments for more details.
> 
> Regards,
> Bhuvan

Bhuvan,

Thanks.  That's not too hard to fix.

What has happened is that you've created the database manually, but not created the tables from the
database schema.

This is why WebCollab can connect to the database, but fails to insert data into the
(non-existent) tables.

The database table schema is in [webcollab]/db and is 'schema-pgsql.sql'.  There are some
instructions in [webcollab]/docs, but basically something like this will work:

# psql -U 'database_user' -e 'database_name' < schema-pgsql.sql

I'll add another error trap to the setup program to look for this condition.

Andrew

Re: [Webcollab-users] unable to connect to database after installation webcollab 3.00

[Bhuvan K. <bh...@sw...>]

I am attaching the relavent log details from apache, postgresql and 
webcollab. I enabled debug in the config.php and tried installing. I got 
this error on the screen.

Database server error:
SQLSTATE[42P01]: Undefined table: 7 ERROR: relation "site_name" does not 
exist LINE 1: UPDATE site_name SET manager_name='WebCollab Project 
Managem... ^

check the attachments for more details.

Regards,
Bhuvan

Re: [Webcollab-users] unable to connect to database after installation webcollab 3.00

[Bhuvan K. <bh...@sw...>]

Hi Andrew,

     Thanks for the quick reply. If their is any irc channel were we 
could discuss and work on the issue at the same time that would be 
really helpful for me. I am available anytime just let me know when you 
are free, If any one else is available for the irc meet even that is 
encouraging. If you prefer mails even that is fine with me. I will check 
with what you have told about enabling debug while installing webcollab. 
Also i will check the logs and get back to you.

Regards,
Bhuvan

On Thursday 05 January 2012 01:40 AM, Andrew Simpson wrote:
> On Wed, 04 Jan 2012 17:31:38 +0530
> Bhuvan Krishna<bh...@sw...>  wrote:
>
>> I have debian OS on which i am able to run drupal instances with any
>> problem I use postgresql as the database. While trying to install
>> webcollab i get a problem with connecting to the database. I did the
>> following steps.
>>
> Actually, further to my previous email:  Can you look in /var/log under apache2 and postgresql
> error logs and see what has been logged?  I am sure there will be something interesting.
>
> Andrew
>
>
> ------------------------------------------------------------------------------
> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
> infrastructure or vast IT resources to deliver seamless, secure access to
> virtual desktops. With this all-in-one solution, easily deploy virtual
> desktops for less than the cost of PCs and save 60% on VDI infrastructure
> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
> _______________________________________________
> Webcollab-users mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webcollab-users

Re: [Webcollab-users] unable to connect to database after installation webcollab 3.00

[Andrew S. <and...@co...>]

On Wed, 04 Jan 2012 17:31:38 +0530
Bhuvan Krishna <bh...@sw...> wrote:

> I have debian OS on which i am able to run drupal instances with any 
> problem I use postgresql as the database. While trying to install 
> webcollab i get a problem with connecting to the database. I did the 
> following steps.
> 

Actually, further to my previous email:  Can you look in /var/log under apache2 and postgresql
error logs and see what has been logged?  I am sure there will be something interesting.

Andrew

Re: [Webcollab-users] unable to connect to database after installation webcollab 3.00

[Andrew S. <and...@co...>]

On Wed, 04 Jan 2012 17:31:38 +0530
Bhuvan Krishna <bh...@sw...> wrote:

> I have debian OS on which i am able to run drupal instances with any 
> problem I use postgresql as the database. While trying to install 
> webcollab i get a problem with connecting to the database. I did the 
> following steps.
> 
> 1) unpack webcollab-3.00.tar.gz to collab directory in /var/www
> 2) changed permission of /var/www/collab/config/config.php to 777
> 3) changed permission of /var/www/collab/files/filebase to 777
> 
> 4) create a database and user with these commands
> createuser collab --pwprompt --encrypted
> createdb collab --owner=collab
> 
> 
> 5) access the setup page through http://localhost/collab/setup.php
> 
> 6) select english as the language
> 
> 7) select no at the option of creating a database by webcollab
> 
> 8) give the credentials of database and other options.
> 
> when i select re-enter i get ok at the database name and other options 
> but database user and database password don't give an error or warning. 
> at the end it says that webcollab was successfully installed and when i 
> select write the configuration file it gives me a page that says unable 
> to connect to database but user and password of webcollab are admin and 
> admin123.
> 
> I am unable to figure out the problem. I checked with postgresql config 
> files in /etc/postgresq/9.1/main/... everything is fine in their.
> 
> Regards,
> Bhuvan

Thanks for the detailed report.  I have a test machine running Debian, though it is Postgresql 8.4
(not 9.1).

It appears that all goes well until WebCollab tries to connect with the database to write the
configuration data.  The message that you are seeing is a graceful exit from a database error.

Could you enable 'debugging' in the config file and install again?  This would cause the error
message from the database to be printed to the screen, and would be very helpful.

Interesting that in Step 4 the username and password are accepted - this step also tries to connect
to the database to test the connection is working.

I will look at the code and Postgresql 9.1 for issues too.

Andrew

[Webcollab-users] unable to connect to database after installation webcollab 3.00

[Bhuvan K. <bh...@sw...>]

I have debian OS on which i am able to run drupal instances with any 
problem I use postgresql as the database. While trying to install 
webcollab i get a problem with connecting to the database. I did the 
following steps.

1) unpack webcollab-3.00.tar.gz to collab directory in /var/www
2) changed permission of /var/www/collab/config/config.php to 777
3) changed permission of /var/www/collab/files/filebase to 777

4) create a database and user with these commands
createuser collab --pwprompt --encrypted
createdb collab --owner=collab


5) access the setup page through http://localhost/collab/setup.php

6) select english as the language

7) select no at the option of creating a database by webcollab

8) give the credentials of database and other options.

when i select re-enter i get ok at the database name and other options 
but database user and database password don't give an error or warning. 
at the end it says that webcollab was successfully installed and when i 
select write the configuration file it gives me a page that says unable 
to connect to database but user and password of webcollab are admin and 
admin123.

I am unable to figure out the problem. I checked with postgresql config 
files in /etc/postgresq/9.1/main/... everything is fine in their.

Regards,
Bhuvan

[Webcollab-users] unable to connect to database after installation

[Bhuvan K. <bh...@sw...>]

I have debian OS on which i am able to run drupal instances with any 
problem I use postgresql as the database. While trying to install 
webcollab i get a problem with connecting to the database. I did the 
following steps.

1) unpack webcollab-3.00.tar.gz to collab directory in /var/www
2) changed permission of /var/www/collab/config/config.php to 777
3) changed permission of /var/www/collab/files/filebase to 777

4) create a database and user with these commands
createuser collab --pwprompt --encrypted
createdb collab --owner=collab


5) access the setup page through http://localhost/collab/setup.php

6) select english as the language

7) select no at the option of creating a database by webcollab

8) give the credentials of database and other options.

when i select re-enter i get ok at the database name and other options 
but database user and database password don't give an error or warning. 
at the end it says that webcollab was successfully installed and when i 
select write the configuration file it gives me a page that says unable 
to connect to database but user and password of webcollab are admin and 
admin123.

I am unable to figure out the problem. I checked with postgresql config 
files in /etc/postgresq/9.1/main/... everything is fine in their.

Regards,
Bhuvan

[Webcollab-users] WebCollab 3.00

[Andrew S. <and...@pa...>]

Hello all,

I am pleased to announce the release of WebCollab 3.00 (Avon):

This version is similar to the former 2.xx series, but has bugfixes and some new features added. 
The principal change is the database backend now uses prepared statements and a PHP Data Objects
(PDO) interface.  Minor speed improvements are expected with database interactions.

The prepared statements with PDO interface provide very good protection against SQL injection
attacks, which in turn are often due to poor coding. (WebCollab has previously had no known SQL 
injection problems).

WebCollab is now fully UTF-8 only.  It has been seven years since the first WebCollab UTF-8
experimental versions were released and UTF-8 offers substantial advantages for
internationalisation. 

The XHTML produced is fully compliant with XHTML 1.0 strict and WebCollab now has a table-less box
model using CSS.  The CSS code has been totally rewritten to allow better CSS skinning of the
display.  The display is buffered using PHP buffers to give better throughput and screen control.

Users can now gain remote access to iCal files using web authorisation.    

Note that new MySQL databases will created be as innodb databases.  The older MyISAM option has
been deprecated in this version.  

The previous release WebCollab 2.71 was a minor release that cleaned up the few known minor bugs and
provided a final clean release for the 2.xx series.

Enjoy!

Andrew Simpson 

[Webcollab-users] WebCollab 3.00

[Andrew S. <and...@pa...>]

Hello all,

I am pleased to announce the release of WebCollab 3.00 (Avon):

This version is similar to the former 2.xx series, but has bugfixes and some new features added. 
The principal change is the database backend now uses prepared statements and a PHP Data Objects
(PDO) interface.  Minor speed improvements are expected with database interactions.

The prepared statements with PDO interface provide very good protection against SQL injection
attacks, which in turn are often due to poor coding. (WebCollab has previously had no known SQL 
injection problems).

WebCollab is now fully UTF-8 only.  It has been seven years since the first WebCollab UTF-8
experimental versions were released and UTF-8 offers substantial advantages for
internationalisation. 

The XHTML produced is fully compliant with XHTML 1.0 strict and WebCollab now has a table-less box
model using CSS.  The CSS code has been totally rewritten to allow better CSS skinning of the
display.  The display is buffered using PHP buffers to give better throughput and screen control.

Users can now gain remote access to iCal files using web authorisation.    

Note that new MySQL databases will created be as innodb databases.  The older MyISAM option has
been deprecated in this version.  

The previous release WebCollab 2.71 was a minor release that cleaned up the few known minor bugs and
provided a final clean release for the 2.xx series.

Enjoy!

Andrew Simpson 

[Webcollab-users] WebCollab 3.00

[Andrew S. <and...@pa...>]

Hello all,

I am pleased to announce the release of WebCollab 3.00 (Avon):

This version is similar to the former 2.xx series, but has bugfixes and some new features added. 
The principal change is the database backend now uses prepared statements and a PHP Data Objects
(PDO) interface.  Minor speed improvements are expected with database interactions.

The prepared statements with PDO interface provide very good protection against SQL injection
attacks, which in turn are often due to poor coding. (WebCollab has previously had no known SQL 
injection problems).

WebCollab is now fully UTF-8 only.  It has been seven years since the first WebCollab UTF-8
experimental versions were released and UTF-8 offers substantial advantages for
internationalisation. 

The XHTML produced is fully compliant with XHTML 1.0 strict and WebCollab now has a table-less box
model using CSS.  The CSS code has been totally rewritten to allow better CSS skinning of the
display.  The display is buffered using PHP buffers to give better throughput and screen control.

Users can now gain remote access to iCal files using web authorisation.    

Note that new MySQL databases will created be as innodb databases.  The older MyISAM option has
been deprecated in this version.  

The previous release WebCollab 2.71 was a minor release that cleaned up the few known minor bugs and
provided a final clean release for the 2.xx series.

Enjoy!

Andrew Simpson 

Re: [Webcollab-users] update 2.61->2.70 : can't log

[Simon G. <sim...@sc...>]

On 19/03/2011 08:11, Andrew Simpson wrote:
> On Fri, 18 Mar 2011 11:14:01 +0100
> Simon GARESTE<sim...@sc...>  wrote:
>
>> Hi,
>> On an Ubuntu 9.3.
>>
>> I'm upgrading our version of webcollab from 2.61 to 2.70. As specified,
>> I changed the config.php file, went on the site at mysite/setup.php, was
>> asked to log as an admin, which I did successfully (meaning that the
>> database is correct up to there), did not wish to create a new database
>> since I had one already functioning, set up my configuration (below is
>> the login part configuration), wrote changes in the file (successfully
>> as well, everything was "tagged" OK, config.php was then with "N" for
>> web_config). Then I get to the login page, enter my login/password (same
>> as the ones I used as admin at first), and just can't log in, it gets
>> back to the login page. I checked /var/log/apache2/mysite/error.log,
>> where my apache configuration writes the stuff, nothing.
>>
> The debugging log will appear on the screen and be emailed to the admin.  What you have done sounds to be correct,
> though after that it is rather strange.
>
> When you say after login it just goes back to the the login page, does it go to an error message first, or just back to
> the login page?
>
> 1. Attempted logins with either no username or password (or neither) will just go straight back to the login screen.
>
> 2. Failed logins will give an error first, then go back to the login screen.
>
> 3. Problems with the database will give an error message.
>
> If you do have the first option (1.) then it is either a problem with the index.php file (corrupted?), or that somehow
> that the HTTP POST is not making it to WebCollab.  Neither sounds very likely though.
>
> You could also try running update.php (it won't update, but it will run and verify your login), and changing the config
> file to accept web logins and seeing if it will accept your login.
>
> Andrew
Hi,
I'm in the 1st option : when I try to log using my name (gareste, as 
defined in the database), the page just seem to refresh, no error 
message, no access denied, nothing (url then comes to 
/index.php?nologin=1). However, if I try using my email address, I'm 
redirected to the error message "access denied" (hence option 2).

index.php corrupted : after downloading again the .tar.gz and extracting 
it, running a diff -ur only gives me some minor differences over the css 
parts, which I changed a bit to correspond to our colors,  and over the 
config.php, of course.

Used update.php, didn't change anything :(

Didn't received anything to the admin mail.

HTTP POST solution : unlinkely indeed, since I get the message in case 
of attempt of login with email address..
Any other suggestion?

Thank you very much!
Simon

-- 
Simon Gareste
Support&  Development Engineer
--
Consortium Scilab
Digiteo
Domaine de Voluceau
Rocquencourt - B.P. 105
78153 Le Chesnay Cedex
--