Messages

  Entire forum

Auto Light Dark

English

Not in the core, there was never any design need for it. Doing it... it's not especially easy to do.

The file you sent here clearly says version 2.0 RC1. And honestly, I don't care what edits it did or didn't make. Not everything in SimpleDesk is done with edits, an awful lot of it is handled with hooks, which don't make edits.

The file you linked, ManageSettings.php does not have the hook facilities, so no, it won't work. There's no call to call_integration_hook, which means SimpleDesk won't appear. You will notice that on your list, there is no edit being made to ManageSettings.php - because no edit should be made.

Your ManageSettings.php is woefully out of date. It's probable other files are too. Try doing the version check in the admin panel, I suspect other files will report the same issue as ManageSettings.php will: that it's out of date.

That's impressive. You managed to install it on a version of SMF that's FAR too old for it to work.

The installer should have flat out told you it wouldn't work. In fact, the installer should have failed on multiple counts if you're really on SMF 2.0 RC1. It was built during RC2 and RC3 and makes use of features only in RC4 and RC5 onwards and only works properly on 2.0.0 through 2.0.7.

If you really are on 2.0 RC1 you need to upgrade as a matter of priority to fix the 50-odd known security issues in your version of SMF. (Between 2.0 RC1 and current, there's 2.0 RC1-1, 2.0 RC1.2, 2.0 RC2, 2.0 RC3, 2.0 RC4, 2.0 RC5, 2.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.0.5, 2.0.6 and currently 2.0.7)

I'm not sure explaining yourself was going to make any difference.

Without a subject, things just will not work properly in the system. Lots of things will break down. It was simply never designed to ever function without tickets having subjects.

For hacking or swearing, that almost sounds like a job for different departments rather than anything else.

The staff member creating a ticket thing? That's easy to explain. There are times I create a ticket that I know needs resolving but it's not ultimately down to me to resolve. There are times my colleagues add a ticket based on customer feedback that will ultimately be passed to me to resolve. It's just a slightly different usage model to yours.

As for changing the urgency levels, showing me is not going to change a thing. The system was NEVER designed to cope with the changes you're asking and please believe me when I tell you that I know the problems associated here. It is a fundamental design flaw that urgency isn't customisable, it can't be fixed without starting from scratch, like many other things.

SimpleDesk was built primarily for Simple Machines' own website use, to replace the creaky one they had, and so many of its behaviours are driven because of that, and not in a good way.

Trust me, you can't just simply comment out the definitions and hope it'll go away because it WILL break things if you try stunts like that.

I should know. I built the bleh thing. All of this is my fault.

Yeah, the code is sufficiently unchanged since the RC days in those areas that it should work fine.

You can change the names in the language files easily enough but changing it so there are more than 6 or less than 6, or altering the balance of 'more serious' (which is permission driven, of course)... ain't gonna happen.

Associating custom fields with urgency levels, would require major overhauls to the guts of both subsystems. Can't really envisage a situation where that would make much sense, actually.

Removing subject completely? No.

Completely different problem. In your case you should be using UTF-8 throughout the forum as the pound sign wouldn't work properly in the main forum either.

Not without a major rewrite and a large performance hit.

Not without a rewrite of a lot of the system, and that isn't going to happen.

There are no known issues with SimpleDesk working on PHP 5.3 or 5.4.

There have never been any reports of security issues with SimpleDesk in its 4 year history.

It should run on any SMF 2.0.x version.

To implement this kind of visibility would require a complete redesign of the guts of SimpleDesk as well as substantially raise the risk of someone accidentally misconfiguring things and making things less private than they should be.

Are you posting a new ticket from within a department (in which case you may need to reselect the department to trigger the fields being displayed, which should also keep the values between posts)

It would have to be implemented from scratch because there's no way to do this in SimpleDesk currently.

Also note you should update to 2.0.6 which was released today Same deal as before, though, won't affect SD.

I would still update it. It should not break anything.

While in your case I would consider the risk low, it is not non existent.