Site is now unavailable

That is strange as it did not have the same issue earlier.

In both Twenty Fourteen and Fourteen Extended there’s the same check on if the function exists or not – same as Jetpack itself – I don’t see why it would throw up an error.

Maybe a fresh pair of eyes can spot something off?

Jetpack’s declaration: modules/theme-tools.php

if ( ! class_exists( 'Featured_Content' ) && 'plugins.php' !== $GLOBALS['pagenow'] ) {
    require_once( JETPACK__PLUGIN_DIR . 'modules/theme-tools/featured-content.php' );
}

Twenty Fourteen’s declaration: functions.php

if ( ! class_exists( 'Featured_Content' ) && 'plugins.php' !== $GLOBALS['pagenow'] ) {
    require get_template_directory() . '/inc/featured-content.php';
}

And Fourteen Extended’s declaration: functions.php

if ( ! class_exists( 'Featured_Content' ) && 'plugins.php' !== $GLOBALS['pagenow'] ) {
    require FOURTEEN_EXTENDED_PLUGIN_DIR . 'inc/featured-content.php';
}

I’m going to move all mods in to the fourteenxt-customizer.php and not have to call the class in the plugin to see if that plays nicely.

Zulf

Hi Zulf,

The issue here I think is just the redeclaration of the same class
Give your class another name (or use namespace) and all should be fine.

Hi Violacase,

Had consider doing that but put it off as I need to set time aside to really give it my full attention. Now that you’ve mentioned I’ll definitely revisit it and see what can be done ??

Thanks,
Zulf