0
Undo
Votes
I have updated my site to Joomla 3.10.11 with JEvents 3.6.43, JEvents - Event Notifications and Messages 3.6.2, Managed Locations 3.7.9.
After the upgrade, events display as expected and using the adminstration back end I am able to add and edit events as expected. However when I try to add an event through the front end, by clicking the 'Add Event' link on my calendar page, I get an error message "Error: 0 Serialization of 'Closure' is not allowed". I have logged out of the user account, cleared the server cache and cleared by browser cache to no effect.
The site is a community association that expects members of the community to be able to post events to the site to promote their activities. But I need to be able to keep the site up-to-date for all the usual reasons.
After the upgrade, events display as expected and using the adminstration back end I am able to add and edit events as expected. However when I try to add an event through the front end, by clicking the 'Add Event' link on my calendar page, I get an error message "Error: 0 Serialization of 'Closure' is not allowed". I have logged out of the user account, cleared the server cache and cleared by browser cache to no effect.
The site is a community association that expects members of the community to be able to post events to the site to promote their activities. But I need to be able to keep the site up-to-date for all the usual reasons.
Can you temporarily enable Joomla debug mode and try again - it should give you more context of what the error is and where it arises. My guess is that its to do with Joomla caching (which uses serialisation) its hard to know for sure without the full context.
JEvents Club members can get priority forum support at the Support Forum. As well as access to a variety of custom JEvents addons and benefits. Join the JEvents club today!
Done. This is what I see when I click on 'Add new event' on my calendar page.
Serialization of 'Closure' is not allowed
.../libraries/src/Cache/Cache.php:664
659 foreach ($headnow as $now => $value)
660 {
661 if (isset($options['headerbefore'][$now]))
662 {
663 // We have to serialize the content of the arrays because the may contain other arrays which is a notice in PHP 5.4 and newer
664 $nowvalue = array_map('serialize', $headnow[$now]);
665 $beforevalue = array_map('serialize', $options['headerbefore'][$now]);
666
667 $newvalue = array_diff_assoc($nowvalue, $beforevalue);
668 $newvalue = array_map('unserialize', $newvalue);
I have seen this type of error before (a LONG time ago) and it is usually caused by a plugin pushing a reference to a PHP closure into something that Joomla tries to cache, JEvents doesn't use closures in this way so its likely to be a plugin of some sort on your site.
Are you able to disable the non-core system and content plugins and re-enable them one at a time to find the problem? If we can identify the cause we can either implement a workaround or I can give you advice on what to ask the developer to do to resolve the problem
Are you able to disable the non-core system and content plugins and re-enable them one at a time to find the problem? If we can identify the cause we can either implement a workaround or I can give you advice on what to ask the developer to do to resolve the problem
JEvents Club members can get priority forum support at the Support Forum. As well as access to a variety of custom JEvents addons and benefits. Join the JEvents club today!
Is the extension up to date- I know that Zoo is no longer being developed? If it is up to date you will need to contact YooTheme to ask for advice on how to stop this closure being added to the head data.
JEvents Club members can get priority forum support at the Support Forum. As well as access to a variety of custom JEvents addons and benefits. Join the JEvents club today!
- Page :
- 1
There are no replies made for this post yet.