Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 Calendar not showing - fatal error allowed memory..... | Event Espresso - Staging Server
I recently upgraded wp to 3.5.1 – and all of the plug-ins. Now using EE 3.1.30.7p and EE Calendar 2.0.4. Everything seems fine, except that the calendar page throws this error message instead of showing the calendar:
Fatal error: Allowed memory size of
134217728 bytes exhausted (tried to
allocate 28915 bytes) in
/home/betalefo/public_html/wp-
includes/formatting.php on line 238
I had also had an issue with genesis simple sidebars plugin which shut me out of the admin panel – but that has been resolved and the calendar issue had shown up prior to that. Site is betalef.org. Not sure what you mean about registration page – admin panel is betalef.org/wp-admin
I am currently on the learning curve (probably a good example of a little bit of knowledge being a dangerous thing) – so please don’t ask me to do anything fancy. :)
Can you go to edit the page that normally displays the calendar and edit the calendar shortcode? You could try changing the shortcode to say something like:
[ESPRESSO_CALENDAR show_expired=”false”]
This will reduce the amount of memory that the calendar uses if there are a lot of old events from the past in the system.
The shortcode won’t (or shouldn’t) affect the category colors one way or another. This setting on the Calendar Settings page does, however.
Check to see if this is set to yes. If it isn’t, then that’s probably why the colors aren’t showing up.
Viewing 3 reply threads
The support post ‘Calendar not showing – fatal error allowed memory…..’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.