|
mzerihoun
|
August 6, 2012 at 7:58 am
This is proberbly super duper easy for you with php-knowledge so plz help me before I go mad…
On my event listing page only one event shows and the follwing text. Exactly what is missing in line 88?
Fatal error: Call to undefined function espresso_show_social_media() in /home/bloggcoa/public_html/wp-content/uploads/espresso/templates/event_list_display.php on line 88
-
Grateful for all help!
-
🙂
-
maira
-
This topic was modified 12 years, 3 months ago by
 Josh. Reason: moving to correct forum topic category
|
|
Josh
|
August 6, 2012 at 8:02 am
Hi Maira,
You can remove line 88 of /wp-content/uploads/espresso/templates/event_list_display.php or rename the /wp-content/uploads/espresso/templates folder to /wp-content/uploads/espresso/templatesOLD so the updated Event Espresso templates can load.
The above error is caused by having out of date template files (from a previous version) in the /wp-content/uploads/espresso/templates/ directory. If you have modified templates in that location, they need to be updated to the new template files included with the current version of the plugin. If you haven’t made any modifications to the templates, these can be removed. If you are not sure if there were modifications made to these files, back these up or rename that folder just in case.
|
|
Visual Artists Guild
|
August 13, 2012 at 2:31 pm
I’m getting the same error on a different page (renaming uploads/templates did NOT help, it made it worse!):
[Mon Aug 13 15:57:08 2012] [warn] mod_fcgid: stderr: PHP Fatal error: Call to undefined function espresso_show_social_media() in /home/rcvag/public_html/wp-content/uploads/espresso/templates/registration_page_display.php on line 25
Please help?!?
|
|
Josh
|
August 14, 2012 at 7:47 am
The error indicates that the /wp-content/uploads/espresso/templates directory is still intact. The uploads/templates directory is not the directory that Event Espresso looks for, it’s /wp-content/uploads/espresso/templates.
You can also remove the /wp-content/uploads/espresso/templates/registration_page_display.php file from this directory, and this will force Event Espresso to load the template that is included in the plugin directory.
|
|
Visual Artists Guild
|
August 15, 2012 at 3:28 pm
Sorry the typo in the path, it was the /wp-content/uploads/espresso/templates directory that I tried renaming but that created an endless loop error that was ugly. The only thing that worked (for me) to make the current ongoing event registration pages show up properly again after the recent update was to comment out the calls for espresso_show_social_media() in /wp-content/uploads/espresso/templates/registration_page_display.php
To prevent future errors with updates, do we need to rename/remove the /wp-content/uploads/espresso/templates/ directory and recreate events that were created before the recent EE update?
|
|
Chris Reynolds
|
August 15, 2012 at 4:01 pm
You don’t need to recreate events. This issue is coming from an older version of the template (either registration_page_display.php or event_list_display.php) using a function (espresso_show_social_media) that is deprecated and has been remove from the plugin in favor of this method:
do_action('espresso_social_display_buttons', $event_id);
So you have several options in how to deal with the issue:
1 – Remove the templates from /wp-content/uploads/espresso/templates — Do this if you have not made any customizations to any of the template files (the two mentioned above, in particular).
2 – Remove the line referenced in the error (which may be different depending on the file that’s listed — Do this if you have made modifications to your template files but are not using the Social Media Buttons add-on.
3 – Replace the line referenced in the error (do a search for espresso_show_social_media) with the one I posted above (that starts with do_action) — Do this if you have made modifications to the template files and you are using the Social Media Buttons add-on.
|
|
Visual Artists Guild
|
August 15, 2012 at 7:59 pm
Ok, that makes sense (at least, I think I finally understand now ;)) and EE appears to be working well on our website now. Thank you Josh and Chris so much for your help with this issue!
|
