Jump to content
apeisa

Release: Thumbnails

Recommended Posts

Haven't thought about that use case at all, to be honest. I think that best way to support that would be offering "real" image cropping tool, that creates copies of original image, not just reference.

Share this post


Link to post
Share on other sites

The main reason I asked was due to the fact that adding a resized image with a link to the fullsize image just acts as a hardlink to it. i guess i could override this with jquery for javascript enabled users to load the image in a lightbox type thing instead.

Share this post


Link to post
Share on other sites

Thanks apeisa, I'm currently again testing with repeaters and there seems an issue with cropimages (not sure if images suffer the same) when I add a new repeater element on page with an cropimage field and upload an image, after saving the page the added element dissapears. Though after adding an element again there's still the image uploaded before (already reported issue on repeater thread, but think not solved yet). But after saving the page again then, it stays there and when clicking the "thumbnail" link a new window opens with this error:

Fatal error: Call to a member function get() on a non-object in /Applications/XAMPP/xamppfiles/htdocs/pw-dev/site/modules/Thumbnails/ProcessCropImage/ProcessCropImage.module on line 50

@soma did you resolve this issue? I am getting the same error when trying to open up the thumbnail cropper on all my CropImage fields (I have about 6). Not sure when this happened - I am using the field in some repeater elements - however the error is affecting all CropImage fields even those not in a repeater element.

The CropImage field is still working and creating all the thumbnails, it's just the crop edit window that is showing this error.

Share this post


Link to post
Share on other sites

@soma did you resolve this issue? I am getting the same error when trying to open up the thumbnail cropper on all my CropImage fields (I have about 6). Not sure when this happened - I am using the field in some repeater elements - however the error is affecting all CropImage fields even those not in a repeater element.

The CropImage field is still working and creating all the thumbnails, it's just the crop edit window that is showing this error.

Nope sorry.

Share this post


Link to post
Share on other sites

@apeisa

A client complained about not seeing the whole image if it is larger then his screen. I was able to fix this simply by adding 2 lines (boxWidth and boxHeight) in ProcessCropImage2.js. Maybe you can add something like this to your official release too?

Btw, this module so really great, and my customers are loving it! Thank you so much for releasing it!

$(function(){
$crop = $('#jcrop_target');
if ($crop.length > 0) {
 var w = $('#jcrop_target').data('width');
 var h = $('#jcrop_target').data('height');
 $crop.Jcrop({
  onChange: showCoords,
  onSelect: showCoords,
  aspectRatio: w/h,
  boxWidth: screen.width - 100,
  boxHeight: screen.height - 100
 });
}
$('#show_preview').click(function(){
 $('#preview-container').toggleClass('hide');
})
});
  • Like 2

Share this post


Link to post
Share on other sites

I had the same repeater problem that Soma reported some time ago. Following changes to ProcessCropImage.module got it working:

			   $this->setFuel('processHeadline', 'Crop images');

+			   $field = $this->input->get->field;
+			   if (preg_match("/_repeater[0-9]+$/", $field)) {
+				   $pages_id = (int) end(explode("_repeater", $field));
+				   $field = str_replace("_repeater$pages_id", "", $field);
+			   } else {
			   $pages_id = (int) $this->input->get->pages_id;
+			   }
		   $filename = $this->input->get->filename;
-			   $field = $this->input->get->field;
		   $height = $this->input->get->height;
		   $width = $this->input->get->width;
		   $prefix = $this->input->get->prefix;

This is a bit of a hack and I haven't even tested it properly, so I'm definitely not saying that anyone should use the same method -- but it worked for me :)

  • Like 2

Share this post


Link to post
Share on other sites

Thanks Guys.

Interrobang: tested and worked nicely - thanks for the tip, I just committed it. Great improvement.

Teppo: I think there should be cleaner way to see if field is repeater. Probably by getting the actual field an checking it's fieldtype. But this is great news to know the solution for this problem. Will look into this soon (before holidays I hope).

  • Like 2

Share this post


Link to post
Share on other sites

So I have a simple question. I am doing something very wrong I guess, I have two issues.

Issue 1. When I go to hover over the thumbnail in the images field, it breaks. Not really sure what is going on here, but I can live with this issue. (found solution to this one.)

Issue 2. I can't figure out how to pull the thumbnails, if they exist into my template. I am currently using this:

