Forum Replies Created

Viewing 15 replies - 1 through 15 (of 61 total)
  • It was the menu toggle button actually, it had a transparent background for some reason.

    On the server it would be in a folder, not zipped up. The folder is likely called contact-form-7. Unzip the file that you downloaded with the older version of CF7 into a folder. On the remote FTP, rename that contact-form-7 folder to something else, or delete it, then upload the new folder that you just unzipped. You should be good to go at that point.

    Yeah… sorry @billsmithem, my bad.

    I actually am riding it out right now by not updating… I have no inclination to repeat this on hundreds of sites 🙁

    Outdated does not necessarily mean it’s a bad thing – in this case they swapped one API (v3 instead of v2) and accidentally broke millions of sites. Apple and Microsoft have done similar things, we’ll get a fix eventually.

    Someone else mentioned WP Rollback as an option too

    https://en-ca.wordpress.org/plugins/wp-rollback/

    May save you some time and effort – however, read their disclaimer first to avoid data loss.

    I’m in that boat. Over 200 to worry about. I’m going to ignore it and hope it gets magically fixed by the morning…. >.>

    It’s a free plugin @tsso0120 – revert back to 5.0.5 instead of making vague threats about switching. We all know it’s more work than it’s worth to switch out tons of forms to another plugin.

    It may not be available, but the code is there for it in class-wp-smush-s3.php. Our client doesn’t have the pro version, but I’m looking at the file right now.

    I wrapped an if statement around line 265, much like inside the function directly below it, and it cleared up the issue, allowing them to run with the newest version of the S3 Offload plugin.

    if ( method_exists( $as3cf, ‘is_attachment_served_by_s3’ ) ) {

    }

    Awesome. In the meantime, if you revert to the previous of S3 then everything goes back to normal. Cheers!

    Hey, are you using Amazon s3 offload?

    We just ran into this.

    Kasia, please pass this on! This is the latest version of S3 offload plugin, and the latest version of Smush.

    [03-Oct-2018 22:00:19 UTC] PHP Fatal error: Call to undefined method Amazon_S3_And_CloudFront::is_attachment_served_by_s3() in /home/username/public_html/wp-content/plugins/wp-smushit/lib/integrations/class-wp-smush-s3.php on line 265
    [03-Oct-2018 22:01:19 UTC] PHP Fatal error: Call to undefined method Amazon_S3_And_CloudFront::is_attachment_served_by_s3() in /home/username/public_html/wp-content/plugins/wp-smushit/lib/integrations/class-wp-smush-s3.php on line 265
    [03-Oct-2018 22:01:21 UTC] PHP Fatal error: Call to undefined method Amazon_S3_And_CloudFront::is_attachment_served_by_s3() in /home/username/public_html/wp-content/plugins/wp-smushit/lib/integrations/class-wp-smush-s3.php on line 265
    [03-Oct-2018 22:03:56 UTC] PHP Fatal error: Call to undefined method Amazon_S3_And_CloudFront::is_attachment_served_by_s3() in /home/username/public_html/wp-content/plugins/wp-smushit/lib/integrations/class-wp-smush-s3.php on line 265

    Found this issue on a client site too.

    The admin-ajax.php throws a 500 error when viewing the media library.

    Emailed diagnostic info to nom@ address.

    Reverted back to 1.4.3 and everything is back to normal!

    Here’s the fatal error – looks to be an incompatibility with Smush?

    [03-Oct-2018 22:00:19 UTC] PHP Fatal error: Call to undefined method Amazon_S3_And_CloudFront::is_attachment_served_by_s3() in /home/username/public_html/wp-content/plugins/wp-smushit/lib/integrations/class-wp-smush-s3.php on line 265
    [03-Oct-2018 22:01:19 UTC] PHP Fatal error: Call to undefined method Amazon_S3_And_CloudFront::is_attachment_served_by_s3() in /home/username/public_html/wp-content/plugins/wp-smushit/lib/integrations/class-wp-smush-s3.php on line 265
    [03-Oct-2018 22:01:21 UTC] PHP Fatal error: Call to undefined method Amazon_S3_And_CloudFront::is_attachment_served_by_s3() in /home/username/public_html/wp-content/plugins/wp-smushit/lib/integrations/class-wp-smush-s3.php on line 265
    [03-Oct-2018 22:03:56 UTC] PHP Fatal error: Call to undefined method Amazon_S3_And_CloudFront::is_attachment_served_by_s3() in /home/username/public_html/wp-content/plugins/wp-smushit/lib/integrations/class-wp-smush-s3.php on line 265

    I’m the host.

    So I looked through your code, and I think it runs out of memory somewhere between the shrink_width and shrink_height functions. They call each other, and a loop in there may cause something like an endless memory leak.

    I don’t have time to work out the actual calculations – BUT previously, the thumbnail dimensions on the catablog options page were set to 220×220. I changed it to 222×220 and the error went away, and it appears to be working now. The image she was uploading was 800×800, if that helps you to troubleshoot.

    Absolutely. I went through all of the error logs trying to find what could have caused it but only once did I see class-edd-session.php so that’s what led me to disable the plugin in the first place. There are a few, the first one being the one that showed up continually (I just copied it once but it’s there at least 60 times):

    [16-Sep-2016 23:27:28 UTC] PHP Warning: strpos(): Empty needle in /home/gro/public_html/wp-includes/plugin.php on line 736

    [18-Sep-2016 01:36:16 UTC] PHP Warning: require(ABSPATHwp-includes/load.php): failed to open stream: No such file or directory in /home/gro/public_html/wp-settings.php on line 21
    [18-Sep-2016 14:54:43 UTC] PHP Warning: session_start(): open(/tmp/sess_17pran360q3t7eo0mulkn85f82, O_RDWR) failed: Permission denied (13) in /home/gro/public_html/wp-content/plugins/easy-digital-downloads/includes/class-edd-session.php on line 377
    [18-Sep-2016 14:54:43 UTC] PHP Warning: Unknown: open(/tmp/sess_17pran360q3t7eo0mulkn85f82, O_RDWR) failed: Permission denied (13) in Unknown on line 0
    [18-Sep-2016 14:54:43 UTC] PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0

    Yes, this is exactly what I needed it for too! Awesome plugin.

    So with the first one, admintic9, it’s because of the ?759 at the end – if you remove that it will show the importer for that image properly. With the next one, leandra, it looks like all of the classes and styles may interfere with it. I’ll see if I can tweak the regex to grab the src only. When I have time :p

Viewing 15 replies - 1 through 15 (of 61 total)