Jump to content
horst

Croppable Image 3

Recommended Posts

the current version is 1.1.15

please update and try again. We have fixed this already. :)

 

  • Thanks 1

Share this post


Link to post
Share on other sites

Sorry, it is the Process module that in version 1.1.10, while the Wrapper module 1.1.15.

The version I installed is up to date already.

Share this post


Link to post
Share on other sites

I used simple var_dump to debug a bit as I don't know why tracy debug is not working(Please tell me if you have any idea :)). I found that the issue is positioned at ProcessCroppableImage3.module line 234 and 235. isset($this->input->post->quality) and isset($this->input->post->sharpening) are returning false. Thus, the value is returned as options['quality'] instead of user input intval($this->input->post->quality).

// when I choose 60 quality
var_dump($this->input->post->quality, isset($this->input->post->quality), is_numeric($this->input->post->quality), 0<intval($this->input->post->quality), 101>intval($this->input->post->quality));
  
// return : string(2) "60" bool(false) bool(true) bool(true) bool(true)

 

Share this post


Link to post
Share on other sites

Updated to latest version PW and CroppableImage3 but old code from templates doesn't work anymore are there code examples to call CroppableImage3 in templates. Thanks!

if($page->mosaik_title_1) { echo "
<div class='three columns'>
<a href='{$page->mosaik_url_1}/'>
<span class='m1'>{$page->mosaik_title_1}</span>
<img src='{$page->mosaic_photo_1->eq(0)->getThumb('thumbnail')}' alt='{$page->mosaic_photo_1->description}' /></a></div>";}

and

foreach($page->children as $child)
            echo "
                <div class='cat1 cat5'>
                <div class='port-item-container'>
                    <div class='port-box'>
                            <a rel='bookmark' title='{$child->title}' href='{$child->url}'>
                            <img src='{$child->overviewimg->eq(0)->getThumb('thumbnail')}' alt='$child->title'>
                            </a>
                    </div>
                    <div class='port-item-title'>
                        <h6>{$child->title}</h6>
                        <span>{$child->overviewtxt}...<a href='{$child->url}'> Lees verder »</a></span>
                    </div>
                </div>
                </div>
                ";

Share this post


Link to post
Share on other sites

changing...

<img src='{$child->overviewimg->eq(0)->getThumb('thumbnail')}' alt='$child->title'>

to...

<img src='{$child->overviewimg->eq(0)->getCrop('thumbnail')}' alt='$child->title'>

did not work...

...and give error:

Exception: There is no crop setting for the template 'home' called 'thumbnail' (in /domains/gemsbok.nl/DEFAULT/fresh/site/modules/CroppableImage3/FieldtypeCroppableImage3/FieldtypeCroppableImage3.module line 209)

And have set the crop setting to square,160,160

Share this post


Link to post
Share on other sites

@Oca2 - please try to avoid double posting and if you do, please follow up on both so people don't try to help you when you've already been helped.

Thanks!

Cheers,
Adrian

Share this post


Link to post
Share on other sites
37 minutes ago, adrian said:

@Oca2 - please try to avoid double posting and if you do, please follow up on both so people don't try to help you when you've already been helped.

Thanks!

Cheers,
Adrian

Ok will follow up this time and next time avoid double post :)

 

  • Like 1

Share this post


Link to post
Share on other sites

No more errors :)

But...

I don't want to go through the update process renaming all images files... to complicated so I will manually update the images...

...But if I select new images from admin they are still not visible on the front-end???

Share this post


Link to post
Share on other sites

Check file in attachment, that should rename all your existing files to the new [please do read instructions carefully, make sure you have a back-up]
BTW, I didn't write it, but I have used it a few times, with success.

also, new syntax is + ->url
So, I guess in your case:

<img src='{$child->overviewimg->eq(0)->getCrop('thumbnail')->url}' alt='$child->title'>

Hope this helps....

cropupdate.php

 

Quote

Exception: There is no crop setting for the template 'home' called 'thumbnail' (in /domains/gemsbok.nl/DEFAULT/fresh/site/modules/CroppableImage3/FieldtypeCroppableImage3/FieldtypeCroppableImage3.module line 209)

This is because, when changing from 'CropImage' to 'CroppableImage3', you actually have to re-enter the Crop Settings, in your case 'thumbnail'

  • Like 1

Share this post


Link to post
Share on other sites
21 hours ago, Oca2 said:

No more errors :)

But...

I don't want to go through the update process renaming all images files... to complicated so I will manually update the images...

...But if I select new images from admin they are still not visible on the front-end???

Look here, there is complete upgrade procedure with help:

 

