Forum Replies Created

Viewing 15 replies - 16 through 30 (of 48 total)
  • Thread Starter heytricia

    (@tendigit)

    Hey!

    Thanks for responding. I’ve already tried using a default theme and deactivating plugins. And I use my dev server for WordPress sites pretty much exclusively – several of them with WooCommerce installed. So I don’t think these things are the issue. I am wondering if something is up with the database for this particular site… it’s been a bit of a sandbox, so maybe there’s some trash somewhere causing this. Given the plugin had just been upgraded, I thought I’d put this out there to see if it was a new bug.

    I’ll try setting up a new install with a fresh database and see what happens.

    I had the same results using the wpengine php compatibility plugin. Sounds like we’re good, but I’m replying so that I can receive follow-up emails.

    Thanks for all you do!

    We are gearing up to upgrade several client servers to PHP7, and also used the WPEngine PHP Compatibility Checker to scan a dev project for issues. Yours was one of two plugins that were flagged. I’ve copied the report below. Will Duplicator be updated to play well with PHP7? Given we have several large sites on WPEngine and others, we need to be proactive and make sure we’re ready for optimal performance.

    FILE: /Users/heytricia/Documents/Websites/mosspinkflora.dev/wp-content/plugins/duplicator/classes/server.php
    ————————————————————————————————————
    FOUND 0 ERRORS AND 2 WARNINGS AFFECTING 2 LINES
    ————————————————————————————————————
    24 | WARNING | INI directive ‘safe_mode’ is deprecated from PHP 5.3 and forbidden from PHP 5.4.
    25 | WARNING | INI directive ‘safe_mode’ is deprecated from PHP 5.3 and forbidden from PHP 5.4.
    ————————————————————————————————————

    FILE: /Users/heytricia/Documents/Websites/mosspinkflora.dev/wp-content/plugins/duplicator/installer/build/ajax.step1.php
    ————————————————————————————————————————
    FOUND 6 ERRORS AFFECTING 6 LINES
    ————————————————————————————————————————
    55 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0 – use mysqli instead.
    276 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0 – use mysqli instead.
    279 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0 – use mysqli instead.
    280 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0 – use mysqli instead.
    283 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0 – use mysqli instead.
    355 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0 – use mysqli instead.
    ————————————————————————————————————————

    FILE: /Users/heytricia/Documents/Websites/mosspinkflora.dev/wp-content/plugins/duplicator/installer/build/ajax.step2.php
    ————————————————————————————————————————
    FOUND 1 ERROR AFFECTING 1 LINE
    ————————————————————————————————————————
    25 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0 – use mysqli instead.
    ————————————————————————————————————————

    FILE: /Users/heytricia/Documents/Websites/mosspinkflora.dev/wp-content/plugins/duplicator/installer/build/classes/class.utils.php
    ———————————————————————————————————————————
    FOUND 3 ERRORS AFFECTING 3 LINES
    ———————————————————————————————————————————
    224 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0 – use mysqli instead.
    248 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0 – use mysqli instead.
    249 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0 – use mysqli instead.
    ———————————————————————————————————————————

    FILE: /Users/heytricia/Documents/Websites/mosspinkflora.dev/wp-content/plugins/duplicator/installer/build/view.step1.php
    ————————————————————————————————————————
    FOUND 0 ERRORS AND 2 WARNINGS AFFECTING 2 LINES
    ————————————————————————————————————————
    31 | WARNING | INI directive ‘safe_mode’ is deprecated from PHP 5.3 and forbidden from PHP 5.4.
    32 | WARNING | INI directive ‘safe_mode’ is deprecated from PHP 5.3 and forbidden from PHP 5.4.
    ————————————————————————————————————————

    FILE: /Users/heytricia/Documents/Websites/mosspinkflora.dev/wp-content/plugins/duplicator/views/tools/diagnostics.php
    ———————————————————————————————————————
    FOUND 0 ERRORS AND 4 WARNINGS AFFECTING 2 LINES
    ———————————————————————————————————————
    174 | WARNING | INI directive ‘safe_mode’ is deprecated from PHP 5.3 and forbidden from PHP 5.4.
    174 | WARNING | INI directive ‘safe_mode’ is deprecated from PHP 5.3 and forbidden from PHP 5.4.
    175 | WARNING | INI directive ‘safe_mode’ is deprecated from PHP 5.3 and forbidden from PHP 5.4.
    175 | WARNING | INI directive ‘safe_mode’ is deprecated from PHP 5.3 and forbidden from PHP 5.4.
    ———————————————————————————————————————

    • This reply was modified 8 years, 6 months ago by heytricia.

    Hey Michael:

    The input field does not have that class:

    <input type="text" class="input-text " name="shipping_postcode" id="shipping_postcode" placeholder="Postcode / Zip" value="80004-5438">

    I double checked to make sure I’m not overriding the Woocommerce template, but only have templates in place for the following:

    /woocommerce/archive-product.php,
    /woocommerce/cart/cart.php,
    /woocommerce/checkout/form-login.php

    Thanks for the quick response!

    Hey Michael!

    I just tried the update, and it works in my dev environment – but not on the live site. My dev site uses an older version of php – the live site uses 5.6.25.

    The cart does now update when the state is changed, but not when the zip is changed. It’s the zip that drives the shipping rate, so changing the state isn’t enough.

    Any ideas for me?

    Thanks much!

    That’s good to hear. I can’t even imagine what it would be like to keep up with support on a plugin like this!

    This is the same issue I reported last week. I checked in hoping for a bit of feedback. Is this plugin still being supported?

    I’m having the same issue – with update 4.0.6

    * The version of WooCommerce – 2.5.5
    * The version of WordPress – 4.5.1
    * Include any PHP errors/warnings/notices (strip out any personal server paths or identifying details, etc.) – I did have PHP errors a week or so ago and disabled the plugin. I’m now trying to get this to work correctly in a dev / local environment. The PHP error is gone with the latest updates.

    I’m using this plugin to do one thing – add a datepicker field to the checkout page. The field shows, but on click does not open up a calendar. The console shows:

    Navigated to https://davidsroasting.dev/checkout/
    JQMIGRATE: Migrate is installed, version 1.4.0
    ‘//@ sourceURL’ and ‘//@ sourceMappingURL’ are deprecated, please use ‘//# sourceURL=’ and ‘//# sourceMappingURL=’ instead.

    We’re having an issue with media upload in combination with the Advanced Custom Fields plugin. Cleared all caches, etc – but we’re unable to add images to pages (posts are fine.) Our pages use custom fields heavily. We’ve disabled WP Smush until we get an update and are able to test it.

    Thread Starter heytricia

    (@tendigit)

    I spoke too soon…. The GitHub version works, but it is buggy. It causes the edit window to flash. I have minimum dims set for the featured image. Even when using the correct image size, the error message appears and disappears causing a flash / flicker effect.

    I’m hoping for a resolution soon… I can deal with the bug, but don’t want to pass on to a client. ??

    Thread Starter heytricia

    (@tendigit)

    I downloaded the latest version from GitHub, and it worked.

    Thread Starter heytricia

    (@tendigit)

    Worked perfectly. Thanks so much!

    – Tricia

    Thread Starter heytricia

    (@tendigit)

    The update did fix the CSS issue. Thanks much!

    Get some brain-rest… looking forward to hearing back from you upon recovery. ??

    – T

    I stand corrected… it does indeed work. Apologies.

    How could this be marked as resolved? The steps lined out will modify the @handlehere as you share, but it will not modify the list that is generated after. Saying ‘Twitter recommends what Twitter wants to recommend’ I think is not at all accurate. There is something in the code that causes AddToAny to be the only link on the list EVERY TIME. How can that be modified?

    Please and thanks?

Viewing 15 replies - 16 through 30 (of 48 total)