phphelpdesk-devel

[PhpHelpdesk-devel] Re: PHP Helpdesk

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

Excellent idea with the menus.  I've also wanted to add a config option t=
o
change to buttons, but just haven't gotten around to it yet.  I tried out
the cookie fix that someone posted, but unfortunately, it broke every
browser except IE 4.01.  At least that was the case in my experience with
it.  Still looking into it.  As far as a new version, I've been working o=
n
some simple reporting features to complete a project at my work.  I plan =
on
expanding those reports.


----- Original Message -----
From: "Martin Skj=F6ldebrand" <ch...@sk...>
To: "Joseph Hoot" <jo...@jo...>
Sent: Thursday, March 22, 2001 11:58 AM
Subject: PHP Helpdesk


> Hi,
>
> Have you had any time looking at the disturbing cookie(?) bug which thr=
ows
> users out of PHP Helpdesk from time to time? And mixes up user rights t=
oo
as
> I've noticed.
>
> I've been adding a few more tricks to PHPHelpdesk (among them ticket
deletion
> as someone on the site wanted) and a new menu system (although that's v=
ery
> alpha - it might break user rights somehow. Haven't checked. Included a
pic
> of what it looks like).
>
> Any plans for a new release?
>
> Cheers,
>
> Martin S.

[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] 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