Dll

+Clients
  • Content count

    628
  • Joined

  • Last visited

1 Follower

About Dll

  • Rank
    Community Regular
  • Birthday

Recent Profile Visitors

17,752 profile views
  1. Ehren designs come great themes, one of which we've been using for over a year now. His support is also excellent, so I'd highly recommend his services.
  2. Dealing with reports in their current form is more laborious than it needs to be, as the redirects after taking any action are quite unhelpful. For instance, if you go into a report, and click to hide or edit the post, after taking that action it then redirects you to the hidden post, leaving the report marked as new. Ideally I think it should leave you in the report screen or give an option to mark the report as complete once the action has been taken. Also, it would be useful to have posts which have been reported marked up within threads in some way, perhaps with inline tools to mark the report as in progress or complete. Thanks
  3. Or maybe I should hope they revisit their decision and recognise it was an odd one, since I'm not sure that *if* it is actually working as intended, it's been thought about very much.
  4. Thanks for the definition. But of course the opting in part of writing a status update would generally be the act of typing a status update. So not sure why it would need an additional action to do that, hence my view that no-one would really intend for it to work in that way.
  5. Surely this is some sort of bug, as I can't see any reason for it not to be enabled by default? What next, new users having to go into their profiles and activate something when they want to post?
  6. It would be useful to have a deselect button in the moderation toolbar which loads on the bottom of the screen, as if you select posts but for whatever reason don't take action, they're then left selected and the moderation toolbar loads every time you revisit the thread. If that thread happens to be busy, it's a time consuming and annoying process to try to find the posts again to deselect them manually.
  7. They could be just like that without any changes to the way they're submitted, it just requires the organisation and the will to make sure someone takes responsibility every day for checking bugs, responding to them, then prioritising and scheduling the work which needs to be done to fix them. Rather than this ad hoc, mark as pending and forget system that we appear to have now. All the fiddling around the edges of the format and who can view bug reports etc etc etc doesn't change the fact that ultimately action needs to be taken to fix bugs in a more timely and co-ordinated manner than it is now. It's not rocket science when it boils down to it.
  8. Triaging and prioritising the bug reports properly would help solve this problem too, rather than putting all of the onus on customers to use the bug reports/tickets as you expect them to. Regardless, though, I don't think anyone here is saying all reported bugs should be sorted within the same time frame as a ticket raised for a show-stopping type problem. But equally, there ought to be no reason a bug is just marked as pending and left sitting with no response for months and months, even if it is a low priority, and too often that is what happens. The sorts of issues in there maybe aren't major, but they're not just tiny things like something not lining up correctly either, and deserve more attention than they're getting.
  9. I agree with this. I don't know if other people do the same, but before raising a ticket about a problem I've seen, I'll tend to check the bug reports, forums etc to see if someone else has reported the problem. If they have then I won't raise the ticket, as I'll assume that the bug report is being looked into and that there's a reasonable likelihood that if others are having the same problem, someone else may have raised a ticket as well. On top of this, and perhaps it's just me, but I'll also tend to test things against a clean install when trying to figure out a bug, and again if it's clearly not just limited to my install, then often I'll post it as a bug rather than just raise a support ticket. Perhaps wrongly I assumed this is a more helpful way of raising bugs as it's public so, in theory it stops duplicates, and helps to save on multiple tickets being raised for the same thing. What I really don't understand is the message being given out that for some reason if I raise the identical problem as a ticket as was raised in a bug report, it'll be looked into faster. Why? Is it really the case that if I go and find a bug report posted and marked as pending months ago, and raise it as a ticket, it'll be fixed straight away for me?
  10. Then why have public bug reporting at all? I assume you recognise how bad it looks when someone takes the time to report a bug to you and it's ignored for months? (Or worse closed without being fixed, which is another fairly regular occurance). You can't have it all ways, either have the bug reports and look after them, or don't. You can't have them, ask people to use them but then ignore lots of them and expect people not to see that and draw negative conclusions from it.
  11. Equally, there are some who report bugs which are problematic only to have them marked as pending and left for months. Not important to you perhaps, but moreso to others, and a poor reflection on yourselves.
  12. Thanks for the suggestion @americanwx, sounds a worthwhile temporary fix. On IPS's part, I think it's quite embarrassing that this has been overlooked for so long, despite the countless threads and bug reports.
  13. Except for virtually every other single release of the 4.1 series. And I thought we were suppose to ignore the bug tracker as most bugs are fixed through tickets? It's not possible to have it all ways, and I don't know which commercial products you're using Charles, but most I've seen do offer some sort of change list or info on the major bugs that have been fixed.
  14. Ignoring that part of the question then, how are decisions on what's added/removed from the feature set made though? I understand feedback is taken into account etc, but from the outside looking in it seems like maybe the developers are driving change, not maybe with what they think is useful or not, but what from a coding perspective makes more sense, or maybe is simpler. Not saying that's wrong as you can't spend weeks making a tiny piece of functionality work when time is better spent elsewhere. But from a user experience point of view it's not ideal, as it just appears that useful features are removed without much or any logical reasoning?