Jump to content
horst

Croppable Image 3

Recommended Posts

Croppable Image 3

for PW 3.0.20+

Module Version 1.1.16

Sponsored by http://dreikon.de/, many thanks Timo & Niko!

You can get it in the modules directory!

Please refer to the readme on github for instructions.

 

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

 

Updating from prior versions:

 

Updating from Croppable Image 3 with versions prior to 1.1.7, please do this as a one time step:

In the PW Admin, go to side -> modules -> new, use "install via ClassName" and use CroppableImage3 for the Module Class Name. This will update your existing CroppableImage3 module sub directory, even if it is called a new install. After that, the module will be recogniced by the PW updater module, what makes it a lot easier on further updates.

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

 

For updating from the legacy Thumbnail / CropImage to CroppableImage3 read on here.

 

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

 

Edited by horst
bumped version to 1.1.16, fixed a small PHP 7 issue
  • Like 20

Share this post


Link to post
Share on other sites

How the new editor window looks like.

  • Like 9

Share this post


Link to post
Share on other sites

This looks great @horst - just one initial request - can we lose the "Wow that looks great" button label and make it simply "Continue" or "Accept" or something similar. And maybe the "Not happy, crop again" link should be a button with "Redo Crop" ?

PS I know these labels are a legacy of the original thumbnails module, but they do sound a little weird to me.

  • Like 8

Share this post


Link to post
Share on other sites
15 hours ago, adrian said:

This looks great @horst - just one initial request - can we lose the "Wow that looks great" button label and make it simply "Continue" or "Accept" or something similar. And maybe the "Not happy, crop again" link should be a button with "Redo Crop" ?

PS I know these labels are a legacy of the original thumbnails module, but they do sound a little weird to me.

What have you done Adrian!?!? 

TBH I was surprised that those lived so long. They always made me smile :)

  • Like 8

Share this post


Link to post
Share on other sites
8 minutes ago, apeisa said:

What have you done Adrian!?!? 

TBH I was surprised that those lived so long. They always made me smile :)

I was waiting for your response here - sorry about that - no offense intended :)

  • Like 2

Share this post


Link to post
Share on other sites

No offense, but oh so many tears. I will get over this. Someday.

  • Like 3

Share this post


Link to post
Share on other sites

I'm thinking about to implement a "show historical label texts" module config checkbox. Antti, would this help to get over this a bit faster?

(Some customers really liked that. "Oh, thats so positive! Fine.") :)

 

  • Like 5

Share this post


Link to post
Share on other sites

Aren't your module sponsors withdraw seeing this? :)

  • Like 2

Share this post


Link to post
Share on other sites

I actually like when software is not so serious. And I think most people do. Or at least it is not stop for success, take a look at MailChimp and Slack for example. 

@horst the legacy labels setting would make my day! 

  • Like 1

Share this post


Link to post
Share on other sites
8 minutes ago, apeisa said:

I actually like when software is not so serious. And I think most people do. Or at least it is not stop for success, take a look at MailChimp and Slack for example. 

@horst the legacy labels setting would make my day! 

Wow - now I feel so boring and serious :)

Seriously (ha ha) though, I think there is a great place for fun elements in software, but I think it's important who it's aimed at and whether they'll see it as fun or just confusing - "you gotta keep it smart people" (dorky TV quote there)!

Getting OT, but why do all phone companies around the world seem to use cute animals in their advertising? I don't see the fun because I can't see the connection - the fun has to be relevant.

  • Like 3

Share this post


Link to post
Share on other sites
1 hour ago, adrian said:

Wow - now I feel so boring and serious :)

Yeah, now I'm thinking about to setup a radio or select with something like:

   "I am serious"

   "I like it funny"

   "I'm brave, surprise me"

 

@apeisa: Yes, that was exactly what one customer said to me a month ago: "Oh, thats nice and not so serious. I like it. It is the same way like Mailchimp do."

  • Like 3

Share this post


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

Aren't your module sponsors withdraw seeing this? :)

Haha, I don't hope so!

Share this post


Link to post
Share on other sites

Version 0.9.12

I added a single centralized translation file. It combines all text strings of all module and dependency files. This way it should be easier or lesser work to translate it. (<- hint @ceberlin, @Manfred62, @yellowled :))

@apeisa: Also the legacy and serious text selection is included. (legacy is default!)

 

 

 

  • Like 6

Share this post


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

legacy is default!

boo! hiss!

Just kidding :) I actually don't mind it at all now that the crop again option is a button rather than a text link.

  • Like 1

Share this post


Link to post
Share on other sites

Haha! Yep, and also, if you or your customer are more from the serious side, it is only a selection and a save click to change it. :)

Share this post


Link to post
Share on other sites
Quote

