Skip Menu |

Thanks for taking the time to report a bug in Spreadsheet-ParseExcel. You should be aware that each and every module available through CPAN is free software and that its author is a volunteer. Because of this, there's no guarantee that your issue will be dealt with immediately. There are a few things you can do to help make sure that your issue gets the attention it deserves:

Try to include any information you think might help the developer isolate, reproduce and fix your problem.

This is a public bug tracking system. Any information provided in this system (such as your phone number in your email signature) will be public and indexed by search engines.

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Spreadsheet-ParseExcel CPAN distribution.

Maintainer(s)' notes

If you are reporting a bug in Spreadsheet::ParseExcel here are some pointers

1) State the issues as clearly and as concisely as possible. A simple program or Excel test file (see below) will often explain the issue better than a lot of text.

2) Provide information on your system, version of perl and module versions. The following program will generate everything that is required. Put this information in your bug report.

    #!/usr/bin/perl -w

    print "\n    Perl version   : $]";
    print "\n    OS name        : $^O";
    print "\n    Module versions: (not all are required)\n";

    my @modules = qw(

    for my $module (@modules) {
        my $version;
        eval "require $module";

        if (not $@) {
            $version = $module->VERSION;
            $version = '(unknown)' if not defined $version;
        else {
            $version = '(not installed)';

        printf "%21s%-24s\t%s\n", "", $module, $version;


3) Upgrade to the latest version of Spreadsheet::ParseExcel (or at least test on a system with an upgraded version). The issue you are reporting may already have been fixed.

4) Create a small example program that demonstrates your problem. The program should be as small as possible. A few lines of codes are worth tens of lines of text when trying to describe a bug.

5) Supply an Excel file that demonstrates the problem. This is very important. If the file is big, or contains confidential information, try to reduce it down to the smallest Excel file that represents the issue. If you don't wish to post a file here then send it to me directly:

6) Say if the test file was created by Excel, OpenOffice, Gnumeric or something else. Say which version of that application you used.

7) If you are submitting a patch you should check with the maintainer whether the issue has already been patched or if a fix is in the works. Patches should be accompanied by test cases.

Asking a question

If you would like to ask a more general question there is the Spreadsheet::ParseExcel Google Group.

The quickest way to report a bug in Spreadsheet-ParseExcel is by sending email to bug-Spreadsheet-ParseExcel [at]

If you want to report a bug via the web, you must login with a Bitcard or other account. Accounts are required due to spam. See the login page for details on obtaining and logging in with a Bitcard account.

Be sure to include at least the following information:

Other things that are often helpful:

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

Please report any issues with to