HESK version 2.2 public BETA (test version)

[Klemen]

UPDATE: HESK 2.2 now officially released, see:
viewtopic.php?t=3171


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


Good news, a new version of HESK is ready for testing! If you are interested please read this post carefully for details.

BETA WARNING

This is a BETA/TEST version of HESK. This version of script has been released for testing purposes only, it should not be used in a live environment! There is no guarantee the functions will work as planned. Use at your own risk! Please report any bugs/problems to this post.

Is the BETA version for me?

The BETA version is for testing purposes only. You should be familiar with previous version of Hesk (successfully installed a previous version of Hesk at least once).

How can I help?

Install HESK 2.2 BETA (in a test folder, not live!), test all features/settings as admin, staff and customer then come back and report any problems. The more feedback I get the sooner I will be able to officially release and support version 2.2

What's new in 2.2 BETA 1
Tip: Click here for a few screenshots

- assign owners to tickets (assign tickets to individual staff members)
- admin panel shows last repliers' name
- more information can be entered into e-mails (category, message, ticket owner, custom fields)
- staff can now submit tickets
- added reporting features
- added staff private messages
- check for duplicate tracking ID
- improved ticket searching
- fixed bug where edit_post rewrites session variables when register_globals is enabled
- fixed bug where e-mails and URLs don't show correctly when editing ticket
- fixed bug where last replier didn't show correctly after deleting a post
- lock/unlock individual tickets
- new way of suggesting KB articles
- ticket history log (who closed, opened, locked or unlocked a ticket)
- more user-friendly error and success message handling
- added checks to fight CSRF-type attacks
- generate URLs that will pre-load category selection when submitting new tickets
- settings will now accept localhost URLs
- purge attachments when the ticket is deleted
- disable customer setting ticket priority level
- a number of minor changes and fixes.

How to report a bug?

To report a bug please reply to this topic and try to include as much info about the bug as possible, but please at least this information:
Operating system (Windows, Linux, ...):
PHP version:
MySQL version:
Description of bug:
Exact steps to reproduce the bug:

Download
(REMOVED, download the official version from www.hesk.com)

Please report any bugs/problems/comments with HESK version 2.2 BETA 1 to this post.

[morsedesign]

When I use a plus sign in a password (which I do in many other programs) I receive the following PHP errors:


Warning: strlen() expects parameter 1 to be string, array given in C:\xampp\xampp\htdocs\hesk\admin\profile.php on line 340

Warning: Cannot modify header information - headers already sent by (output started at C:\xampp\xampp\htdocs\hesk\admin\profile.php:340) in C:\xampp\xampp\htdocs\hesk\inc\common.inc.php on line 156


I do not receive the error when I omit a plus sign in the password.

[m4dbra1n]

Hi Klemen,

I'm giving a look to the new beta and, given the fact that I've modded my 2.1 installation, I would like to ask you: is it possible to add some of the new features that you introduce in 2.2 (eg. reports and calendar near data field) in my 2.1, modding in the right way all the needed pages?

Since I'm not a PHP master, the personalizations take some time to be done and with 2.2 I have to make all the work again from the beginning (ok, maybe I'm a bit lazy...).



Thanks in advance and continue your work with this powerful script!

Just a hint: why don't you make the UI more 2.0? Raven can definitely give you an hand

[Klemen]

@morsedesign: thanks for reporting the bug, will be taken care off.

@m4dbra1n: please keep this topic about 2.2 BETA bugs/comments/suggestions only, as I don't want to lose track/focus. But to answer your question - a lot has changed in 2.2 so in my pinion you would be better off noting the changes you made to 2.1 and applying them to 2.2 (but to the final release, not the beta).

I do plan to develop a more Web 2.0 style interface to Hesk (with divs instead tables, with much more AJAX functionality, ...), but version 2.2 will keep the old one. Who knows, maybe Hesk 3.0 comes by

[rubycat]

Just two quick observations/bugs...

1) When the "priority" select menu isn't available for customers on the front end, it seems that new tickets are going in as "high"

2) Am getting an "invalid request" error as a customer trying to open or close an existing ticket

3) In print.php, the priority function seems to be the one from the current version...?

[rubycat]

...in certain circumstances.

For example, if I'm logged-in on the backend but messing around on the frontend...

I go to the ticket.php page, enter a non-existent tracking ID and submit it.

I get the ticket not found error but...

...the hesk_url link on the frontend leads to admin_main.php

I see it in common.inc.php but am not well-versed enough in PHP to understand what I'm looking at.

[Klemen]

rubycat thanks for reporting all the observations. I will check each and every report to make sure the final release is as bug-free as possible.

Keep them comming!

[rubycat]

I'm trying to keep notes as I go along but am finding that I can't read my handwriting! So frustrating! Process is going very slowly as I try to bring over all my 2.1 changes on the backend to the beta. So, um, while I've got you for a moment...is there any magical way to disengage the whole treemenu thing for the knowledgebase? The whole category/subcat thing is going to confuse admins (they're not too bright) and it's JS-dependent. The functions are so enmeshed that I can't seem to extract the necessary parts to still make one level of categories work.

[Klemen]

I'm afraid it would require a lot of modifications, out of the scope of my support.

I would recommend that you wait with applying your 2.1 modifications to 2.2 until the final release, as quite a few code from the BETA will change.

[rubycat]

Trying to change category of a ticket on admin_ticket.php page
Goes to move_category.php and displays following error:

Code: Select all

Can't execute SQL: SELECT `email`,`isadmin`,`categories` FROM `hesk_users` WHERE `notify`='1' AND `id`!=1

MySQL said:
Unknown column 'notify' in 'where clause'

...but the change does go through...

[lupolo]

Wen creating a ticket for a customer within the admin panel, and after that you wanne reply, it will give the following error:

Code: Select all

Interne programmeer-fout: No valid orig_email 

[lupolo]

I'm afraid it would require a lot of modifications, out of the scope of my support.

I would recommend that you wait with applying your 2.1 modifications to 2.2 until the final release, as quite a few code from the BETA will change.

Why not create directly SMTP support the FIX is working wonderful, must have a little adjustment with the reply email.

Is there also a adjustment for ripping the subject?

[lupolo]

Wenn locking a ticket it will disapear from the open tickets, beause it will close also automaticly

Other question regarding this isseu what does it send to catchup in the "admin_reply_ticket.php" ?

Like for example:

if ($new_status == 3) that it will close the ticket, see also my auto reponse by closing a ticket post.

[m4dbra1n]

@Klemen

Thanks anyway Klemen and sorry, I apologize for my mistake.

I will follow your advice; 'til the final release good work

[lupolo]

Wenn asking for your tickets wenn jou have lost them, it will give a error:

Code: Select all

Warning: Missing argument 2 for hesk_getEmailMessage(), called in /home/sites/site16926/web/helpdesktest/index.php on line 960 and defined in /home/sites/site16926/web/helpdesktest/inc/common.inc.php on line 314

But the email will send succesfully