this way it should be easier or lesser work to translate it. (<- hint

Ok, I will take care of the translation to DE tonight...

  • Like 2

Share this post


Link to post
Share on other sites

Hi Horst,

it's great to see CoppableImage again in PW3!
For me as Superuser all is fine, but if I login with another role (with right "page-edit-image") the modal crop-window switches to the pagetree-view.

  • Like 1

Share this post


Link to post
Share on other sites

Hmmm after installing the new Version I have a problem:

When clicking on "Wow that looks great / Accept" the modal window does not close anymore. It does not close, when I click on the "X" in the upper right corner either.

Plus, there are a few Javascript errors:

InputfieldCroppableImage3.js:31 Uncaught TypeError: Cannot read property 'width' of undefined

I testet in on my Mac with Chrome and Firefox. Same behaviour in both browsers.

Share this post


Link to post
Share on other sites

Here it is working without errors. Also, the relevant part for that hasn't changed between the last versions.

Maybe browser cache issue, or, if that doesn't help. Delete all files and folders under site/modules/CroppableImage3/ ... and copy a fresh one new Version into it, to make sure to have all the latest versions?

I can switch force and back between the two modal windows multiple times, and I also can close it via the buttons and the X.

13 hours ago, Noboru said:

For me as Superuser all is fine, but if I login with another role (with right "page-edit-image") the modal crop-window switches to the pagetree-view.

I will test this and come back here, when done.

Share this post


Link to post
Share on other sites
13 hours ago, Noboru said:

Hi Horst,

it's great to see CoppableImage again in PW3!
For me as Superuser all is fine, but if I login with another role (with right "page-edit-image") the modal crop-window switches to the pagetree-view.

Same behave here, sorry.

What I encountered in short, is: I get different color for the modal windows title bar (?), and it doesn't open the processPage. So, it is an access issue. I need to investigate further. ...

Share this post


Link to post
Share on other sites

Somehow I had lost the permission settings during the rewrite. Also there were a chance for some interfere with the permission of the older Croppable module.

Now I have fixed it with the update to version 0.9.14

But it will not update / correct itself, :(

To get rid of the bug, everyone who has installed a version lesser than 0.9.14 should follow these manual steps:

  1. copy the module files >= 0.9.14 into site/modules/CroppableImage3/
  2. goto admin > modules > site > ProcessCroppableImage3, open it, select uninstall and uninstall it
  3. now refresh the modules cache
  4. and install the ProcessCroppableImage3
  5. open all your user roles that need edit rights for crop images and add the new " image-crop-3 " permission to them

Ready!

For fresh installs of version 0.9.14+, everything works out of the box.

  • Like 5

Share this post


Link to post
Share on other sites

Hello Horst,

I got problems with the crop function. I always get the error message "process returns no content" after clicking the cropping button:

Here are the crop settings of my image field:

Screenshot_13.jpg

As you can see I have added pre-defined crop settings to the image field.

And here you can see what happens if I press the crop button:


5xsM3xVPfB.gif

The modal window always shows that no content will be returned. I have tried to catch an error with Tracy Debugger but not luck.

PW: 3.0.32, User: Superuser, PHP 5.6.25, Server: Apache, Croppable image 3: version 0.9.14

Any idea?

Best regards Jürgen

Share this post


Link to post
Share on other sites

How do you have installed it? Was a previous version there before?

If there is no Process installed, that could be because:

the ProcessImageCroppable3 isn't installed or not installed correct. maybe it misses its admin page?

Have you checked that ProcessCroppableImage3 is installed?

Did you have under Admin > Pages > a page with title "Croppable Images 3", and what is its process and name?

 

  • Like 1

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 Robin S
      A community member raised a question and I thought a new sanitizer method for the purpose would be useful, hence...
      Sanitizer Transliterate
      Adds a transliterate method to $sanitizer that performs character replacements as defined in the module config. The default character replacements are based on the defaults from InputfieldPageName, but with uppercase characters included too.
      Usage
      Install the Sanitizer Transliterate module.
      Customise the character replacements in the module config as needed.
      Use the sanitizer on strings like so:
      $transliterated_string = $sanitizer->transliterate($string);
       
      https://github.com/Toutouwai/SanitizerTransliterate
      https://modules.processwire.com/modules/sanitizer-transliterate/
       
    • By dimitrios
      Hello,
      this module can publish content of a Processwire page on a Facebook page, triggered by saving the Processwire page.
      To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers:
      Minimum Required Facebook App configuration:
      on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version to 2.10, add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "http://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. This module is configurable as follows:
      Templates: posts can take place only for pages with the defined templates. On/Off switch: specify a checkbox field that will not allow the post if checked. Specify a message and/or an image for the post.
      Usage
      edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, an access token is kept.
       
      Download
      PW module directory: http://modules.processwire.com/modules/auto-fb-post/ Github: https://github.com/kastrind/AutoFbPost   Note: Facebook SDK for PHP is utilized.


    • By thomasaull
      I created a little helper module to trigger a CI pipeline when your website has been changed. It's quite simple and works like this: As soon as you save a page the module sets a Boolean via a pages save after hook. Once a day via LazyCron the module checks if the Boolean is set and sends a POST Request to a configurable Webhook URL.
      Some ideas to extend this:
      make request type configurable (GET, POST) make the module trigger at a specified time (probably only possible with a server cronjob) trigger manually Anything else? If there's interest, I might put in some more functionality. Let me know what you're interested in. Until then, maybe it is useful for a couple of people 🙂
      Github Repo: https://github.com/thomasaull/CiTrigger
    • By Robin S
      I created this module a while ago and never got around to publicising it, but it has been outed in the latest PW Weekly so here goes the support thread...
      Unique Image Variations
      Ensures that all ImageSizer options and focus settings affect image variation filenames.

      Background
      When using methods that produce image variations such as Pageimage::size(), ProcessWire includes some of the ImageSizer settings (height, width, cropping location, etc) in the variation filename. This is useful so that if you change these settings in your size() call a new variation is generated and you see this variation on the front-end.
      However, ProcessWire does not include several of the other ImageSizer settings in the variation filename:
      upscaling cropping, when set to false or a blank string interlace sharpening quality hidpi quality focus (whether any saved focus area for an image should affect cropping) focus data (the top/left/zoom data for the focus area) This means that if you change any of these settings, either in $config->imageSizerOptions or in an $options array passed to a method like size(), and you already have variations at the requested size/crop, then ProcessWire will not create new variations and will continue to serve the old variations. In other words you won't see the effect of your changed ImageSizer options on the front-end until you delete the old variations.
      Features
      The Unique Image Variations module ensures that any changes to ImageSizer options and any changes to the focus area made in Page Edit are reflected in the variation filename, so new variations will always be generated and displayed on the front-end.
      Installation
      Install the Unique Image Variations module.
      In the module config, set the ImageSizer options that you want to include in image variation filenames.
      Warnings
      Installing the module (and keeping one or more of the options selected in the module config) will cause all existing image variations to be regenerated the next time they are requested. If you have an existing website with a large number of images you may not want the performance impact of that. The module is perhaps best suited to new sites where image variations have not yet been generated.
      Similarly, if you change the module config settings on an existing site then all image variations will be regenerated the next time they are requested.
      If you think you might want to change an ImageSizer option in the future (I'm thinking here primarily of options such as interlace that are typically set in $config->imageSizerOptions) and would not want that change to cause existing image variations to be regenerated then best to not include that option in the module config after you first install the module.
       
      https://github.com/Toutouwai/UniqueImageVariations
      https://modules.processwire.com/modules/unique-image-variations/
    • By Sebi
      I've created a small module which lets you define a timestamp after which a page should be accessible. In addition you can define a timestamp when the release should end and the page should not be accessable any more.
      ProcessWire-Module: http://modules.processwire.com/modules/page-access-releasetime/
      Github: https://github.com/Sebiworld/PageAccessReleasetime
      Usage
      PageAccessReleasetime can be installed like every other module in ProcessWire. Check the following guide for detailed information: How-To Install or Uninstall Modules
      After that, you will find checkboxes for activating the releasetime-fields at the settings-tab of each page. You don't need to add the fields to your templates manually.
      Check e.g. the checkbox "Activate Releasetime from?" and fill in a date in the future. The page will not be accessable for your users until the given date is reached.
      If you have $config->pagefileSecure = true, the module will protect files of unreleased pages as well.
      How it works
      This module hooks into Page::viewable to prevent users to access unreleased pages:
      public function hookPageViewable($event) { $page = $event->object; $viewable = $event->return; if($viewable){ // If the page would be viewable, additionally check Releasetime and User-Permission $viewable = $this->canUserSee($page); } $event->return = $viewable; } To prevent access to the files of unreleased pages, we hook into Page::isPublic and ProcessPageView::sendFile.
      public function hookPageIsPublic($e) { $page = $e->object; if($e->return && $this->isReleaseTimeSet($page)) { $e->return = false; } } The site/assets/files/ directory of pages, which isPublic() returns false, will get a '-' as prefix. This indicates ProcessWire (with activated $config->pagefileSecure) to check the file's permissions via PHP before delivering it to the client.
      The check wether a not-public file should be accessable happens in ProcessPageView::sendFile. We throw an 404 Exception if the current user must not see the file.
      public function hookProcessPageViewSendFile($e) { $page = $e->arguments[0]; if(!$this->canUserSee($page)) { throw new Wire404Exception('File not found'); } } Additionally we hook into ProcessPageEdit::buildForm to add the PageAccessReleasetime fields to each page and move them to the settings tab.
      Limitations
      In the current version, releasetime-protected pages will appear in wire('pages')->find() queries. If you want to display a list of pages, where pages could be releasetime-protected, you should double-check with $page->viewable() wether the page can be accessed. $page->viewable() returns false, if the page is not released yet.
      If you have an idea how unreleased pages can be filtered out of ProcessWire selector queries, feel free to write an issue, comment or make a pull request!
×
×
  • Create New...