WordPress.org

Forums

Jetpack Lite
[resolved] new update crashed my site!! (45 posts)

  1. MorphMan
    Member
    Posted 1 year ago #

    Just updated the plugin and crashed my whole site

    Fatal error: Call to undefined function is_plugin_active() in /home/content/26/11868026/html/wp-content/plugins/jetpack-lite/jetpack-lite.php on line 12

    had to go in to my hosting provider account and delete the plugin root folder to gain access back to my site!

    others be careful before updating, what may happens to your site will scare a novice webmaster.

    hopefully a fix will come soon so I can re-install this plugin

    http://wordpress.org/plugins/jetpack-lite/

  2. unknownnobody
    Member
    Posted 1 year ago #

    I am having the same problem and am now losing money while I wait on my host to clear this up. I deleted the plugin via FTP but still get the fatal error.

  3. Bharath Mandava
    Member
    Posted 1 year ago #

    Updated the plugin and crashed my blog. Seems like there is an issue with the recent release.

  4. bluehash
    Member
    Posted 1 year ago #

    Mine too. Entire site, admin is down.

  5. Piet Bos
    Member
    Posted 1 year ago #

    Same here, cannot access admin anymore Fatal Errors all around!

    Downloading the error file points to Jetpack Lite and browsing though the changelog shows that now all of a sudden Jetpack itself should be installed too (!!!)

    You might have added an update notice to make people aware and not just kill sites if they don't have Jetpack installed. With more than 40K downloads it is your duty to inform your users when you make such dramatic changes to your plugin!

    I though that the whole point of your plugin was not to have Jetpack installed? By now making it an Addon, I am seriously asking myself why I would want your plugin? How do I know what kind of impact Jetpack has on my site?

    Bad practice this is and I will have to adjust my 5-star rating now.

    Update
    Even after installing Jetpack (if only to see what your "addon" does) it completely crashes the site.
    Uninstall

  6. golfczech2
    Member
    Posted 1 year ago #

    I did get a message to make sure I had Jetpack installed which yes, does defeat the entire purpose of Jetpack LITE. However, I did install the regular Jetpack and then tried to update the LITE plug in and the site still crashed.

    I had to get into my server files and delete the LITE plug in.

    Unbelievable.

  7. gaplauche
    Member
    Posted 1 year ago #

    Same here. Even after installing Jetpack first, installing and activating Jetpack Lite causes the error described by the OP.

    Assuming Jetpack Lite gets updated to fix this problem, is the new design philosophy going to be as lightweight as before? I'll end up with two plugins instead of one. Is resource usage going to be heavier now that Jetpack Lite is suppressing most of Jetpack's features instead of being slimmed down version of Jetpack?

  8. MarkRH
    Member
    Posted 1 year ago #

    Glad I looked here prior to updating. Don't think I'll update to version 3.0 (unless a solution is found in this thread). May need to stop updating this plug-in like I stopped updating All In One SEO Pack and still use version 1.6.15.3 of it.

    Worst case, I can always look at Awstats and Webalizer in my webhost's control panel.

  9. MorphMan
    Member
    Posted 1 year ago #

    I've given up on the jetpack lite plugin and have installed the Google analytics plugin instead http://wordpress.org/plugins/google-analytics-dashboard-for-wp/

    i was a long time user of the jetpack lite but this latest update has made me move elsewhere

  10. Piet Bos
    Member
    Posted 1 year ago #

    Thanks for the tip @MorphMan

  11. Samuel Aguilera
    Member
    Plugin Author

    Posted 1 year ago #

    Fatal error: Call to undefined function is_plugin_active() in /home/content/26/11868026/html/wp-content/plugins/jetpack-lite/jetpack-lite.php on line 12

    is_plugin_active() function is present in WordPress since 2.5 as you all can see in the codex and min WP version requirement for the plugin is set to WP 3.1.

    So... Which WordPress version are you using? Because the error you posted indicates that is_plugin_active() function is not present in your WordPress, and that only can happen if you're running a very outdated WordPress version and not matching the requirement of the plugin.

    I have Jetpack Lite running without any problem in dozens of sites running WordPress 3.8.

    Assuming Jetpack Lite gets updated to fix this problem, is the new design philosophy going to be as lightweight as before? I'll end up with two plugins instead of one. Is resource usage going to be heavier now that Jetpack Lite is suppressing most of Jetpack's features instead of being slimmed down version of Jetpack?

    When I created Jetpack Lite years ago, I did it as fork of Jetpack because no other method to do was available at that moment.

    Fortunately, today Jetpack can be trimmed down without the need of making a fork. That's why I changed the way Jetpack Lite do the work. In fact, now, Jetpack Lite doesn't use any resource, it only says to Jetpack to only load the Stats and Shorlinks modules, so the other modules won't load or consume any resource.

    This way is much better, because now you don't need to wait for me to update a whole new plugin when a new Jetpack gets published. So you'll get updates to the modules you want to use faster than before.

    You might have added an update notice to make people aware and not just kill sites if they don't have Jetpack installed. With more than 40K downloads it is your duty to inform your users when you make such dramatic changes to your plugin!

    The changes are informed in the upgrade notice and in the changelog. Your WordPress installation is your responsability not mine, so it's your responsability to check changes before installing anything, to check requirements, or to have a way to rollback if something fails.

    And, by the way, more than 200 people downloaded the plugin in the latest 24h and only 8 people are complaining (1 of them without even installing the plugin) here...

    What about to stop a moment and think that maybe the problem can be in your side?? what about to read first and blame later? What about to have a little of respect for someone that brings his work and time to you without asking anything in return?

  12. MorphMan
    Member
    Posted 1 year ago #

    good luck with your plugin - your attitude to your users as just cemented my change to a different plugin

    all the best!

    ps, I know my way around WordPress!

  13. Samuel Aguilera
    Member
    Plugin Author

    Posted 1 year ago #

    @MorphMan Ok, you blame to me but dont provide the information I have requested to you about your WordPress version...

    Then I'll assume you're running a WordPress version below the min. WP requirement as your error message indicates. And marks the thread as resolved.

    Your attitude will make me to stop giving any support, because I'm tired of people like you that wants all for nothing and does not collaborate in any way.

  14. shefi
    Member
    Posted 1 year ago #

    Fatal error: Call to undefined function is_plugin_active() in /home/****/public_html/blogs/[blog title]/wp-content/plugins/jetpack-lite/jetpack-lite.php on line 12

    My WP installation is on automatic update so I am running the latest version of WP (3.8).

    This matter is unresolved. The error message appears whatever link I click in the WP Admin sidebar. Even closing the window and opening a new one (set to "wp-admin") brings up the same error message.

    Only "solution" was to enter via cPanel and delete the Jetpack lite plugin folder.

    Too bad. Was a very useful little plugin.

  15. MorphMan
    Member
    Posted 1 year ago #

    FYI i'm using the latest version of WordPress - and i'm not blaming anyone, please read my original post I was actually reaching out for help.

    But now kind of lost for words with the response I've received from you??

    Not to worry I've moved on and by the way "who are people like me"

    Your attitude sucks my friend!!

  16. tschaplin
    Member
    Posted 1 year ago #

    Under WordPress 3.8 I am getting the same notorious error with the update to jetpack lite 3.0:
    Fatal error: Call to undefined function is_plugin_active() in /.../wp-content/plugins/jetpack-lite/jetpack-lite.php on line 12 Call Stack: 0.0011 1001944 1. {main}() /.../wp-admin/plugins.php:0 0.0016 1127784 2. require_once('/.../wp-admin/admin.php') /.../wp-admin/plugins.php:10 0.0018 1156000 3. require_once('/.../wp-load.php') /.../wp-admin/admin.php:30 0.0020 1179008 4. require_once('/.../wp-config.php') /.../wp-load.php:29 0.0025 1326872 5. require_once('/.../wp-settings.php') /.../wp-config.php:89 0.1772 35125040 6. include_once('/.../wp-content/plugins/jetpack-lite/jetpack-lite.php') /.../wp-settings.php:210.

    Only disabling jetpack lite via ftp brings up the wp-admin frontend again.

    And the reason is definitively jetpack lite, since any other plugins (including a test installation of jetpack) are working well.

    Btw, I like this plugin and its slim concept, but till this issue is fixed any further use will be impossible.

    Greetz
    tschaplin

    P.S.: And to some people in this mail listing complaining in an inappropriate way to the author: please keep in mind, anybody making available plugins for free, is working at his/her best and providing a great service to the user community. So if you want to complain, then PAY.

  17. Samuel Aguilera
    Member
    Plugin Author

    Posted 1 year ago #

    @tschaplin The fact is that I have it running without problem in dozen sites... So I cant reproduce the problem here.

    And it's weird because is_active_plugin() is a WordPress core function, not mine, and is present since WordPress 2.5...

    So I think that there's something at your installations that is causing for some reason the problem with the use of that function.

    Did you make any change to WordPress defaults? maybe changed wp-content path or anything?

    PS. Anyway, I'm uploading an update for respectful and helpful people like you, disabling the use of that function to avoid more problems while tracking the issue.

  18. tschaplin
    Member
    Posted 1 year ago #

    @Samuel Thanks for your reply. At the moment I am not aware of having made any sensitive changes in my WP defaults, but I will check it.
    In my experience these error messages rarely are pointing to the real culprit - so some hardcore debugging will be necessary - I will try to do it later this afternoon.

    Anyway, thanks for your work, I really appreciate it.

    tschaplin

  19. Samuel Aguilera
    Member
    Plugin Author

    Posted 1 year ago #

    Thank your for your kind words @tschaplin I appreciate it very much. If you gather any other info that I can use to debug it please let me know.

    In the other hand 3.0.1 is available and will solve the issue for those that have it.

  20. tschaplin
    Member
    Posted 1 year ago #

    Yep, 3.0.1 brings the fix - thx. But anyway I will try to find out what was the reason with the 3.0 issue.

  21. shefi
    Member
    Posted 1 year ago #

    I updated to version 3.0 directly from within my WP admin page (where it says "update now"), never having had any problems with updating other plugins.

    After restoring functionality to my blog by simply deleting the Jetpack Lite plugin folder on cPanel, I came here and read, "IMPORTANT: Starting from version 3.0 this plugin becomes a Jetpack addon and not a standalone plugin as in previous versions. Now you need to install Jetpack too."

    I did not have Jetpack installed (didn't know I needed it). Could this have been the cause of the problem?

  22. Piet Bos
    Member
    Posted 1 year ago #

    I have a few plugins that depend on other plugins, but I am not using the is_active_plugin() function, instead I am using a function adapted from a post on wpengineer. Not only does that actually work instead of shutting down entire sites, it also "dies" in a nice way with a customizable error message.

    If you're interested, you can have a look at my SO Related Posts plugin I released the other day, which uses it.

    In my opinion it is wrong when Jetpack is not active to disable an entire site. It's just ridiculous that both frontend and backend fall apart after upgrading your plugin. I am very sorry to say, but that is your responsibility, not mine. Especially since you don't have bothered to add an upgrade notice to your readme.txt! You only added it to the changelog, but such an important change should be added to the Upgrade Notice as well, same as you have done for 2.3.4 and 2.3.4.1.

    The sites I updated Jetpack Lite on are all running either WP 3.8 or WP 3.9-alpha nightly build versions, so nice try, but that certainly is not the problem.

    Also when an error log says that the fatal error has been detected on line 12 of jetpack-lite.php, then why would you blame the user for having it wrong? That's just weird, dude!

    I can imagine you're frustrated with an obvious too early release of your plugin update, but blaming the users that report this issue is just not going to score you any goodwill here.

    and min WP version requirement for the plugin is set to WP 3.1

    Actually it is 3.5 as line 17 of your plugin clearly says: define( 'JETPACK__MINIMUM_WP_VERSION', '3.5' );

    I had a quick look at 3.0.1, but that just doesn't make any sense, so for now I have followed @MorphMan's suggestion for the sites that fell apart and for the sites that I could save in time for now I am using an adapted version of 2.3.4.1, the latest working version of your plugin.

  23. gaplauche
    Member
    Posted 1 year ago #

    I'm running the most recent version of WordPress, 3.8, and got the error.

  24. tschaplin
    Member
    Posted 1 year ago #

    @gaplauche try updating to 3.0.1 - and don't forget to have installed jetpack too. That should work now.

  25. gaplauche
    Member
    Posted 1 year ago #

    @tschaplin I just tried Jetpack Lite 3.0.1 and it's working fine. 3.0 did give me the OP's error, however, even with Jetpack installed first on WordPress 3.8.

    My WordPress installation is a one-click install on DreamHost, unmodified by me, running the Thesis 2.1 theme.

  26. tschaplin
    Member
    Posted 1 year ago #

    @gaplauche seems that we have the same combination. Strangely the WP 3.8/ jetpack-lite 3.0 didn't work in none of my installations. I am still trying to track down the reason, but couldn't find any clue till now.

    Though I preferred the standalone concept of jetpack-lite, it even makes sense now combined with jetpack. Several quick scans with the P3 plugin performance profiler showed the load is cut by more than 50 percent with jetpack-lite in comparison with jetpack alone. The only disadvantage now is having lying about lots of useless data of the several MB heavy jetpack installation.

  27. Piet Bos
    Member
    Posted 1 year ago #

    @tschaplin @gaplauche I think the problem simply sits in the code: the 3.0 version of the plugins is these lines:

    if ( is_plugin_active( 'jetpack/jetpack.php' ) ) {
    
    		function Leave_only_JetpackLite_modules ( $modules ) {
    		    $return = array();
    		    $return['stats'] = $modules['stats'];
    		    $return['shortlinks'] = $modules['shortlinks'];
    		    return $return;
    		}
    
    		add_filter( 'jetpack_get_available_modules', 'Leave_only_JetpackLite_modules' );
    
    		function Activate_only_JetpackLite_modules() {
    		    return array( 'stats', 'shortlinks' );
    		}
    
    		add_filter( 'jetpack_get_default_modules', 'Activate_only_JetpackLite_modules' );
    
    }

    So what happens if ( ! is_plugin_active( 'jetpack/jetpack.php' ) ) ?

    Everything falls apart, that's what happens.

    As mentioned before, requiring a plugin can be done entirely different:

    $plugins = get_option( 'active_plugins' );
    
    $required_plugin = 'jetpack/jetpack.php';
    
    // multisite throws the error message by default, because the plugin is installed on the network site, therefore check for multisite
    if ( ! in_array( $required_plugin , $plugins ) && ! is_multisite() ) {
    
    	add_action( 'admin_notices', 'so_no_jetpack_warning' );
    
    }
    
    function so_no_jetpack_warning() {
    
        // display the warning message
        echo '<div class="message error"><p>';
    
        printf( __( 'The <strong>Jetpack Lite Addon</strong> only works if you have the <a href="%s">Jetpack</a> plugin installed.', 'jetpack-lite' ),
            'http://wordpress.org/plugins/jetpack/' );
    
        echo '</p></div>';
    
        // and deactivate the plugin
        deactivate_plugins( plugin_basename( __FILE__ ) );
    }

    Another option would be to include the TGM Plugin Activation Class, which enables the user who is unaware the plugin has been changed into an Addon and is now dependant on Jetpack to function, to install Jetpack straight from the Dashboard. I have not worked with that class myself yet, but it has been recommended to me by another developer.

  28. Piet Bos
    Member
    Posted 1 year ago #

    In addition to what I mentioned above, I think that on a squeaky clean brand new WP install the 3.0 version could actually work.

    But updating from 2.3.4.1 to 3.0 will fail miserably, because none of the old settings are removed from the user's options, the plugin goes from 20 something files to 1 file and all the rest is simply not there anymore.

    In my opinion that is recipe for disaster...

    In 3.0.1 the author has removed the if statement, so I expect that Jetpack Lite simply does not function anymore without Jetpack installed, but many users will only discover that next week or even further down the line, because not everyone watches their stats with the same frequency.

    Therefore 3.0.1 is hardly a solution, but merely postponing a shitstorm.

    Again, I want to emphasise that this is just my opinion.

  29. tschaplin
    Member
    Posted 1 year ago #

    @Piet, thanks - the code proposed by you is working - chapeau. However 3.0.1 is working too. So the question remains, why 3.0 didn't work? You may be right, that old scrap might prevent it from working. (I will spend some further time to investigate this).

    It's true, as a mere addon jetpack-lite now needs jetpack to be installed (and users accustomed to read the release notes carefully - other than me - lol). Nevertheless with 3.0.1 working jetpack-lite brings considerable benefits in speed and system load compared with the full jetpack package standalone. So in my opinion it is a solution as for preventing any unnecessary overloads.

  30. gaplauche
    Member
    Posted 1 year ago #

    So a solution would be to uninstall Jetpack Lite, then use a plugin like Clean Options to clear out the old Jetpack Lite settings before installing it?

Topic Closed

This topic has been closed to new replies.

About this Plugin

  • Jetpack Lite
  • Frequently Asked Questions
  • Support Threads
  • Reviews

About this Topic

Tags

No tags yet.