Jump to content
horst

CroppableImage

Recommended Posts

Yep. You just aim between the eyes and that's it :)

  • Like 2

Share this post


Link to post
Share on other sites

Regarding a cropped version: Is it right that we easily can create a new cropped-out image (variation) with the individual cropping tool of the core imagefield, and then, in a second step, select this new one an define the focus point?

If this would be possible, I think then there is nothing left out. :)

Share this post


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

Regarding a cropped version: Is it right that we easily can create a new cropped-out image (variation) with the individual cropping tool of the core imagefield, and then, in a second step, select this new one an define the focus point?

If this would be possible, I think then there is nothing left out. :)

I think that is a novel way of setting the focus point! But I don't necessarily agree that it should be the only option.

I have feeling more novice users/editors would be confused by it not being "specific" enough, as they might not be able to visualise how that appears in the front-end on their news article for example. Unless the pre-defined crop areas - as they exist now - will still show a preview step, somehow? Perhaps I've been thrown by the multiple tiles in the demo?

I just really enjoy how, for me and the projects I've worked on, CroppableImage has been one of the best image-related things in PW. It just helps so much being able to specify the dimensions images should be :)

  • Like 1

Share this post


Link to post
Share on other sites

Cropping for different devices shouldn't mean crop to smaller sizes by default. Say you have a photo with a group of people and one of that group is the subject. It wouldn't be weird to crop out only that person for smaller devices.

  • Like 2

Share this post


Link to post
Share on other sites

hi,

i also think that this would be a great addition but should NOT be the only option. playing around with the jquery demo (http://jonom.github.io/jquery-focuspoint/demos/helper/index.html) i see that it would lead to problems when you only want to show a small part of the image that is located near the border of the image. i think a more advanced concept like the imagefoucsarea plugin would be better.

the best would be to have the good old cropping plugin with predefined ratios and/or dimensions, have a simple focus point option and even more have a more advanced focus-area option like in the plugin linked above :)

  • Like 4

Share this post


Link to post
Share on other sites

Any updates on supporting PW3? As it's almost done now would be the time. Right?

  • Like 1

Share this post


Link to post
Share on other sites

In the last Blog Post Ryan said he and Horst are working on it have had a chat about it... On Mobile no Link sorry ;) Link in the next post

  • Like 2

Share this post


Link to post
Share on other sites

Ryan said that we have had a chat,
but I'm working on it. :)

  • Like 4

Share this post


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

Ryan said that we have had a chat,
but I'm working on it. :)

haha ok sorry for that, i corrected my post ;) here is the link: http://processwire.com/blog/posts/tesla-model-s/

Quote

Also for those that have been looking to use the CroppableImage module in PW3, Horst and I chatted this week and found a way to make it work so I imagine the option will be there very soon as well.

@horst

is it possible to share some details about that? what is planned? there was a lot of discussion around this topic in the past, i think it would be good to consider some of that feedback for a new version of the corefield (or will it again be a module?). i can't find the right topic now where we were talking about presets in the core field... what i found was only these two topics:

 

and still on my wishlist, because that would make building image galleries a breeze:

any chance that client side resizing finds its way to this update? at least it was mentioned in the roadmap for 2016 :) https://processwire.com/blog/posts/happy-new-year-heres-a-roadmap-for-processwire-in-2016/#what-else-is-coming-for-processwire-3.x-in-2016

Quote

Client-side image resizing. This will enable images to be resized before upload. This will be particularly handy for cases where clients are uploading giant photos that are time consuming and/or impossible to resize server-side.

thank you for all your work on the images field so far!! :)

Share this post


Link to post
Share on other sites

Just to clarify, I'm not working on the core image field, I only work on the CroppableImage Modules, to make them work with the new core Imagefield in PW3. It will inject a small section with buttons into the head of the edit area, like here, (predefined Crops)

noisy-thumbnail-background.gif

The buttons will open a modal editor window. The editor window should get some new styling. Thats it.

And this only is possible because of the sponsoring through DREIKON, who are so kind to donate 500+ Euro for my work on this, what is much appreciated. Otherwise I wouldn't be able to invest the needed time for it, atm.

Current state is: injection works, modal open and close works, rearanging / styling of the editor window needs to be done, testing needs to be done.

  • Like 12

Share this post


Link to post
Share on other sites

Is there any chance that this module will be updated to work with 2.8.x?

Share this post


Link to post
Share on other sites

