phphelpdesk-devel

Re: [PhpHelpdesk-devel] Is This List Dead? Is Development of Helpdesk Dead?

[Andrew W. <ajw...@ro...>]

Hi Roy;

I've been very busy with work and everything else recently, and I
havn't had any time to work on the project.  If you or anyone else
is interested in working on it, I would be more than happy to give
you developer access to the CVS tree.  Just send me your
sourceforge id.

I appolagize to everyone for not responding to emails.

Andrew



On Monday 28 January 2002 03:51, Roy Rapoport wrote:
> About 12 days ago, I sent two emails to this list.  Neither was
responded
> to.  OK, I'd figure maybe my questions were either too dumb or too
complex
> for anyone to answer, but I also noticed absolutely no traffic on this

> list.
>
> So the question is, what's going on with PHPHelpdesk development? The
> reason I'm asking is that I'm being tasked with putting a whole bunch
of
> functionality into our instance of it.
>
> If development is continuing, I'd love to find a way to perhaps
develop
> these feature enhancements in a way that could lead to them being
rolled
> into the product at some point.  If not, then I'll figure I have the
> freedom to do what I want with the product under the assumption that
it's
> basically dead from a development stance.
>
> I'm not *too* hopeful I'll get a response to this email, of course.
If I
> don't see any response within a week, I'll post to the helpdesk users
> mailing list.
>
> -roy
>
>
>
> _______________________________________________
> Phphelpdesk-devel mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phphelpdesk-devel

[PhpHelpdesk-devel] Sending e-mail to IT personnel on every change/addition (PATCH)

[Vladimir V. <vu...@cs...>]

On Wed, 2002-01-30 at 18:23, Roy Rapoport wrote:
> Speaking of which, by the way, would you care to share with the group the
> diff for making it possible to email for every change of status of a
> ticket? I need this functionality also and would love to not reinvent the
> wheel.

Per popular request I am attaching changes we made. This might or might
not be useful to you. We are a 3 person IT department and all IT people
have ISMANAGER privileges in PHPHelpdesk. We wanted to get notified any
time any of us made a change in the Helpdesk system or as soon as a
ticket was filed. Something similar to WebRT. If you do not require such
functionality these patches are not for you.

The "patch" contains 

1. vj_sendnotification.php file that is attached. Copy it into the
scripts/ directory
2. addjob.scp.php DIFF file
3. vj_addevent.scp.php DIFF file

-----

1. Contains two functions. Get_manager_emails gets addresses of all
people who are "ISMANAGER". The other function was used to send
notification for 3.
2. This sends notification to ISMANAGER as soon as the ticket is
submitted.
3. Sends notification to ISMANAGER of a change in a ticket status.


That is it. All in all about 25-30 lines of code. Nothing too fancy or
complicated.


Vladimir

Re: [PhpHelpdesk-devel] Is This List Dead? Is Development of Helpdesk Dead?

[Matt G. <ma...@ma...>]

I agree about finding Andrew.  He was just announced as the new project 
manager, so it would be kinda soon to give up on him.
Matt

At 09:14 PM 1/28/2002 -0800, Roy Rapoport wrote:
>On 28 Jan 2002, Vladimir Vuksan wrote:
> > interest these are the things we can do
> >
> > a) An interested party should become the project lead
> > b) Project should be forked
> >
> > Of course a) is preferable but it does seem quite frustrating trying to
> > contact PHP Helpdesk developers.
> >
> > So anyone want to be a project lead :-) ?
>
>I support Vladimir's nomination to be project lead :)
>
>(on a more serious note, I think forking the project would be silly.  I'm
>much more inclined to see if we can find Andrew Walker and get him to
>either get reinvolved or relinquish control).
>
>-roy
>
>
>_______________________________________________
>Phphelpdesk-devel mailing list
>Php...@li...
>https://lists.sourceforge.net/lists/listinfo/phphelpdesk-devel

Re: [PhpHelpdesk-devel] Is This List Dead? Is Development of Helpdesk Dead?

[Roy R. <rs...@ae...>]

On 28 Jan 2002, Vladimir Vuksan wrote:
> interest these are the things we can do
> 
> a) An interested party should become the project lead
> b) Project should be forked
> 
> Of course a) is preferable but it does seem quite frustrating trying to
> contact PHP Helpdesk developers.
> 
> So anyone want to be a project lead :-) ?

I support Vladimir's nomination to be project lead :)

(on a more serious note, I think forking the project would be silly.  I'm
much more inclined to see if we can find Andrew Walker and get him to
either get reinvolved or relinquish control).

-roy

Re: [PhpHelpdesk-devel] Is This List Dead? Is Development of Helpdesk Dead?

[Vladimir V. <vu...@cs...>]

