horst

Croppable Image 3

Recommended Posts

Croppable Image 3 (beta)

for PW 3.0.20+

Module Version 1.1.15

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.

 

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

 

Sticking with a PW legacy 2.8.20+ Version (none namespaced)? - I have created a CroppableImage2 snapshot, which you can get from the github repo branch: CroppableImage2 


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

 

Edited by horst
new infos for updating!
  • 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

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 bernhard
      Some of you might have followed the development of this module here: https://processwire.com/talk/topic/15524-previewdiscussion-rockdatatables/ . It is the successor of "RockDataTables" and requires RockFinder to get the data for the grid easily and efficiently. It uses the open source part of agGrid for grid rendering.
       
      WHY?
      ProcessWire is awesome for creating all kinds of custom backend applications, but where it is not so awesome in my opinion is when it comes to listing this data. Of course we have the built in page lister and we have ListerPro, but none of that solutions is capable of properly displaying large amounts of data, for example lists of revenues, aggregations, quick and easy sorts by the user, instant filter and those kind of features. RockGrid to the rescue 😉 
       
      Features/Highlights:
      100k+ rows Instant (client side) filter, search, sort (different sort based on data type, eg "lower/greater than" for numbers, "contains" for strings) extendable via plugins (available plugins at the moment: fullscreen, csv export, reload, batch-processing of data, column sum/statistics, row selection) all the agGrid features (cell renderers, cell styling, pagination, column grouping etc) vanilla javascript, backend and frontend support (though not all plugins are working on the frontend yet and I don't plan to support it as long as I don't need it myself)  
      Limitations:
      While there is an option to retrieve data via AJAX the actual processing of the grid (displaying, filtering, sorting) is done on the client side, meaning that you can get into troubles when handling really large datasets of several thousands of rows. agGrid should be one of the most performant grid options in the world (see the official example page with a 100k row example) and does a lot to prevent problems (such as virtual row rendering), but you should always have this limitation in mind as this is a major difference to the available lister options that do not have this limitation.
      Currently it only supports AdminThemeUikit and I don't plan to support any other admin theme.
       
      Download: https://gitlab.com/baumrock/FieldtypeRockGrid
      Installation: https://gitlab.com/baumrock/RockGrid/wikis/Installation
      Quikckstart: https://gitlab.com/baumrock/RockGrid/wikis/quickstart
      Further instructions: https://gitlab.com/baumrock/RockGrid/wikis/quickstart#further-instructions
      German Translation File: site--modules--fieldtyperockgrid--fieldtyperockgrid-module-php.json
      Changelog: https://gitlab.com/baumrock/FieldtypeRockGrid/raw/master/changelog.md
       
      Module status: alpha, License: MIT
      Note that every installation and uninstallation sends an anonymous google analytics event to my google analytics account. If you don't want that feel free to remove the appropriate lines of code before installation/uninstallation.
       
      Contribute:
      You can contribute to the development of this and other modules or just say thank you by
      testing, reporting issues and making PRs at gitlab liking this post buying me a drink: paypal.me/baumrock/5 liking my facebook page: facebook.com/baumrock hiring me for pw work: baumrock.com  
      Support: Please note that this module might not be as easy and plug&play as many other modules. It needs a good understanding of agGrid (and JavaScript in general) and it likely needs some looks into the code to get all the options. Please understand that I can not provide free support for every request here in the forum. I try to answer all questions that might also help others or that might improve the module but for individual requests I offer paid support for 60€ per hour (excl vat).
       
      Use Cases / Examples:
      Colored grid cells, Icons, Links etc. The Grid also has a "batcher" feature built in that helps communicating with the server via AJAX and managing resource intensive tasks in batches:

      Filters, PW panel links and instant reload on panel close:

      You can combine the grid with a chart library like I did with the (outdated) RockDataTables module:

    • By thomasaull
      Some time ago I created a site profile for creation of a REST API with ProcessWire. Since I kept struggeling with updating stuff between different projects which use this, I decided to convert it into a module. It is now ready for testing: https://github.com/thomasaull/RestApi
      Additionally I added a few small features:
      automatic creation of JWT Secret at module install routes can be flagged as auth: false, which makes them publicly accessible even though JWT Auth is activated in module settings To check things out, download and install the module and check the folder /site/api for examples.
      If you find any bugs or can think of improvements, please let me know!
    • By kongondo
      Sites Manager
       
      16 September 2018:
      FOR NOW, PLEASE DO NOT USE THIS MODULE IN A PRODUCTION SITE. A  RECENT ProcessWire UPDATE HAS BROKEN THE MODULE. I AM WORKING ON A FIX.
       
      ################
       
      Sites Manager is a module for ProcessWire that allows Superusers to easily create/install ProcessWire sites on the same serverspace the module is running in. Only Superusers can use the module. You can create both stand-alone and multi-sites.
       
      Single/Stand-alone Sites
      Stand-alone or single-sites are sites that will run in their own document root/directory with their own wire and site folders, .htaccess, index.php, etc. In other words, a normal ProcessWire site.
      Multiple Sites
      Multi-sites are sites that will run off one wire folder (shared amongst two or more sites) each having their own site folder and database. In this regard, it is important to note that Sites Manager is not in itself a multiple sites solution! Rather, it is a utility that helps you create multi-sites to be run using the ProcessWire core multiple sites feature. For more on this core feature, see the official ProcessWire documentation, specifically the solution referred to as Option #1.
      Option #1 approach requires the site admin to initially install ProcessWire in a temporary directory for each new site. The directory then needs to be renamed as site-xxx, where ‘xxx’ is any name you want to use to differentiate the installation from other sites, before it is moved to the webroot. For instance, site-mysite, site-another, site-whatever. In addition, the /wire/index.config.php file must be copied/moved to the webroot. Each time a site is added, the index.config.php has to be edited to add ‘domain’ => ‘site-directory’ key=>value pairs for the site. This process can become a bit tedious. This module aims to automate the whole multi-site site creation process.
      The module is based off the official ProcessWire installer. Creating a site is as simple as completing and submitting a single form! You also have the option to type and paste values or reuse a pre-defined install configuration.
       
      The module will:
      Install a ProcessWire site in your named directory, applying chmod values as specified
      Move the directory to your webroot
      Update/Create a Superuser account as per the submitted form, including setting the desired admin theme and colour
      For multi sites, update sites.json (used by index.config.php to get array of installed sites)
       
      For multi sites, the only difference in relation to the core multi-sites index.config.php is that this file is slightly different from the one that ships with ProcessWire.
      Download from GitHub: Sites Manager (Beta Release)
      Features
      Install unlimited number of sites in one (multi-sites) or independent (single-site) ProcessWire installs. Install by completing a Form, Typing or pasting in configurations or using pre-created install configurations. Choose an Admin Theme to auto-install along with the site installation. For single-sites installation, download, save and reuse ProcessWire versions of your choice. Install and maintain site profiles for reuse to create other sites. Create install configurations to speed up installation tasks. Client and server-side validation of site creation values. Edit uploaded profiles (e.g., replace profile file). Lock installed sites, configurations and profiles to prevent editing. Bulk delete items such as site profiles, installed site directories and/or databases (confirmation required for latter two). View important site details (admin login, chmod, etc). Links to installed sites home and admin pages. Timezones auto-complete/-suggest. Pre-requisites, Installation & Usage
      Please see the documentation.
      Technicalities/Issues
      Only Superusers can use the module.
      ProcessWire 2.7 - 3.x compatible
      Currently using ProcessWire 2.7 installer (install.php)
      For multi-sites, potential race condition when sites.json is being updated on a new site install vs. index.config.php accessing the json file?
      Not tested with sub-directory installs (for instance localhost/pw/my-site-here/)
      Currently not doing the extra/experimental database stuff (database charset and engine)
      Future Possibilities
      Install specified modules along with the ProcessWire install
      Profile previews?
      Credits
      @ryan: for the ProcessWire installer
      @abdus: for the index.config.php reading from JSON idea
      @swampmusic: for the challenge
      Video Demo
      Demo  showing how quick module works on a remote server [YMMV!]. Video shows downloading and processing two versions of ProcessWire (~takes 7 seconds) and installing a single/stand-alone ProcessWire 3 site using the new Admin Theme UI Kit (~2 seconds) on a remote server.
       
      Screens
      1

      2

       
       
    • By Robin S
      Breadcrumb Dropdowns
      Adds dropdown menus of page edit links to the breadcrumbs in Page Edit.

      Installation
      Install the Breadcrumb Dropdowns module. The module requires ProcessWire >= v3.0.83 and AdminThemeUikit.
      There is a checkbox option in the module config that determines if the breadcrumb dropdowns will include pages that the user does not have permission to edit.
      Features/details
      The module adds an additional breadcrumb item at the end for the currently edited page. That's because I think it's more intuitive for the dropdown under each breadcrumb item to show the item's sibling pages rather than the item's child pages. In the dropdown menus the current page and the current page's parents are highlighted in a crimson colour to make it easier to quickly locate them in case you want to edit the next or previous sibling page. Unpublished and hidden pages are indicated in the dropdowns with similar styling to that used in Page List. If the option to include uneditable pages is selected then those pages are indicated by italics with a reduced text opacity and the "not-allowed" cursor is shown on hover. There is a limit of 25 pages per dropdown for performance reasons and to avoid the dropdown becoming unwieldy. If the current user is allowed to add new pages under the parent page an "Add New" link is shown at the bottom of the breadcrumb dropdown. If the currently edited page has children or the user may add children, a caret at the end of the breadcrumbs reveals a dropdown of up to the first 25 children and/or an "Add New" link. Overriding the listed siblings for a page
      If you want to override the siblings that are listed in the dropdowns you can hook the BreadcrumbDropdowns::getSiblingsmethod and change the returned PageArray. For most use cases this won't be necessary.
      Incompatibilities
      This module replaces the AdminThemeUikit::renderBreadcrumbs method so will potentially be incompatible with other modules that hook the same method.
       
      https://modules.processwire.com/modules/breadcrumb-dropdowns/
      https://github.com/Toutouwai/BreadcrumbDropdowns
    • By Ken Muldrew
      I'm trying to get a short routine to run once per day that will look at some pages and send a reminder email when that customer's subscription (yearly) is about to expire. When I run the code in a template then it works without issue, but inside my lazycron service routine, I get an "Error: Uncaught Error: Call to a member function get() on null" as if the database cannot be found. My autoload module is just the sample HelloWorld module included with ProcessWire, editted to perform this task. The whole of it is included below (I've stripped out the code that generates the email because it never gets past $pages->find):
       
      <?php namespace ProcessWire;
      /**
       * ProcessWire 'LazyCronLoad'  module
       *
       */
      class LazyCronLoad extends WireData implements Module {
          public static function getModuleInfo() {
              return array(
                  'title' => 'LazyCronLoad', 
                  'version' => 1, 
                  'summary' => 'Just loads a lazy cron callback.',
                  'singular' => true, 
                  'autoload' => true, 
                  );
          }
          public function init() {
              // initialize the hook in the AutoLoad module
              $this->addHook('LazyCron::everyDay', $this, 'myHook');
              
          }
          public function myHook(HookEvent $e) {
              // called once per day
              wire('log')->save('user_activities',' lazy cron service routine');
                  $transport_pages = $pages->find("template=aggregate-entry, aggregate_type.title='Transport'");
                  foreach ($transport_pages as $page) {
                      if (($page->purchase_date + 30325800 < time()) && ($page->purchase_date + 30412600 > time())) { // between 351 and 352 days
                          wire('log')->save('user_activities', $page->id . ' email reminder sent');
                          // send email
                  }
              }
          }        
          
      }
      The first wire('log') shows up but the second one doesn't (the purchase_date condition is met (as demonstrated by running the code in a template close in time to when the lazycron routine executes)). The error log gives the Uncaught Error shown above. 
      I think this is a beginner's mistake with something obvious being missed and would be grateful for any assistance in fixing it.