Share this post


Link to post
Share on other sites
8 minutes ago, horst said:
22 hours ago, Oca2 said:

 

Look here, there is complete upgrade procedure with help:

Thanks for chiming in @horst - I have already linked to that: 

This is the problem with multiple threads for the same issue, :) but I think @Oca2 has the message on that now :)

  • Like 1

Share this post


Link to post
Share on other sites
On 1/26/2018 at 1:36 AM, adrian said:

Thanks for chiming in @horst - I have already linked to that: 

This is the problem with multiple threads for the same issue, :) but I think @Oca2 has the message on that now :)

I think it is to complicated... would be nice if this was fixed by a default update... not by hand going through source codes 2 much time and possibility's 2 break stuff.

Share this post


Link to post
Share on other sites
Just now, Oca2 said:

I think it is to complicated... would be nice if this was fixed by a default update... not by hand going through source codes 2 much time and possibility's 2 break stuff.

Remember that these modules were built by different developers - CroppbaleImage3 is not an upgrade to the Thumbnails module. The Thumbnails module was abandoned and @horst was kind enough to build this one and also put together a script to make the migration as easy as possible. 

The conversion from Thumbnails to CroppableImage is the only issue I have had with migrating any of my sites from PW 2 to 3 - I think that is pretty incredible for a major version upgrade.

I am not meaning to sound dismissive, I understand it's not a simple migration, but I don't think it should be expected to be automatic in this scenario - I hope you understand.

  • Like 3

Share this post


Link to post
Share on other sites
26 minutes ago, adrian said:

Remember that these modules were built by different developers - CroppbaleImage3 is not an upgrade to the Thumbnails module. The Thumbnails module was abandoned and @horst was kind enough to build this one and also put together a script to make the migration as easy as possible. 

The conversion from Thumbnails to CroppableImage is the only issue I have had with migrating any of my sites from PW 2 to 3 - I think that is pretty incredible for a major version upgrade.

I am not meaning to sound dismissive, I understand it's not a simple migration, but I don't think it should be expected to be automatic in this scenario - I hope you understand.

Yes I understand 101% now!

I thought it was a core plugin...

Can't wait to have the code up and running I'm on 50% updating... 50% works :)

This works :)

<img src='{$page->mosaic_photo_2->eq(0)->getCrop('thumbnail')->url}' alt='{$page->mosaic_photo_2->description}' /></a></div>";}

