Title: benntech's Replies | WordPress.org

---

# benntech

  [  ](https://wordpress.org/support/users/benntech/)

 *   [Profile](https://wordpress.org/support/users/benntech/)
 *   [Topics Started](https://wordpress.org/support/users/benntech/topics/)
 *   [Replies Created](https://wordpress.org/support/users/benntech/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/benntech/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/benntech/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/benntech/engagements/)
 *   [Favorites](https://wordpress.org/support/users/benntech/favorites/)

 Search replies:

## Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)

 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [-scaled applied RETROACTIVELY to existing images](https://wordpress.org/support/topic/scaled-applied-retroactively-to-existing-images/)
 *  Thread Starter [benntech](https://wordpress.org/support/users/benntech/)
 * (@benntech)
 * [5 years, 8 months ago](https://wordpress.org/support/topic/scaled-applied-retroactively-to-existing-images/#post-13651797)
 * Thanks for your reply, Joy. However, it doesn’t help me at all. In fact, are 
   you seriously suggesting that rather than insert a single line of code in my 
   child theme that I should write an entire plugin just to disable this feature?
   Wow. I have to question if you understand themes at all. What do you think the
   purpose of a theme’s functions.php file is? WordPress themes literally require
   lines of code to work.
 * Regardless, there is already a plugin to disable this “feature” ([https://wordpress.org/plugins/disable-big-image-threshold/](https://wordpress.org/plugins/disable-big-image-threshold/))
   with currently 10,000+ active installs. That means there are at least other 10,000
   websites that didn’t want this moronic feature, and that number doesn’t include
   all of us who implemented it as a single line of code IN OUR THEME. Even if everyone
   affected by this spent only 10 minutes researching and fixing this problem, that’s
   literally thousands of manhours wasted on this issue, costing businesses tens
   of thousands of dollars. Shouldn’t you–and frankly everyone–be advocating that
   this “feature” be implemented as a toggle in the Dashboard? That could drastically
   reduce the time and money wasted on this issue. BTW, in my case, neither the 
   line of code nor plugin fix my issue and restore my old images and proper names.
 * For those of you like me who have been screwed by this “feature”, the only solution
   I have found so far is to manually restore all my downscaled images, after working
   all night, I am about halfway through my restore of hundreds of photos. Here 
   is the process I am using:
    1.  Install and activate “Enable Media Replace” plugin ([https://wordpress.org/plugins/enable-media-replace/](https://wordpress.org/plugins/enable-media-replace/)).
        This will allow you to replace the image and restore the original name without
        losing any customized attributes like title, description, etc.
    2.  Get direct access to your /wp-content/uploads folder. For most hosted websites,
        this is usually via FTP.
    3.  Find an image that this “feature” f*d up, e.g., MyBigImage-scaled.jpg.
    4.  Download the ORIGINAL image, e.g., MyBigImage.jpg from your /wp-content/uploads
        folder. This saves you the trouble tracking down that original image that you
        uploaded days/months/years ago.
    5.  Delete ALL versions of the image in /wp-content/uploads, e.g., MyBigImage.jpg,
        MyBigImage-scaled.jpg, MyBigImage-300×300.jpg, MyBigImage-scaled-300×300.jpg.**
        WARNING: If you fail to remove the existing files, the replacement image will
        have “-1” appended to its name, which will break all your existing links to
        the image!** (Also, instead of deleting, I personally moved the files to a 
        temporary directory just in case.)
    6.  Go to Media Library and the Attachment Details for the crappily downscaled 
        image, then click the “Upload a new file” button (created by the above plugin).
    7.  Click “Choose File” and select the full-scale image you downloaded above, e.
        g., MyBigImage.jpg. Note that the first line should read `NOTE: You are about
        to replace the media file "MyBigImage-scaled.jpg". There is no undo. Think 
        about it!`
    8.  Under Replacement Options, select “Replace the file, use new file name and 
        update all links”. For Date Options, your choice, but I select “Keep the date”.
        Note that “update all links” doesn’t find everything and is especially lacking
        when the image has been used in 3rd party sliders or theme builders like Elementor,
        so if you did link to a “-scaled” image, you’ll need to manually track down
        all the broken links. Have fun with that.
    9.  Click “Upload” and wait.
    10. Repeat starting at step 3 for all f*d up images.
 * Now, as for 5.6 breaking my theme, I created a child theme from an Imagely theme
   based on the Genesis framework. I just happened across this video [https://www.youtube.com/watch?v=FLM1kjJobbk](https://www.youtube.com/watch?v=FLM1kjJobbk).
   Fast forward to 1 minute mark. Apparently WordPress 5.6 is implementing a huge
   JQuery change that is going to break all Imagely themes and presumably all themes
   based on the Genesis framework. I can only assume there are countless other themes
   and plugins that are going to break as well.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Adaptive Images for WordPress] Switched to HTTPS – does not work anymore](https://wordpress.org/support/topic/switched-to-https-does-not-work-anymore/)
 *  [benntech](https://wordpress.org/support/users/benntech/)
 * (@benntech)
 * [8 years, 12 months ago](https://wordpress.org/support/topic/switched-to-https-does-not-work-anymore/#post-9355847)
 * Thanks, gklauda! Great solution.
 * Nevma, I understand your stance of not knowing where wp-content is located, but
   looking at your code, you’re just hard coding the location in that variable anyway.
   gklauda’s solution just adds the “S” to HTTPS pages without changing anything
   for non-HTTPS. Simple and elegant. You should really consider incorporating gklauda’s
   code–it’s a great fix for the majority of people with standard WordPress installations.
 * Again gklauda, great find. Thanks!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Adaptive Images for WordPress] All Images Broken After Plugin Activation](https://wordpress.org/support/topic/all-images-broken-after-plugin-activation/)
 *  [benntech](https://wordpress.org/support/users/benntech/)
 * (@benntech)
 * [9 years ago](https://wordpress.org/support/topic/all-images-broken-after-plugin-activation/#post-9316475)
 * Definitely fixes it for me. auto_globals_jit = on, no images. auto_globals_jit
   = off with no other changes, images work. Here’s some references:
    [https://odd.blog/2015/02/12/php-notice-undefined-variable-_server-in/](https://odd.blog/2015/02/12/php-notice-undefined-variable-_server-in/)
   [https://stackoverflow.com/questions/5235775/error-using-server-in-a-variable-variable-php](https://stackoverflow.com/questions/5235775/error-using-server-in-a-variable-variable-php)
 * Not sure why it’s an issue on my server–I have canonical names on, server name
   defined, etc.. However, I’m not too concerned because this is only a temporary
   virtual appliance. If this issue was more prevalent among your users, it might
   be worth additional troubleshooting. As it is, this appliance will get deleted
   once the site is moved to a permanent host.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Adaptive Images for WordPress] All Images Broken After Plugin Activation](https://wordpress.org/support/topic/all-images-broken-after-plugin-activation/)
 *  [benntech](https://wordpress.org/support/users/benntech/)
 * (@benntech)
 * [9 years ago](https://wordpress.org/support/topic/all-images-broken-after-plugin-activation/#post-9313927)
 * Update: this broke on me again with same error, but my above fix no longer works.
   Had to disable it for a few days while I researched and found a new solution.
   Edit Apache’s php.ini and set
 * > auto_globals_jit = Off
 * Hopefully Adaptive Images will be more stable once I move it to a permanent host.
   Hate to lose its functionality.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Adaptive Images for WordPress] All Images Broken After Plugin Activation](https://wordpress.org/support/topic/all-images-broken-after-plugin-activation/)
 *  [benntech](https://wordpress.org/support/users/benntech/)
 * (@benntech)
 * [9 years, 1 month ago](https://wordpress.org/support/topic/all-images-broken-after-plugin-activation/#post-9250593)
 * I was about post a new topic with the same error. However, I figured mine out
   while gathering information, so I thought I would share a possible solution for
   everyone with this problem.
 * My Apache logs showed the error “Undefined variable: _SERVER” in adaptive-images-
   script.php. I checked out the script, and via that tracked down that my setup
   had no server name defined and had UseCanonicalName set to off.
 * My fix was to set either or both of these in my Apache2 virtual server directives:
 * > UseCanonicalName On
   >  ServerName my.servername.com

Viewing 5 replies - 1 through 5 (of 5 total)