• Resolved NightL

    (@nightl)


    I have been developing on localhost on my home computer – no issues

    Upload website to server and go to activate jetpack – the moment I select “Free Plan” my website went down – Including admin.

    After far too many hours and uploading earlier version of jetpack 4.4.2 – upload whole website etc

    I turned off all plugins and was finally able to activate latest version of jetpack

    I turned on all plugins one at a time leaving Booster for WooCommerce until after Woocommerce

    Booster instantly caused issues – wiped out jetpack features and also cleared top admin bar of woocommerce while viewing front end.

Viewing 9 replies - 1 through 9 (of 9 total)
  • Thread Starter NightL

    (@nightl)

    what I posted on jetpack support:

    I went back to jetpack.3.9.7 and it activated fine

    https://downloads.www.ads-software.com/plugin/jetpack.3.9.7.zip

    But when I turned on woocommerce booster again it fell over.

    1. woocommerce booster Version 2.5.9 and jetpack 4.6 (not connected) both activated – initially I thought it OK but some of my longer pages where not dispalying (content area) Then I connected jetpack to wordpress.com account to activate features, Front end and admin down. FTP remove jetpack and reinstall/activate plugin – some issues with wordpress top admin not displaying (the space was there – but not filled) – fell over completely on connection again

    2. jetpack 4.6 with woocommerce booster off still had irregular issues with error 500

    3. jetpack.3.9.7 and woocommerce booster Version 2.5.9 – failure again on trying to connect to wordpress.com account

    4. jetpack 4.6 with older woocommerce booster 2.5.6 – on connecting jetpack to wordpress.com – still have the front end but admin pages are blank.

    ________________________
    I have another website with Booster for WooCommerce 2.5.9 and jetpack 4.5 running fine – I am certainly not going to update jetpack 4.5 to 4.6 and risk wasting another day of income over this mess.

    • This reply was modified 8 years, 1 month ago by NightL.

    Hi,

    It’s possible that this is the issue with memory. Could you please try increasing WP memory limit by adding to your wp-config.php file:
    define( ‘WP_MEMORY_LIMIT’, ‘512M’ );
    define( ‘WP_MAX_MEMORY_LIMIT’, ‘512M’ );

    Please let me know if that makes any difference.

    Best regards,
    Tom

    Thread Starter NightL

    (@nightl)

    Upped from 256 to 512 – no change

    The instant I click “Select Free” for connecting Jetpack my site falls to HTTP ERROR 500
    while woocommerce booster is active.

    If I have woocommerce booster deactivated I can connect Jetpack but the moment I activate woocommerce booster I start to have troubles – will be locked out of admin – and after a short while (minutes) the front end will go down.

    I am using a reseller VPS account with above average resources – all my websites fly compared to previous budget hosting – I previously had also increased max allowances via my WHM

    Jetpack have requested a debug – I will post results here as well.

    Obviously there could and probably be a third component to this – as I have a woocommerce booster and jetpack combination (different theme) working with no issue on the same VPS hosting.

    Theme I use on the problem site is NOTA by Swiftideas

    Thread Starter NightL

    (@nightl)

    Also worth noting, if I go into wordpress.com and disconnect jetpack for that website the website becomes live again.

    Thread Starter NightL

    (@nightl)

    Debug – I changed my domain info obviously
    The moment below reflects when I click “Select Free” to connect

    [01-Mar-2017 21:56:45 UTC] PHP Notice: Constant WP_MEMORY_LIMIT already defined in /home/XXXXXXXXau/public_html/wp-config.php on line 104
    [01-Mar-2017 21:56:45 UTC] PHP Notice: Constant WP_MAX_MEMORY_LIMIT already defined in /home/XXXXXXXXau/public_html/wp-config.php on line 105
    [01-Mar-2017 21:56:46 UTC] PHP Notice: Constant WP_MEMORY_LIMIT already defined in

    [Excessive code redacted. Please use pastebin.com for large amounts of code.]

    • This reply was modified 8 years, 1 month ago by kmessinger.
    Thread Starter NightL

    (@nightl)

    I cleared the debug file – deactivated woocommerce booster (left it off) then connected Jetpack again.

    Editing:
    /home/xxxxxxxxxxxxau/public_html/wp-content/debug.log
    Encoding: Re-open Use Code Editor Close Save Changes

    [01-Mar-2017 22:06:19 UTC] PHP Notice: Constant WP_MEMORY_LIMIT already defined in /home/xxxxxxxxxxxxau/public_html/wp-config.php on line 104
    [01-Mar-2017 22:06:19 UTC] PHP Notice: Constant WP_MAX_MEMORY_LIMIT already defined in /home/xxxxxxxxxxxxau/public_html/wp-config.php on line 105
    [01-Mar-2017 22:06:20 UTC] PHP Notice: Constant WP_MEMORY_LIMIT already defined in /home/xxxxxxxxxxxxau/public_html/wp-config.php on line 104
    [Excessive code redacted. Please use pastebin.com for large amounts of code.]

    • This reply was modified 8 years, 1 month ago by kmessinger.
    Thread Starter NightL

    (@nightl)

    OK – I found a tip over point

    there is a cumulative thing going on

    I turned off all plugins except woocommerce booster and jetpack – then connected Jetpak OK – I turned on each other plugin one at a time – refreshing admin and front end at each step.

    The theme I am using is feature rich and has a lot of plugins – along with adding a few of my favourites of my own, woocommerce booster off and jetpack included.

    As I turned on each plugin from about woocommerce on I noticed the front end admin bar taking longer to load – I finally got to https://en-au.www.ads-software.com/plugins/youtube-embed-plus/ and bang – Error 500

    I turned off all – activated woocommerce booster, jetpack and YouTube then connected JetPack – all OK.

    Here is the debug for that last step:
    [01-Mar-2017 23:49:08 UTC] PHP Notice: Constant WP_MEMORY_LIMIT already defined in /home/linxxxxxxxxxxau/public_html/wp-config.php on line 105
    [01-Mar-2017 23:49:08 UTC] PHP Notice: Constant WP_MAX_MEMORY_LIMIT already defined in /home/linxxxxxxxxxxau/public_html/wp-config.php on line 106
    [01-Mar-2017 23:49:09 UTC] PHP Notice: Constant WP_MEMORY_LIMIT already defined in /home/linxxxxxxxxxxau/public_html/wp-config.php on line 105
    [01-Mar-2017 23:49:09 UTC] PHP Notice: Constant WP_MAX_MEMORY_LIMIT already defined in /home/linxxxxxxxxxxau/public_html/wp-config.php on line 106
    [01-Mar-2017 23:49:12 UTC] PHP Notice: Constant WP_MEMORY_LIMIT already defined in /home/linxxxxxxxxxxau/public_html/wp-config.php on line 105
    [01-Mar-2017 23:49:12 UTC] PHP Notice: Constant WP_MAX_MEMORY_LIMIT already defined in /home/linxxxxxxxxxxau/public_html/wp-config.php on line 106

    [Excessive code redacted. Please use pastebin.com for large amounts of code.]

    • This reply was modified 8 years, 1 month ago by kmessinger.
    • This reply was modified 8 years, 1 month ago by kmessinger.
    Thread Starter NightL

    (@nightl)

    and finally – all plugins off except jetpack – then activating jetpack

    [01-Mar-2017 23:58:25 UTC] PHP Notice: Constant WP_MEMORY_LIMIT already defined in /home/linxxxxxxxxxxau/public_html/wp-config.php on line 105
    [01-Mar-2017 23:58:25 UTC] PHP Notice: Constant WP_MAX_MEMORY_LIMIT already defined in /home/linxxxxxxxxxxau/public_html/wp-config.php on line 106
    [01-Mar-2017 23:58:26 UTC] PHP Notice: Constant WP_MEMORY_LIMIT already defined in /home/linxxxxxxxxxxau/public_html/wp-config.php on line 105

    [Excessive code redacted. Please use pastebin.com for large amounts of code.]

    • This reply was modified 8 years, 1 month ago by kmessinger.
    • This reply was modified 8 years, 1 month ago by kmessinger.
    Thread Starter NightL

    (@nightl)

    OK – totally memory issue
    the wp-config.php of
    define( ‘WP_MEMORY_LIMIT’, ‘512M’ );
    define( ‘WP_MAX_MEMORY_LIMIT’, ‘512M’ );

    did not work – I checked

    used the php.ini method and got the 512

    With all plugins active I disconnected Jetpack and reconnected – so far all is fine.

    Time to trim off unnecessary plugins.

    At least I learnt some more through all this…

    I consider this resolved – even if there is a memory leak somewhere the site is running.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘clash with Jetpack Version 4.6 and earlier’ is closed to new replies.