HESK version 2.7.0 RC 1 (release candidate)

[Klemen]

UPDATE (Nov 11, 2016): HESK 2.7.0 has been released: HESK.com

Thank you to everyone who helped test it!




HESK 2.7.0 RC 1 is now available for preview. You are encouraged to test this version carefully, and report any bugs and incompatibilities.

THIS IS A RELEASE CANDIDATE. IT IS CONSIDERED MORE STABLE THAN BETA BUT STILL NOT RECOMMENDED FOR USE IN PRODUCTION!

» How can I help?

Install this version in a test folder, carefully test all features/settings as admin, staff and customer, and report any problems detected.

The more feedback I get the sooner I will be able to officially release and support the new version.

» How do I report a bug?

To report a bug please reply to this topic and try to include as much info about the bug as possible, especially exact steps required to reproduce the bug.

» Download: HESK 2.7.0 RC 1


» Please report any bugs/problems/comments/feedback by replying to this topic


» Changelog
- custom fields have been improved significantly:
» translate title
» change display order
» tie them to specific categories
» private (staff only) custom fields supported
» mark as required for everyone or just for customers
» checkboxes now require only a single option (before: two)
» increased number of available custom fields to 50
» improved interface and moved under "Tools"
» do not show double punctuation in forms
» new types: date, email, hidden
- you can now create custom ticket statuses
- improved language loading (fallback if not found, custom text)
- automatically reload pages with list of tickets every X seconds/minutes
- require tickets to be assigned before staff is able to reply to them (option)
- implemented IMAP fetching (import emails to tickets from an IMAP email server)
- email templates can now be modified from the Admin panel (Tools > Email templates)
- removed LIMIT 1 from SQL UPDATE/DELETE statements to avoid replication warnings
- in admin panel show a link to the public knowledgebase article location
- new staff permissions:
» can resolve tickets
» can submit tickets to any category
» can move tickets to any category
- ticket message can be set to not required
- ticket subject can be set to not required
- ticket email can be set to not required
- HESK can now force SSL connections

» Diff files:
HESK 2.7.0 beta 1 unified diff
HESK 2.7.0 beta 1 to beta 2 unified diff
HESK 2.7.0 beta 2 to beta 3 unified diff
HESK 2.7.0 beta 3 to RC 1 unified diff
HESK 2.7.0 RC 1 to FINAL unified diff

[wed]

thank you for this new version Klemen

I just installed the beta on a new server
I imported my support database 200 mo

Here are the first return hot

the custom field have not migrated, I was obliged to recreate with tool on admin tools

I can not change the hesk_settings.inc.php: Forbidden writing (chmod 777) with admin tools
You do not-have permission to access this document. for moemnt I change the language directly from the file

Here is another information
after migrating the database all my tickets are gone .inprogress

I give you the information
wed

[Klemen]

If I understand correctly, you first installed the beta version and then copied over the database?

It shouldn't be done like that, to upgrade you need a working 2.6.8 (or previous) version and upgrade on top of that.

So, you might want to:

- create a full working copy of your existing Hesk
- upgrade that to 2.7.0 beta 1 following upgrade steps in the docs

[Klemen]

There were indeed some issues with status in the upgrade script. I fixed those and made BETA 2 available.

[mkoch227]

PHP version: 5.5.38 (MySQLi)
MySQL version: 10.0.27-MariaDB-cll-lve
Description of bug: Autorefresh still enabled when unchecked in profile
Exact steps to reproduce the bug:

1. Check off "Automatically reload page with ticket list every" and enter a positive value. Save.
2. Go back to ticket page. Autorefresh checkbox is displayed with a countdown as expected
3. Uncheck the autoreload checkbox on the ticket page, then recheck it.
4. Go to profile page and unchecked the "Automatically reload..." checkbox. Save.
5. Go back to ticket page. Autorefresh checkbox is still checked and counting down from the previous value.

It looks like the issue may be caused by the "autorefresh" cookie that is set when the checkbox is checked/unchecked. I haven't had a chance to look through the code much, however, so there may be more/less to it.

Proposed Solution: Clear the "autorefresh" cookie whenever the user's profile is changed and the autoreload setting has changed (checked -> unchecked or vice-versa)

[wed]

Hello
here are my last test this morning.
nice work and thank you for your responsiveness
I'll test the function imap in the day

I continue my tests I come back to you once all validated.

I am finalizing the translation FR



here is the list of my tests :

