Jump to content
horst

CroppableImage

Recommended Posts

 

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

                             for PW 3.0+ please follow this link!

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

Croppable Image

Module for PW >= 2.5.11 and PW <= 2.7.3

Version 0.8.3 alpha


Hey, today I can announce an early (alpha) release of CroppableImage, what was forked from Anttis Thumbnails module.

Until now there was a lot of work done by owzim, Martijn Geerts and me.

We have solved the issues regarding the list from here:

  • The modules are bundled together so that you only can and have to use FieldtypeCroppableImage for install, uninstall & configure.
     
  • It uses new naming scheme that was introduced with PW 2.5.0 that supports suffixes.
     
  • The complete image rendering is delegated to the core ImageSizer, or to any optional hooked in rendering engine.
     
  • Template-settings are now fully supported, including removing variations when settings have changed.
     
  • It fully respects settings for upscaling. If upscaling is set to false, you cannot select rectangles smaller than the crop setting.
     

We implemented these enhancements:

  • The GridView now is very nice and compact, and also benefits from the lately introduced setting for $config->adminThumbOptions.
     
  • Permanent storage of the crop coordinates, quality and sharpening settings are now implemented native. No need to use PiM for this anymore.
     
  • The usage/display of the Quality and Sharpening DropDown-Selects can be globally disabled/allowed in the modules Configpage. (additionally to that a setting on a 'per field base' is planned.)

And the most wanted feature by the community: It gives back a pageimage and not the URL-string. This way you can use it like this:

// get the first image instance of crop setting 'portrait'
$image = $page->images->first()->getCrop('portrait');

You can further use every pageimage property like 'url', 'description', 'width' & 'height' with it:

// get the first image instance of crop setting 'portrait'
$image = $page->images->first()->getCrop('portrait');
echo "<img src='{$image->url}' alt='{$image->description}' />";

And you can proceed further image rendering with it:

// get the first image instance of crop setting 'portrait' and proceed a resize with imagesizer
$image = $page->images->first()->getCrop('portrait');
$thumb = $image->width(200);

// or like this:
$thumb = $page->images->first()->getCrop('portrait')->width(200);

// and if you have installed Pia, you can use it here too:
$thumb = $page->images->first()->getCrop('portrait')->crop("square=120");

The only downside with this is that when you (as the site developer) have enabled the usage of DropDown-Selects in the images editor, you do not know the values the editors have chosen for the images.

As a workaround for this you can use the getCrop() method with a second param. This is a PW selector string. It can contain as many of the known pageimage options like 'quality', 'sharpening', 'cropping', etc, as you need, but none of them is required. But required is at least one setting for 'width' or 'height':

$image = $page->images->first()->getCrop('portrait', "width=200");
$image = $page->images->first()->getCrop('portrait', "width=200, height=200, quality=80");
$image = $page->images->first()->getCrop('portrait', "height=400, sharpening=medium, quality=75");

.

.

You can get the module from GitHub: https://github.com/horst-n/CroppableImage

(Better Docs are coming soon)


Screenshots

croppable-image_screens-01.jpg

croppable-image_screens-02.jpg
croppable-image_screens-03.jpg



Related Infos

A good setting in site/config.php for the AdminThumbs are: (height=>200 and scale=>0.5 !)

 

$config->adminThumbOptions = array(
  'width' => 0,
  'height' => 200,
  'scale' => 0.5,
  'imageSizer' => array(
    'upscaling' => false,
    'cropping' => true,
    'autoRotation' => true,
    'sharpening' => 'soft',
    'quality' => 90,
    'suffix' => array(),
  )
);
Edited by horst
added link to new PW 3 version
  • Like 33

Share this post


Link to post
Share on other sites

Thanks to the three of you for you work on this! Can't wait to test - will definitely be using it on a new site that is starting dev in the next couple of weeks. I'll let you know how it goes!

  • Like 2

Share this post


Link to post
Share on other sites

Thanks for this, folks. Looks great, can't wait to give it a try!

As a minor observation, you might want to repeat some of the recent fixes for Thumbnails module here too (strict standards, repeater permissions, etc.)

  • Like 2

Share this post


Link to post
Share on other sites

Very nice! As the thumbnails module got more and more out of date it faded from my default modules list. But I think this will be the replacement mighty soon.

  • Like 2

Share this post


Link to post
Share on other sites

How stable is this version? I plan to try this for a recent project that's going live soon. Thanks for the work put into this!

  • Like 2

Share this post


Link to post
Share on other sites

Would be great to build easy gallery fields with different thumbs or a imagefield for blogposts....really thumbs up.

