horst

@Mats, please can you verify that you are using the latest version of CAI3 that is: 1.2.0 ?? If you have used an automated update service, it potentially stuck with version 1.1.18. I now manually updated the record in the modules directory to 1.2.0!

Hey Mats, thanks for testing. I tested saving of different Crop Settings and also edited and or removed them later without issues. So, cannot reproduce. Have you tested it locally or on a online server? Have you used CAI4 alone, or is CAI3 also installed there when you tested? You mean, you are not able to store any settings, never? Or occurred the issue occasionally?

I successfully tested it on one site several times (ca. 10x) with ProCaches between 50 and 700 pages! ? Nice work!

Hey, I've made good progress. I think I have solved the issue for updating / changing from CAI3 to CAI4! ? - So, if you want to use a CroppableImage field for a fresh new site, simply go directly with CroppableImage4! (once it is officially released) - And if you have the CroppableImage3 on an existing site, but want to upgrade to CroppableImage4, (because you need WebP support), follow these easy steps: First update CroppableImage3 to the latest version 1.2.0! After that, additionally install CroppableImage4. Now you can use both modules with the same ->getCrop() method call on pageimages. The getCrop hook "knows" from which field and module version it comes. ? Therefore, from now on, you are free to start using CAI4 for new created template calls to CAI4 fields, while the older CAI3 calls can stay in and are fully functional without any changes. If you want to switch CAI3 fields to CAI4 fields, to benefit from the new functionalities, you can do that in the admin > setup > fields > YOURFIELDNAME editor, by changing the (field) type. (see screenshot beneath, & yes, KEEP SETTINGS!) The only thing you have to check, before doing that, is: looking into your templates code, if you have made use of the optional second param in the old CAI3 ->getCrop() calls. If no, what I think is 99.9% the case, you have to do nothing. If you make use of it, you need to change / adapt your method call in the template file. That's it. Summary: update CAI3 install CAI4 change the fieldtype(s) from CAI3 to CAI4 When I've got some feedback from beta testers (and everything works out as expected) I will release the CAI4 through the modules directory. Until then, you get the RC2 version of it on GitHub: https://github.com/horst-n/CroppableImage4

- + - + - + - + - + - + - + - + - + - NEWS - 2020/03/19 - + - + - + - + - + - + - + - + - + - There is a new Version in the pipe, that supports WebP too: - + - + - + - + - + - + - + - + - + - NEWS - 2020/03/19 - + - + - + - + - + - + - + - + - + -

Hi @Pete, thanks for the warm words. And yep, the times without web fonts was way more challenging in regards to satisfy designers dreams. Especialy when working with designers coming from print media. ?

Hi all, I'm searching for Alpha/Beta tester of the new rewritten Croppable Image module. I opened a new repo on Github, with the name CroppableImage4: https://github.com/horst-n/CroppableImage4 It is a rewrite of the CAI3. I dropped all internal image manipulations, to be more future safe. Now I delegate all this to the parent core image fields methods. To be able to do this, I need to change some things and the module is no longer backwards compatible. A) For the alpha & beta testing, there is a new crop method name: $image->getCrop4(), this may be changed later to the legacy $image->getCrop() method. But for the testing period to avoid conflicts with CAI3, it is named getCrop4(). <- OBSOLETE, see the next post here in thread B) With the first param, you pass the cropname into the method. Optionally you can pass image processing options as a second param, like with the core image field. To do this, you may use an array or a selector string. C) You can use every known options param. Width, Height, Size is ignored! If you also want create WebPs in one go, please add "webpAdd" => true to the options array, (or webpAdd=1 to the options selector string)! D) The resulting image variation names will differ from those of the previous version 3! Please refer to the readme of the repo and, maybe compare it against the version 3, if you not already know it. Thats it so far. I have tested it a bit in the last days and haven't found any issues. But it would be nice if some of you can test it too.

This seems to have to do with problems at the hosting company. Since yesterday I noticed very slow or even timed out connections with a lot domains and also E-Mail connections, hosted on different machines / IPs, but on the same hosting company. ?

Thanks @adrian, this one I have already fixed yesterday for newly cached pages. But there are currently 4500+ pages in ProCache that needs to be rebuild.

@wbmnfktr many thanks, but the design wasn't my work. This goes to Quandel Staudt Design ! I'm more responsible for the massive disk space usage. ? I only have built the homepage and the menus, - and worked on little (front end) things like the archive thumbnails on the homepage for mobile view. The design agency wanted to have fixed partial blue overlays in the bottom, with blur effect for the covered image part. I found out, that sometimes the text was to long to fit into the blue area. My recommended solution was to extend the boxes downwards, so that longer texts fit, but not too much of the image motifs get covered. Since the thumbnails are on white background, it was not possible to simply extend the semi-transparent text boxes downwards. So, now the pictures automatically get lengthened with a black, transparent gradient below and also get the blurred effect directly embedded into the pixels. original thumb like in the desktop version the lengthened (and blurred) thumb the result with the fixed partial overlay

