Support » Plugin: Child Themify » Warnings and Fatal Error upon activating Child Themify

  • Resolved powerfullove

    (@powerfullove)


    Upon activating Child Themify, I immediately got the messages, below. Now I cannot access any of my pages or the backend of WordPress. I have not idea how to resolve this, as I cannot get into my Plugins to deactivate any of them… Suggestions please?

    This is the site: http://liquidphi.com

    Warning: require_once(): http:// wrapper is disabled in the server configuration by allow_url_include=0 in /home/liquidphiadmin/public_html/wp-content/plugins/custom-twitter-feeds/custom-twitter-feed.php on line 32

    Warning: require_once(http://www.liquidphi.com/wp-content/plugins/child-themify/child-themify.php/inc/widget.php): failed to open stream: no suitable wrapper could be found in /home/liquidphiadmin/public_html/wp-content/plugins/custom-twitter-feeds/custom-twitter-feed.php on line 32

    Fatal error: require_once(): Failed opening required ‘http://www.liquidphi.com/wp-content/plugins/child-themify/child-themify.php/inc/widget.php’ (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in /home/liquidphiadmin/public_html/wp-content/plugins/custom-twitter-feeds/custom-twitter-feed.php on line 32

    https://wordpress.org/plugins/child-themify/

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author John P. Bloch

    (@johnpbloch)

    You can get your site back up by renaming the child themify plugin folder using FTP (or even simply deleting it). I’ll take a look at the error later to see if there’s anything in the code that caused this.

    Plugin Author John P. Bloch

    (@johnpbloch)

    This appears to be a conflict with the Custom Twitter Feeds plugin. Both Custom Twitter Feeds and Child Themify are defining the CTF_URL constant. As a workaround, I would suggest disabling Custom Twitter Feeds before enabling Child Themify. After you use Child Themify to create your child theme, you can disable Child Themify and turn Custom Twitter Feeds back on.

    I’m inclined to say that it’s not really worth changing the code since Child Themify doesn’t need to be active any longer than necessary to create a child theme. I’m open to persuasion, though.

    That worked perfectly… i appreciate your clear, quick response 🙂

    Do you know if Child Themify needs to be active when my theme is updated?

    Plugin Author John P. Bloch

    (@johnpbloch)

    It does not. Child Themify only creates the child theme and keeps its hands out of the cookie jar otherwise.

    Cool!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Warnings and Fatal Error upon activating Child Themify’ is closed to new replies.