Messages

  Entire forum

Auto Light Dark

English

tfs,
Is there any such bugs which need addressed?  Trying to get back into SMF stuff, I should try to spend time with SD and get working with it again.

I'd be willing to install any number of test forums for you and I to work with.  I'll perform beta testing for you to your heart's delight. 

I use SimpleDesk daily in my real-world job.  I've probably worked through a thousand tickets since we started using it.  But as far as bugs go, I just don't have a good idea of what they are right now (besides the two Arantor linked).  Once the code went to GitHub I threw up my hands in frustration. 

Have a safe trip.  No hurry.  As it is now, 99% of it is fixed.  It's rare for us that there's a ticket with overridden fields.  My boss just happened to hit one just after I told him it was fixed.  LOL!

Found a glitch.  If there's a second custom field that has a *required entry (in addition to the large text box), when you hit the [Edit ticket] button and you get sent back to the ticket and are presented the "Override the custom fields requirements" checkbox... the damage is already done and the BR tags are there.

At that point you can edit the large text box again, removing the BR tags, check the "Override" check box and it works OK. 

Excellent!  Thank you.  This issue just wasn't something we were going to catch as beta testers since it took the buildup of thousands of entries before I started getting the WSOD.  And then for the longest time I thought it was due to some screwy high ASCII character sneaking into a ticket.

Only thing I changed was...

$context['displaypage'] = 30;

...changed to...

$context['displaypage'] = 500;

I prefer a large page of items.  I'm assuming that was the only change necessary to have a different count per page?  It seems to work fine.

Seems to have fixed the issue on my live help desk.  Thanks Arantor!!!

I sure wish that development would continue.  I'd donate money and time gladly.  I rely on SD every single day, but I could use some fixes and tweaks.

You did a great job!  Had we had time to bring along a FUP version or two I think it would have smoothed it all out.

The log paginates when viewing the full log...

?action=admin;area=helpdesk_info;sa=actionlog

But not when viewing the individual users' help desk log...

?action=profile;u=1;area=hd_actionlog

I'm not sure if the one visible on the ticket itself paginates, though I have one with 129 entries and it's not paginating, so presumably that doesn't paginate.  I don't expect that'll become an issue for me because a single ticket is unlikely to get thousands of log entries... though of course it could happen.  However, on an individual ticket the log is displayed at the same time as the rest of the ticket, so presumably it's not quite straight forward how the pagination would mesh into the display of the rest of the ticket.

I sure miss having you around working on SD. 

Just one last note re logfile size... I ran this query from phpMyAdmin...

Code Select Expand

delete FROM `smf_helpdesk_log_action`
where id_member = 205
and from_unixtime(log_time) not like '2013%'
and from_unixtime(log_time) not like '2012%'

...which deleted my own entries entered before 1/1/2012, and leaves me with 3154 logfile entries.  I can now view my own log, though it takes a while to finish displaying since there's so many in the grid.

I have noticed that when certain characters are used (slanted quotation marks and extended hyphens amongst them) within a ticket, then that ticket becomes unreadable, clicking on any link to it leads to a blank page.

Also, whatever page the ticket is listed in will also be blank.

Please advise accordingly.

BTW UKStu, sorry for hijacking your thread with my logfile issues.  I've also noticed that certain characters will cause WSOD if embedded within a ticket.  I had lots of trouble with that initially until I reinstalled my forum and used a different character encoding... and I'm sorry, I can't remember exactly what the different was.  Was it UTF8 maybe?  Whatever it was, it did help.

The biggest trouble seemed to stem from people writing the body of the ticket in MS Word and then pasting into the ticket body.

Also, you could possibly use phpMyAdmin to fix some of these tickets.  If you could find a filter to locate them, and then use the edit ability on phpMyAdmin to remove the offending characters.

If anyone's interested, the from_unixtime() function is what you need to see the log_time field in a more readable manner.  Example...

Code Select Expand

SELECT from_unixtime(log_time) as date_time, id_action, log_time, id_member, ip, action, id_ticket, id_msg, extra
FROM `smf_helpdesk_log_action`
where id_member = 205
and from_unixtime(log_time) not like '2013%'

That returns all log entries for user 205 that are not in 2013.  To delete them you'd substitute "delete" in place of "select xxx".  Such as ...

Code Select Expand

DELETE
FROM `smf_helpdesk_log_action`
where id_member = 205
and from_unixtime(log_time) not like '2013%'

Hmmmm... I'll have to figure out that unix date field.

Also, I suppose there's some types of activities that I'd be more willing to delete than others.  Though the ones I'd like to keep seem to be the most populous.

Code Select Expand

SELECT count( * ) , ACTION
FROM `smf_helpdesk_log_action`
WHERE id_member =205
GROUP BY ACTION
ORDER BY count( * ) DESC
LIMIT 0 , 30

1777    newreply
702    assign
550    cf_tktchange_staffadmin
437    editticket
268    editreply
229    cf_tktchange_userstaffadmin
157    cf_rplchange_userstaffadmin
102    cf_tktchgdef_userstaffadmin
64    cf_tktchgdef_staffadmin
52    rel_linked
25    monitor
25    newticketproxy
21    urgency_increase
14    rel_duplicated
14    delete_reply
11    newticket
8    urgency_decrease
2    rel_child
2    rel_parent
2    rel_delete
2    unresolve
2    cf_rplchgdef_userstaffadmin
2    rel_re_duplicated
1    cf_tktchange_admin
1    resolve
1    restore_reply

I can fairly well confirm that the WSOD on the individual users' action logs is a size issue, because there's no pagination on the action log when viewed for an individual user.  First I did this query in phpMyAdmin...

Code Select Expand

SELECT count( * ) , `id_member`
FROM `smf_helpdesk_log_action`
GROUP BY `id_member`
ORDER BY count( * ) DESC
LIMIT 0 , 30

Then I went down the list.  The two users with the most entries (4k & 5k) have the same problem.  The 3rd user has 1359 entries and his still works.

I'll look into crafting a delete query on those two problematic users and delete from smf_helpdesk_log_action back to the end of the year just for them.

Nothing in the logs.

I decided I'd purge the help desk action log up to the beginning of the year, to rid the system of the offending entry, and I can't recall now if that's possible.  The action log has a [Empty out the entire log] option, but nothing to do a partial date based purge.  Does anyone recall if a date based purge option is in there?

There's a good chance, I believe, that this WSOD on my log is a size issue.  I've got a TON of entries.  Many x times more than anyone else.

I've been getting WSOD's on my ticket log page...

https://www.xyz.com/helpdesk/index.php?action=profile;area=hd_actionlog

But if I look at the same tickets via the main log, sorted by username, it works OK.

https://www.xyz.com/helpdesk/index.php?action=admin;area=helpdesk_info;sa=actionlog;sort=member;asc;start=17100