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
Comment #2
shadcn CreditAttribution: shadcn commentedDoes this error still occurs if you use the stable versions of Radix and Sizzle?
Comment #3
shadcn CreditAttribution: shadcn commentedComment #4
eljay CreditAttribution: eljay as a volunteer commentedI'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
Comment #5
shadcn CreditAttribution: shadcn commentedAre you seeing the fatal error on all pages?
Comment #6
eljay CreditAttribution: eljay as a volunteer commentedYes, it is on all pages at the bottom.
Comment #7
shadcn CreditAttribution: shadcn commentedAre you still seeing this error?
Comment #8
eljay CreditAttribution: eljay as a volunteer commentedI 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.
Comment #9
shadcn CreditAttribution: shadcn as a volunteer and at Chapter Three commentedMarking this as fixed. Please reopen if not. Thanks.
Comment #10
shadcn CreditAttribution: shadcn as a volunteer and at Chapter Three commentedComment #11
shadcn CreditAttribution: shadcn as a volunteer and at Chapter Three commented