- custom fields have been improved significantly: ok Work GREAT en update data base is OK
» translate title ok
» change display order ok
» tie them to specific categories
» private (staff only) custom fields supported
» mark as required for everyone or just for customers
» checkboxes now require only a single option (before: two) OK
» increased number of available custom fields to 50 ok
» improved interface and moved under "Tools" ok
» do not show double punctuation in forms
» new types: date, email, hidden OK
- you can now create custom ticket statuses OK
- improved language loading (fallback if not found, custom text) OK
- automatically reload pages with list of tickets every X seconds/minutes I have not seenon option this parameter
- require tickets to be assigned before staff is able to reply to them (option) OK
- implemented IMAP fetching (import emails to tickets from an IMAP email server)
- email templates can now be modified from the Admin panel (Tools > Email templates) ok
- removed LIMIT 1 from SQL UPDATE/DELETE statements to avoid replication warnings
- in admin panel show a link to the public knowledgebase article location ok
- new staff permissions:
» can resolve tickets ok after migration the case is check
» can submit tickets to any category : had already function with the other version I do not understand what changes
» can move tickets to any category had already function with the other version I do not understand what changes
- ticket message can be set to not required ok
- ticket subject can be set to not required ok
- ticket email can be set to not required ok
- HESK can now force SSL connections great function

wed

[Klemen]

@Mike

Nice find, thanks for reporting it. Will be fixed by setting an empty cookie if "autoreload" is unchecked and Profile saved.

@wed

Thank you for testing and reporting it. A few pointers:

- automatically reload pages with list of tickets every X seconds/minutes
On the top left corner of main admin page you will now see a "Auto reload page" checkbox, you can check it to automatically reload homepage. Number of seconds to refresh is set in Profile > Preferences

» can submit tickets to any category
» can move tickets to any category
Correct, this was already available for staff, but now you can take away this permission (for example to create staff that can only submit tickets to categories he has access to, not to any category)

[wed]

HI Klemen

thank you for the refresh option

Here is my contribution to the translation FR 2.7.0, i was sent PM message with download link.

and i was tested imap fetched, it's work's
my email configuration : Office 365
imap server : outlook.office365.com
port : 993 with SSL


I continued to test this new version that sounds very good

Klemen is it possible to add an option to attach it to an email fetched by category ?
In my case, I created an email by categories and I have to create as many check mail file categories in /inc/mail
I have about a 10 categories, and it would be best if we could attach an Email to a category
Example the creation of a category: add the option (check box) check new tichets by email and put the relevant Email
Then reveal the URL to make a regular check email with cron

thx

wed

[Klemen]

For email to category you could try editing the "inc/pipe_functions.inc.php" directly.

Find

Code: Select all

// Process "To:" email (not yet implemented, for future use)  

and try using something like this in that place:

Code: Select all

$tmpvar['to_email']	= hesk_validateEmail($results['to'][0]['address'],'ERR',0);
switch ($tmpvar['to_email'])
{
    case 'sales@example.com':
        $set_category = 2;
        break;
    case 'support@example.com':
        $set_category = 3;
        break;
    case 'category10@example.com':
        $set_category = 10;
        break;
}

It's a bit off-topic so if you have issues with it please open a new topic.

[mkoch227]

Looking at edit_post.php, I see the following at line 255:

Code: Select all

$custom_SQL = '';
for ($i=1; $i<=20; $i++)
{
	$custom_SQL .= '`custom'.$i.'`=' . (isset($tmpvar['custom'.$i]) ? "'".hesk_dbEscape($tmpvar['custom'.$i])."'" : "''") . ',';
}

Shouldn't this go up to 50 since the user can have (at most) 50 custom fields? I haven't had a chance to check all other areas yet; just noticed this one instance now

[Klemen]

It should indeed be 50, thank you!

[mkoch227]

In new_ticket.php, there is a $hidden_cf_buffer. All of the hidden fields are appended to this buffer; however the buffer is never echoed to the page. Is there something I'm missing, or should this be echoed with the other hidden fields?

I haven't checked any other pages that use this buffer, but I'll let you know if I notice this behavior elsewhere.

[Klemen]

This was indeed a problem, yes, but I decided to turn hidden fields into text inputs in the admin side to allow them to be modifiable by staff.

Here is the code that will be used (2 places in new_ticket.php)
(disregard, see next comment)


I have a couple of other changes from beta 2, will post them here later this week then we can hopefully move to an official release in the near future.

Thank you for testing and code review, please do let me know if you (or anyone else) find any other issues (even if not sure).

[Klemen]

Disregard previous code, I will modify this them to be handled the same code as Text fields by staff.

As mentioned, I will publish my beta 2 modifications later this week.

[Lisaweb]

Not sure if this is a bug, but trying to use a custom minimum date field which is has a default of +1 days, and trying to save a minimum accepted date of +0 days, so it will accept today's date or any future date after that. But it will not save the change. It will save +1 or +2, etc. But it will not save +0. Am I doing this wrong? Or is there a bug? Thanks!