The site of Jörg Hempel was built back in 2013/2014 the first time with ProcessWire, (version 2.3+ or 2.4). Then, over the years, individual areas were repeatedly rebuilt, equipped with new features, etc. Once, more than 50000 original images had to be exchanged and replaced by larger ones. I still remember that I wrote two days on the scripts, with which all original images were automatically exchanged via SFTP and all variants were recreated. At that time, a local computer ran three days and nights continuously in four parallel tasks. The exchange ran smoothly and without a single minute downtime of the live page. Today, the images (incl. variants) occupy over 130 GB disk space. :-) But due to the different version changes, PW 2.4, 2.5, 2.6, 2.7, 2.8(!), all none namespaced, to the namespaced 3.0+, a lot of unsightly solutions were created, e.g. to adapt unmaintained third party modules etc. In the front end were some old libraries in use, too. Therefore Jörg Hempel decided to rework all areas. (design, frontend and backend). Jörg developed the design together with the design agency Quandel Staudt Design from Frankfurt, Germany. The front end was built as a HTML click dummy by Benedikt Seifert from Jena, Germany. I was left with the wiring of front end and back end, as well as the redesign of all server-side processes. The new site now runs on PW 3.0.148 and PHP 7.4, using ProCache, AOS and my image helpers (Pia, PageimageManipulator2, CroppableImage3). All images use lazyload, and infinite scrolling was dropped, so we don't have to use the m.domain for mobiles any more. The extensive filtering possibilities of the archive and the blog from the old site have been preserved. Url segments are used for the filters.

Maybe you have changed something of the startpages template family settings? Especially the allowed child templates?

Have you emptied the trash?

Goldkinder Psychotherapie Website of the child and youth psychotherapist Heike Maßen from Mönchengladbach, Germany. A one-pager that gives an insight into her work and her practice rooms, as well as information about many relevant aspects. It's a simple responsive one-pager with a nice design from Uta Hugenbruch. The front end is build without any framework.

@Robin S, a side question here: Do you know a way how to make the labels multilanguage aware? With the CAI3, I also use a textareafield like yours in the configpage. It would be pretty fine, if there would be an easy to maintain way for the users / devs to translate the labelnames.

Hi Jim Bailie of @Davis Harrison Dion, if you not already have noticed, Pete lately has worked on the developer directory and everything seems to be working fine now. Even (later) changes of the content and the approval processes are working well again.

currently this is not supported, but I build a new version of the module and will try to include this, because it is a useful feature.

You mean for multilanguage usage?

@kunago, here a screenshot with the selections for a 1920x750 px variation and a mobile version of 960x750 px: The live site of this example is https://www.die-wurzen-studie.de/ , where all of those fullwidth images (1920x750 px) have a mobile version of 960x750 px for the smaller screen resolutions.

@kunago: CroppableImages only purpose is the creation of variations with fixed aspect ratios. But you need to define it in pixels. Lets say you need a 3:1 result, your original image is 3000x3000 px, you need to define the outcoming pixeldimensions, for example 900x300, or 1800x600, or 3000x1000, ... Then you will get a fixed aspect ratio rectangle to select your desired area. The result then is rendered as variation with your defined pixel dimensions.

Yep. ?

there is a thirdparty module available, that let you define different crops with absolute width x height sizes. It is called CroppableImage3.

then you can let this out. try it like this: $p->of(false); $title = trim($p->get('seo_title')); $title = $title ? $title : 'inherit'; $desc = trim($p->get('seo_description')); $desc = $desc ? $desc : 'inherit'; var_dump($title); var_dump($desc); $p->seo->meta->title = $title; $p->seo->meta->description = $desc; echo $p->save() ? " - 1" : " - 0";

so you need to check that the fieldnames (your old fieldnames and the new ones) are adressed correct in the script part that came from Wanze. Also you can output the result of the save() method, for example by using var_dump($p->save());

Hi, you need to remove my name from the check, if its a Superuser, who called the script. Please follow the comments in the script to adapt all parts to suit your needs, (selector, fieldnames, ...), and you may add some temporary checks when testing the script first time. AT FIRST, uncomment the //die('BREAK!!'); line, so that you only test with one page. (Script stops after first loop). Maybe this is already all what is to do. If not, come back and tell what is missing or has happened.