On Mon, 2002-01-28 at 04:51, Michael Stucki wrote:

> I just subscribed to the list last Friday. I'm looking out for a powerful 
> helpdesk solution, and phpHelpdesk seems to be quite promising.
> 
> But since there are not all features that we need (i.e. I didn't see any 
> knowlege base functionality), it's important that development goes on!
> 
> > So the question is, what's going on with PHPHelpdesk development? The
> > reason I'm asking is that I'm being tasked with putting a whole bunch of
> > functionality into our instance of it.
> 
> That'd be great! :-)
> 
> > If development is continuing, I'd love to find a way to perhaps develop
> > these feature enhancements in a way that could lead to them being rolled
> > into the product at some point.  If not, then I'll figure I have the
> > freedom to do what I want with the product under the assumption that it's
> > basically dead from a development stance.
> 
> If the current project manager hasn't enough time to spend for it, we should 
> look out for a successor.

Couple months ago I tried contacting the person in charge of PHPHelpdesk
since I had some minor patches related to e-mailing the IT team on each
change of a ticket. He never got back to me. After posting to this
mailing list one of the developers (Andrew Walker) got back to me and
asked me to send him the patches. Andrew later took over as the project
lead but I haven't seen any new releases.

I would definitely like to see improvements to the project and I am sure
a lot of people out there have their own patches. If there is enough
interest these are the things we can do

a) An interested party should become the project lead
b) Project should be forked

Of course a) is preferable but it does seem quite frustrating trying to
contact PHP Helpdesk developers.

So anyone want to be a project lead :-) ?

Vladimir

Re: [PhpHelpdesk-devel] Is This List Dead? Is Development of Helpdesk Dead?

[Michael S. <mu...@gm...>]

Hi Roy,

> About 12 days ago, I sent two emails to this list.  Neither was responded
> to.  OK, I'd figure maybe my questions were either too dumb or too complex
> for anyone to answer, but I also noticed absolutely no traffic on this
> list.

I just subscribed to the list last Friday. I'm looking out for a powerful 
helpdesk solution, and phpHelpdesk seems to be quite promising.

But since there are not all features that we need (i.e. I didn't see any 
knowlege base functionality), it's important that development goes on!

> So the question is, what's going on with PHPHelpdesk development? The
> reason I'm asking is that I'm being tasked with putting a whole bunch of
> functionality into our instance of it.

That'd be great! :-)

> If development is continuing, I'd love to find a way to perhaps develop
> these feature enhancements in a way that could lead to them being rolled
> into the product at some point.  If not, then I'll figure I have the
> freedom to do what I want with the product under the assumption that it's
> basically dead from a development stance.

If the current project manager hasn't enough time to spend for it, we should 
look out for a successor.

> I'm not *too* hopeful I'll get a response to this email, of course.  If I
> don't see any response within a week, I'll post to the helpdesk users
> mailing list.

It seems you're wrong ;-)

Anyway, a feedback from the users list (is anybody interested on ongoing 
development of phpHelpdesk?) should be interesting.

Michael

[PhpHelpdesk-devel] Is This List Dead? Is Development of Helpdesk Dead?

[Roy R. <rs...@ae...>]

About 12 days ago, I sent two emails to this list.  Neither was responded
to.  OK, I'd figure maybe my questions were either too dumb or too complex
for anyone to answer, but I also noticed absolutely no traffic on this
list.

So the question is, what's going on with PHPHelpdesk development? The
reason I'm asking is that I'm being tasked with putting a whole bunch of
functionality into our instance of it.  

If development is continuing, I'd love to find a way to perhaps develop
these feature enhancements in a way that could lead to them being rolled
into the product at some point.  If not, then I'll figure I have the
freedom to do what I want with the product under the assumption that it's
basically dead from a development stance.

I'm not *too* hopeful I'll get a response to this email, of course.  If I
don't see any response within a week, I'll post to the helpdesk users
mailing list.

-roy

[PhpHelpdesk-devel] What is s_isroot? (Re: Auto-Adding Companies)

[Roy R. <rs...@ae...>]

On Tue, 15 Jan 2002, Roy Rapoport wrote:
> I'd like to make it so when I add a client, a collection of users
> automatically gets updated to be able to manage that client.  I'm thinking
> that I'm going to do this by searching on everyone who can manage users and
> then updating them in the userdepartments table.

I noticed the s_isroot field in security.  This seems to be a perfect fit
to identify the people I want to identify, but it looks like everyone is
created with this being set to 0, with no opportunity to set it elsewise.
What's s_isroot used for?

-roy

[PhpHelpdesk-devel] Auto-Adding Companies

[Roy R. <rs...@ae...>]