will test asap!

  • Like 1

Share this post


Link to post
Share on other sites

Hey guys - I have just started using this and have a couple of issue:

Notice the way the image is transparent over the grey info bar?

post-985-0-96098200-1421094173_thumb.png

In thumbnail view, the crop button is not showing.

Also I have two croppable image fields and toggling the thumb/list view buttons on one change the view on the other - not sure if this is related to croppable image or not though.

post-985-0-94478100-1421094099_thumb.png

One more thing - might just be me, but I'd prefer to see the crop buttons just below the image - ie, above the description and tags fields.

Thanks!

Share this post


Link to post
Share on other sites

Hey @adrian, just to clarify:

1) in grid view (thumbnail view) you need to hover over the little headline (width x height), than this changes to "Edit" and you need to  click this to get into a little modal window that holds all crop buttons and all the text inputfields, for e.g. description, tags, etc. Does this not work for you? If not, what browser version you are using?

2) what admin theme are you using?

3)

One more thing - might just be me, but I'd prefer to see the crop buttons just below the image - ie, above the description and tags fields.

Is this related to the list view or the grid view, or both?

Share this post


Link to post
Share on other sites
1) in grid view (thumbnail view) you need to hover over the little headline (width x height), than this changes to "Edit" and you need to  click this to get into a little modal window that holds all crop buttons and all the text inputfields, for e.g. description, tags, etc. Does this not work for you? If not, what browser version you are using?

Good point - sorry I had seen that - I was confusing list view with thumbnails displayed vs grid/thumbnails view. I think it works as you have it, but I think things look a little ugly in list view when you don't have the field set to use thumbnails, but rather the full sized version - maybe that is why I am getting the image centered and overlapping the info bar above?

2) what admin theme are you using?

I am just using the standard default theme - PW 2.5.13

Is this related to the list view or the grid view, or both?

Probably doesn't matter in the popup for the grid view, but in the list view I think it would be more obvious for users, but not a big deal.

Share this post


Link to post
Share on other sites

Ah, I always use Thumbnails in Listview, have tried the fullsize images in Listview a while ago.

Yes, the (unhovered) titlebar is transparent and overlaps the image. Maybe we simply should make it opaque? Or do you think this few lines can be important enough to not get covered?

But anyways, I have to hand this over to @Martijn !

------

One more thing - might just be me, but I'd prefer to see the crop buttons just below the image - ie, above the description and tags fields. ( <= Related to Listview with fullsize images)

Probably doesn't matter in the popup for the grid view, but in the list view I think it would be more obvious for users, but not a big deal.

In Listview with thumbnails I like it as it is now, but in Listview with centered fullsize images it may look a bit better if the buttons are appear directly under the image and centered too, followed by the text inputfields. But I have to give this to @Martijn too :)

  • Like 1

Share this post


Link to post
Share on other sites
Or do you think this few lines can be important enough to not get covered?

I guess I don't understand why the look is different to a standard PW images field - ie opaque and not covering the image - I think it is important to see all the image.

Thanks for looking into these things Martijn!

Share this post


Link to post
Share on other sites

Notice the way the image is transparent over the grey info bar?

 

That's not a bug, it's meant to be like that. This wil result in more visual image and less UI (margin/paddings), it'll save you at least 45px height per image. Making it totally transparent can be an option, but i'm a little bit afraid text and buttons in the header will be hard to read.

 

One more thing - might just be me, but I'd prefer to see the crop buttons just below the image - ie, above the description and tags fields.

Problem is amount of crop variations, the length of the crop text (especially in European languages) and extra vertical space the crop should take due to repetitive buttons. In most cases it'll double the vertical space (I started this way), IMHO it's not an option.

  • Like 1

Share this post


Link to post
Share on other sites

@Martijn: ah, for me this makes sense: saving space with full images.

And with a lot of images so boringly showing repetitive cropnames throws away the focus from the thumbnails.

And that it is visually different from default images field is a plus.

@Martijn: have you also read that if you have two or more croppable fields on one page, toggling the viewmode (list/grid) always affects all fields?

  • Like 1

Share this post


Link to post
Share on other sites

@Martijn: have you also read that if you have two or more croppable fields on one page, toggling the viewmode (list/grid) always affects all fields?

No didn't read that. ( I'm a bad reader :unsure:  ) Oké will look into that, should not be hard to fix I guess....

  • Like 1

Share this post


Link to post
Share on other sites

Is there any particular feature from PHP 5.4 you are using? I think many are using Ubuntu's release cycle (5 year LTS from 2012), where there will be PHP 5.3. for two more years (of course possible to update to 14.04).

  • Like 2

