Jump to content
horst

Croppable Image 3

Recommended Posts

Thanks a lot for your reply.  This is the result:

1033 
 news->name 
title 
headline 
summary 
kategorie 
body 
images 
  count: 2
Pageimage

The error was probably because I had never before created a new field with the fieldtyp CroppableImage3. Because I already had some images fields, I have only changed the input field type of the existing fields and not created a new one. After I had created a test field with the fieldtyp CroppableImage3, the other fields now work as desired.

printscreen.PNG

  • Like 1

Share this post


Link to post
Share on other sites

THIS MODULE IS AWESOME! ;) just to say it....

  • Like 3

Share this post


Link to post
Share on other sites
On 19/10/2016 at 2:26 PM, horst said:

If you want to give the user the possibility to choose from different formats for one single place, you need a special setup with e.g. pagetable or the ProFields Repeater Matrix wrapped around the image field.

Hi Horst,

I've wrapped a repeater around my image and bullet selection (The user can thus choose which cropping to use). It works when I upload an image for the first time, it creates 4 standard croppings (panorama, portrait, etc.). However, if I make a custom cropping it doesn't save it. I'd actually want the custom cropping to overwrite other files, but that doesn't work either. 

Is there a known issue between croppable image 3 and repeaters? Should i use ProFields Repeater Matrix (haven't tried it so far). Pagetable is also a possibility, but not as intuitive and fast as a repeater.

Thanks for your help!

David

Share this post


Link to post
Share on other sites

I'm not aware of any issues with repeaters or repeater-matrix. (Repeater-Matrix would do no change, I believe, as it somehow extends repeater)

Custom cropping is made for which user / role. Does he have the right permission added to his role?

Share this post


Link to post
Share on other sites
23 hours ago, horst said:

I'm not aware of any issues with repeaters or repeater-matrix. (Repeater-Matrix would do no change, I believe, as it somehow extends repeater)

Custom cropping is made for which user / role. Does he have the right permission added to his role?

I tested even without the repeater and I get similar errors. So I think we can leave the repeaters out of it. Permissions are OK.

I tried to recreate the issue (can't tell yet exactly when it works and when not). 

I created 4 cropping-presets. These create the 4 croppings automatically. So far ok. When the user (whichever) creates a custom cropping, the new cropping doesn't overwrite the old one. Or I should rather say, sometimes it does, but most of the times it doesn't.

Workaround is to delete the generated croppings in the "variations" window prior to creating a custom one. This works, but it's not a nice solution for the end user.

Am I the first one reporting this bug?

Thanks.

Share this post


Link to post
Share on other sites
2 hours ago, lenoir said:

Am I the first one reporting this bug?

I wouldn't consider it a bug of the croppable image module, as this seems to be only at your server (setup).

Please provide the exact reproducable steps you have done, incl. installing and configuring the module. (You may try this by yourself in a test account, and if this behaves as you described, tell us the steps here, so that we will be able to reproduce it.)

What does "Permisions ar OK" mean, exactly?

Share this post


Link to post
Share on other sites
On 9/3/2016 at 7:59 PM, horst said:

Or directly use the markup srcset module from @tpr and only pass the master to it!

Just tried this and it works:

<img <?php echo $page->portfolio_images->first()->getCrop('portfolio-item')->srcset('portfolio-item'); ?> class="lazyload" alt="">

This was the first time I added CroppableImage to a project and it seems great. Some UI facelift here and there could be beneficial though :)

  • Like 3

Share this post


Link to post
Share on other sites
4 hours ago, tpr said:

Some UI facelift here and there could be beneficial though :)

@tpr: Hah, - you are more than welcome to contribute in this regard, Mr. AOS! ^-^:lol: 

  • Like 3

Share this post


Link to post
Share on other sites

Could it be that for square image crops, only width to add, and use that for the height too?

portfolio-item-small,360

 

Share this post


Link to post
Share on other sites
10 minutes ago, tpr said:

Could it be that for square image crops, only width to add, and use that for the height too?


portfolio-item-small,360

 

What is the intention of the question? Lesser to write? Or something other?

Share this post


Link to post
Share on other sites

Yes, less to write.

  • Like 1

Share this post


Link to post
Share on other sites

I add it to the ToDo, but may take some time to get done.

  • Like 1

Share this post


Link to post
Share on other sites

No, it should work with whatever PW accepts via installed ImageRenderingEngine-Modules.

Your Image is black. How work this image out with api rendered image variations? What is the source image type(s)? Is it with all images, regardless of type / format?

Share this post


Link to post
Share on other sites