I've found a procedural problem that I'm about to hack my way around and I
wanted to see if anyone had any good ideas on how to deal with it or at
least tell me "no! don't do that! it's a stupid idea because ... !" :)

We're a consulting house, and as we add clients, we add them into
PHPHelpdesk.

Now, we have a few consultants who are 'superconsultants' -- they can (and
will) work for pretty much all of our clients.   These consultants are
highly trusted, and have the power to do everything within Helpdesk.  

Right now, I find that when we add a client, we then have to go and,
individually, add the ability to manage that client to each of the
consultants.  

I'd like to make it so when I add a client, a collection of users
automatically gets updated to be able to manage that client.  I'm thinking
that I'm going to do this by searching on everyone who can manage users and
then updating them in the userdepartments table.

Any thoughts?

-roy

[PhpHelpdesk-devel] ticketparts tweak

[Roy R. <rs...@ae...>]

We are attempting to use PHPHD to track time and resources spent for a
given client for a given timeperiod, even if the ticket itself spans a
longer time period.  In other words, 
Lets assume the ticket is opened 11/23
The ticket is closed 12/17
During the lifetime of the ticket, there are 
2 hours spent on 11/25
$30 in parts used on 11/27
5 hours spent on 12/5
$50 in parts used on 12/7
2 hours spent on 12/16

We're working on a report right now that will allow us to see that, say,
for 12/1-12/15, we did 5 hours of work on this ticket and spent $50 in
parts.

All good, except that the ticketparts table associates part to ticket, but
doesn't do datestamping.

Well, until now :)

Attached are two diffs:  One adds a datestamp column to the ticketparts
table; the other modifies vj_addevent.scp.php slightly to accomodate the
first change.

Let me know if this is contrary to some sort of global vision of the PHPHD
development team.

-roy

[PhpHelpdesk-devel] Minor Display Security Tweaks diff

[Roy R. <rs...@ae...>]

I hope I'm not overstepping my bounds, and that I didn't just miss a
configuration option somewhere.

My company's a fairly new PHPHelpdesk user.  One of the issues we
discovered was this:
Our setup is to have each company client be tightly segregated from the
others.  This means that someone who's authorized to view tickets for
company A shouldn't be able to view/modify tickets for company B.  This
capability is built into PHPHelpdesk already.  

However, we also wanted the number of open tickets reported in the title
bar to reflect the number of open tickets open in the companies that the
user who's logged in has access to.  In other words, if we have:
Company:   Open tickets:
A          1
B          2
C          1
D          4

Then a user who has access to all companies should see 8 open tickets; a
user who has access to only companies A and B will see only 3 open tickets,
etc. 

This didn't seem to be easily modifiable, so we hacked functions.inc.php
slightly.  This seems to do what we want.  I'm not necessarily arguing that
this should be rolled into the actual PHPHelpdesk release, but it seems
somewhat antisocial to change source code for an open-source proram and
then keep the mods to ourselves.

The diff is attached.

-roy

[PhpHelpdesk-devel] Andrew Walker - New Project Manager

[Joe H. <jo...@jo...>]

Hi Everyone,

    As many of you know, lately I have not responded to most of you =
emails for support on this project.  I have been tremendously busy on =
other work related projects and thus have not had time to implement any =
changes to PHP Helpdesk.  This has been going on for about six months =
now.  I have been wanting to make the project much more robust with =
object oriented code, W3C standardization, better themes and graphics, =
more featuers, and bug fixes, along with continuing to promote the =
project.  However, everytime I say I'm going to sit down and work on it, =
I would get a phone call to go into the office because a server was down =
or something like that.
    Therefore, On December 1st I asked Andrew to become the Project =
Manager.  He has been very helpful, along with the rest of you, in =
making this project a team effort.  I think he will be a great project =
manager.  I enjoyed working on the project for the time that I did and =
would be glad to answer questions that you may have.  I still do have =
time constraints and may respond slowely to your emails, however.
    PHP Helpdesk is a great Help Desk tool.  The program work great for =
organizing trouble tickets/jobs and have a queue.  It compares to other =
$5,000 - $10,000 programs and the best thing is that it is GPL and FREE =
to use!  In any case, take care.  I hope the project continues to =
develop into a wonderful alternative to the comercial products.

Thanks,=20

Joseph Hoot
Systems Architect
jo...@ne...

[PhpHelpdesk-devel] Re: [Phphelpdesk-help] Anyone alive ?

[Andrew <ajw...@ro...>]

Hi Vladimir;

I've taken a bit of a break from the project, and I havn't heard much
from Joe lately either.  Anyway, please send me your patches, I will
gladly add them.  I also just added a file upload/attachment feature, so 
I'll ask Joe to create a new release soon.

Thanks;
Andrew




