Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
There is no textfield in the config settings to specify imageinfo_cache_url_key, although that variable is used and checked in a few places. It would be nice to have an addition to the admin page to allow that to be entered.
Comment | File | Size | Author |
---|---|---|---|
#4 | imageinfo_cache-1160936-4.patch | 1.69 KB | mikeytown2 |
Comments
Comment #1
rjbrown99 CreditAttribution: rjbrown99 commentedActually this seems to work differently than I would expect. I would think you set a shared key on the server and client, and perform an access check on that key on the async worker before proceeding. It doesn't seem like that is the case? Or is the current assumption that you are passing async between systems that have the same backend DB? I would want to spin up cache-only servers with their own DB to minimize the Drupal memory load on the worker machines.
Comment #2
rjbrown99 CreditAttribution: rjbrown99 commentedUI was easy enough... dropped this in to imageinfo_cache.admin.inc. Now I can set keys to match on servers with different backends.
Comment #3
rjbrown99 CreditAttribution: rjbrown99 commentedHmm... one of the other assumptions seems to be that you have a shared underlying filesystem between the primary server and async workers. It runs imagecache_generate_image($preset, $file->filepath); I would have thought it would return that to the caller but it writes it out. So I guess I need to mount the files dir between the two hosts.
Comment #4
mikeytown2 CreditAttribution: mikeytown2 commentedThis is the patch that was committed.