Share this post


Link to post
Share on other sites

I can't remember why it was set to PHP >= 5.4.0.  (@owzim: can you remember it?)

I also have no server with PHP 5.3 at hand. Maybe you (or someone other) can edit the three *.info.json files to point to PHP>=5.3.8 and try if it runs or throws any error?

If not it will take a while for me to get ready testing this. But it is noted on my ToDo now.

Share this post


Link to post
Share on other sites

I could quickly set a shared host account via its config panel to run under PHP 5.3.28 cgi.

The CroppableImage Editor worked, - but I could not test all functions in depth. If you want use it in a none productional site with PHP < 5.4.0, simply change the values in the 3 *.info.json files

// from this
	"requires": "ProcessWire>=2.5.11, PHP>=5.4.0, FieldtypeCroppableImage>=82",

// to this
	"requires": "ProcessWire>=2.5.11, PHP>=5.3.8, FieldtypeCroppableImage>=82",
  • modules/CroppableImage/FieldtypeCroppableImage/FieldtypeCroppableImage.info.json
  • modules/CroppableImage/InputfieldCroppableImage/InputfieldCroppableImage.info.json
  • modules/CroppableImage/ProcessCroppableImage/ProcessCroppableImage.info.json

Share this post


Link to post
Share on other sites

Hello,

first of all thank you for this great module!

I still have a feature request though: It would be even greater if it would be possible to have the option to specify an aspect ratio instead of a pixel width and height. That would make this field perfect for my use case :)

Any chance to get this feature?

Cheers

Share this post


Link to post
Share on other sites

Looks very good guys! Its very good to see that finally the cropping module gets an upgrade!

I would love to be able to add some more (very simple) text fields to the images, in the likes of http://modules.processwire.com/modules/fieldtype-image-extra/ This is something that I think the regular image fieldtype should also include, but maybe you take a lead here :)

(My reason is that right now I'm working on a very media-rich site, with artworks needing titles, descriptions, and 3 distinct handmade crops. Separate pages aren't an option because the drag&drop is so much better. I currently tackled this by splitting the description string, but that seems counter intuitive.)

Share this post


Link to post
Share on other sites

@Eelke Feenstra

Especially for rich media sites I would suggest going for flexibility. So using pages would be the better plan. Drag and drop can still be managed with a pagetable.

Share this post


Link to post
Share on other sites

Hey,

actually there is no time, even not for thinking in depth about this request. But maybe this suites your needs better: https://processwire.com/talk/topic/8079-imagefocusarea/

Reading the description it does look like this one does not have any ratio option either though.

Nevertheless thank u very much for the tipp!  I might install it and check it out anyways.

Share this post


Link to post
Share on other sites

@Michael, dealing with aspect ratio is in most cases more the task of CSS. Could you explain more in depth what you are after, then maybe we can help you with other possibilities. 

Share this post


Link to post
Share on other sites

Not sure it was mentioned somewhere, but I can't find a "cancel" button when on the Editor. I know you can just close the tab/window, but hey I had to think about.

  • Like 4

Share this post


Link to post
Share on other sites