On Tuesday 20 November 2001 19:38, Vladimir Vuksan wrote:
> I have contacted couple of the PHP Helpdesk developers about submitting
> patches but have received no answer. Last release was more than 3 months
> ago so I was just wondering what are the developers up to. Are other
> developers simply too busy ?
>
> Thanks,
>
> Vladimir
>
>
>
>
> _______________________________________________
> Phphelpdesk-help mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phphelpdesk-help

[PhpHelpdesk-devel] Anyone alive ?

[Vladimir V. <vu...@sa...>]

I have contacted couple of the PHP Helpdesk developers about submitting
patches but have received no answer. Last release was more than 3 months
ago so I was just wondering what are the developers up to. Are other
developers simply too busy ?

Thanks,

Vladimir

[PhpHelpdesk-devel] Security Bug - add/delete user problem

[Kevin M. S. <sh...@cg...>]

I am cross-posting this here as well as the support request board.
I am sorry if you are seeing this multiple times.

-k

-------

If a privileged account deletes a Department before deleting the users 
assigned to that department, then the user is unable to be deleted or 
modified, but still has the ability to login. 

I discovered this during the implementation. I used the phphelpdesk.mysql 
to create my datatbase. I wanted to test behavior with the sample data 
first. When I was done cleaning out the phoney data with the web interface, 
I went back and tried to login in with "it"/"it". I was surprised to see that I 
got in. 


I have a detailed explanation below. 

Any questions feel free to email me. 
---- 
load page: http://phphelpdesk.yourdomain.com/index.php 

1. Login. 

2. Click on "Add Department", Follow proper steps to add the department. 
   To test, do not be bothered aligning permissions, any will do. 
   I added (testdepartment). 

3. When main page returns, click on "Add User", Follow proper steps, 
   be sure that you adding your user to the "testdepartment" ONLY. 
   If two departments are assigned to one user, and one department 
   get's deleted, then some useless data is left behind in some tables, 
   but no security hole should exist. 
   I added (testuser2). 

4. Now verify from the mysql prompt that both department and user 
   exist as expected. My table output is here: 

	mysql> select * from department; 
	+----------------+ 
	| d_name | 
	+----------------+ 
	| Client | 
	| Internal | 
	| testdepartment | 
	+----------------+ 
	3 rows in set (0.00 sec) 

	mysql> select * from userdepartments ;
	+-------+-----------+----------------+ 
	| ud_id | s_user | d_name | 
	+-------+-----------+----------------+ 
	| 2 | admin | Client | 
	| 6 | testuser2 | testdepartment | 
	| 5 | admin | testdepartment | 
	| 3 | shortt | Client | 
	| 1 | admin | Internal | 
	| 4 | shortt | Internal | 
	+-------+-----------+----------------+ 
	6 rows in set (0.00 sec) 

	mysql> select s_user from security; 
	+-----------+ 
	| s_user | 
	+-----------+ 
	| admin | 
	| shortt | 
	| testuser2 | 
	+-----------+ 
	3 rows in set (0.00 sec) 

	mysql> 

5. Click on "Delete Department". Follow the proper steps to delete a department. 
   I deleted (testdepartment). 
6. Now verify from the mysql prompt that department was deleted as expected. 
   Notice that testuser2 still exists in the security table.My table output is here: 

	mysql> select * from department; 
	+----------+ 
	| d_name | 
	+----------+ 
	| Client | 
	| Internal | 
	+----------+ 
	2 rows in set (0.00 sec) 

	mysql> select * from userdepartments; 
	+-------+--------+----------+ 
	| ud_id | s_user | d_name | 
	+-------+--------+----------+ 
	| 2 | admin | Client | 
	| 3 | shortt | Client | 
	| 1 | admin | Internal | 
	| 4 | shortt | Internal | 
	+-------+--------+----------+ 
	4 rows in set (0.00 sec) 

	mysql> select s_user from security; 
	+-----------+ 
	| s_user | 
	+-----------+ 
	| admin | 
	| shortt | 
	| testuser2 | 
	+-----------+ 
	3 rows in set (0.00 sec) 

	mysql> 

7. Click on "Delete User". The only users (in my case) to choose are "shortt"and "admin". 
8. Log out. 
9. Log back in using testuser2. 
   Bingo!!! you're back in. 

Re: [PhpHelpdesk-devel] PHP helpdesk seems to break

[Digital R. <d_r...@ya...>]

> What do you mean do anything to PHP?
> Do you mean add users or departments?
> Matt

Nah, it seemed like if I configured it, it would stop working. It looks like
I managed to trip a cookie in the header, so it'd reset. I think I'm ok now,
just won't mess with any javascript.

Thanks

Bob


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

[PhpHelpdesk-devel] PHP helpdesk seems to break

