After installing the dev versions (not published yet) of Radix and Sizzle it has become impossible to run cron from within the site or to do a manual check, the following is shown:

"Er is een AJAX HTTP fout opgetreden. HTTP-resultaatcode: 200 Debug informatie volgt. Pad: /restaurant2/batch?id=23&op=do Statustekst: OK Antwoordtekst: {"status":true,"percentage":"55","message":"Controle of updategegevens beschikbaar zijn ...\u003Cbr \/\u003EDe beschikbare updategegevens voor \u003Cem class=\u0022placeholder\u0022\u003EPanopoly Config\u003C\/em\u003E zijn gecontroleerd."}

Fatal error: Call to undefined method panels_display::__set_state() in /home/deboezer/public_html/restaurant2/profiles/restaurant/modules/contrib/features/features.export.inc(748) : eval()'d code on line 135"

In status report the following is shown:
Notice: Undefined index: value in theme_status_report() (regel 2602 van /home/deboezer/public_html/restaurant2/modules/system/system.admin.inc).

When running cron the following is shown:
Fatal error: Call to undefined method panels_display::__set_state() in /home/deboezer/public_html/restaurant2/profiles/restaurant/modules/contrib/features/features.export.inc(748) : eval()'d code on line 135

Comments

eljay created an issue. See original summary.

shadcn’s picture

Does this error still occurs if you use the stable versions of Radix and Sizzle?

shadcn’s picture

Status: Active » Postponed (maintainer needs more info)
eljay’s picture

I've tried to uninstall Radix and Sizzle as admin in appearance, but Sizzle cannot be uninstalled. Then on the server side I replaced both Radix and Sizzle with the new versions, but to no avail. And still the same error appears:

Fatal error: Call to undefined method panels_display::__set_state() in /home/deboezer/public_html/profiles/restaurant/modules/contrib/features/features.export.inc(748) : eval()'d code on line 158

I also installed the new version of open restaurant-7-01, which goes with the standard install, but NOT with the demo install. Then either replaced the DB with the production DB or imported the production DB in the new DB. In both cases the WSOD with the same error.

Please advice, as I am unable to clear the cache, run cron or run features.

Thanks in advance

shadcn’s picture

Are you seeing the fatal error on all pages?

eljay’s picture

Yes, it is on all pages at the bottom.

shadcn’s picture

Are you still seeing this error?

eljay’s picture

I replaced this version with the latest one. I could not transfer the data in the DB because then the error kept coming back. So I'm rebuilding the site.

shadcn’s picture

Marking this as fixed. Please reopen if not. Thanks.

shadcn’s picture

shadcn’s picture

Status: Postponed (maintainer needs more info) » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.