<ul class='gallery'>
<?php
foreach($page->images as $image) {
$thumb = $image->size(500, 400);
echo "<li class='gallery-item'>";
echo "<a href='{$image->url}' class='albumImageLinks fancybox-button' rel='fancybox-button'>";
echo "<img class='gallery-image' src='{$thumb->url}' alt='{$thumb->description}' /></a>";
echo "</li>";
}

?>
</ul>

However, I want to pull a thumbnail if it exist for certain images which I need to crop using your module. I have tried everything in the directions, but I keep getting errors involving eq.

Sorry I am not the best at php.

------------------------------------------------

Solved my problem: for people in the future here is the code that worked for me:

<ul class='gallery'>
<?php
foreach($page->port_images as $image) {
  $thumb = $image->getThumb('thumbnail');
  echo "<li class='gallery-item'>";
  echo "<a href='{$image->url}' class='albumImageLinks fancybox-button' rel='fancybox-button'>";
  echo "<img class='gallery-image' src='{$thumb}' /></a>";
  echo "</li>"; 
}

?>
</ul>

Also you need to create a thumbnail settings that matches what you were going to use for the size parameters. For me I was using 500/400, if you describe these settings, they are defaulted, then you can crop to the size you need for specific pictures, the rest are center cropped, which is exactly what I needed! Thanks for this fantastic solution for cropping images!

  • Like 2

Share this post


Link to post
Share on other sites

The problem you might have (I think) is if you change the fieldtype from Image to cropImage, it automatically creates a default thumbnail so you can't test for the absence of one and use your original Image fieldtype-cropped image. I might be totally wrong here though.

If you were using a one-page-per-image setup it might be easier because you can just serve an alternative cropped image.

[example written in the browser so not sure it works exactly]