HI,

Has anyone encountered quality issues with the croppable module? 

I know I'm very picky when it comes to image quality, but I'm getting pretty bad results and I'm wondering what i can do about it. I've tried no sharpening, sharpening soft, quality 90 and 80, but the images still look "pixelated", specially in the diagonals. 

See screenshot attached. Original left, cropping on the right.

image_quality.jpg

Share this post


Link to post
Share on other sites

CroppableImages uses the core images rendering engines. So there is no special "Croppable image rendering".

Your original image left is very blurry, and the one on the right site is much to much sharpened. Please try a variation with sharpening soft or none.

  • Like 1

Share this post


Link to post
Share on other sites
2 minutes ago, horst said:

Your original image left is very blurry, and the one on the right site is much to much sharpened. Please try a variation with sharpening soft or none.

Yes, I'm aware of that. That's my issue. That's what I get with sharpening set on SOFT. 

Are the core rendering engines just not that good? 

Share this post


Link to post
Share on other sites

Hi, does anyone know if this works with @kongondo's Media Manager? 

Edit: having just bought the media manager, pretty sure there's no clear way to make them play nice together.

Edited by cjx2240

Share this post


Link to post
Share on other sites
22 hours ago, lenoir said:

Are the core rendering engines just not that good? 

Based on my experiences with

  • several thousand images of mine,
  • several thousand images of my customers
  • and many image variations from many sites around the world (from the showcase directory),

I can say: The core rendering engines seem to do a pretty good job !  ^-^:lol::ph34r:

But that are just my experiences. ;)

  • Like 2

Share this post


Link to post
Share on other sites

Just upgraded to PW 3.043 dev and getCrop() doesn't seem to work (returns NULL). Downgraded to 3.042 and no issues.

I've downloaded a fresh copy of both PW versions so 3.043 should contain Ryan's fix too.

Anyone having the same issue?

Share this post


Link to post
Share on other sites

I have upgraded a site yesterday too. Here everything is working as expected. With both, existing and new created images.

(PW 3.0.39 to 3.0.43)

Share this post


Link to post
Share on other sites

I was hoping the opposite :) Not sure what's going on here.

Share this post


Link to post
Share on other sites

I'm not sure if this is the intended functionality: 

When I click to edit a crop under 'predefined Crops', the overlaid 'marquee' always reverts to the far top left of the image, even when I move it around and click 'Crop and go'.

I know the crop has saved correctly because I can hover the button and see a thumbnail appear.

Share this post


Link to post
Share on other sites

