outreach-general — General purpose OPT mailing list

[OPT-general] [ outreach-Patches-1507815 ] Overall project progress graph

[SourceForge.net <no...@so...>]

Patches item #1507815, was opened at 2006-06-17 15:22
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410241&aid=1507815&group_id=34206

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Marcus Nilsson (marcusn)
Assigned to: Nobody/Anonymous (nobody)
Summary: Overall project progress graph

Initial Comment:
Adds an overall project progress graph, showing the 
total effort left over time.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410241&aid=1507815&group_id=34206

[OPT-general] [ outreach-Bugs-1441978 ] Database permissions wrong: segmentation fault

[SourceForge.net <no...@so...>]

Bugs item #1441978, was opened at 2006-03-02 20:22
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410239&aid=1441978&group_id=34206

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: OPT 1.X (Max)
Status: Open
Resolution: None
Priority: 5
Submitted By: Martin Vernooij (martinfst)
Assigned to: Martin Vernooij (martinfst)
Summary: Database permissions wrong: segmentation fault

Initial Comment:
When installing (well actually restoring from backup)
an OPT installation and the user permissions are not
set correctly, OPT will die with a segmentation fault.
This is caused by the error handler, which keeps on
trying to connect to the database, while a connection
cannot be made.

In my case, I didn't grant the opt_user access to my
database, so I couldn't start OPT at all. All I got was
an apache segfault.

The error routine needs to be fixed, or the check for
database access needs to be extended.

function CRM_query_error($err_msg) in include/general.php

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410239&aid=1441978&group_id=34206

[OPT-general] [ outreach-Feature Requests-1436781 ] Would like subversion support

[SourceForge.net <no...@so...>]

Feature Requests item #1436781, was opened at 2006-02-22 07:57
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410242&aid=1436781&group_id=34206

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Would like subversion support

Initial Comment:
Would like subversion support

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410242&aid=1436781&group_id=34206

[OPT-general] Announcement of new project release for DMO

[Paul G. <pa...@la...>]

Dear OPT fans,

We are pleased to announce a major new release of DMO (Database of 
Managed Objects v2.0beta), from the same company which developed OPT.

This is a significant release, with a large number of features.  It is 
also much easier to install, as it is based on XAMPP (a popular 
distribution of LAMP that is very easy to install.)

Please check out our site on Sourceforge:

http://sourceforge.net/projects/dmo/

The download site is here (it's 10 Mb of compressed source code):

http://prdownloads.sourceforge.net/dmo/dmo-2.0beta.tar.gz?download

cheers
Paul Gillingwater
CSO Lanifex GmbH

[OPT-general] (no subject)

[Amit A. <am...@mi...>]

Hi there,

 

First of all opt is a great system, we love it, we have been using this for
the last one year now. We are having some problems for which we need your
help and advice, Please comment and advice on the below  matter, it is very
urgent.

 

 

4) If the subject line is such as "Project:competitivecommercialcarpet"

(case insensitive) opt  will look for project "competitivecommercialcarpet%"
in databse(case insennsitive and note the wildcard character at the end) and
add the mail to the email archive of that project

 

2)If this fails, then it will go ahead and parse the mail in the usual way,
attempting to add the email to the task comment. You must remove the logic
that scans the email configured in "project settings > email archive"
because that logic overrides putting the email in the task comment (in other
words, if the email is a response to a comment and the email address is
configured in "project

settings>email archive", it needs to put the email in the task comment.

Note that it

does NOT do this now, instead it will put the email in the project archive

 

3)Then, it should see if the sender email is a user on the system.  If it
finds one, it will locate the project(s) attached to that user.  If there is
only one project, it will automatically put the mail in the project archive
for that project.

 

4)If even this fails, it should check the email configured in Project
settings >Email archive and file the mail in the project email archive

 

5)In parsing emails, it needs to scan for the line ">!Dear"  or "> !Dear"

and discard the remainder of the message.  This is so that we don't copy the
whole quoted message trailer to the history (we will make message to say
"!Dear Joe, etc")

 

 

Further to this I want to change opt mail notification message , which file
do I have to modify

 

For eg to this

 

Dear Mr. Beneteau,

Mr. Amit Arora posted a new comment on task #21, \"Resources in action -
post article as pdf\" related to the \"ResourcesInAction.com\" project.  

 

By replying to this mail you may provide feedback to the developer(s). 

Please delete the quoted message body (other than your reply) as this will
get unnecessarily added to the task history.  

 

 

 

Please help me out in the above, I will be very greatful  to you, ur advice
will be highly valuable

 

amit

 

 

 

 

[OPT-general] [ outreach-Bugs-1151287 ] SQL Select Error on MySQL 4.1 for date value

[SourceForge.net <no...@so...>]

Bugs item #1151287, was opened at 2005-02-24 20:23
Message generated for change (Comment added) made by martinfst
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410239&aid=1151287&group_id=34206

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: OPT 1.X (Max)
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: SQL Select Error on MySQL 4.1 for date value

Initial Comment:
On MySQL 4.1 and above all queries with date values in
it fail. This happens because MySQL changed the format
of the returned value of typ timestamp. Before the
format was a number. In this version of MySQL the
format is in form "yyyy-mm-dd hh:MM:ss". 

A possible solution is to quote the value which is
inserted in the select string.
example from forum_lib.php: 

$sql="select (forums.date>$newDate) from forums where
id=$msg";

change to:
$sql="select (forums.date>'$newDate') from forums where
id=$msg";


Above is one errormessage from the OPT system:

The following query failed:
select (forums.date>2005-02-24 18:12:34) from forums
where id=1
You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the
right syntax to use near '18:12:34) from forums where
id=1' at line 1

This error occured while xxxx was accessing
/forums/Msg_List/ 

