Viewing 13 replies - 1 through 13 (of 13 total)
  • Plugin Author Nick Diego

    (@ndiego)

    Hi NuttyHiker,

    The plugin will deactivate itself if you switch to a non-Genesis theme. Could this be what is happening?

    In not, can you let me know what theme you are using and the version of Genesis you are using?

    Thanks,
    Nick

    Thread Starter TxGirl

    (@nuttyhiker)

    Hi Nick,

    No, I am not switching themes. I am using the Pretty Chic Theme on Genesis 2.2.7.

    Plugin Author Nick Diego

    (@ndiego)

    Hmm this is very interesting. I have a test site setup with Pretty Chic running and the plugin activated. I will keep an eye on it and see if it deactivates the plugin, nothing yet. In doing a cursory look through the theme files, I cannot see anything that would cause this…

    In the meantime, are there any other new plugins that you have installed recently? There may be some conflicts between this plugin and another one.

    Thread Starter TxGirl

    (@nuttyhiker)

    Sorry Nick, just seeing this. No, I did not install any new plugins. It started immediately doing it as soon as I installed the plugin. Thought it was just a glitch at first, but it kept doing it so I had to deactivate it.

    Plugin Author Nick Diego

    (@ndiego)

    Thanks for the update. Sorry about this. I have been unable to replicate the issue on my end.

    I am having the same issue, using Showcase Pro. Happens at least once a week.

    Plugin Author Nick Diego

    (@ndiego)

    Good morning bamcclendon,

    The plugin does contain a deactivation trigger if the theme is switched to a non-Genesis theme. This doesn’t seem to be the case, but could you have switched themes at all?

    If not, the last thing I can think of is a conflict with another plugin. Can you provide me with a list of the plugins you are using on your site and I will setup a test site with Showcase Pro to see if I can replicate.

    The test site I setup for NuttyHiker is still running and I have seen no deactivation issues so I am thinking this has to be a conflict with another plugin.

    I appreciate the help. I would love to get this mystery solved.

    Nick

    Thanks for writing back so quickly, Nick.
    Here’s a list. It’s happened at least twice today.

    Inactive
    Academic Blogger’s Toolkit
    Akismet
    Contact Form Maker
    Contact Form Widget
    Genesis Subpage Sidebar
    Google Doc Embedder
    Google Forms
    Hello Dolly
    Image Widget Deluxe
    Kcite
    MOJO Marketplace
    Wordpress Carousel Free
    WP Display Header
    WP Pubmed Reflist

    Active
    Advanced Custom Fields
    BE Subpages Widget
    Carousel Horizontal Posts Content Slider
    Contact Form Add
    Custom Post Widget
    Flexible Posts Widget
    Genesis Club Lite
    Genesis Featured Page Advanced
    Genesis Responsive Slider
    Genesis Simple Edits
    Genesis Simple Hooks
    Genesis Simple Menus
    Genesis Visual Hook Guide
    Image Widget
    Inline Google Spreadsheet Viewer
    Max Mega Menu
    PHP Code Widget
    Q2W3 Fixed Widget
    Revolution Slider
    Swifty Image Widget by WPGens
    Tabs Responsive
    Team Showcase
    Widget Logic
    WYSIWYG Widgets / Widget Blocks

    Can I deactivate the deactivation trigger since I am using a genesis-based theme?

    Plugin Author Nick Diego

    (@ndiego)

    Good morning bamcclendon,

    I just setup a test site with all the plugins you listed and am going to try and see what is causing GFPA to deactivate. In the meantime, you can delete the snippet of code that runs the deactivation.

    To remove this piece of code, go to your Plugins page in the backend. Navigate to Genesis Featured Page Advanced and click on the little “Edit” button. On the following screen, scroll down in the text box until you find the following:

    add_action( 'admin_init', 'fpa_deactivate_check' );
    /**
     * This function runs on admin_init and checks to make sure Genesis is active, if not, it
     * deactivates the plugin. This is useful for when users switch to a non-Genesis themes.
     */
    function fpa_deactivate_check() {
        if ( ! function_exists('genesis_pre') ) {
    		deactivate_plugins( plugin_basename( __FILE__ ) ); // Deactivate plugin
        }
    }

    Delete all of this, and ONLY this. This is a temporary solution, but you “should” no longer have any deactivation issues. Please let me know either way though. If this solves it, then there is an issue with this deactivation trigger. If the plugin deactivates even after this, then something really bizarre is going on!

    Nick

    Thanks, Nick. I deleted a few plugins last night and no issues since. I’ll let you know. I did not comment out the deactivation code yet.

    Deleted
    Academic Blogger’s Toolkit
    Contact Form Maker
    Contact Form Widget
    Google Doc Embedder
    Google Forms
    MOJO Marketplace
    Wordpress Carousel Free

    Inactive
    Akismet
    Genesis Club Lite
    Genesis Subpage Sidebar
    Hello Dolly
    Image Widget Deluxe
    Kcite
    WP Display Header
    WP Pubmed Reflist

    Active
    Advanced Custom Fields
    BE Subpages Widget
    Carousel Horizontal Posts Content Slider
    Contact Form Add
    Custom Post Widget
    Flexible Posts Widget
    Genesis Featured Page Advanced
    Genesis Responsive Slider
    Genesis Simple Edits
    Genesis Simple Hooks
    Genesis Simple Menus
    Genesis Visual Hook Guide
    Image Widget
    Inline Google Spreadsheet Viewer
    Max Mega Menu
    PHP Code Widget
    Q2W3 Fixed Widget
    Revolution Slider
    Swifty Image Widget by WPGens
    Tabs Responsive
    Team Showcase
    Widget Logic
    WYSIWYG Widgets / Widget Blocks

    Happened again, so I deactivated the trigger.

    Not a programmer, but could it be this?

    function fpa_activation_check() {
    $latest = ‘2.0’;
    $theme_info = wp_get_theme( ‘genesis’ );

    Does genesis have to be specifically 2.0?

    Plugin Author Nick Diego

    (@ndiego)

    Man….I am baffled. I thought it might have been that Mojo Marketplace plugin, but you deleted that so that can’t be it.

    That 2.0 is for activation, and it basically says when you go and try to activate the plugin, Genesis needs to be version 2.0 or higher. If you tried to activate the plugin without Genesis, you would get an error message.

    Now that the trigger is deactivated, if it happens again please let me know! At this point my only thought is that the trigger fails under certain rare circumstances. But if it deactivates while the trigger itself is deactivated, then something really fishy is going on.

    I really appreciate your continual feedback on this!

    Nick

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Keeps deactivating’ is closed to new replies.