I had this thought with the Thumbnails module, too. I don't even know if clients would notice, that there's a new tab opened.

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 d'Hinnisdaël
      Format Datetime fields as Carbon instances.
      You can find the latest release and the complete readme on Github.
      Installation
      composer require daun/datetime-carbon-format Usage
      All Datetime fields will now be formatted as Carbon instances instead of strings. Some examples:
      // $page->date is a Datetime field // Output format: j/n/Y echo $page->date; // 20/10/2020 echo $page->date->add('7 days'); // 27/10/2020 echo $page->date->format('l, F j'); // Monday, October 20 echo $page->date->year; // 2020 echo $page->date->diffForHumans(); // 28 minutes ago Frontend only
      The ProcessWire admin seems to expect datetime fields to be strings. This module will only return Carbon instances on frontend page views.
      Date output format
      When casting a Carbon instance to a string (usually when outputting the field in a template), the field's date output format will be respected.
      Links
      GitHub • Readme • Carbon docs
       
       
      PS. I remember reading about a Carbon module in a recent newsletter, but couldn't find it anywhere. Was that you, @bernhard?
    • By MoritzLost
      TrelloWire
      This is a module that allows you to automatically create Trello cards for ProcessWire pages and update them when the pages are updated. This allows you to setup connected workflows. Card properties and change handling behaviour can be customized through the extensive module configuration. Every action the module performs is hookable, so you can modify when and how cards are created as much as you need to. The module also contains an API-component that makes it easy to make requests to the Trello API and build your own connected ProcessWire-Trello workflows.
      Warning: This module requires ProcessWire 3.0.167 which is above the current stable master release at the moment.
      Features
      All the things the module can do for you without any custom code: Create a new card on Trello whenever a page is added or published (you can select applicable templates). Configure the target board, target list, name and description for new cards. Add default labels and checklists to the card. Update the card whenever the page is updated (optional). When the status of the card changes (published / unpublished, hidden / unhidden, trashed / restored or deleted), move the card to a different list or archive or delete it (configurable). You can extend this through hooks in many ways: Modifiy when and how cards are created. Modify the card properties (Target board & list, title, description, et c.) before they are sent to Trello. Create your own workflows by utilizing an API helper class with many convenient utility methods to access the Trello API directly. Feedback & Future Plans
      Let me know what you think! In particular:
      If you find any bugs report them here or on Github, I'll try to fix them. This module was born out of a use-case for a client project where we manage new form submissions through Trello. I'm not sure how many use-cases there are for this module. If you do use it, tell me about it! The Trello API is pretty extensive, I'll try to add some more helper methods to the TrelloWireApi class (let me know if you need anything in particular). I'll think about how the module can support different workflows that include Twig – talk to me if you have a use-case! Next steps could be a dashboard to manage pages that are connected to a Trello card, or a new section in the settings tab to manage the Trello connection. But it depends on whether there is any interest in this 🙂 Links
      Repository on Github Complete module documentation (getting started, configuration & API documentation) TrelloWire in the modules directory Module configuration

    • By David Karich
      ProcessWire InputfieldRepeaterMatrixDuplicate
      Thanks to the great ProModule "RepeaterMatrix" I have the possibility to create complex repeater items. With it I have created a quite powerful page builder. Many different content modules, with many more possible design options. The RepeaterMatrix module supports the cloning of items, but only within the same page. Now I often have the case that very design-intensive pages and items are created. If you want to use a content module on a different page (e.g. in the same design), you have to rebuild each item manually every time.
      This module extends the commercial ProModule "RepeaterMatrix" by the function to duplicate repeater items from one page to another page. The condition is that the target field is the same matrix field from which the item is duplicated. This module is currently understood as proof of concept. There are a few limitations that need to be considered. The intention of the module is that this functionality is integrated into the core of RepeaterMatrix and does not require an extra module.
      Check out the screencast
      What the module can do
      Duplicate multible repeater items from one page to another No matter how complex the item is Full support for file and image fields Multilingual support Support of Min and Max settings Live synchronization of clipboard between multiple browser tabs. Copy an item and simply switch the browser tab to the target page and you will immediately see the past button Support of multiple RepeaterMatrix fields on one page Configurable which roles and fields are excluded Configurable dialogs for copy and paste Duplicated items are automatically pasted to the end of the target field and set to hidden status so that changes are not directly published Automatic clipboard update when other items are picked Automatically removes old clipboard data if it is not pasted within 6 hours Delete clipboard itself by clicking the selected item again Benefit: unbelievably fast workflow and content replication What the module can't do
      Before an item can be duplicated in its current version, the source page must be saved. This means that if you make changes to an item and copy this, the old saved state will be duplicated Dynamic loading is currently not possible. Means no AJAX. When pasting, the target page is saved completely No support for nested repeater items. Currently only first level items can be duplicated. Means a repeater field in a repeater field cannot be duplicated. Workaround: simply duplicate the parent item Dynamic reloading and adding of repeater items cannot be registered. Several interfaces and events from the core are missing. The initialization occurs only once after the page load event Attention, please note!
      Nested repeaters cannot be supported technically. Therefore a check is made to prevent this. However, a nested repeater can only be detected if the field name ends for example with "_repeater1234". For example, if your MatrixRepeater field is named like this: "content_repeater" or "content_repeater123", this field is identified as nested and the module does not load. In version 2.0.1 the identification has been changed so that a field ending with the name repeater is only detected as nested if at least a two-digit number sequence follows. But to avoid this problem completely, make sure that your repeater matrix field does NOT end with the name "repeater".
      Changelog
       
      2.0.1
      Bug fix: Thanks to @ngrmm I could discover a bug which causes that the module cannot be loaded if the MatrixRepeater field ends with the name "repeater". The code was adjusted and information about the problem was provided 2.0.0
      Feature: Copy multiple items at once! The fundament for copying multiple items was created by @Autofahrn - THX! Feature: Optionally you can disable the copy and/or paste dialog Bug fix: A fix suggestion when additional and normal repeater fields are present was contributed by @joshua - THX! 1.0.4
      Bug fix: Various bug fixes and improvements in live synchronization Bug fix: Items are no longer inserted when the normal save button is clicked. Only when the past button is explicitly clicked Feature: Support of multiple repeater fields in one page Feature: Support of repeater Min/Max settings Feature: Configurable roles and fields Enhancement: Improved clipboard management Enhancement: Documentation improvement Enhancement: Corrected few typos #1 1.0.3
      Feature: Live synchronization Enhancement: Load the module only in the backend Enhancement: Documentation improvement 1.0.2
      Bug fix: Various bug fixes and improvements in JS functions Enhancement: Documentation improvement Enhancement: Corrected few typos 1.0.1
      Bug fix: Various bug fixes and improvements in the duplication process 1.0.0
      Initial release Support this module
      If this module is useful for you, I am very thankful for your small donation: Donate 5,- Euro (via PayPal – or an amount of your choice. Thank you!)
      Download this module (Version 2.0.1)
      > Github: https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate
      > PW module directory: https://modules.processwire.com/modules/inputfield-repeater-matrix-duplicate/
      > Old stable version (1.0.4): https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate/releases/tag/1.0.4
    • By picarica
      so i am trying to put CustomHooksForVariations.module, a custom module, i am placing it into site/modules direcotry yet my modules page in admin panel gives me errors
      so this is the screen show when i refresh modules, i dont know why the shole hook is written on top of the page :||

      and this next image is when i try to install it, i saw that it is not defiuned modules.php but it shouldnt need to be ?, any ways i dont want to edit site's core just to make one moulde work there has to be a way

    • By Robin S
      A new module that hasn't had a lot of testing yet. Please do your own testing before deploying on any production website.
      Custom Paths
      Allows any page to have a custom path/URL.
      Note: Custom Paths is incompatible with the core LanguageSupportPageNames module. I have no experience working with LanguageSupportPageNames or multi-language sites in general so I'm not in a position to work out if a fix is possible. If anyone with multi-language experience can contribute a fix it would be much appreciated!
      Screenshot

      Usage
      The module creates a field named custom_path on install. Add the custom_path field to the template of any page you want to set a custom path for. Whatever path is entered into this field determines the path and URL of the page ($page->path and $page->url). Page numbers and URL segments are supported if these are enabled for the template, and previous custom paths are managed by PagePathHistory if that module is installed.
      The custom_path field appears on the Settings tab in Page Edit by default but there is an option in the module configuration to disable this if you want to position the field among the other template fields.
      If the custom_path field is populated for a page it should be a path that is relative to the site root and that starts with a forward slash. The module prevents the same custom path being set for more than one page.
      The custom_path value takes precedence over any ProcessWire path. You can even override the Home page by setting a custom path of "/" for a page.
      It is highly recommended to set access controls on the custom_path field so that only privileged roles can edit it: superuser-only is recommended.
      It is up to the user to set and maintain suitable custom paths for any pages where the module is in use. Make sure your custom paths are compatible with ProcessWire's $config and .htaccess settings, and if you are basing the custom path on the names of parent pages you will probably want to have a strategy for updating custom paths if parent pages are renamed or moved.
      Example hooks to Pages::saveReady
      You might want to use a Pages::saveReady hook to automatically set the custom path for some pages. Below are a couple of examples.
      1. In this example the start of the custom path is fixed but the end of the path will update dynamically according to the name of the page:
      $pages->addHookAfter('saveReady', function(HookEvent $event) { $page = $event->arguments(0); if($page->template == 'my_template') { $page->custom_path = "/some-custom/path-segments/$page->name/"; } }); 2. The Custom Paths module adds a new Page::realPath method/property that can be used to get the "real" ProcessWire path to a page that might have a custom path set. In this example the custom path for news items is derived from the real ProcessWire path but a parent named "news-items" is removed:
      $pages->addHookAfter('saveReady', function(HookEvent $event) { $page = $event->arguments(0); if($page->template == 'news_item') { $page->custom_path = str_replace('/news-items/', '/', $page->realPath); } }); Caveats
      The custom paths will be used automatically for links created in CKEditor fields, but if you have the "link abstraction" option enabled for CKEditor fields (Details > Markup/HTML (Content Type) > HTML Options) then you will see notices from MarkupQA warning you that it is unable to resolve the links.
      Installation
      Install the Custom Paths module.
      Uninstallation
      The custom_path field is not automatically deleted when the module is uninstalled. You can delete it manually if the field is no longer needed.
       
      https://github.com/Toutouwai/CustomPaths
      https://modules.processwire.com/modules/custom-paths/
×
×
  • Create New...