This is not intended, but its previous state is only saved for jpegs, not for png or gif formats.

  • Like 1

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 teppo
      Needed a really simple solution to embed audio files within page content and couldn't find a module for that, so here we go. Textformatter Audio Embed works a bit like Textformatter Video Embed, converting this:
      <p>https://www.domain.tld/path/to/file.mp3</p> Into this:
      <audio controls class="TextformatterAudioEmbed"> <source src="https://www.domain.tld/path/to/file.mp3" type="audio/mpeg"> </audio> The audio element has pretty good browser support, so quite often this should be enough to get things rolling 🙂
      GitHub repository: https://github.com/teppokoivula/TextformatterAudioEmbed Modules directory: https://modules.processwire.com/modules/textformatter-audio-embed/
    • By Richard Jedlička
      Tense    
      Tense (Test ENvironment Setup & Execution) is a command-line tool to easily run tests agains multiple versions of ProcessWire CMF.
      Are you building a module, or a template and you need to make sure it works in all supported ProcessWire versions? Then Tense is exactly what you need. Write the tests in any testing framework, tell Tense which ProcessWire versions you are interested in and it will do the rest for you.

      See example or see usage in a real project.
      How to use?
      1. Install it: 
      composer global require uiii/tense 2. Create tense.yml config:
      tense init 3. Run it:
      tense run  
      For detailed instructions see Github page: https://github.com/uiii/tense
       
      This is made possible thanks to the great wireshell tool by @justb3a, @marcus and others.
       
      What do you think about it? Do you find it useful? Do you have some idea? Did you find some bug? Tell me you opinion. Write it here or in the issue tracker.
    • By Chris Bennett
      Hi all, I am going round and round in circles and would greatly appreciate if anyone can point me in the right direction.
      I am sure I am doing something dumb, or missing something I should know, but don't. Story of my life 😉

      Playing round with a module and my basic problem is I want to upload an image and also use InputfieldMarkup and other Inputfields.
      Going back and forth between trying an api generated page defining Fieldgroup, Template, Fields, Page and the InputfieldWrapper method.

      InputfieldWrapper method works great for all the markup stuff, but I just can't wrap my head around what I need to do to save the image to the database.
      Can generate a Field for it (thanks to the api investigations) but not sure what I need to do to link the Inputfield to that. Tried a lot of stuff from various threads, of varying dates without luck.
      Undoubtedly not helped by me not knowing enough.

      Defining Fieldgroup etc through the api seems nice and clean and works great for the images but I can't wrap my head around how/if I can add/append/hook the InputfieldWrapper/InputfieldMarkup stuff I'd like to include on that template as well. Not even sure if it should be where it is on ___install with the Fieldtype stuff or later on . Not getting Tracy errors, just nothing seems to happen.
      If anyone has any ideas or can point me in the right direction, that would be great because at the moment I am stumbling round in the dark.
       
      public function ___install() { parent::___install(); $page = $this->pages->get('name='.self::PAGE_NAME); if (!$page->id) { // Create fieldgroup, template, fields and page // Create new fieldgroup $fmFieldgroup = new Fieldgroup(); $fmFieldgroup->name = MODULE_NAME.'-fieldgroup'; $fmFieldgroup->add($this->fields->get('title')); // needed title field $fmFieldgroup->save(); // Create new template using the fieldgroup $fmTemplate = new Template(); $fmTemplate->name = MODULE_NAME; $fmTemplate->fieldgroup = $fmFieldgroup; $fmTemplate->noSettings = 1; $fmTemplate->noChildren = 1; $fmTemplate->allowNewPages = 0; $fmTemplate->tabContent = MODULE_NAME; $fmTemplate->noChangeTemplate = 1; $fmTemplate->setIcon(ICON); $fmTemplate->save(); // Favicon source $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeImage"); $fmField->name = 'fmFavicon'; $fmField->label = 'Favicon'; $fmField->focusMode = 'off'; $fmField->gridMode = 'grid'; $fmField->extensions = 'svg png'; $fmField->columnWidth = 50; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon(ICON); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($fmField); // Favicon Silhouette source $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeImage"); $fmField->name = 'fmFaviconSilhouette'; $fmField->label = 'SVG Silhouette'; $fmField->notes = 'When creating a silhouette/mask svg version for Safari Pinned Tabs and Windows Tiles, we recommend setting your viewbox for 0 0 16 16, as this is what Apple requires. In many cases, the easiest way to do this in something like illustrator is a sacrificial rectangle with no fill, and no stroke at 16 x 16. This forces the desired viewbox and can then be discarded easily using something as simple as notepad. Easy is good, especially when you get the result you want without a lot of hassle.'; $fmField->focusMode = 'off'; $fmField->extensions = 'svg'; $fmField->columnWidth = 50; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon(ICON); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($fmField); // Create: Open Settings Tab $tabOpener = new Field(); $tabOpener->type = new FieldtypeFieldsetTabOpen(); $tabOpener->name = 'fmTab1'; $tabOpener->label = "Favicon Settings"; $tabOpener->collapsed = Inputfield::collapsedNever; $tabOpener->addTag(MODULE_NAME); $tabOpener->save(); // Create: Close Settings Tab $tabCloser = new Field(); $tabCloser->type = new FieldtypeFieldsetClose; $tabCloser->name = 'fmTab1' . FieldtypeFieldsetTabOpen::fieldsetCloseIdentifier; $tabCloser->label = "Close open tab"; $tabCloser->addTag(MODULE_NAME); $tabCloser->save(); // Create: Opens wrapper for Favicon Folder Name $filesOpener = new Field(); $filesOpener->type = new FieldtypeFieldsetOpen(); $filesOpener->name = 'fmOpenFolderName'; $filesOpener->label = 'Wrap Folder Name'; $filesOpener->class = 'inline'; $filesOpener->collapsed = Inputfield::collapsedNever; $filesOpener->addTag(MODULE_NAME); $filesOpener->save(); // Create: Close wrapper for Favicon Folder Name $filesCloser = new Field(); $filesCloser->type = new FieldtypeFieldsetClose(); $filesCloser->name = 'fmOpenFolderName' . FieldtypeFieldsetOpen::fieldsetCloseIdentifier; $filesCloser->label = "Close open fieldset"; $filesCloser->addTag(MODULE_NAME); $filesCloser->save(); // Create Favicon Folder Name $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeText"); $fmField->name = 'folderName'; $fmField->label = 'Favicon Folder:'; $fmField->description = $this->config->urls->files; $fmField->placeholder = 'Destination Folder for your generated favicons, webmanifest and browserconfig'; $fmField->columnWidth = 100; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon('folder'); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($tabOpener); $fmFieldgroup->add($filesOpener); $fmFieldgroup->add($fmField); $fmFieldgroup->add($filesCloser); $fmFieldgroup->add($tabCloser); $fmFieldgroup->save(); /////////////////////////////////////////////////////////////// // Experimental Markup Tests $wrapperFaviconMagic = new InputfieldWrapper(); $wrapperFaviconMagic->attr('id','faviconMagicWrapper'); $wrapperFaviconMagic->attr('title',$this->_('Favicon Magic')); // field show info what $field = $this->modules->get('InputfieldMarkup'); $field->name = 'use'; $field->label = __('How do I use it?'); $field->collapsed = Inputfield::collapsedNever; $field->icon('info'); $field->attr('value', 'Does this even begin to vaguely work?'); $field->columnWidth = 50; $wrapperFaviconMagic->add($field); $fmTemplate->fields->add($wrapperFaviconMagic); $fmTemplate->fields->save(); ///////////////////////////////////////////////////////////// // Create page $page = $this->wire( new Page() ); $page->template = MODULE_NAME; $page->parent = $this->wire('pages')->get('/'); $page->addStatus(Page::statusHidden); $page->title = 'Favicons'; $page->name = self::PAGE_NAME; $page->process = $this; $page->save(); } }  
    • By Sebi
      Since it's featured in ProcessWire Weekly #310, now is the time to make it official:
      Here is Twack!
      I really like the following introduction from ProcessWire Weekly, so I hope it is ok if I use it here, too. Look at the project's README for more details!
      Twack is a new — or rather newish — third party module for ProcessWire that provides support for reusable components in an Angular-inspired way. Twack is implemented as an installable module, and a collection of helper and base classes. Key concepts introduced by this module are:
      Components, which have separate views and controllers. Views are simple PHP files that handle the output for the component, whereas controllers extend the TwackComponent base class and provide additional data handling capabilities. Services, which are singletons that provide a shared service where components can request data. The README for Twack uses a NewsService, which returns data related to news items, as an example of a service. Twack components are designed for reusability and encapsulating a set of features for easy maintainability, can handle hierarchical or recursive use (child components), and are simple to integrate with an existing site — even when said site wasn't originally developed with Twack.
      A very basic Twack component view could look something like this:
      <?php namespace ProcessWire; ?> <h1>Hello World!</h1> And here's how you could render it via the API:
      <?php namespace Processwire; $twack = $modules->get('Twack'); $hello = $twack->getNewComponent('HelloWorld'); ?> <html> <head> <title>Hello World</title> </head> <body> <?= $hello->render() ?> </body> </html> Now, just to add a bit more context, here's a simple component controller:
      <?php namespace ProcessWire; class HelloWorld extends TwackComponent { public function __construct($args) { parent::__construct($args); $this->title = 'Hello World!'; if(isset($args['title'])) { $this->title = $args['title']; } } } As you can see, there's not a whole lot new stuff to learn here if you'd like to give Twack a try in one of your projects. The Twack README provides a really informative and easy to follow introduction to all the key concepts (as well as some additional examples) so be sure to check that out before getting started. 
      Twack is in development for several years and I use it for every new project I build. Also integrated is an easy to handle workflow to make outputs as JSON, so it can be used to build responses for a REST-api as well. I will work that out in one section in the readme as well. 
      If you want to see the module in an actual project, I have published the code of www.musical-fabrik.de in a repository. It runs completely with Twack and has an app-endpoint with ajax-output as well.
      I really look forward to hear, what you think of Twack🥳!
      Features Installation Usage Quickstart: Creating a component Naming conventions & component variants Component Parameters directory page parameters viewname Asset handling Services Named components Global components Ajax-Output Configuration Versioning License Changelog
    • By Robin S
      Page Reference Default Value
      Most ProcessWire core inputfield types that can be used with a Page Reference field support a "Default value" setting. This module extends support for default values to the following core inputfield types:
      Page List Select Page List Select Multiple Page Autocomplete (single and multiple) Seeing as these inputfield types only support the selection of pages a Page List Select / Page List Select Multiple is used for defining the default value instead of the Text / Textarea field used by the core for other inputfield types. This makes defining a default value a bit more user-friendly.
      Note that as per the core "Default value" setting, the Page Reference field must be set to "required" in order for the default value to be used.
      Screenshot

       
      https://github.com/Toutouwai/PageReferenceDefaultValue
      https://modules.processwire.com/modules/page-reference-default-value/
×
×
  • Create New...