[Digital R. <d_r...@ya...>]

I don't know what I'm doing wrong, it seems like if I do anything to PHP
helpdesk, it will break after a while. Mainly the breakage occurs when I log
in, and click on any link, it just resets back to the 'what department are
you in' screen.
Any thoughts? I've been doing this for weeks now.

Bob


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

[PhpHelpdesk-devel] Enter Tickets via Email

[Matthew C. G. <mi...@ci...>]

Here is a script that allows you to enter tickets to phphelpdesk via an email.
Assumed is that you have phphelpdesk up and running, and that you have php 
compiled for command line scripts.  Also, you need to have qmail running, 
and have an email account that can run this forward script.
For example, I have an email account called helpdesk.  I have a .qmail file 
which contains the command

|/home/helpdesk/mail_to_db.php

Copy this script in, edit the user and the category, put the .qmail file in 
/home/helpdesk, and whenever this user receives email, it will show up 
instantly in the support database.

This will run the command that is needed.
Note that this does not add the email as the user.  All email tickets are 
added under one account.  It would be simple enough to parse out the user's 
email address, and submit it that way, but this is definitely simpler.  It 
might be an idea to create multiple category email addresses, and have 
emails categorized that way.
Follows is the mail_to_db.php script.
You will need to edit the variables for such things as what user do you 
want the email to be added to, what department, company, category, etc..

------------------------------------------
#!/usr/bin/php -q
<?php
#This connects to your database - put your mysql server, user, & pass here
$link = mysql_connect("localhost", "root", "")
	or die ("could not connect\n");
mysql_select_db ("phphelpdesk")
	or die ("could not select database\n");
$fp = fopen("./helplog", "a");

#This makes it so that all emails sent to this email address show up under
#the same user in PHPHelpdesk
$ctgry = "Other";
$tbl = "ticket";
$usr = "admin";
$dpt = "crag";
$loc = "idunno";
$nowtime = date('Y-m-d H:i:s');
$priority = "1";
$e_stat = "REGISTERED";
$e_des = "Ticket Assigned";
#Read the entire email, including headers.  It is being passed to stdin.
#The last 2 lines carve out only the message body, and trim leading and
#trailing whitespaces.
$fd = fopen("php://stdin","r");
while (!feof($fd)) {
$data = fgets($fd, 4096);
$testdata = "$testdata$data";
}
$body = strstr($testdata, "\n\n");
$body = trim ($body);
#This builds the query that adds the ticket to the ticket table.
$qry = "INSERT INTO $tbl SET t_category='$ctgry', t_detail='$body', 
t_user='$usr', t_priority='$priority', t_timestamp_opened='$nowtime', 
t_department='$dpt', t_location='$loc', t_summary='$UFLINE'";
$testresult = fwrite ($fp, $qry);
$testresult = fwrite ($fp, "\n");
#This executes the query that adds the ticket to the ticket table.
$result = mysql_query ($qry)
	or die ("Query Failed\n");
#This saves the Ticket ID created.  It is needed to create an Authorize Event.
$t_id = mysql_insert_id ($link);
#	or die ("Query Tid Failed\n");
$testresult = fwrite ($fp, $t_id);
$testresult = fwrite ($fp, "\n");
$tbl = "events";
#This builds the query that adds a new Authorize Event to the Event table.
#An Authorize Event in the event table is needed for the ticket to show up.
$qry2 = "INSERT INTO $tbl SET t_id='$t_id', s_user='$usr', 
e_assignedto='$usr', e_status='$e_stat', e_description='$e_des'";
$testresult = fwrite($fp, $qry2);
$testresult = fwrite($fp, "\n");
#This executes the query that adds a new Authorize Event to the Event table.
$result = mysql_query ($qry2)
	or die ("Query2 Failed\n");
#This closes the link to the database.
mysql_close ($link);
?>

[PhpHelpdesk-devel] Little admin mail advisory patch for phphelpdesk

[Enrico G. <Enr...@cc...>]

Hi all,

I don't know if you have already inserted this option, but for us it would 
be nice to have a Email notification to the administrator after a Ticket 
assignment.

I have made a quick (and dirty) patch for the module 
"scripts/addjob.scp.php".
Maybe you can use it:

please cut here 
---------------------------------------------------------------------------
------------

--- addjob.scp.php.orig	Thu Aug 23 09:11:42 2001
+++ addjob.scp.php	Thu Aug 23 09:15:27 2001
@@ -48,6 +48,24 @@
     $mailbody .= "$l_senton ".$readable_date." ".$readable_time." 
$l_usingusername \"$user.\"";
     $mailbody .= 
"\n------------------------------------------------------------------------
";