<?php
$featured = $pages->get("/page/")->children;
foreach($featured as $feature) {
$thumbnail = $feature->thumbfield; /*check for the thumbnail field */
 if(!$thumbnail) {
 $thumbnail = $feature->imagefield->size(400,500); /* if no thumbnail field just use the regular image field */
 echo "<img src='{$thumbnail->url}' alt='{$feature->title}'/>";
} else {
 echo "<img src='{$thumbnail->getThumb('thumbs')}' alt='{$feature->title}'/>";
}

Regards

Marty

Share this post


Link to post
Share on other sites

Just merged pull request from Ryan, which includes few nice improvements to this module:

1. Support for securefiles (coming in 2.3)

2. Works on regular image files

3. Some minor code tweaks (sanitizing & indentation)

Ryan: about "works on regular image field also": how does it work? Thumbnail settings are set per field basis, and the setting field is visible only when fieldtype is cropImages - so where does it get thumbnail sizes for regular images?

I tested the commit before merging and it didn't break anything on my test installation - so it should be safe to just pull in the latest changes.

Thanks for the update Ryan!

  • Like 3

Share this post


Link to post
Share on other sites

4. One other thing I added: If you delete an image, it won't leave the crops behind (they get deleted too). Previously the crop files would stick around even after the original image was gone.

Ryan: about "works on regular image field also": how does it work? Thumbnail settings are set per field basis, and the setting field is visible only when fieldtype is cropImages - so where does it get thumbnail sizes for regular images?

The field config is defined in InputfieldCropImage.module rather than FieldtypeCropImage.module, so that's why it works. It's more your doing than mine, as I only had to tweak a couple things to make it work. It was an accidental find too. Meaning, I wasn't intending to add this specifically, but noticed it worked through my own error of forgetting to change the fieldtype. It's possible I'm missing something, but it all seemed to work fine here. Of course, the FieldtypeCropImage is still a necessary component. But it's acting like an autoload module, adding hooks to Pageimage and Pageimages.

  • Like 2

Share this post


Link to post
Share on other sites

Ah, actually the per field settings were another community contribution. I think it wouldn't be too hard to get rid of the FieldtypeCropImage alltogether, need to take a good look at it some point.

Share this post


Link to post
Share on other sites

I just added this module to a standard 2.2.9 installation, had two existing posts with images already uploaded using the core 'Image' field type and changed the 'images' field's type and input field type to 'CropImage'.

Now I am getting a 'There is no thumb called thumbnail' message (with the rest of the page being blank, no input forms displayed) whenever I open an existing post with previously uploaded images. When I create a new post, I get the same message within the image upload form after uploading an image.

Any idea what I am doing wrong?

Share this post


Link to post
Share on other sites

From mobile: check field settings and resave the field. Empty modules cache.

Share this post


Link to post
Share on other sites

From mobile: check field settings and resave the field. Empty modules cache.

Emptying the cache and resaving did the job. I also temporarily added a second thumbnail configuration but removed it again, so I am not sure what the actual problem was. Thanks for the lightning fast support!

By the way: the whole UI is really state of the art, props!

Share this post


Link to post
Share on other sites

It has problems if you change a image field to cropimage field. At least it was for me.

Share this post


Link to post
Share on other sites

Thanks a lot for this great module, this really makes image handling in Processwire a breeze.

That said, I'm looking for a quite specific feature that seems to be hard to accomplish with the current module. I'd like to recrop a given image with the same visible section as a given image version. Imagine I have an image version for crop image set up to be 150x100. Then I need a version of that image in 100x100, but cropping from the section that was selected for the 150x100 version. The new image should be generated from the originally uploaded one to not run into more issues with quality, for sure.

Does anyone see a way how this might be possible already?

And can this be integrated in the module? I'm imagining something like

$page->myImage->getThumb('sizename', 100, 100);

With kind regards, Marc

Share this post


Link to post
Share on other sites

That is really special edge case, I don't think I'll take this module into that direction, sorry Marc. But of course you could use this module as a starting point for your need for sure. Difficult to say how to achieve that goal though...

Share this post


Link to post
Share on other sites

Thanks for your quick answer, Anttii!

I can really understand that this doesn't fit in there too well. Still I'm wondering how to do it, too.

One option would be to define addional sizes that inherit proportions and section from another size in the field settings already:

thumbnail, 150, 100
thumbnailvariant, 100, 100, thumbnail

'thumnailvariant' would then not be shown when editing the field and might be generated right after 'thumbnail' is generated. This wouldn't enable to get arbitrary sized images, but should be relatively easy to accomplish and would definitely fit my needs at the moment.

To enable this, it would be necessary to store the data from jCrop (x and y coordinates, width and height) in it's own table in the DB to do custom crops based on that data later. This variant sounds like a lot of work but also would be a great basis for a lot of other features that might come later (i.e. being able to change the proportions of certain image sizes without losing all custom crops already done by batch processing existing images).

I'll definitely wrap my head around this, might take some time though.

Share this post


Link to post
Share on other sites
Does anyone see a way how this might be possible already?

I think that you can do this all with CSS. Once you've got a crop, you can automatically CSS position it within a markup container (that has overflow hidden) to achieve variations like those you mentioned. That is, so long as the crop is something smaller than the original. You could go about it either using an <img> in a <div>, or just a <div> with a background image. If you need to just scale, or scale and crop, you'd probably want to use an actual <img> tag that specifies either the target width OR height (not both) with the other dimension overflow:hidden by the container. If you are supporting high DPI/retina displays, you are probably already doing this to some extent, in terms of the scaling aspect. 

  • Like 1

Share this post


Link to post
Share on other sites

Hi Ryan, thanks for your answer. I think you're pretty right for a lot of use cases, but this doesn't serve my use case here.

I think I didn't make it clear enough that I don't only want to crop but zoomcrop, cropping of the larger dimension so that after zooming the smaller dimension fits. Also I want to use these different versions of the image on different pages (overviews, recommendations to other pages, etc).

I still might scale browserside with an <img> tag resized with CSS, but this isn't a good practice, the resizing of older browser is quite bad and it will limit me to an aspect ratio.

For the project I'm working on now, I'm just going to add another image variant in the CropImage field settings. This is a little less comfort, but since this won't be used too much either way, I can't afford to spent the time to rewrite the CropImage module to serve my needs. I'll definitely come back to this, because I think that I'd still want to see this in the module.

Thanks for all your help so far,

Marc

Share this post


Link to post
Share on other sites
I still might scale browserside with an <img> tag resized with CSS, but this isn't a good practice, the resizing of older browser is quite bad and it will limit me to an aspect ratio.

This was a bad practice years ago. Correct me if I'm wrong, but this is not a bad good practice now, at least if you want to support high DPI screens? I mean if you go inspect the ProcessWire logo in the upper left hand corner and open it in a new window, you'll see the actual image is much larger than it appears on the site. That's the only reason it looks sharp on a retina screen. Yes, this might make it look bad on IE6, but well… if you are using IE6, life is already a bummer. :)

The purpose of specifying one dimension with the <img> tag and using an overflow:hidden for the other is to prevent any stretching of the image (maintain aspect ratio).

I've not personally used this technique, so not speaking from experience. But it seems so simple that I'm inclined to try it. 

I think I didn't make it clear enough that I don't only want to crop but zoomcrop, cropping of the larger dimension so that after zooming the smaller dimension fits

Unless you are talking about upscaling an image (I'm guessing not) then it just means you've got to start with a bigger crop, in terms of physical dimensions.

Share this post


Link to post
Share on other sites

Ryan, you're pretty right about everything you said there, but I just didn't make my use case clear:

I don't want to support retina screens, but I want completely different version of an image while saving the same clipping. What I want is for example let the user crop an image to 400x300 with the CropImage-Inputfield and use this image somewhere (i.e. as a preview in article overviews) as it is.

At another place I want the same image sized to 200x100. Everything's different about this, the size and the aspect ratio. I don't want my user to crop to this size on his own (because that might get a lot of different versions of an image for a large site) and I just assume, that what is in the 400x300 version is the most important part of the image and will work in the smaller dimension, too. So I want to zoomcrop my 200x100 version from the center of the 400x300 version, but not working with that image again but with the original image to get the best quality.

I hope this is more understandable now :-)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Sten
      Hello
      Till now I hacked something with the twig template but it works no more with new PW versions so I look forward to create a module. I am working on a site in multiple languages : French, English, Italian, German, Spanish, Portuguese, Hebrew, Russian. The new posts are entered in any language with a field for language. Till now, I got twig files to get the translations with constants defined for each part of the pages.
      So I'd like to create a module to include theses files added according to the url /fr/en/...
      Have you some observations to do before I begin about the direction to take ?
      Thank you
    • By ukyo
      Mystique Module for ProcessWire CMS/CMF
      Github repo : https://github.com/trk/Mystique
      Mystique module allow you to create dynamic fields and store dynamic fields data on database by using a config file.
      Requirements
      ProcessWire 3.0 or newer PHP 7.0 or newer FieldtypeMystique InputfieldMystique Installation
      Install the module from the modules directory:
      Via Composer:
      composer require trk/mystique Via git clone:
      cd your-processwire-project-folder/ cd site/modules/ git clone https://github.com/trk/Mystique.git Module in live reaction with your Mystique config file
      This mean if you remove a field from your config file, field will be removed from edit screen. As you see on youtube video.
      Using Mystique with your module or use different configs path, autoload need to be true for modules
      Default configs path is site/templates/configs/, and your config file name need to start with Mystique. and need to end with .php extension.
      Adding custom path not supporting anymore !
      // Add your custom path inside your module class`init` function, didn't tested outside public function init() { $path = __DIR__ . DIRECTORY_SEPARATOR . 'configs' . DIRECTORY_SEPARATOR; Mystique::add($path); } Mystique module will search site/modules/**/configs/Mystique.*.php and site/templates/Mystique.*.php paths for Mystique config files.
      All config files need to return a PHP ARRAY like examples.
      Usage almost same with ProcessWire Inputfield Api, only difference is set and showIf usage like on example.
      <?php namespace ProcessWire; /** * Resource : testing-mystique */ return [ 'title' => __('Testing Mystique'), 'fields' => [ 'text_field' => [ 'label' => __('You can use short named types'), 'description' => __('In file showIf working like example'), 'notes' => __('Also you can use $input->set() method'), 'type' => 'text', 'showIf' => [ 'another_text' => "=''" ], 'set' => [ 'showCount' => InputfieldText::showCountChars, 'maxlength' => 255 ], 'attr' => [ 'attr-foo' => 'bar', 'attr-bar' => 'foo' ] ], 'another_text' => [ 'label' => __('Another text field (default type is text)') ] ] ]; Example:
      site/templates/configs/Mystique.seo-fields.php <?php namespace ProcessWire; /** * Resource : seo-fields */ return [ 'title' => __('Seo fields'), 'fields' => [ 'window_title' => [ 'label' => __('Window title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'attr' => [ 'placeholder' => __('Enter a window title') ] ], 'navigation_title' => [ 'label' => __('Navigation title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'showIf' => [ 'window_title' => "!=''" ], 'attr' => [ 'placeholder' => __('Enter a navigation title') ] ], 'description' => [ 'label' => __('Description for search engines'), 'type' => Mystique::TEXTAREA, 'useLanguages' => true ], 'page_tpye' => [ 'label' => __('Type'), 'type' => Mystique::SELECT, 'options' => [ 'basic' => __('Basic page'), 'gallery' => __('Gallery'), 'blog' => __('Blog') ] ], 'show_on_nav' => [ 'label' => __('Display this page on navigation'), 'type' => Mystique::CHECKBOX ] ] ]; Searching data on Mystique field is limited. Because, Mystique saving data to database in json format. When you make search for Mystique field, operator not important. Operator will be changed with %= operator.
      Search example
      $navigationPages = pages()->find('my_mystique_field.show_on_nav=1'); $navigationPages = pages()->find('my_mystique_field.page_tpye=gallery');
    • By Robin S
      This is a module I made as an experiment a while ago and never got around to releasing publicly. At the time it was prompted by discussions around using Repeater fields for "page builder" purposes, where the depth feature could possibly be used for elements that would be nested inside other elements. I thought it would be useful to enforce some depth rules and translate the depth data into a multi-dimensional array structure.
      I'm not using this module anywhere myself but maybe it's useful to somebody.
      Repeater Depth Helper
      This module does two things relating to Repeater fields that have the "Item depth" option enabled:
      It enforces some depth rules for Repeater fields on save. Those rules are:
      The first item must have a depth of zero. Each item depth must not be more than one greater than previous item depth. It provides a RepeaterPageArray::getDepthStructure helper method that returns a nested depth structure for a Repeater field value.
      Helper method
      The module adds a RepeaterPageArray::getDepthStructure method that returns a multi-dimensional array where the key is the page ID and the value is an array of nested "child" items, or null if there are no nested children.
      Example

      The module doesn't make any assumptions about how you might want to use the depth structure array, but here is a way you might use it to output a nested unordered list.
      // Output a nested unordered list from a depth structure array function outputNestedList($depth_structure, $repeater_items) { $out = "<ul>"; foreach($depth_structure as $page_id => $nested_children) { $out .= "<li>" . $repeater_items->get("id=$page_id")->title; // Go recursive if there are nested children if(is_array($nested_children)) $out .= outputNestedList($nested_children, $repeater_items); $out .= "</li>"; } $out .= "</ul>"; return $out; } $repeater_items = $page->my_repeater; $depth_structure = $repeater_items->getDepthStructure(); echo outputNestedList($depth_structure, $repeater_items);
       
      https://github.com/Toutouwai/RepeaterDepthHelper
      https://modules.processwire.com/modules/repeater-depth-helper/
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
    • By MoritzLost
      This module allows you to integrate hCaptcha bot / spam protection into ProcessWire forms. hCaptcha is a great alternative to Google ReCaptcha, especially if you are in the EU and need to comply with privacy regulations.

      The development of this module is sponsored by schwarzdesign.
      The module is built as an Inputfield, allowing you to integrate it into any ProcessWire form you want. It's primarily intended for frontend forms and can be added to Form Builder forms for automatic spam protection. There's a step-by-step guide for adding the hCaptcha widget to Form Builder forms in the README, as well as instructions for API usage.
      Features
      Inputfield that displays an hCaptcha widget in ProcessWire forms. The inputfield verifies the hCaptcha response upon submission, and adds a field error if it is invalid. All hCaptcha configuration options for the widget (theme, display size etc) can be changed through the inputfield configuration, as well as programmatically. hCaptcha script options can be changed through a hook. Error messages can be translated through ProcessWire's site translations. hCaptcha secret keys and site-keys can be set for each individual inputfield or globally in your config.php. Error codes and failures are logged to help you find configuration errors. Please check the README for setup instructions.
      Links
      Github Repository and documentation InputfieldHCaptcha in the module directory (pending approval) Screenshots (configuration)

      Screenshots (hCaptcha widget)

       
       

       
×
×
  • Create New...