Jump to content

Croppable Image 3


horst

Recommended Posts

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)

 

Link to comment
Share on other sites

  • 1 month later...

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>
                ";
Link to comment
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

Link to comment
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
Link to comment
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???

Link to comment
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
Link to comment
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:

 

Link to comment
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
Link to comment
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.

Link to comment
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
Link to comment
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
Link to comment
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

Link to comment
Share on other sites

  • 3 weeks later...

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. 

Link to comment
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...

Link to comment
Share on other sites

  • 2 months later...

@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
Link to comment
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
Link to comment
Share on other sites

  • 3 months later...

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 Sebi
      AppApiFile adds the /file endpoint to the AppApi routes definition. Makes it possible to query files via the api. 
      This module relies on the base module AppApi, which must be installed before AppApiFile can do its work.
      Features
      You can access all files that are uploaded at any ProcessWire page. Call api/file/route/in/pagetree?file=test.jpg to access a page via its route in the page tree. Alternatively you can call api/file/4242?file=test.jpg (e.g.,) to access a page by its id. The module will make sure that the page is accessible by the active user.
      The GET-param "file" defines the basename of the file which you want to get.
      The following GET-params (optional) can be used to manipulate an image:
      width height maxwidth maxheight cropX cropY Use GET-Param format=base64 to receive the file in base64 format.
    • By MarkE
      This fieldtype and inputfield bundle was built for storing measurement values within a field, rendering them in a variety of formats and converting them to other units or otherwise modifying them via the API.
      The API consists of a number of predefined functions, some of which include...
      render() for rendering the measurement object, valueAs() for converting the value to another unit value, convertTo() for converting the whole measurement object to different units, and add() and subtract() for for modifying the stored value by the value (converted as required) in another measurement. In the admin the inputfield includes a checkbox (which can be optionally disabled) for converting values on page save. For an example if a value was typed in as centimeters, the unit was changed to metres, and the page saved with this checkbox selected, said value would be automatically converted so that e.g. 170 cm becomes 1.7 m.

      A simple length field using Fieldtype Measurement and Inputfield Measurement.
      Combination units (e.g. feet and inches) are also supported.
      Please note that this module is 'proof of concept' at the moment - there are limited units available and quite a lot of code tidying to do. More units will be added shortly.
      See the GitHub at https://github.com/MetaTunes/FieldtypeMeasurement for full details and updates.
    • By tcnet
      File Manager for ProcessWire is a module to manager files and folders from the CMS backend. It supports creating, deleting, renaming, packing, unpacking, uploading, downloading and editing of files and folders. The integrated code editor ACE supports highlighting of all common programming languages.
      https://github.com/techcnet/ProcessFileManager

      Warning
      This module is probably the most powerful module. You might destroy your processwire installation if you don't exactly know what you doing. Be careful and use it at your own risk!
      ACE code editor
      This module uses ACE code editor available from: https://github.com/ajaxorg/ace

      Dragscroll
      This module uses the JavaScript dragscroll available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability to drag the table horizontally with the mouse pointer.
      PHP File Manager
      This module uses a modified version of PHP File Manager available from: https://github.com/alexantr/filemanager
       
    • By tcnet
      This module implements the website live chat service from tawk.to. Actually the module doesn't have to do much. It just need to inserted a few lines of JavaScript just before the closing body tag </body> on each side. However, the module offers additional options to display the widget only on certain pages.
      Create an account
      Visit https://www.tawk.to and create an account. It's free! At some point you will reach a page where you can copy the required JavaScript-code.

      Open the module settings and paste the JavaScript-code into the field as shown below. Click "Submit" and that's all.

      Open the module settings
      The settings for this module are located int the menu Modules=>Configure=>LiveChatTawkTo.

       
    • By tcnet
      Session Viewer is a module for ProcessWire to list session files and display session data. This module is helpful to display the session data of a specific session or to kick out a logged in user by simply delete his session file. After installation the module is available in the Setup menu.

      The following conditions must be met for the module to work properly:
      Session files
      Session data must be stored in session files, which is the default way in ProcessWire. Sessions stored in the database are not supported by this module. The path to the directory where the session files are stored must be declared in the ProcessWire configuration which is by default: site/assets/sessions.
      Serialize handler
      In order to transform session data easier back to a PHP array, the session data is stored serialized. PHP offers a way to declare a custom serialize handler. This module supports only the default serialize handlers: php, php_binary and php_serialize. WDDX was dropped in PHP 7.4.0 and is therefore not supported by this module as well as any other custom serialize handler. Which serialize handler is actually used you can find out in the module configuration which is available under Modules=>Configure=>SessionViewer.

      Session data
      The session data can be displayed in two different ways. PHP's default output for arrays print_r() or by default for this module nice_r() offered on github: https://github.com/uuf6429/nice_r. There is a setting in the module configuration if someone prefers print_r(). Apart from the better handling and overview of the folded session data the output of nice_r() looks indeed nicer.

      Links
      ProcessWire module directory
      github.com
×
×
  • Create New...