It should be working with the namespaced Version CroppableImage3.

  • If it doesn't, you may strip out the namespace ProcessWire; at the top of all files,
  • then install it with $config->debug = true; and look out for any failing function or class instance call that is prefixed with a backslash (\),
  • if there are any of those errors or warnings, go into that file and line and remove the backslash (\).

After that it will work.

Other way would be to notify Ryan, that this module doesn't work with automaticly switching from v3.0 to v2.8 through the FileCompiler. Maybe he is willing to look at it and can justify the FileCompiler to identify and handle some special cases there too.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks Horst. It worked. I'll ping Ryan soon!

Share this post


Link to post
Share on other sites

Oops - I accidentally upgraded a small site from 2.7.X to 3.X not realising that CI was running and am getting following error:

Error: Uncaught Error: Class 'ProcessWire\ProcessCroppableImage' not found in /var/www/vhosts/domain.com/httpdocs/site/modules/ProcessCroppableImage/InputfieldCroppableImage/InputfieldCroppableImage.module:170
Stack trace:
#0 /var/www/vhosts/domain.com/httpdocs/site/modules/ProcessCroppableImage/InputfieldCroppableImage/InputfieldCroppableImage.module(147): InputfieldCroppableImage->getCropLinks(Object(ProcessWire\Pageimage))
#1 [internal function]: InputfieldCroppableImage->___renderItem(Object(ProcessWire\Pageimage), 'Images_e711d4de...', 0)
#2 /var/www/vhosts/domain.com/httpdocs/wire/core/Wire.php(348): call_user_func_array(Array, Array)
#3 /var/www/vhosts/domain.com/httpdocs/wire/core/WireHooks.php(548): ProcessWire\Wire->_callMethod('___renderItem', Array)
#4 /var/www/vhosts/domain.com/httpdocs/wire/core/Wire.php(373): ProcessWire\WireHooks->runHooks(Object(InputfieldCroppableImage), 'renderItem', Arr (line 170 of /var/www/vhosts/domain.com/httpdocs/site/modules/ProcessCroppableImage/InputfieldCroppableImage/InputfieldCroppableImage.module)

This error message was shown because: you are logged in as a Superuser. Error has been logged.

Would the manual upload of the PW3 folder and creation of CI3 image field solve this or do I need to restore the site to 2.7X and start again?

I'm out of the office right now and thought I'd ask first in case it makes things worse.

Thanks
P

 

 

Share this post


Link to post
Share on other sites
On 27/08/2016 at 8:50 AM, horst said:

Just to clarify, I'm not working on the core image field, I only work on the CroppableImage Modules, to make them work with the new core Imagefield in PW3. It will inject a small section with buttons into the head of the edit area, like here, (predefined Crops)

noisy-thumbnail-background.gif

The buttons will open a modal editor window. The editor window should get some new styling. Thats it.

And this only is possible because of the sponsoring through DREIKON, who are so kind to donate 500+ Euro for my work on this, what is much appreciated. Otherwise I wouldn't be able to invest the needed time for it, atm.

Current state is: injection works, modal open and close works, rearanging / styling of the editor window needs to be done, testing needs to be done.