+
+    $mailbody2 = "\n\nHello Admin group member,\n";
+    $mailbody2 .= "\nthe User $txtUserLastName has opened this new 
Ticket:";
+    $mailbody2 .= 
"\n\n----------------------------------------------------------------------
--\n";
+    if ($g_dept_or_comp == 0) {
+      $mailbody2 .= "$l_department:  $Company\n";
+    }
+    else {
+      $mailbody2 .= "$l_company:  $Company\n";
+    }
+    $mailbody2 .= "$l_category: $lstCategory\n";
+    $mailbody2 .= "$l_summary:  $txtSummary\n";
+    $mailbody2 .= "$l_detail:   $txtDetail\n";
+    $mailbody2 .= "$l_location $txtLocation\n";
+    $mailbody2 .= "\n";
+    $mailbody2 .= "$l_senton ".$readable_date." ".$readable_time." 
$l_usingusername \"$user.\"";
+    $mailbody2 .= 
"\n------------------------------------------------------------------------
";
+
     if ($g_domainmailfrom == "") {
       $mailheader = "From: $user@$g_mailservername";
     }
@@ -58,9 +76,11 @@
     $mailbody = stripslashes($mailbody);
     if (!empty($txtUserEmail)) {
       mail($mailto, $mailsubject, $mailbody, $mailheader);
+      mail($g_helpdesk_email, $mailsubject, $mailbody2, $mailheader);
     }
     if ($s_email != NULL) {
       mail($s_email, $mailsubject, $mailbody, $mailheader);
+      mail($g_helpdesk_email, $mailsubject, $mailbody2, $mailheader);
     }
     print "<center>$l_areceiptwassent $txtUserFirstName 
$txtUserLastName<BR></center>\n";

@@ -105,6 +125,7 @@
       $mailheader = "From: $user@$g_mailservername";

       mail($mailto, $mailsubject, $mailbody, $mailheader);
+      mail($g_helpdesk_email, $mailsubject, $mailbody2, $mailheader);
       print "<center>$l_mailwassent $lstAssignedto<BR></center>\n";

     }

please cut here 
---------------------------------------------------------------------------
---------------------

Enjoy
E. Giakas

[PhpHelpdesk-devel] Closed tickets

[Matthew C. G. <mi...@ci...>]

I don't know if anyone has already posted this (I did search the list 
archive), but here's an idea I saw mentioned in a 'what people are saying 
email'.
It is nice to show people that you ARE doing things.  I wanted to show the 
number of tickets that were closed in the header.
First was the fact that the header Open count did not include Registered 
tickets.
Here's what I did.
I edited functions.inc.php.

Ater:
    $openTickets = 0;
    $userTickets = 0;

I added.

    $closedTickets = 0;

After:
    print "Closed Tickets: $closedTickets<br>\n";
    print "Open Tickets: $openTickets<br>\n";

I added.

    print "Assigned to you: $userTickets<br>\n";

In the line
            if( $prev_e_status == "OPEN" )

I added.
            or $prev_e_status == "REGISTERED"
For a result of:
            if( $prev_e_status == "OPEN" or $prev_e_status == "REGISTERED") {

At the end of this if statement, between the closing } and }, I added
            else $closedTickets++;
For a result of:
            }
            else $closedTickets++;
        }

Please forgive me if this has already been added or is way so obvious, but 
since my search didn't find it, I figured I'd post it to the list so that a 
newbie like myself could find it.  Thanks.

Matt
mi...@ci...

[PhpHelpdesk-devel] RE: Phphelpdesk Login Problem

[Joe H. <jo...@ne...>]

Unfortunately, no.   If you look at <phphelpdesk
home>/includes/cookie.inc.php, you will see how the cookie is set.  In
order for everything to work correctly, the <phphelpdesk
home>/includes/logout.inc.php also needs to reflect what the cookie file
does.  The problem is that we've tried to include the login domain and
stuff so that IE can work.  Once we do that, Netscape and everything
else stops working.  I haven't had time to sit and correct the problem.


Anyone is welcome to try to fix this problem.

Joe

-----Original Message-----
From: Armin.Sch=F6ntag [mailto:a.s...@pu...]=20
Sent: Thursday, July 26, 2001 1:56 AM
To: 'Joe Hoot'
Subject: AW: Phphelpdesk Login Problem

I tried NetScape 4.7 and MSIE 5.5
Before I asked you I checked that PHP4 is able to set cookies correctly.
I did this, besause it seems to me that the session information is not
set.
The Phphelpdesk-versions I tried are 6.1 and 6.15=20
Is there a former version available without that cookie issue?