The user came here from
http://xxxxxx/forums/Msg_Add/?att_type=projects&att_id=2 

Please make sure you include the lines above when
submitting a bug report!


----------------------------------------------------------------------

>Comment By: Martin Vernooij (martinfst)
Date: 2005-09-29 19:52

Message:
Logged In: YES 
user_id=608879

This is all because the functionality of the date field in
MySQL. MySQL has two forms as can be seen from the MySQL
function now() 
[copy/paste from
http://dev.mysql.com/doc/mysql/en/date-and-time-functions.html]

NOW()

Returns the current date and time as a value in 'YYYY-MM-DD
HH:MM:SS' or YYYYMMDDHHMMSS format, depending on whether the
function is used in a string or numeric context.

mysql> SELECT NOW(); [1]
        -> '1997-12-15 23:50:26'
mysql> SELECT NOW() + 0; [2]
        -> 19971215235026

On the demo site, I don't have the problems, because the
database was originally running on MySQL 3.23. By just
copying the data I still have in the demo site the values
like: 20050929164937. As longs as all tables use this,
you're oke. But what I see happening is that a lot of new
setups, automagically start filling the tables with the
string format. While [2] is an arithmatic value, [1] is a
string and the minus sign is interpreted by the database
server. And the space brakes the sql statement all together.

On the list there have been suggestions to quote every used
date function/field, so effectively start using format [1].
To be honest: I'm not convinced this is the right approach.
I would prefer either format [2] or use the UNIX_TIMESTAMP()
function. But whatever solution is choosen, it means quite
some work to locate every used date functionality in the
scripts. And as I said before: I'm pretty busy. And
unfortunately for Outreach it's not on my top-priority list,
as my paying customers are.

As soon as I can find some time, I'll dig into this and
probably go for an intermediate 1.2.7 release to get these
breaking SQL statements out of the way.

----------------------------------------------------------------------

Comment By: chrismai (chris_mai)
Date: 2005-09-28 14:05

Message:
Logged In: YES 
user_id=1353122

There are more bugs, if you use OPT with MYSQL 4.1. The most
critical bug is, that there is a function nicedate () in
include/gui.php.
This function edits the date to show it in a better format.
To use this function an error message  will be shown, if you
want to see the people/task report:

The following query failed:
select
if (year(2005-09-28 13:28:49)!=year(now()),
date_format(2005-09-28 13:28:49,"%b %d %Y"),
if (dayofyear(2005-09-28 13:28:49)=dayofyear(now()),
"Today",
date_format(2005-09-28 13:28:49,"%b %d")
)
)
from people where id="6"
You have an error in your SQL syntax; check the manual that
corresponds to your MySQL server version for the right
syntax to use near '13:28:49)!=year(now()),
date_format(2005-09-28 13:28

This error occured while Administrator was accessing
/opt/tasks/report/people_task.php?proj=2

The user came here from
http://eisfair/opt/tasks/leftmenu/?proj=2.

If you convert the variable $field in the function nicedate
(), the date will never be shown. For example in the mask
Forums the threads don´t have a dateinformation or in the
Admin area the logs for all users will not be shown.

----------------------------------------------------------------------

Comment By: Matthias Munnich (langelino)
Date: 2005-07-02 01:32

Message:
Logged In: YES 
user_id=596252

I ran into the same problem and was able to fix it by adding
quotes around 4 variables in two file. See the patch
belowWARNING: I am a php illiterate so this might be a bad
way to fix it, however is works for me.

Langelino


--- OPT_1-2-6_MAX/opt/index.php       2002-08-28
04:15:36.000000000 -0700
+++ index.php   2005-07-01 16:16:59.000000000 -0700
@@ -81,13 +81,13 @@
       if ($CRM_comp==1)
       {
         $sql="select count(*) from news
-              where chindate>$lastlog";
+              where chindate>'$lastlog'";
       }
       else
       {
         $sql="select count(*) from news
               where (company=$CRM_comp or company=0)
-              and chindate>$lastlog";
+              and chindate>'$lastlog'";
       }
       $result=CRM_run_query($sql);
       $myrow=OPT_fetch_row($result);



--- OPT_1-2-6_MAX/opt/main_menu/welcome/index.php    
2004-12-16 23:56:54.000000000 -0800
+++ index.php   2005-07-01 16:17:47.000000000 -0700
@@ -299,7 +299,7 @@
       //      Other logins
       // ========================
       $lastlog=getvalue("people","prevlog",$CRM_user);
-      $sql="select count(*) from people where
lastlog>$prevlog and id!=$CRM_user";
+      $sql="select count(*) from people where
lastlog>'$prevlog' and id!=$CRM_user";
       $result=crm_run_query($sql);
       list($people_logged)=OPT_fetch_row($result);
       if ($people_logged) {
@@ -311,7 +311,7 @@
       // ========================
       if ($CRM_user > 5)
       {
-        $doc_count=crm_elements("documents"," and
chindate>$prevlog");
+        $doc_count=crm_elements("documents"," and
chindate>'$prevlog'");
         if ($docs=OPT_num_rows($doc_count)) {
             echo(sprintf(__("%d documents have been posted
since you last logged in"),$docs)."<br>\n");
         }



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410239&aid=1151287&group_id=34206

[OPT-general] [ outreach-Bugs-1151287 ] SQL Select Error on MySQL 4.1 for date value

[SourceForge.net <no...@so...>]

Bugs item #1151287, was opened at 2005-02-24 19:23
Message generated for change (Comment added) made by chris_mai
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410239&aid=1151287&group_id=34206

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: OPT 1.X (Max)
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: SQL Select Error on MySQL 4.1 for date value

Initial Comment:
On MySQL 4.1 and above all queries with date values in
it fail. This happens because MySQL changed the format
of the returned value of typ timestamp. Before the
format was a number. In this version of MySQL the
format is in form "yyyy-mm-dd hh:MM:ss". 

A possible solution is to quote the value which is
inserted in the select string.
example from forum_lib.php: 

$sql="select (forums.date>$newDate) from forums where
id=$msg";

change to:
$sql="select (forums.date>'$newDate') from forums where
id=$msg";


Above is one errormessage from the OPT system:

The following query failed:
select (forums.date>2005-02-24 18:12:34) from forums
where id=1
You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the
right syntax to use near '18:12:34) from forums where
id=1' at line 1

This error occured while xxxx was accessing
/forums/Msg_List/ 

The user came here from
http://xxxxxx/forums/Msg_Add/?att_type=projects&att_id=2 

Please make sure you include the lines above when
submitting a bug report!


----------------------------------------------------------------------

Comment By: chrismai (chris_mai)
Date: 2005-09-28 12:05

Message:
Logged In: YES 
user_id=1353122

There are more bugs, if you use OPT with MYSQL 4.1. The most
critical bug is, that there is a function nicedate () in
include/gui.php.
This function edits the date to show it in a better format.
To use this function an error message  will be shown, if you
want to see the people/task report:

The following query failed:
select
if (year(2005-09-28 13:28:49)!=year(now()),
date_format(2005-09-28 13:28:49,"%b %d %Y"),
if (dayofyear(2005-09-28 13:28:49)=dayofyear(now()),
"Today",
date_format(2005-09-28 13:28:49,"%b %d")
)
)
from people where id="6"
You have an error in your SQL syntax; check the manual that
corresponds to your MySQL server version for the right
syntax to use near '13:28:49)!=year(now()),
date_format(2005-09-28 13:28

This error occured while Administrator was accessing
/opt/tasks/report/people_task.php?proj=2

The user came here from
http://eisfair/opt/tasks/leftmenu/?proj=2.

If you convert the variable $field in the function nicedate
(), the date will never be shown. For example in the mask
Forums the threads don´t have a dateinformation or in the
Admin area the logs for all users will not be shown.

----------------------------------------------------------------------

Comment By: Matthias Munnich (langelino)
Date: 2005-07-01 23:32

Message:
Logged In: YES 
user_id=596252

I ran into the same problem and was able to fix it by adding
quotes around 4 variables in two file. See the patch
belowWARNING: I am a php illiterate so this might be a bad
way to fix it, however is works for me.

Langelino


--- OPT_1-2-6_MAX/opt/index.php       2002-08-28
04:15:36.000000000 -0700
+++ index.php   2005-07-01 16:16:59.000000000 -0700
@@ -81,13 +81,13 @@
       if ($CRM_comp==1)
       {
         $sql="select count(*) from news
-              where chindate>$lastlog";
+              where chindate>'$lastlog'";
       }
       else
       {
         $sql="select count(*) from news
               where (company=$CRM_comp or company=0)
-              and chindate>$lastlog";
+              and chindate>'$lastlog'";
       }
       $result=CRM_run_query($sql);
       $myrow=OPT_fetch_row($result);



--- OPT_1-2-6_MAX/opt/main_menu/welcome/index.php    
2004-12-16 23:56:54.000000000 -0800
+++ index.php   2005-07-01 16:17:47.000000000 -0700
@@ -299,7 +299,7 @@
       //      Other logins
       // ========================
       $lastlog=getvalue("people","prevlog",$CRM_user);
-      $sql="select count(*) from people where
lastlog>$prevlog and id!=$CRM_user";
+      $sql="select count(*) from people where
lastlog>'$prevlog' and id!=$CRM_user";
       $result=crm_run_query($sql);
       list($people_logged)=OPT_fetch_row($result);
       if ($people_logged) {
@@ -311,7 +311,7 @@
       // ========================
       if ($CRM_user > 5)
       {
-        $doc_count=crm_elements("documents"," and
chindate>$prevlog");
+        $doc_count=crm_elements("documents"," and
chindate>'$prevlog'");
         if ($docs=OPT_num_rows($doc_count)) {
             echo(sprintf(__("%d documents have been posted
since you last logged in"),$docs)."<br>\n");
         }



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410239&aid=1151287&group_id=34206

[OPT-general] [ outreach-Bugs-1151287 ] SQL Select Error on MySQL 4.1 for date value

[SourceForge.net <no...@so...>]

Bugs item #1151287, was opened at 2005-02-24 11:23
Message generated for change (Comment added) made by langelino
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410239&aid=1151287&group_id=34206

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: OPT 1.X (Max)
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: SQL Select Error on MySQL 4.1 for date value

Initial Comment:
On MySQL 4.1 and above all queries with date values in
it fail. This happens because MySQL changed the format
of the returned value of typ timestamp. Before the
format was a number. In this version of MySQL the
format is in form "yyyy-mm-dd hh:MM:ss". 

A possible solution is to quote the value which is
inserted in the select string.
example from forum_lib.php: 

$sql="select (forums.date>$newDate) from forums where
id=$msg";

change to:
$sql="select (forums.date>'$newDate') from forums where
id=$msg";


Above is one errormessage from the OPT system:

The following query failed:
select (forums.date>2005-02-24 18:12:34) from forums
where id=1
You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the
right syntax to use near '18:12:34) from forums where
id=1' at line 1

This error occured while xxxx was accessing
/forums/Msg_List/ 

The user came here from
http://xxxxxx/forums/Msg_Add/?att_type=projects&att_id=2 

Please make sure you include the lines above when
submitting a bug report!


----------------------------------------------------------------------

Comment By: Matthias Munnich (langelino)
Date: 2005-07-01 16:32

Message:
Logged In: YES 
user_id=596252

I ran into the same problem and was able to fix it by adding
quotes around 4 variables in two file. See the patch
belowWARNING: I am a php illiterate so this might be a bad
way to fix it, however is works for me.

Langelino


--- OPT_1-2-6_MAX/opt/index.php       2002-08-28
04:15:36.000000000 -0700
+++ index.php   2005-07-01 16:16:59.000000000 -0700
@@ -81,13 +81,13 @@
       if ($CRM_comp==1)
       {
         $sql="select count(*) from news
-              where chindate>$lastlog";
+              where chindate>'$lastlog'";
       }
       else
       {
         $sql="select count(*) from news
               where (company=$CRM_comp or company=0)
-              and chindate>$lastlog";
+              and chindate>'$lastlog'";
       }
       $result=CRM_run_query($sql);
       $myrow=OPT_fetch_row($result);



--- OPT_1-2-6_MAX/opt/main_menu/welcome/index.php    
2004-12-16 23:56:54.000000000 -0800
+++ index.php   2005-07-01 16:17:47.000000000 -0700
@@ -299,7 +299,7 @@
       //      Other logins
       // ========================
       $lastlog=getvalue("people","prevlog",$CRM_user);
-      $sql="select count(*) from people where
lastlog>$prevlog and id!=$CRM_user";
+      $sql="select count(*) from people where
lastlog>'$prevlog' and id!=$CRM_user";
       $result=crm_run_query($sql);
       list($people_logged)=OPT_fetch_row($result);
       if ($people_logged) {
@@ -311,7 +311,7 @@
       // ========================
       if ($CRM_user > 5)
       {
-        $doc_count=crm_elements("documents"," and
chindate>$prevlog");
+        $doc_count=crm_elements("documents"," and
chindate>'$prevlog'");
         if ($docs=OPT_num_rows($doc_count)) {
             echo(sprintf(__("%d documents have been posted
since you last logged in"),$docs)."<br>\n");
         }



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410239&aid=1151287&group_id=34206

[OPT-general] [ outreach-Bugs-1151287 ] SQL Select Error on MySQL 4.1 for date value

[SourceForge.net <no...@so...>]

Bugs item #1151287, was opened at 2005-02-24 11:23
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410239&aid=1151287&group_id=34206

Category: None
Group: OPT 1.X (Max)
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: SQL Select Error on MySQL 4.1 for date value

Initial Comment:
On MySQL 4.1 and above all queries with date values in
it fail. This happens because MySQL changed the format
of the returned value of typ timestamp. Before the
format was a number. In this version of MySQL the
format is in form "yyyy-mm-dd hh:MM:ss". 

A possible solution is to quote the value which is
inserted in the select string.
example from forum_lib.php: 

$sql="select (forums.date>$newDate) from forums where
id=$msg";

change to:
$sql="select (forums.date>'$newDate') from forums where
id=$msg";


Above is one errormessage from the OPT system:

The following query failed:
select (forums.date>2005-02-24 18:12:34) from forums
where id=1
You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the
right syntax to use near '18:12:34) from forums where
id=1' at line 1

This error occured while xxxx was accessing
/forums/Msg_List/ 

The user came here from
http://xxxxxx/forums/Msg_Add/?att_type=projects&att_id=2 

Please make sure you include the lines above when
submitting a bug report!


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410239&aid=1151287&group_id=34206

[OPT-general] [ outreach-Bugs-1120756 ] create newsletter does not set company id

[SourceForge.net <no...@so...>]

Bugs item #1120756, was opened at 2005-02-11 14:06
Message generated for change (Comment added) made by martinfst
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410239&aid=1120756&group_id=34206

Category: None
Group: OPT 1.X (Max)
>Status: Closed
Resolution: None
Priority: 5
Submitted By: Tobias Dittrich (lasrik)
>Assigned to: Martin Vernooij (martinfst)
Summary: create newsletter does not set company id

Initial Comment:
If you create a newsletter and choose "People in a
company" as destination the drop down box you get for
selecting which company does not contain the correct
comapny IDs. Instead all values of the option tags are
empty.

This is due to a small typo in line 117 in
nl_add/index.php: it says <option value=\$myrow[0]\
but should rather by <option value=\$myrow2[0]\

I included a patch file for this tiny bug :)

----------------------------------------------------------------------

>Comment By: Martin Vernooij (martinfst)
Date: 2005-02-12 20:45

Message:
Logged In: YES 
user_id=608879

Fixed in CVS for upcomming release 1.2.7

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410239&aid=1120756&group_id=34206

[OPT-general] [ outreach-Patches-1114755 ] Big Newsletter Patch

[SourceForge.net <no...@so...>]

Patches item #1114755, was opened at 2005-02-02 14:54
Message generated for change (Comment added) made by lasrik
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410241&aid=1114755&group_id=34206

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Tobias Dittrich (lasrik)
Assigned to: Nobody/Anonymous (nobody)
Summary: Big Newsletter Patch

Initial Comment:
Consequently following my last patch I further improved
the newsletter sending tool. This patch oudates my last
posting.

The following things are adressed:

- Inactive people or people with "no notification"
setting get all newsletters, edited distribution to fix
this.

- Newsletter to "everyone" did not work at all. Fixed
viewing/ deleting rights for this and edited
distribution to fix this.

- Newsletter to project only selects people directly
assigned to the project, not those assigned via their
company. Edited distribution to include them.


----------------------------------------------------------------------

>Comment By: Tobias Dittrich (lasrik)
Date: 2005-02-11 16:38

Message:
Logged In: YES 
user_id=768400

Added 2 fixes for new bugs I reported.

NOTE: the patch is against the cvs version not against prior
patched versions.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410241&aid=1114755&group_id=34206

[OPT-general] [ outreach-Bugs-1120845 ] Newsletter list broken (shows too much entries)

[SourceForge.net <no...@so...>]

Bugs item #1120845, was opened at 2005-02-11 16:21
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410239&aid=1120845&group_id=34206

Category: None
Group: OPT 1.X (Max)
Status: Open
Resolution: None
Priority: 5
Submitted By: Tobias Dittrich (lasrik)
Assigned to: Nobody/Anonymous (nobody)
Summary: Newsletter list broken (shows too much entries)

Initial Comment:
The newsletter list shows too many entries due to a
broken sql statement (the statement returns as many
rows as there are entries in the tables it joins over).
This does not occur for the administrator or guests.

Possible patch as usual included :) 
NOTE: this patch is against the cvs version not against
the modified versions you get due to applying former
patches I submitted.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410239&aid=1120845&group_id=34206

[OPT-general] [ outreach-Bugs-1120756 ] create newsletter does not set company id

[SourceForge.net <no...@so...>]

Bugs item #1120756, was opened at 2005-02-11 14:06
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410239&aid=1120756&group_id=34206

Category: None
Group: OPT 1.X (Max)
Status: Open
Resolution: None
Priority: 5
Submitted By: Tobias Dittrich (lasrik)
Assigned to: Nobody/Anonymous (nobody)
Summary: create newsletter does not set company id

Initial Comment:
If you create a newsletter and choose "People in a
company" as destination the drop down box you get for
selecting which company does not contain the correct
comapny IDs. Instead all values of the option tags are
empty.

This is due to a small typo in line 117 in
nl_add/index.php: it says <option value=\$myrow[0]\
but should rather by <option value=\$myrow2[0]\

I included a patch file for this tiny bug :)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410239&aid=1120756&group_id=34206

[OPT-general] [ outreach-Patches-1114755 ] Big Newsletter Patch

[SourceForge.net <no...@so...>]

Patches item #1114755, was opened at 2005-02-02 14:54
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410241&aid=1114755&group_id=34206

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Tobias Dittrich (lasrik)
Assigned to: Nobody/Anonymous (nobody)
Summary: Big Newsletter Patch

Initial Comment:
Consequently following my last patch I further improved
the newsletter sending tool. This patch oudates my last
posting.

The following things are adressed:

- Inactive people or people with "no notification"
setting get all newsletters, edited distribution to fix
this.

- Newsletter to "everyone" did not work at all. Fixed
viewing/ deleting rights for this and edited
distribution to fix this.

- Newsletter to project only selects people directly
assigned to the project, not those assigned via their
company. Edited distribution to include them.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410241&aid=1114755&group_id=34206

[OPT-general] [ outreach-Patches-1016980 ] Newsletter sent to everyone

[SourceForge.net <no...@so...>]

Patches item #1016980, was opened at 2004-08-26 18:02
Message generated for change (Settings changed) made by lasrik
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410241&aid=1016980&group_id=34206

Category: None
Group: None
>Status: Closed
>Resolution: Out of Date
Priority: 5
Submitted By: Tobias Dittrich (lasrik)
Assigned to: Nobody/Anonymous (nobody)
Summary: Newsletter sent to everyone

Initial Comment:
For newsletter if you choose destination "people in a
company" you can then choose to send to "Everybody".
However this leads to several bugs since it writes 0 as
ownerID in the database which is not interpreted well
by the rest of OPT :)

I have patched several files to get this working -- not
nice but works for me :)

Here's a short list of changed files and a short
description:

nl_distribute/index.php
main change to get nl distribution working. Just added
a check for owner==0 and then select everybody from the
database for this nl.

nl_entry/index.php
changed the rights check to allow everybody to see nl
entries.

nl_delentry/index.php
changed rights check to allow everybody to delete
entries -- don't patch if you don't want this

leftMenu/index.php
changed rights checking so everybody can add articles
to newsletter. Don't change if you don't want everybody
to add articles etc.

nl_list/index.php
cosmetic change to correct the display from "Company
n/a" to "Everybody".


----------------------------------------------------------------------

Comment By: Tobias Dittrich (lasrik)
Date: 2005-01-28 14:33

Message:
Logged In: YES 
user_id=768400

Can you please put this into the project since the
newsletter function is pretty much useless as it is at the
moment (at least for my uses) :(

I'd be happy to give every form of support for this, since
this is a very handy and much used function in our current
installation...

Thanks
Lasrik

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410241&aid=1016980&group_id=34206

Bulgarian translations (was [OPT-general] Thanks :)

[Martin V. <mar...@ti...>]

>Also, today I had a request from someone for a Bulgarian
>version -- does
>anyone know what translations already exist?

The whole multi language environment has evolved to a rather complex
setup. Originally done with gettext, now many text is directly coded in
several programs. This is partly due to the amount of former plugins,
that are now part of the 1.2.x versions, and partly due to most likely
less attention to the internationalization (my guess, looking at the
code).

I've already given the internationalization some thoughts, but still
haven't decided which route to take. I see two options:

1. Go for gettext again and rework all code to use gettext all over.
Personally I think this is bit of a hassle, because you get .po and .mo
files all over, there are many versions of gettext out there (not
available on all platforms and with different bugs and required
workarounds). If you want to edit messages in a relatively easy way,
you'll need a "special" editor, etc.

2. Move all messages/text to a table in the database and create an admin
interface which will show you the original (English) text and the
translation in a box, which allows you to edit it. This would give you a
lot of freedom to incorporate languages on the fly, and even maintain
them in a central database, much like the current upgrade utility. It
also give you the opportunity to delete languages you don't use. I use a
CMS that has such a structure for my websites.

Although I have a preference in this (pretty obvious), I'd also like to
use this opportunity to ask you (the users) about your opinion. Anyone
willing to share his/her view? Or even suggest better alternatives?

Thanks,

Martin

Re: [OPT-general] Thanks :)

[Paul G. <pa...@la...>]

Tobias Dittrich wrote:

>Now it's close to become a comany-wide installation for >700 
>employees and will then be used in 3 european countries and 
>taiwan! :-)
>  
>
Dear Tobias,

Hey thanks for the note, that's really cool to hear.

I'd love to hear similar things from any other OPT users -- how far has 
this little tool spread?

Also, today I had a request from someone for a Bulgarian version -- does 
anyone know what translations already exist?

cheers
Paul Gillingwater

[OPT-general] [ outreach-Bugs-1111366 ] Still one week missing

[SourceForge.net <no...@so...>]

Bugs item #1111366, was opened at 2005-01-28 12:15
Message generated for change (Comment added) made by lasrik
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410239&aid=1111366&group_id=34206

Category: Timesheets
Group: OPT 1.X (Max)
Status: Open
Resolution: None
Priority: 5
Submitted By: Tobias Dittrich (lasrik)
Assigned to: Martin Vernooij (martinfst)
Summary: Still one week missing

Initial Comment:
In the timesheets sections there is still one week
missing (the first week of this year). Also all
following weeks are shiftet by one week, so that always
the wrong week is displayed. I think this has to to
with the 53. week of the last year (week one of a year
starts with the first thursday of the year).

This bug is still present in the new 1.2.6 MAX release.

----------------------------------------------------------------------

>Comment By: Tobias Dittrich (lasrik)
Date: 2005-01-28 16:51

Message:
Logged In: YES 
user_id=768400

Well, I dirty hacked it for now: i just subtract 2 rather
than 1 (return $week_one_start+(3600*24*7*($week-2)); ).
This works for me, but I don't know about the implications...

Frankly I think this is all a bit overcomplicated, maybe due
to prior versions of PHP or so ... next week I might have
time to install the fresh version and maybe try to learn a
bit about date calculations in PHP. Might be that I am just
fastidious from my usual programming language Java :)


----------------------------------------------------------------------

Comment By: Martin Vernooij (martinfst)
Date: 2005-01-28 14:28

Message:
Logged In: YES 
user_id=608879

Wild guess, but perhaps it's a good one. I Googled for
locale german and date functions and saw from the php manual
an interesting comment: see e.g. http://nl.php.net/strftime

<quote>
Note:  %G and %V, which are based on ISO 8601:1988 week 
numbers can give unexpected (albeit correct) results if the
numbering system is not thoroughly understood. See %V above
and example below.
</quote>

OPT uses a date function like:
$is_weekone = strftime("%V", $first_day) == 1;

I only looked at this briefly, but it looks like the example
in the link above is showing the %V variable and the
different results you get with different locales.

Well, as I plan to rework the whole language stuff handling
for a next major release, I'm not sure how much time I
should spent on fixing this, as locale support is "less
optimal" in OPT right now anyway.

Let me know what you find with a fresh install and I'll give
this some more thoughts.

Martin.

----------------------------------------------------------------------

Comment By: Tobias Dittrich (lasrik)
Date: 2005-01-28 14:26

Message:
Logged In: YES 
user_id=768400

Okay I found the place where the error occurs, but since I'm
no PHP programmer I can't say what exactly is wrong :-}

The problem is the function: get_date_from_week in
date_funcs.php. This always returns a date one week later
than apropriate which in turn is then used as starting point
for the strtotime function.

Btw: it's not necessary to calculate the $week_start every
loop, is it? :)


----------------------------------------------------------------------

Comment By: Tobias Dittrich (lasrik)
Date: 2005-01-28 13:18

Message:
Logged In: YES 
user_id=768400

I get this error via: People->Timesheets  then there is already the 
incorrect week displayed (1 week shifted). When I use the "Previous" 
links at week "Jan 10, 2005" it skips directly to "Dez 27, 2004". 
 
Maybe this has something to do with the german locale I am using? 
See also the bug report about the missing locale from me... (okay 
this is just a blind shot :)). Or just that I use a complete german 
system (apache and php are localised also). 
 
I will try setting up a fresh new installation of the new OPT release (I 
just upgraded our current installation which already contained the 
patches I reported). 

----------------------------------------------------------------------

Comment By: Martin Vernooij (martinfst)
Date: 2005-01-28 12:54

Message:
Logged In: YES 
user_id=608879

It has to do with week 53, absolutely. 
Problem is, I cannot reproduce this failure. You can try on
the demo site (http://opt.tiempo.nl) and you will see all
weeks, and nothing shiufted. Unless you're taking another
route to get there.

Do you mind sharing which menu steps you do in the menu's to
get to the incorrect behaviour? 

Thanks, Martin

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410239&aid=1111366&group_id=34206

[OPT-general] Thanks :)

[Tobias D. <dit...@wa...>]

Hi all,

just wish to thank all active (and once active :) ) persons 
on this project. OPT is a great tool and very useful for my 
departement. 

Special thanks to those who recently took care of the 
project and made the new release possible - it was a great 
relief for me to see OPT gets carried on...

We have OPT in use since 12/03 and since then it has spread 
from a small sollution only for my departement (with 13 
programmers) over 4 other departments in our company -- 
everytime another departement got a newsletter or saw the 
forums or so they got jealous and wanted it too :)

Now it's close to become a comany-wide installation for >700 
employees and will then be used in 3 european countries and 
taiwan! :-)

Please keep it up
Tobias

[OPT-general] [ outreach-Patches-1016980 ] Newsletter sent to everyone

[SourceForge.net <no...@so...>]

Patches item #1016980, was opened at 2004-08-26 18:02
Message generated for change (Comment added) made by lasrik
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410241&aid=1016980&group_id=34206

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Tobias Dittrich (lasrik)
Assigned to: Nobody/Anonymous (nobody)
Summary: Newsletter sent to everyone

Initial Comment:
For newsletter if you choose destination "people in a
company" you can then choose to send to "Everybody".
However this leads to several bugs since it writes 0 as
ownerID in the database which is not interpreted well
by the rest of OPT :)

I have patched several files to get this working -- not
nice but works for me :)

Here's a short list of changed files and a short
description:

nl_distribute/index.php
main change to get nl distribution working. Just added
a check for owner==0 and then select everybody from the
database for this nl.

nl_entry/index.php
changed the rights check to allow everybody to see nl
entries.

nl_delentry/index.php
changed rights check to allow everybody to delete
entries -- don't patch if you don't want this

leftMenu/index.php
changed rights checking so everybody can add articles
to newsletter. Don't change if you don't want everybody
to add articles etc.

nl_list/index.php
cosmetic change to correct the display from "Company
n/a" to "Everybody".


----------------------------------------------------------------------

>Comment By: Tobias Dittrich (lasrik)
Date: 2005-01-28 14:33

Message:
Logged In: YES 
user_id=768400

Can you please put this into the project since the
newsletter function is pretty much useless as it is at the
moment (at least for my uses) :(

I'd be happy to give every form of support for this, since
this is a very handy and much used function in our current
installation...

Thanks
Lasrik

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410241&aid=1016980&group_id=34206

[OPT-general] [ outreach-Bugs-1111366 ] Still one week missing

[SourceForge.net <no...@so...>]

Bugs item #1111366, was opened at 2005-01-28 12:15
Message generated for change (Comment added) made by martinfst
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410239&aid=1111366&group_id=34206

Category: Timesheets
Group: OPT 1.X (Max)
Status: Open
Resolution: None
Priority: 5
Submitted By: Tobias Dittrich (lasrik)
Assigned to: Martin Vernooij (martinfst)
Summary: Still one week missing

Initial Comment:
In the timesheets sections there is still one week
missing (the first week of this year). Also all
following weeks are shiftet by one week, so that always
the wrong week is displayed. I think this has to to
with the 53. week of the last year (week one of a year
starts with the first thursday of the year).

This bug is still present in the new 1.2.6 MAX release.

----------------------------------------------------------------------

>Comment By: Martin Vernooij (martinfst)
Date: 2005-01-28 14:28

Message:
Logged In: YES 
user_id=608879

Wild guess, but perhaps it's a good one. I Googled for
locale german and date functions and saw from the php manual
an interesting comment: see e.g. http://nl.php.net/strftime

<quote>
Note:  %G and %V, which are based on ISO 8601:1988 week 
numbers can give unexpected (albeit correct) results if the
numbering system is not thoroughly understood. See %V above
and example below.
</quote>

OPT uses a date function like:
$is_weekone = strftime("%V", $first_day) == 1;

I only looked at this briefly, but it looks like the example
in the link above is showing the %V variable and the
different results you get with different locales.

Well, as I plan to rework the whole language stuff handling
for a next major release, I'm not sure how much time I
should spent on fixing this, as locale support is "less
optimal" in OPT right now anyway.

Let me know what you find with a fresh install and I'll give
this some more thoughts.

Martin.

----------------------------------------------------------------------

Comment By: Tobias Dittrich (lasrik)
Date: 2005-01-28 14:26

Message:
Logged In: YES 
user_id=768400

Okay I found the place where the error occurs, but since I'm
no PHP programmer I can't say what exactly is wrong :-}

The problem is the function: get_date_from_week in
date_funcs.php. This always returns a date one week later
than apropriate which in turn is then used as starting point
for the strtotime function.

Btw: it's not necessary to calculate the $week_start every
loop, is it? :)


----------------------------------------------------------------------

Comment By: Tobias Dittrich (lasrik)
Date: 2005-01-28 13:18

Message:
Logged In: YES 
user_id=768400

I get this error via: People->Timesheets  then there is already the 
incorrect week displayed (1 week shifted). When I use the "Previous" 
links at week "Jan 10, 2005" it skips directly to "Dez 27, 2004". 
 
Maybe this has something to do with the german locale I am using? 
See also the bug report about the missing locale from me... (okay 
this is just a blind shot :)). Or just that I use a complete german 
system (apache and php are localised also). 
 
I will try setting up a fresh new installation of the new OPT release (I 
just upgraded our current installation which already contained the 
patches I reported). 

----------------------------------------------------------------------

Comment By: Martin Vernooij (martinfst)
Date: 2005-01-28 12:54

Message:
Logged In: YES 
user_id=608879

It has to do with week 53, absolutely. 
Problem is, I cannot reproduce this failure. You can try on
the demo site (http://opt.tiempo.nl) and you will see all
weeks, and nothing shiufted. Unless you're taking another
route to get there.

Do you mind sharing which menu steps you do in the menu's to
get to the incorrect behaviour? 

Thanks, Martin

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410239&aid=1111366&group_id=34206

[OPT-general] [ outreach-Bugs-1111366 ] Still one week missing

[SourceForge.net <no...@so...>]

Bugs item #1111366, was opened at 2005-01-28 12:15
Message generated for change (Comment added) made by lasrik
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410239&aid=1111366&group_id=34206

Category: Timesheets
Group: OPT 1.X (Max)
Status: Open
Resolution: None
Priority: 5
Submitted By: Tobias Dittrich (lasrik)
Assigned to: Martin Vernooij (martinfst)
Summary: Still one week missing

Initial Comment:
In the timesheets sections there is still one week
missing (the first week of this year). Also all
following weeks are shiftet by one week, so that always
the wrong week is displayed. I think this has to to
with the 53. week of the last year (week one of a year
starts with the first thursday of the year).

This bug is still present in the new 1.2.6 MAX release.

----------------------------------------------------------------------

>Comment By: Tobias Dittrich (lasrik)
Date: 2005-01-28 14:26

Message:
Logged In: YES 
user_id=768400

Okay I found the place where the error occurs, but since I'm
no PHP programmer I can't say what exactly is wrong :-}

The problem is the function: get_date_from_week in
date_funcs.php. This always returns a date one week later
than apropriate which in turn is then used as starting point
for the strtotime function.

Btw: it's not necessary to calculate the $week_start every
loop, is it? :)


----------------------------------------------------------------------

Comment By: Tobias Dittrich (lasrik)
Date: 2005-01-28 13:18

Message:
Logged In: YES 
user_id=768400

I get this error via: People->Timesheets  then there is already the 
incorrect week displayed (1 week shifted). When I use the "Previous" 
links at week "Jan 10, 2005" it skips directly to "Dez 27, 2004". 
 
Maybe this has something to do with the german locale I am using? 
See also the bug report about the missing locale from me... (okay 
this is just a blind shot :)). Or just that I use a complete german 
system (apache and php are localised also). 
 
I will try setting up a fresh new installation of the new OPT release (I 
just upgraded our current installation which already contained the 
patches I reported). 

----------------------------------------------------------------------

Comment By: Martin Vernooij (martinfst)
Date: 2005-01-28 12:54

Message:
Logged In: YES 
user_id=608879

It has to do with week 53, absolutely. 
Problem is, I cannot reproduce this failure. You can try on
the demo site (http://opt.tiempo.nl) and you will see all
weeks, and nothing shiufted. Unless you're taking another
route to get there.

Do you mind sharing which menu steps you do in the menu's to
get to the incorrect behaviour? 

Thanks, Martin

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410239&aid=1111366&group_id=34206

[OPT-general] [ outreach-Bugs-1111366 ] Still one week missing

[SourceForge.net <no...@so...>]

Bugs item #1111366, was opened at 2005-01-28 12:15
Message generated for change (Comment added) made by lasrik
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410239&aid=1111366&group_id=34206

Category: Timesheets
Group: OPT 1.X (Max)
Status: Open
Resolution: None
Priority: 5
Submitted By: Tobias Dittrich (lasrik)
Assigned to: Martin Vernooij (martinfst)
Summary: Still one week missing

Initial Comment:
In the timesheets sections there is still one week
missing (the first week of this year). Also all
following weeks are shiftet by one week, so that always
the wrong week is displayed. I think this has to to
with the 53. week of the last year (week one of a year
starts with the first thursday of the year).

This bug is still present in the new 1.2.6 MAX release.

----------------------------------------------------------------------

>Comment By: Tobias Dittrich (lasrik)
Date: 2005-01-28 13:18

Message:
Logged In: YES 
user_id=768400

I get this error via: People->Timesheets  then there is already the 
incorrect week displayed (1 week shifted). When I use the "Previous" 
links at week "Jan 10, 2005" it skips directly to "Dez 27, 2004". 
 
Maybe this has something to do with the german locale I am using? 
See also the bug report about the missing locale from me... (okay 
this is just a blind shot :)). Or just that I use a complete german 
system (apache and php are localised also). 
 
I will try setting up a fresh new installation of the new OPT release (I 
just upgraded our current installation which already contained the 
patches I reported). 

----------------------------------------------------------------------

Comment By: Martin Vernooij (martinfst)
Date: 2005-01-28 12:54

Message:
Logged In: YES 
user_id=608879

It has to do with week 53, absolutely. 
Problem is, I cannot reproduce this failure. You can try on
the demo site (http://opt.tiempo.nl) and you will see all
weeks, and nothing shiufted. Unless you're taking another
route to get there.

Do you mind sharing which menu steps you do in the menu's to
get to the incorrect behaviour? 

Thanks, Martin

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410239&aid=1111366&group_id=34206

[OPT-general] [ outreach-Bugs-1111366 ] Still one week missing

[SourceForge.net <no...@so...>]

Bugs item #1111366, was opened at 2005-01-28 12:15
Message generated for change (Comment added) made by martinfst
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410239&aid=1111366&group_id=34206

Category: Timesheets
Group: OPT 1.X (Max)
Status: Open
Resolution: None
Priority: 5
Submitted By: Tobias Dittrich (lasrik)
>Assigned to: Martin Vernooij (martinfst)
Summary: Still one week missing

Initial Comment:
In the timesheets sections there is still one week
missing (the first week of this year). Also all
following weeks are shiftet by one week, so that always
the wrong week is displayed. I think this has to to
with the 53. week of the last year (week one of a year
starts with the first thursday of the year).

This bug is still present in the new 1.2.6 MAX release.

----------------------------------------------------------------------

>Comment By: Martin Vernooij (martinfst)
Date: 2005-01-28 12:54

Message:
Logged In: YES 
user_id=608879

It has to do with week 53, absolutely. 
Problem is, I cannot reproduce this failure. You can try on
the demo site (http://opt.tiempo.nl) and you will see all
weeks, and nothing shiufted. Unless you're taking another
route to get there.

Do you mind sharing which menu steps you do in the menu's to
get to the incorrect behaviour? 

Thanks, Martin

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410239&aid=1111366&group_id=34206

[OPT-general] [ outreach-Bugs-1111366 ] Still one week missing

[SourceForge.net <no...@so...>]

Bugs item #1111366, was opened at 2005-01-28 12:15
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410239&aid=1111366&group_id=34206

Category: Timesheets
Group: OPT 1.X (Max)
Status: Open
Resolution: None
Priority: 5
Submitted By: Tobias Dittrich (lasrik)
Assigned to: Guy Davis (guy_davis)
Summary: Still one week missing

Initial Comment:
In the timesheets sections there is still one week
missing (the first week of this year). Also all
following weeks are shiftet by one week, so that always
the wrong week is displayed. I think this has to to
with the 53. week of the last year (week one of a year
starts with the first thursday of the year).

This bug is still present in the new 1.2.6 MAX release.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410239&aid=1111366&group_id=34206