Any news on this?

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 MoritzLost
      This is a new module that provides a simple solution to clearing all your cache layers at once, and an extensible interface to perform various cache-related actions.
      The simple motivation behind this module was that I was tired of manually clearing caches in several places after deploying a change on a live site. The basic purpose of this module is a simple Clear all caches link in the Setup menu which clears out all caches, no matter where they hide. You can customize what exactly the module does through it's configuration menu:
      Expire or delete all cache entries in the database, or selectively clear caches by namespace ($cache API) Clear the the template render cache. Clear out specific folders inside your site's cache directory (/site/assets/cache) Refresh version strings for static assets to bust client-side browser caches (this requires some setup, see the full documentation for details). This is the basic function of the module. However, you can also add different cache management action through the API and execute them through the module's interface. For this advanced usage, the module provides:
      An interface to see all available cache actions and execute them. A system log and logging output on the module page to see verify what the module is doing. A CacheControlTools class with utility functions to clear out different caches. An API to add cache actions, execute them programmatically and even modify the default action. Permission management, allowing you granular control over which user roles can execute which actions. The complete documentation can be found in the module's README.
      Beta release
      Note that I consider this a Beta release. Since the module is relatively aggressive in deleting some caches, I would advise you to install in on a test environment before using it on a live site.
      Let me know if you're getting any errors, have trouble using the module or if you have suggestions for improvement!
      In particular, can someone let me know if this module causes any problems with the ProCache module? I don't own or use it, so I can't check. As far as I can tell, ProCache uses a folder inside the cache directory to cache static pages, so my module should be able to clear the ProCache site cache as well, I'd appreciate it if someone can test that for me.
      Future plans
      If there is some interest in this, I plan to expand this to a more general cache management solution. I particular, I would like to add additional cache actions. Some ideas that came to mind:
      Warming up the template render cache for publicly accessible pages. Removing all active user sessions. Let me know if you have more suggestions!
      Links
      https://github.com/MoritzLost/ProcessCacheControl ProcessCacheControl in the Module directory

    • By joshua
      This module is (yet another) way for implementing a cookie management solution.
      Of course there are several other possibilities:
      - https://processwire.com/talk/topic/22920-klaro-cookie-consent-manager/
      - https://github.com/webmanufaktur/CookieManagementBanner
      - https://github.com/johannesdachsel/cookiemonster
      - https://www.oiljs.org/
      - ... and so on ...
      In this module you can configure which kind of cookie categories you want to manage:

      You can also enable the support for respecting the Do-Not-Track (DNT) header to don't annoy users, who already decided for all their browsing experience.
      Currently there are four possible cookie groups:
      - Necessary (always enabled)
      - Statistics
      - Marketing
      - External Media
      All groups can be renamed, so feel free to use other cookie group names. I just haven't found a way to implement a "repeater like" field as configurable module field ...
      When you want to load specific scripts ( like Google Analytics, Google Maps, ...) only after the user's content to this specific category of cookies, just use the following script syntax:
      <script type="optin" data-type="text/javascript" data-category="statistics" data-src="/path/to/your/statistic/script.js"></script> <script type="optin" data-type="text/javascript" data-category="marketing" data-src="/path/to/your/mareketing/script.js"></script> <script type="optin" data-type="text/javascript" data-category="external_media" data-src="/path/to/your/external-media/script.js"></script> <script type="optin" data-type="text/javascript" data-category="marketing">console.log("Inline scripts are also working!");</script> The type has to be "optin" to get recognized by PrivacyWire, the data-attributes are giving hints, how the script shall be loaded, if the data-category is within the cookie consents of the user. These scripts are loaded asynchronously after the user made the decision.
      If you want to give the users the possibility to change their consent, you can use the following Textformatter:
      [[privacywire-choose-cookies]] It's planned to add also other Textformatters to opt-out of specific cookie groups or delete the whole consent cookie.
      You can also add a custom link to output the banner again with a link / button with following class:
      <a href="#" class="privacywire-show-options">Show Cookie Options</a> <button class="privacywire-show-options">Show Cookie Options</button> This module is still in development, but we already use it on several production websites.
      You find it here: https://github.com/blaueQuelle/privacywire/tree/master
      Download: https://github.com/blaueQuelle/privacywire/archive/master.zip
      I would love to hear your feedback 🙂
      Edit: Updated URLs to master tree of git repo
       
    • By David Karich
      Admin Page Tree Multiple Sorting
      ClassName: ProcessPageListMultipleSorting
      Extend the ordinary sort of children of a template in the admin page tree with multiple properties. For each template, you can define your own rule. Write each template (template-name) in a row, followed by a colon and then the additional field names for sorting.
      Example: All children of the template "blog" to be sorted in descending order according to the date of creation, then descending by modification date, and then by title. Type:
      blog: -created, -modified, title  Installation
      Copy the files for this module to /site/modules/ProcessPageListMultipleSorting/ In admin: Modules > Check for new modules. Install Module "Admin Page Tree Multible Sorting". Alternative in ProcessWire 2.4+
      Login to ProcessWire backend and go to Modules Click tab "New" and enter Module Class Name: "ProcessPageListMultipleSorting" Click "Download and Install"   Compatibility   I have currently tested the module only under PW 2.6+, but think that it works on older versions too. Maybe someone can give a feedback.     Download   PW-Repo: http://modules.processwire.com/modules/process-page-list-multiple-sorting/ GitHub: https://github.com/FlipZoomMedia/Processwire-ProcessPageListMultipleSorting     I hope someone can use the module. Have fun and best regards, David
    • 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 (has been tested up to v3.3), add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "https://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.


×
×
  • Create New...