Thank you for your quick reply!

	Best regards
	Armin Sch=F6ntag

	_________________________________________

	Armin Sch=F6ntag
	Production Manager
	Publicis NetWorks GmbH

	E-Mail	a.s...@pu...
	Phone		+49-89-28 69 80-341
	Fax		+49-89-28 69 80-500
	Web		http://www.publicis-networks.de
	Address	Chiemgaustr. 109=20
			D-81549 Munich
	_________________________________________



-----Urspr=FCngliche Nachricht-----
Von: Joe Hoot [mailto:jo...@ne...]
Gesendet: Donnerstag, 26. Juli 2001 08:24
An: 'armin schoentag'
Betreff: RE: Phphelpdesk Login Problem


I don't know if I responded to your message yet or not, but its probably
not your configuration.  PHPHelpdesk has been known to have a cookie
issue that nobody can seem to resolve.  Unfortunately, I have never run
into this problem.  Therefore, it is hard for me to troubleshoot.

-----Original Message-----
From: nobody [mailto:no...@us...] On Behalf Of
armin schoentag
Sent: Wednesday, July 25, 2001 8:21 AM
To: jo...@ne...
Subject: Phphelpdesk Login Problem

Hello,

we would like to use Phphelpdesk. I installed it=20
on a Linux-PHP4-MySQL-System. The database is=20
running, and after logging in I can see the list=20
of tickets. Hitting any link (e.g. view jobs)=20
leads me back to the start page, where I have to=20
login again.

Is there anything wrong in my configuration?

You can contact me also under:
a.s...@pu...

Best regards
Armin Schoentag

[PhpHelpdesk-devel] RE: PHP Helpdesk

[Joe H. <jo...@ne...>]

Actually, there is a s_deletetickets field that we should probably be
using for that.  I put that in there specifically for the ability to
delete tickets, but just never implemented the delete tickets.

I think that just adding one table element shouldn't be too difficult.
We'll just state in the upgrade script that it only upgrades from 0.6.1
to the latest version.

This project is still very young, in my opinion.  I think if we can
pound out the basic features.  The ones you've included pretty much
tighten up the features.  Then, after we stabilize it ( I don't think
that there's much work to do except to make sure the cookie thing is
working ).  Then, we can release the 1.0.0 version. 

After that is released, we can begin working on the 2.0.0 version.  This
new version will be much more object oriented and will use PHP Sessions
instead of cookie based authentication.  I would like to possibly work
with doing themes for it or at least some nice looking graphics and
icons or buttons like TWIG (twig.screwdriver.net) uses.  Also, I would
like to make sure that all the html that results from the PHP is W3C
compliant.  We can make the tickets, search, permissions, reports,
database layer, and other things all object oriented instead of just
variables.  I would like to add a few more databases-- I am currently
working on getting it to work with MSSQL.  I would like to add oracle
and postgress at some point.  I would like to have a database
abstraction layer so that the program can easily work with any database.

Also, one thing that I've tried to do is to make sure that can run on
both Win32 and UNIX.  At this point, it does run on both with Apache and
with IIS on Windows.  It is just PHP so it shouldn't be much of a
problem.

-----Original Message-----
From: an...@pa...
[mailto:an...@pa...] On Behalf Of Andrew Walker
Sent: Saturday, July 14, 2001 7:07 AM
To: Joe Hoot
Subject: Re: PHP Helpdesk

Hi Joe;

Ok,  if we're adding columns to the database that makes it
a bit more complicated as far as the users being able
to upgrade easily... We should try and think of
anything we'll need to add in the near future and
try and do it all at onece..   Like for deleting tickets,
I used the existing "s_ismanager" column, we should
create a new column at the same time.  Maybe
we should add a column which grants privilige to
delete his own tickets, and another which allows
them to delete any ticket, as well as the change
password flag you suggested.

Actually, we could eliminate all these columns and
have only one column which would contain an
integer which was the sum of all the security flags..

eg:
s_register_new_ticket = 1
s_authorize_ticket = 2
s_assign_ticket = 4
s_update_ticket = 8
..etc..

So if the user has access to s_register_new_ticket and s_assign_ticket,
their security value would be 5.  With this scheme you can easily add
more security flags without having to change the database, but would
be a pain to implement.

Also, have you played with the object oriented features of PHP?
You can create classes and objects, etc..   It could be useful for code
re-use
such as the view-ticket javascript code -- if we rewrite that as an
object
that can display any set of tickets, it would be easy to reuse it for
viewing
the results of many different queries (such as the search feature, or
other special views of the tickets - like view my open tickets, view
another
users open tickets, etc).

Anyway, let me know what you think!

Andrew




Joe Hoot wrote:

