• Resolved lennardv

    (@lennardv)


    When using 100×0 the image will have a width of 100 and a height that maintains the aspect ratio. However, the file does not seem to be written to the resized folder. Only the first call to the url it will do the resizing, the next time it’s the full image.

    Can you support this kind of behaviour in the plugin?

    • This topic was modified 6 years ago by lennardv.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author alpipego

    (@alpipego)

    Unfortunately, I can’t reproduce this behavior. Could you please link to an image where I can see this? If this is still an issue, could you please also add your ResizeFly settings to this issue via the following MySQL query:

    
    SELECT option_name, option_value FROM wp_options WHERE option_name LIKE "resizefly%";
    

    Please see https://www.nambaheins.de/uploads/resizefly/2018/06/nh-start-100×[email protected] for an image that works this way.

    • This reply was modified 6 years ago by alpipego.
    Thread Starter lennardv

    (@lennardv)

    Is the 100×[email protected] written to the resized folder? The 0 is replaced here with the resized value (which happens in Handler->parseRequestedImageSize()). The next time i call this image, it’s going through php again, creating an unnecessary added delay.

    I fixed this for myself in resizefly by using REQUEST_URI in Handler->setImageName().

    option_name	option_value
    resizefly_options	a:2:{s:5:"cache";a:3:{s:6:"suffix";s:7:"resized";s:4:"path";s:68:"/www/****/public_html/wp-content/uploads/resized";s:3:"url";s:58:"https://****/wp-content/uploads/resized";}s:10:"duplicates";a:2:{s:6:"suffix";s:19:"resizefly-duplicate";s:4:"path";s:80:"/www/****/public_html/wp-content/uploads/resizefly-duplicate";}}
    resizefly_purge_cache	
    resizefly_remove_resized	
    resizefly_resized_path	resized
    resizefly_restrict_sizes	
    resizefly_sizes	a:4:{s:9:"thumbnail";a:4:{s:6:"active";b:1;s:5:"width";i:150;s:6:"height";i:150;s:4:"crop";b:1;}s:6:"medium";a:4:{s:6:"active";b:1;s:5:"width";i:300;s:6:"height";i:300;s:4:"crop";b:0;}s:12:"medium_large";a:4:{s:6:"active";b:1;s:5:"width";i:768;s:6:"height";i:0;s:4:"crop";b:0;}s:5:"large";a:4:{s:6:"active";b:1;s:5:"width";i:1024;s:6:"height";i:1024;s:4:"crop";b:0;}}
    resizefly_sizes_outofsync	a:3:{s:3:"new";a:0:{}s:7:"updated";a:0:{}s:7:"missing";a:0:{}}
    resizefly_user_sizes	a:0:{}
    resizefly_version	3.0.0
    resizefly_version_initial	2.1.4

    resizefly_version seems to be 3.0.0 in database but resizefly.php tells me it’s 3.1.0.

    Plugin Author alpipego

    (@alpipego)

    I now understand what you’re getting at:
    It’s true that the image is written as e.g. 100×[email protected] to the uploads folder because that is the image size being created.

    You want the image to actually be written as [email protected] to the filesystem… In my design so far, the request to 0 image sizes always implied a PHP-roundtrip.
    I’ll have to think about if it’s reasonable to create two image sizes whenever a 0-size is requested.

    Can you share how you changed the code in Handler->setImageName()?

    (Thanks for catching the bug in the 3.0.0/3.1.0 version number).

    • This reply was modified 6 years ago by alpipego.
    • This reply was modified 6 years ago by alpipego.
Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Using 100×0 to keep aspect ratio’ is closed to new replies.