Most support issues require a lot of information, as we have to deal with external stuff and many variable options and site setups.

We need some debugging information to speed up analysis of bug reports and half-time of support requests.

- Installed editors (similar to the current installation instructions)
- Contents of the wysiwyg module directory (to see which editor folders are there)
- Status of JS and CSS aggregation performance settings of Drupal
- Scan page.tpl.php for existence of print $closure;
- Client-side browser/user agent information
- Server-side OS information
- Export of all configured profiles
- Export of all configured input formats, including filter configuration
- List of enabled modules
- jQuery version

This information is unnecessary for the user, I'm thinking of a text file export like in my patch in #99529: Add text file export of status report.

Comments

blockedmind’s picture

Priority: Normal » Critical

.

sun’s picture

I've taken over http://drupal.org/project/debug to get this done (once for all contrib).

sun’s picture

Project: Wysiwyg » Debug
Version: 6.x-1.x-dev » 6.x-2.x-dev