> Two things that that we should do, however, is to 1) make sure that
> these new scripts work well with the language files.  And 2) on the
> change password link, I would like to have another database column in
> the security table s_canchangepassword, or something like that.  This
> way, if we don't want them changing their passwords, then they won't
be
> able to.  Lets do some of these before we make the new release.  Then
> we'll make it 0.7.0 or something like that.
>
> -----Original Message-----
> From: an...@to...dis [mailto:an...@to...dis] On Behalf
Of
> Andrew Walker
> Sent: Friday, July 13, 2001 10:06 AM
> To: Joe Hoot
> Subject: PHP Helpdesk
>
> Hi Joe;
>
> I've made some additions to PHP Helpdesk, including a change password
> feature
> (under the preferences option), a search option, some new reports and
a
> delete ticket option (avaliable to people with ismanager security
> privilidge -
> new button appears on View Ticket screen).  Please take a look at
these
> and do
> some tests if you have time (let me know of any problems)... If it
looks
> ok,
> maybe we should make a new release?  For the users to upgrade there is
> nothing
> they need to do except download the new vsion and copy over the old
one
> (the database and config files are compatible).
>
> Thanks;
> Andrew

[PhpHelpdesk-devel] RE: PHP Helpdesk

[Joe H. <jo...@ne...>]

I tried out those functions... they're great!   I haven't really kept up
well on how I've released things.  I guess what I've been doing is to
increment the third number everytime I make a change in the CHANGELOG.
And then increment the middle number when major changes have taken
place.  And the first number is when a new major change has come out...
this first, in my opinion, should be used for stable releases.  This is
why I haven't given PHPHelpdesk a 1.0.0 release yet.  Until it is
stable, I'd like to keep using the middle and third numbers for
releases.

My suggestion is that this release is 0.6.13


What do you think about the release ideas?

-----Original Message-----
From: an...@to...dis [mailto:an...@to...dis] On Behalf Of
Andrew Walker
Sent: Friday, July 13, 2001 10:06 AM
To: Joe Hoot
Subject: PHP Helpdesk

Hi Joe;

I've made some additions to PHP Helpdesk, including a change password
feature
(under the preferences option), a search option, some new reports and a
delete ticket option (avaliable to people with ismanager security
privilidge -
new button appears on View Ticket screen).  Please take a look at these
and do
some tests if you have time (let me know of any problems)... If it looks
ok,
maybe we should make a new release?  For the users to upgrade there is
nothing
they need to do except download the new vsion and copy over the old one
(the database and config files are compatible).

Thanks;
Andrew

[PhpHelpdesk-devel] New Release 0.6.1 - Internationalization Release

[Joe H. <jo...@jo...>]

Hey Everyone,
 
I know that you've all helped out a lot in including some language files
for the project.  I have been moving and getting myself settled into my
new home and haven't worked on the project for a few weeks.  But, the
time has come for me to include a new release with all of your language
files.
 
PHP Helpdesk version 0.6.1 now includes the following language files:
 
            -Brazilian Portuguese
            -Dutch
            -English
            -French
            -Norwegian
            -Swedish
 
 
A few users are currently working on the following language files:
 
            -German
            -Spanish
            -Turkish
            -Portuguese Standard
 
If anyone else is interested in adding to the list of language files
available, please email me at jo...@ne... to make sure that
no one else has asked to create these files.  If nobody else has asked,
then you are welcome to start translating into your language of choice.
Also, any updates to these current language files can be emailed to me
and they will be included with the next release.
 
 
The newest release can be downloaded at
http://prdownloads.sourceforge.net/phphelpdesk/phphelpdesk.0.6.1.tar.gz
 
 
If you have any questions then please send an email to
php...@li....  We will then try to help you
out.
 
Thanks,
Joe Hoot
 

[PhpHelpdesk-devel] Introduction of myself and some developmentquestions

[Benjamin K. <ben...@in...>]

Hello there,

My name ist Benjamin and im currently building an intranet for
the company im working for.
we are quite impressed with php helpdesk and i would like to
include the helpdesk in our intranet, but there are a few points
i would like to know about the future development.

as far as i see it, the helpdesk is using frames, is there any
theme concept for a non-frame bases solution? 
it is obvious, that i want to include the helpdesk in our CD, and
our CD does (rightfully) not allow frames

furthermore, you have an own user management and i would like to
use our LDAP. will there be any ldap integration or at least an
open user-interface to build own or include existing user-management
stuff? (like the way phpBB2 is going to build there user mgmt)

i can also offer my help for any of the above points, if you need
some help developing helpdesk in that direction.

but the more important question is of course, do you want your
helpdesk developt with these features?

Regards,
  Benjamin

-- 
Benjamin Krause, ben...@in...
Infopark AG
Kitzingstr. 15, D-12277 Berlin, Germany
Tel +49(0)-30-747.993.0, Fax +49(0)-30-747.993.93
http://www.infopark.de/