FireFox won't go to the bug report website.
in The Commons
I tired to delete this light group from my scene so I could try a different one, but as soon as I select it, DS4.9 latest version will crash immediately. So I followed the instructions and created a bug report, but now I can't submit that because Firefox won't go to the website because it said the website wasn't created properly and may not be safe. (I can't remember exactly what the wording was.) Has anyone else ever had that happen?
I submitted a help desk ticket then and attached the bug report. Not sure if that will get it to the right place or not.

Comments
You just report the bug in a standard ticket. The is no special website for it anymore.
There is nothing wrong with the site...just the link. It is the modern paranoia over redirects (somewhat justifiable).
..the original Manits site was so much more efficient particularly if you were experiencing an issue that others were as you could just add a note/comment to an already filed ticket instead of having to write one up from scratch. I would also think it would simplify the process for teh development team as instead of having a bunch of tickets on the same topic to sift through, there theoretically would be only need to be one if people checked the ticket database before posting to see if what they were dealing with was already written up.
You could also see the status/progress of tickets as well .
The inability to add comments to other people's bug reports is a problem, but I think the biggest problem they had with two separate systems is having people using the wrong one, particularly using the bug reporting system to report customer support issues. With one system, customer support triages what's appropriate to go to QA/development.
And you can see the progress of your own tickets.
Yes, but (after the most recent page design change) this is only accessible if you click on a link in a drop-down menu (your name in the top corner) that doesn't seem to be a menu at all.
What is it with "modern" web design philosophies constantly hiding everything? When this change came through, it took me a while to work out that yes, I could after all still look at all of my old support tickets. It's even worse when Support totally misreads what you thought you'd written clearly and abruptly closes your ticket — the link to re-open it is similarly hidden.
I filed a complaint about that stupid drop-down setup. No change planned.
There's only so much that can fit on a seven inch screen(or more like a 4.5" one)...
...bottom line, we need the Mantis site back.
Let customer support be handled through the Zendesk and bug reports/technical issues handled in Mantis. Very simple, it's not bloody rocket surgery.
Except that people would file customer support issue in Mantis and bug reports with customer support. Doing it this way ensures that only genuine developer issuse are passed to the developers while CS gets all CS issues immediately.
Doesn't that happen anyway when someone uses the wrong option in the "Department" drop-down? I can't see that there'd be much effective difference; the ticket still gets delayed until it's redirected to the proper place.
And there's still the issue of the redesign being opaque, clunky, and with fewer features. I've been using the various DAZ help systems for over ten years now, and this one is by far the worst for usability.
...nothing a little "education" on the main help page couldn't fix. Just mention say, "Bug Reports and Technical Support: click on to Mantis Site Icon". "CS/Store/Purchase issues: Click on Zendesk Site Icon."
First people need to work out what is a bug and what is not.