madshi.net

My previous comment (including the question and suggestions) still stands as a reply to your new problem.

Thanks for confirming this.

Sorry to resurrect this.. :oops: I'm having another fatal and vague "has stopped working" crash in other software now. No bugreport and the system event log doesnt provide more details. I have the bug narrowed down to networking code using WinSock2 (ws2_32.dll) since this was moved into th...

i'll post insights on resolving this

This problem seems to have resolved itself after a Windows 10 update back in 2015.

So madExcept sends bugreports to mantisbt and that works fine, but not since i tried upgrading to mantisbt 2.0.0 I looked into what goes wrong .. because madexcept does not understand a 302 redirect i tried using a mod_rewrite redirect on the server, but that does not seem to pass path_info to manti...

I had the same problem (302 not supported by madexcept) after upgrading MantisBT;
viewtopic.php?f=4&t=27945&hilit=302+301

Thanks for your thorough yet fast answer. Reason 1 seems probable, if only because the uxtheme.dll seems to be a part of Windows so its very possibly loaded before my application. I'll try your suggestions, and i'll post insights on resolving this here if only for posterity / others having such a pr...

Obtained via Event Viewer Local > Windows Logs > Application: Windows 10 crash event 1: Log Name: Application Source: Application Error Date: 10/27/2015 2:46:15 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: DESKTOP-FPIG4PK Description: Faulting application...

First, I’d like to point out we are happy with MadExcept. :) I just encountered something, I wonder if madExcept should/could intercept this. This crash is reproducible (random, odds 1/10) by dragging my application to dock to the screen sides in a Windows 10 VM. There appears a “QLedText has stoppe...

First off, i'm fine with this not being fixed. I understand its not as simple and quite disruptive. I'm all for keeping madExcept nimble and -above all- stable. :) And since you ask - yes an URL change is never likely, but they do occur.. for example when upgrading Mantis and having the version in t...

Thanks for looking into this. Indeed it would make sense to never change the URL .. if possible :) As it stands now, i am OK with madExcept not redirecting. By now, the user impact is minimal, according to my metrics. The only users impacted are those with internet, yet (for some reason) did not upd...

The old host still does a "HTTP 302 Temporary Redirect" to this new URL. I expect that to go offline in a few months.

For your convenience i forwarded my email with MES file again, and will add the old link.

Has there been any progress on this? I am about to pull the deprecated mantis installation, that also hold the test account for you. A .htaccess illustration for future reference: RewriteEngine On # madExcept upload works (the rewrite happens behind the scenes) RewriteRule ^mantisbt-1.2.14/(.+)$ man...

Well, I'd need to be able to reproduce the problem somehow, in order to fix this... Can you confirm what scenarios would cause multiple bugreports to be appended, or is this not supposed to happen at all? I am under the impression that this is a feature that stashes bugreports until sent successful...

OK i just emailed you a MES file.

Thanks for looking into this.

Let me know if there's more i can do to help fix this for future madExcept versions.
I am impacted anyway.. if autoupdate does its job i may be able to stop the manual workaround in a month or so.

I know of no other way to have madExcept (in our currently distributed applications) use the new URL..
Suggestions welcome. Have MantisBT connect to the new host database is not an option.

So for now i'll keep the old site up and manually recreate any significant report on the new site.