# Import History page throws fatal error once any import has been logged (v30.0.02, still in main)

**URL:** <https://ask.gibbonedu.org/t/import-history-page-throws-fatal-error-once-any-import-has-been-logged-v30-0-02-still-in-main/15613>\
**Category:** Developers\
**Created:** [November 16, 2026, 8:51pm UTC](https://ask.gibbonedu.org/t/import-history-page-throws-fatal-error-once-any-import-has-been-logged-v30-0-02-still-in-main/15613 "2026-11-16T20:51:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tiekubd](https://ask.gibbonedu.org/user_avatar/ask.gibbonedu.org/tiekubd/32/163_2.png) [@tiekubd](https://ask.gibbonedu.org/u/tiekubd)\
**Post date:** [November 16, 2026, 8:51pm UTC](https://ask.gibbonedu.org/t/import-history-page-throws-fatal-error-once-any-import-has-been-logged-v30-0-02-still-in-main/15613/1 "2026-11-16T20:51:03Z")

</div>

Hi @sandra and @Ali

I came across a small bug in **System Admin \> Import From File \> Import History**. As soon as there’s at least one import in gibbonLog, the page shows the generic “Oh no! Something has gone wrong” error.

The cause is in modules/System Admin/import\_history.php. The array\_map closure calls $logGateway-\>getLogData(), but $logGateway isn’t included in the closure’s use list, so it’s undefined inside the function:

> $logsByType = array\_map(function ($log) use (&$importTypeList) {
> 
> ```
> $log\['data'\] = $logGateway->getLogData($log\['serialisedArray'\] ?? '');
> 
> ```

The fix is a one-line change:

> $logsByType = array\_map(function ($log) use (&$importTypeList, $logGateway) {

I’ve patched it locally on a v30.0.02 site and the page loads fine now. It’s still present in main as of this week. Would one of you be able to pick it up in a PR?

Thanks,  
Tieku

---

<div class="post-metadata">

**Author:** ![sandra](https://ask.gibbonedu.org/user_avatar/ask.gibbonedu.org/sandra/32/5_2.png) [@sandra](https://ask.gibbonedu.org/u/sandra)\
**Post date:** [November 16, 2026, 11:49pm UTC](https://ask.gibbonedu.org/t/import-history-page-throws-fatal-error-once-any-import-has-been-logged-v30-0-02-still-in-main/15613/2 "2026-11-16T23:49:55Z")

</div>

Hi Tieku, thanks for the heads up, I’ve [applied a fix here](https://github.com/GibbonEdu/core/commit/14992c405f0f502377fbf7bd448f90ccf42e6da3) and it will be part of v30.0.03, which will be released in the coming week.