This not :(

<img src='{$child->overviewimg->eq(0)->getCrop('thumbnail')->url}' alt='$child->title'>

 

Edited by Oca2
  • Like 1

Share this post


Link to post
Share on other sites
Just now, Oca2 said:

One hundred and one % working now, Thanks ProcessWire Crew for the help & info!

Oca2

It was missing the setting "thumbnail,160,160"

Share this post


Link to post
Share on other sites

Any chance we can get the addition of a method to check if there has been a crop defined for the image (over the default)? And possibly some way in the admin to reset the crops?

By all means if I get a chance I will look at doing this myself and submitting a pull request.

 

Thansk @horst

Share this post


Link to post
Share on other sites

I'm not sure if it is worth the (for me ATM, not available) time to add new functionality to this module as we got the "focus point thingy" now in the core. When this get a zoom functionality too, it is much much easier to use for authors and devs too.

https://processwire.com/blog/posts/pw-3.0.89/

@adamspruijt

 

Share this post


Link to post
Share on other sites

Is it safe to migrate from Croppable Image 3 to the New Core Image Focus/Zoom on a production site? Has anyone done that? If yes what are the steps to do it properly to avoid messing things up?

Share this post


Link to post
Share on other sites

There are no such steps. The cropable image and the focus point are completly different things and can be used side by side. 

If you want to drop cai and use focus point, you have to switch the api code in your templates. Before you completely remove cai calls, you may change them to a call to remove variations. But others then that isn't necessary. 

Share this post


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

There are no such steps. The cropable image and the focus point are completly different things and can be used side by side. 

If you want to drop cai and use focus point, you have to switch the api code in your templates. Before you completely remove cai calls, you may change them to a call to remove variations. But others then that isn't necessary. 

I haven't used the Focus/Zoom yet but I thought that they actually do the same job as Croppable Image 3...

Share this post


Link to post
Share on other sites

@horst, sorry to bother you with this (and sorry if it's a dumb question in the first place), but what's the current state of this module like?

I'm in desperate need of "pixel perfect" pre-defined crops, and while the focus and zoom feature is really cool, it solves a different problem entirely. Reading some of the posts here I'm wondering if this module is still something I should go with, or do I just need to wait and hope that @ryan decides to add pre-defined crop areas to the core one day?

Thanks! 🙂

  • Like 1

Share this post


Link to post
Share on other sites

@teppo, This module is ready to use with the current stable and dev versions of PW (3.0.99+). I know that many users (and me too) actively uses it in many sites. It is also simple to use in conjunction with MarkupSourceSet.

So, I think I will not add new features to it, but I will maintain the compatibility of it with future PW versions!

Some time ago, it becomes compatible with new UIKit-AdminTheme. Here is a screen:

screen_cai3_01.thumb.jpg.789512e64e54f920915cdfd021079ab6.jpg

 

  • Like 4
  • Thanks 1

Share this post


Link to post
Share on other sites

Hi @horst, is it possible to have a hookable method that for creation of variation image? I would like to hook it to upload the newly created variation image to somewhere else.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.56
      Composer: rockett/jumplinks
      Jumplinks is an enhanced version of the original ProcessRedirects by Antti Peisa.
      The Process module manages your permanent and temporary redirects (we'll call these "jumplinks" from now on, unless in reference to redirects from another module), useful for when you're migrating over to ProcessWire from another system/platform. Each jumplink supports wildcards, shortening the time needed to create them.
      Unlike similar modules for other platforms, wildcards in Jumplinks are much easier to work with, as Regular Expressions are not fully exposed. Instead, parameters wrapped in curly braces are used - these are described in the documentation.
      Under Development: 2.0, to be powered by FastRoute
      As of version 1.5.0, Jumplinks requires at least ProcessWire 2.6.1 to run.
      View on GitLab
      Download via the Modules Directory
      Read the docs
      Features
      The most prominent features include:
      Basic jumplinks (from one fixed route to another) Parameter-based wildcards with "Smart" equivalents Mapping Collections (for converting ID-based routes to their named-equivalents without the need to create multiple jumplinks) Destination Selectors (for finding and redirecting to pages containing legacy location information) Timed Activation (activate and/or deactivate jumplinks at specific times) 404-Monitor (for creating jumplinks based on 404 hits) Additionally, the following features may come in handy:
      Stale jumplink management Legacy domain support for slow migrations An importer (from CSV or ProcessRedirects) Feedback & Feature Requests
      I’d love to know what you think of this module. Please provide some feedback on the module as a whole, or even regarding smaller things that make it whole. Also, please feel free to submit feature requests and their use-cases.
      Note: Features requested so far have been added to the to-do list, and will be added to 2.0, and not the current dev/master branches.
      Open Source

      Jumplinks is an open-source project, and is free to use. In fact, Jumplinks will always be open-source, and will always remain free to use. Forever. If you would like to support the development of Jumplinks, please consider making a small donation via PayPal.
      Enjoy! :)
    • By BitPoet
      As threatened in Ryan's announcement for 3.0.139, I built a little module for sliding toggles as a replacement for checkboxes. Styling of the input is CSS3 only (with all the usual caveats about older browsers), no JS necessary, and may still be a bit "rough around the edges", so to speak, since I didn't have much time for testing on different devices or brushing things up enough so I'd feel comfortable pushing it to the module directory. But here's the link to the GitHub repo for now:
      InputfieldSlideToggle
      Fieldtype and Inputfield that implements smartphone-style toggles as replacement for checkbox inputs. The visualization is CSS-only, no additional JS necessary.
      Status
      Still very alpha, use with caution!
      Features / Field Settings
      Size
      You can render the toggles in four different sizes: small, medium, large and extra large.
      Off Color
      Currently, "unchecked" toggles can be displayed either in grey (default) or red.
      On Color
      "Checked" toggles can be rendered in one of these colors: blue (default), black, green, grey, orange or red.
      Screenshots

      Some examples with checkbox label


      View all Size and Color Combinations
      Small toggles Medium toggles Big toggles Extra big toggles  









    • By Orkun
      Hi Guys
      I needed to add extended functionalities for the InputfieldDatetime Module (module is from processwire version 2.7.3) because of a Request of Customer.
      So I duplicated the module and placed it under /site/modules/.
      I have added 3 new Settings to the InputfieldDatetime Module.
      1. Day Restriction - Restrict different days based on weekdays selection (e.g. saturday, sunday) - WORKING

       
      2. Time Slots - Define Time slots based on custom Integer Value (max is 60 for 1 hour) - WORKING

       
      3. Time Range Rules per Weekday - Define a minTime and MaxTime per Weekday (e.g. Opening Hours of a Restaurant) - NOT WORKING PROPERLY

       
      The Problem
      Time Slots and Day Restriction working fine so far. But the Time Range Rules per Weekday doesn't work right.
      What should happen is, that when you click on a date, it should update the minTime and maxTime of the Time Select.
      But the change on the select only happens if you select a date 2 times or when you select a date 1 time and then close the datepicker and reopen it again.
      The time select doesn't get change when you select a date 1 time and don't close the picker.
      Here is the whole extended InputfieldDatetime Module.
      The Files that I have changed:
      InputfieldDatetime.module InputfieldDatetime.js jquery-ui-timepicker-addon.js (https://trentrichardson.com/examples/timepicker/) - updated it to the newest version, because minTime and maxTime Option was only available in the new version  
      Thats the Part of the JS that is not working correctly:
      if(datetimerules && datetimerules.length){ options.onSelect = function(date, inst) { var day = $(this).datetimepicker("getDate").getDay(); day = day.toString(); var mintime = $(this).attr('data-weekday'+day+'-mintime'); var maxtime = $(this).attr('data-weekday'+day+'-maxtime'); console.log("weekday: "+day); console.log("minTime: "+mintime); console.log("maxTime: "+maxtime); var optionsAll = $(this).datetimepicker( "option", "all" ); optionsAll.minTime = mintime; optionsAll.maxTime = maxtime; $(this).datetimepicker('destroy'); $(this).datetimepicker(optionsAll); $(this).datetimepicker('refresh'); //$.datepicker._selectDate($(this).attr("id"),date); //$.datepicker._base_getDateDatepicker(); // var inst = $.datepicker._getInst($(this)); // $.datepicker._updateDatepicker(inst); /*$(this).datetimepicker('destroy'); InputfieldDatetimeDatepicker($(this), mintime, maxtime); $(this).datetimepicker('refresh'); */ // $(this).datetimepicker('option', {minTime: mintime, maxTime: maxtime}); } } Can you have a look and find out what the Problem is?
      InputfieldDatetime.zip
       
      Kind Regards
      Orkun
    • By teppo
      This module tracks changes, additions, removals etc. of public (as in "not under admin") pages of your site. Like it's name says, it doesn't attempt to be a version control system or anything like that - just a log of what's happened.
      At the moment it's still a work in progress and will most likely be a victim of many ruthless this-won't-work-let's-try-that-instead cycles, but I believe I've nailed basic functionality well enough to post it here.. so, once again, I'll be happy to hear any comments you folks can provide
      https://modules.processwire.com/modules/process-changelog/
      https://github.com/teppokoivula/ProcessChangelog
      How does it work?
      Exactly like it's (sort of) predecessor, Process Changelog actually consists of two modules: Process Changelog and Process Changelog Hooks. Hooks module exists only to serve main module by hooking into various functions within Pages class, collecting data of performed operations, refining it and keeping up a log of events in it's own custom database table (process_changelog.) Visible part is managed by Process Changelog, which provides users a (relatively) pretty view of the contents of said log table.
      How do you use it?
      When installed this module adds new page called Changelog under Admin > Setup which provides you with a table view of collected data and basic filtering tools See attached screenshots to get a general idea about what that page should look like after a while.
      For detailed installation instructions etc. see README.md.
       


    • By Gadgetto
      Status update links (inside this thread) for SnipWire development will be always posted here:
      2019-08-08
      2019-06-15
      2019-06-02
      2019-05-25
      If you are interested, you can test the current state of development:
      https://github.com/gadgetto/SnipWire
      Please note that the software is not yet intended for use in a production system (alpha version).
      If you like, you can also submit feature requests and suggestions for improvement. I also accept pull requests.
      ---- INITIAL POST FROM 2019-05-25 ----
      I wanted to let you know that I am currently working on a new ProcessWire module that fully integrates the Snipcart Shopping Cart System into ProcessWire. (this is a customer project, so I had to postpone the development of my other module GroupMailer).
      The new module SnipWire offers full integration of the Snipcart Shopping Cart System into ProcessWire.
      Here are some highlights:
      simple setup with (optional) pre-installed templates, product fields, sample products (quasi a complete shop system to get started immediately) store dashboard with all data from the snipcart system (no change to the snipcart dashboard itself required) Integrated REST API for controlling and querying snipcart data webhooks to trigger events from Snipcart (new order, new customer, etc.) multi currency support self-defined/configurable tax rates etc. Development is already well advanced and I plan to release the module in the next 2-3 months.
      I'm not sure yet if this will be a "Pro" module or if it will be made available for free.
      I would be grateful for suggestions and hints!
      (please have a look at the screenshots to get an idea what I'm talking about)
       




×
×
  • Create New...