Title: Fatal error in 2.1.0 Last modified: August 22, 2016 --- # Fatal error in 2.1.0 * [Sybre Waaijer](https://wordpress.org/support/users/cybr/) * (@cybr) * [11 years, 7 months ago](https://wordpress.org/support/topic/fatal-error-in-210/) * Fatal error: Call to undefined function genesis_html5() in ***/wp-content/plugins/ genesis-simple-edits/plugin.php on line 102 * On websites not running genesis in a multisite environment. * [https://wordpress.org/plugins/genesis-simple-edits/](https://wordpress.org/plugins/genesis-simple-edits/) Viewing 15 replies - 1 through 15 (of 28 total) 1 [2](https://wordpress.org/support/topic/fatal-error-in-210/page/2/?output_format=md) [→](https://wordpress.org/support/topic/fatal-error-in-210/page/2/?output_format=md) * Thread Starter [Sybre Waaijer](https://wordpress.org/support/users/cybr/) * (@cybr) * [11 years, 7 months ago](https://wordpress.org/support/topic/fatal-error-in-210/#post-5363989) * Fixed it by editing the line from: `'footer_output' => genesis_html5() ? $footer_html5: $footer_xhtml,` * To: * `'footer_output' => function_exists('genesis_html5()') ? $footer_html5 : $footer_xhtml,` * Enjoy! * [Afrophire Magazine](https://wordpress.org/support/users/afrophire-magazine/) * (@afrophire-magazine) * [11 years, 7 months ago](https://wordpress.org/support/topic/fatal-error-in-210/#post-5363998) * I’m receiving the same error message and am unable to access the dashboard or anything else. Is there any way to fix this? * Fatal error: Call to undefined function genesis_html5() in wp-content/plugins/ genesis-simple-edits/plugin.php on line 102 * My site is afrophire.com. * [Afrophire Magazine](https://wordpress.org/support/users/afrophire-magazine/) * (@afrophire-magazine) * [11 years, 7 months ago](https://wordpress.org/support/topic/fatal-error-in-210/#post-5364005) * Figured it out. I accessed the plugin.php file through hosting and was able to edit the html code. * Plugin Contributor [Ron Rennick](https://wordpress.org/support/users/wpmuguru/) * (@wpmuguru) * [11 years, 7 months ago](https://wordpress.org/support/topic/fatal-error-in-210/#post-5364129) * > On websites not running genesis in a multisite environment. * The plugin requires the Genesis Framework. Whether or not you edit it to eliminate the fatal error it runs on the hooks in Genesis to output the content to the front end of the site. * [jstuartj](https://wordpress.org/support/users/jstuartj/) * (@jstuartj) * [11 years, 7 months ago](https://wordpress.org/support/topic/fatal-error-in-210/#post-5364197) * This bug is effecting Genesis 2.0 sites running older themes that need xHTML theme support enabled. Will there be a update to correct this issue. * Plugin Author [Nathan Rice](https://wordpress.org/support/users/nathanrice/) * (@nathanrice) * [11 years, 7 months ago](https://wordpress.org/support/topic/fatal-error-in-210/#post-5364220) * The fix above actually changes the logic of that line to something other than what is intended. It goes from asking if the child theme supports HTML5 markup, to asking if Genesis 2.0+ is active. * So, I would not recommend that as a fix. * I’m curious about the manifestation of this bug. Are you network activating this plugin? If so, don’t … unless you can be sure that every site in the network will be running a Genesis child theme and you are running the latest version of Genesis. * > This bug is effecting Genesis 2.0 sites running older themes that need xHTML > theme support enabled. * It shouldn’t be. That line is what checks for HTML5/xHTML support. If a child theme is still running xHTML, that line will determine to use xHTML markup instead of HTML5. If you are getting the “undefined function” error, it means that either you’re not using a Genesis child theme, or you are running a version of Genesis older than 2.0. * [WPGoddess](https://wordpress.org/support/users/wpgoddess/) * (@wpgoddess) * [11 years, 7 months ago](https://wordpress.org/support/topic/fatal-error-in-210/#post-5364221) * Hi Nathanrice, we are using an older theme that the newer Genesis does not support– it broke the theme when we tried to upgrade once. There are months of customizations to this very customized website, so obviously my client does not want a complete redesign. Can you just tell us where to get the previous version of this plugin? Thanks. * Plugin Author [Nathan Rice](https://wordpress.org/support/users/nathanrice/) * (@nathanrice) * [11 years, 7 months ago](https://wordpress.org/support/topic/fatal-error-in-210/#post-5364222) * [https://downloads.wordpress.org/plugin/genesis-simple-edits.1.7.1.zip](https://downloads.wordpress.org/plugin/genesis-simple-edits.1.7.1.zip) * [WPGoddess](https://wordpress.org/support/users/wpgoddess/) * (@wpgoddess) * [11 years, 7 months ago](https://wordpress.org/support/topic/fatal-error-in-210/#post-5364223) * Thank you so much, Nathan. That worked like a charm and everything is back just as it was before. :-* * Thread Starter [Sybre Waaijer](https://wordpress.org/support/users/cybr/) * (@cybr) * [11 years, 7 months ago](https://wordpress.org/support/topic/fatal-error-in-210/#post-5364229) * Yes, I must admit it’s a quick and dirty fix. However, I do not want to crash the admin panel of my users after they switch themes when they have the plugin still activated. This simply shouldn’t happen. * I think this bug exists because genesis_html5() will never be called in the whole script, and acts upon the code thinking it should exist. I think a simple code that would create the function genesis_html5() if no Genesis theme is activated. So that’s why I made that function above, which I neither do recommend. * I have network activated the plugin for convenience use, and I see the plugin submenu only rising up when they actually use one of your amazing Genesis themes. So that’s good. * The server I’m running is luckily powerful enough to handle a few hundred sites with “bad” plugins, however, I have never expected something like that from the StudioPress team. * I hope you’ll release a working and updated version of your plugin, with hopefully better support for network activation. This way, we multisite owners can enjoy your product even better in the future without overloading our servers. * Thank you for your hard work and time (to look into this). * PS. I made a (hopefully) better way of solving this, after I looked somewhat deeper into the code (and longer than 5 minutes lol): * line 46, change from: `if ( ! defined( 'PARENT_THEME_VERSION' ) || ! version_compare( PARENT_THEME_VERSION, '2.1.0', '>=' ) ) {` * to: `if ( ! defined( 'PARENT_THEME_VERSION' ) || ! version_compare( PARENT_THEME_VERSION,' 2.1.0', '>=' ) || wp_get_theme(is_genesis_child()) ) {` * I can see in the code that it only determines if the parent theme is version 2.1.0 or bigger. Unfortunately, this is a too narrow of a determination, because many other themes might be using version 2.1.0. * [annalea.avery](https://wordpress.org/support/users/annaleaavery/) * (@annaleaavery) * [11 years, 7 months ago](https://wordpress.org/support/topic/fatal-error-in-210/#post-5364269) * First, let me tell you that I’m a beginner at this kind of stuff and might need some hand holding. I recently tried to change my theme and I got the following error message: Fatal error: Call to undefined function genesis_html5() in /home1/ aelanna/public_html/wp-content/plugins/genesis-simple-edits/plugin.php on line 102 * I cannot access my dashboard or any admin area of my webpage. I see all of the responses above, but I’m not sure how to go about accessing my FTP in order to change the HTML or fix the plugin. That is like explaining the ocean to a well frog. If anyone can point me in the right direction I would be so grateful! my website is [annaleaaveryphotography.info](http://annaleaaveryphotography.info) * Plugin Contributor [Ron Rennick](https://wordpress.org/support/users/wpmuguru/) * (@wpmuguru) * [11 years, 7 months ago](https://wordpress.org/support/topic/fatal-error-in-210/#post-5364271) * @annalea.avery 0 If you have a non-html5 child theme, delete the version you have installed & install the 1.7.1 version (from [https://wordpress.org/plugins/genesis-simple-edits/developers/](https://wordpress.org/plugins/genesis-simple-edits/developers/)). * [annalea.avery](https://wordpress.org/support/users/annaleaavery/) * (@annaleaavery) * [11 years, 7 months ago](https://wordpress.org/support/topic/fatal-error-in-210/#post-5364272) * @ Ron Rennick, the link you gave didn’t go to anything. How do I delete the theme that I installed if I can’t access my dashboard? Do I do that through filezilla? Thanks for the response!! * [iocchelli](https://wordpress.org/support/users/iocchelli/) * (@iocchelli) * [11 years, 7 months ago](https://wordpress.org/support/topic/fatal-error-in-210/#post-5364273) * Add one more to the list of those needed to revert to 1.7.1. * [lizardwebs](https://wordpress.org/support/users/lizardwebs/) * (@lizardwebs) * [11 years, 7 months ago](https://wordpress.org/support/topic/fatal-error-in-210/#post-5364274) * And yet another – on several sites… Viewing 15 replies - 1 through 15 (of 28 total) 1 [2](https://wordpress.org/support/topic/fatal-error-in-210/page/2/?output_format=md) [→](https://wordpress.org/support/topic/fatal-error-in-210/page/2/?output_format=md) The topic ‘Fatal error in 2.1.0’ is closed to new replies. * ![](https://s.w.org/plugins/geopattern-icon/genesis-simple-edits_393a3b.svg) * [Genesis Simple Edits](https://wordpress.org/plugins/genesis-simple-edits/) * [Frequently Asked Questions](https://wordpress.org/plugins/genesis-simple-edits/#faq) * [Support Threads](https://wordpress.org/support/plugin/genesis-simple-edits/) * [Active Topics](https://wordpress.org/support/plugin/genesis-simple-edits/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/genesis-simple-edits/unresolved/) * [Reviews](https://wordpress.org/support/plugin/genesis-simple-edits/reviews/) * 28 replies * 12 participants * Last reply from: [VintageChicCreations](https://wordpress.org/support/users/vintagechiccreations/) * Last activity: [11 years, 3 months ago](https://wordpress.org/support/topic/fatal-error-in-210/page/2/#post-5364333) * Status: not resolved