Various issues, crashes, bugs can arise while testing beta snapshots of PHPEdit, as well as ideas that you would like to get implemented in future builds. To help us manage these issues the more efficiently possible, please make sure to follow the following instructions.

Exception handler

PHPEdit can recover for most of the errors that can happen and offers you to send the report to us to try and fix the issue.

You can see in the bottom tabs the different contents that will be included in the report, and select which ones you want to include or exclude.

Make sure to enter your email in the "Me" tab, that way the report will be associated to you, and you will be able to edit it online, give feedback on the problem, etc...

You can also use the "Save as..." button to save the report on disk if you get trouble sending it.

Once you selected what you want to include in the report (PHPEdit remembers the choices if the crash is not too severe), you can decide what to do with it and if PHPEdit should continue.

You can select one from three different handlings of the report:

You can either have PHPEdit send it to our servers now, or store it in your profile directory for later, or just disregard it.

Click then on one of the possible continuations: "Continue" to ignore the error and continue PHPEdit, "Restart" or "Stop".

Freeze handler

PHPEdit also monitors its own activity and detects when it becomes unresponsive for a certain period of time. In that case, you will get a dialog similar to the exception handler, that will offer you to send us the report.

Note that sometimes you will get this dialog in case of a system wide slowdown: for example if you start PHPEdit as well as other applications just after your computer booted you might get this message before PHPEdit finishes loading.

Standard error handler

Sometimes PHPEdit is unable to recover from a crash and the system standard error handler catches the error, and you get this dialog:

In that case, please click on the "Details" button, select all the error message and create a new issue on our bug tracker with it, and with comments if you have any informations. (See below for informations about posting on the bugtracker).

 

 

 

Submitting a bug (non crash) or feature request

Using the integrated dialog

You can find in the "Help" menu a "Submit bug report/feature request" command. It will show you a dialog that will allow you to quickly submit an issue to us without having to leave the IDE:

Select the kind of report: Bug or feature request.

Enter a title describing the problem/request. The title should be enough to understand what the problem or request is, without having to read the details. It shouldn't just be a category. For example:

• FTP -> BAD
• FTP doesn't work -> BAD
• FTP explorer can't connect through a proxy -> GOOD

Enter details if you have more informations, for example steps to reproduce the issue, etc...

Only one bug or feature request per report! Please try to report problems one at the time, even if it's in the same "category", because they can have completely different implications and resolutions, and we might be able to solve one very quickly, but need more time and feedbacks for the other.

Don't assume we can reproduce your bug! Very often we won't be able to reproduce the bug you are having, even if it seems very reproducable to you. It can be specific to your system, or to your configuration, or to the particular way you are using the tool. So please avoid writing reports like: "Click on that button and see the problem". There's a good chance the problem will not happen to us, or if it does, maybe it's not a bug but a feature and we won't see what you believe is a problem. Instead, please describe what happens to you and that you don't expect, and a screenshot always helps for fast comprehension.

Using the bug tracker

All the reports that or sent to us by PHPEdit are automatically imported as new issues on our online bugtracker. As long as you specify your email correctly when you submit an issue, you can manage your issues online, edit them, and you can also submit new ones on the website.

Go to http://issues.waterproof.fr/ to access the website and log in with the same credentials as on the www.waterproof.fr website, and you can start posting issues.

Sending stored/saved reports

If you choose to store the report for later when you get a exception handler dialog in PHPEdit, the reports are stored in your profile, %APPDATA%\WaterProof\PHPEdit\<>\Modules\StoredReports. You can either send them manually or have PHPEdit send all of them automatically.

• To send them manually, just attach them to an email addressed to wit-import-phpedit3@waterproof.fr. Don't send anything else than .zip reports generated by PHPEdit to this address. It is retrieved by an robot that discard other messages. Don't send your .zip reports to an other address, and don't create an issue directly in the bugtracker attaching the .zip. The zip report needs to be processed by this robot, some parts need to be decrypted, and it also manages duplicates automatically to save us some time.
• To have PHPEdit send them automatically, just click on the "Send stored reports" in the "Help" menu.

Nothing works

It these tools don't work as expected, it doesn't send report, you can't login, etc..., don't hesitate and contact us directly at support@waterproof.fr or at one of our addresses and explain the situation.