jasonrogena / jasonrogena/php-excel-reader

Excessive Errors In Apache Logs

Open
#101 0 comments 0 reactions 0 assignees View on GitHub
auto-migrated Priority-Medium Type-Defect
Dominant language
PHP
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

```
Created a new 2004 format spreadsheet with a single sheet, 3 columns and 7 rows.

A simple parse of each sheet to print out count of row and column numbers
followed by a call to the dump function.

This short script resulted in 143 'Undefined offset' errors in my Apache logs:

0 in excel_reader2.php on line 397
0 in excel_reader2.php on line 400
cellsInfo in excel_reader2.php on line 383
cellsInfo in excel_reader2.php on line 626
in excel_reader2.php on line 521
in excel_reader2.php on line 524
in excel_reader2.php on line 527
in excel_reader2.php on line 530

All seem to be array out of bounds issues but I can't track it down any further.

Have tried to put plenty of tracking information but can't work out what is
happening.

Anyone else seeing this? Any bright ideas?
```

Original issue reported on code.google.com by `asanyful...@gmail.com` on 5 Dec 2010 at 10:02

Attachments:
- [wibble.xls](https://storage.googleapis.com/google-code-attachments/php-excel-reader/issue-101/comment-0/wibble.xls)

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the report with the attached wibble.xls and the described single-sheet, three-column, seven-row input. Start by tracing the accesses reported in excel_reader2.php on lines 383, 397, 400, 521, 524, 527, 530, and 626. Done means identifying why the 143 undefined-offset errors occur and preventing them for this input.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.