Jump to content
apeisa

Release: Thumbnails

Recommended Posts

I did run some local test, and I absolutely love it now! :)

apeisa & smd, thanks for the awesome module.

I think I will definately use it in a future projects, and in my moms gallery website now. Wohooh! ;)

---

Just tested again to see if thumbs get deleted, and they don't (after deleting image on page). What's the current state regarding this?

Share this post


Link to post
Share on other sites

Thanks Soma for kind words. I also like how this turned out, very nice to use.

Just tested again to see if thumbs get deleted, and they don't (after deleting image on page). What's the current state regarding this?

This is on the "not essential, but definitely nice to have - will be done in next version". There is no promise or schedule for next version. Might be next week or next year. Depends on my needs (or someone else's needs).

Share this post


Link to post
Share on other sites

I'm not sure if this is a bug or it's something else I've done, but I can't seem to remove an image description. I can alter the text but not completely delete it.

Regards

Martin

Share this post


Link to post
Share on other sites
I'm not sure if this is a bug or it's something else I've done, but I can't seem to remove an image description. I can alter the text but not completely delete it.

This actually is a bug, but not todo with this module.

My Boss experienced it a few days ago, and I forgot to report... :)

You can only delete it if you put a space char inside the textfield.

Share this post


Link to post
Share on other sites

Thanks Martin and Soma. Yep, it seems to be a minor bug in InputfieldImage or FieldtypeImage. When that bug is fixed there CropImages will get fix also, since these are inherit from those classes.

Share this post


Link to post
Share on other sites

I wasn't aware of this, just added to issues list.

Thanks,

Ryan

Share this post


Link to post
Share on other sites

Antti - just wanted to say I've (finally) just started using this module and it's amazing! Great work! :)

The only suggestion I have is that it would be nice to have a way to make the configurations for thumbnails somehow able to link to certain templates, for example if I want a specific thumbnail size for news article images then I'm unlikely to want that thumbnail option anywhere other than when I'm creating a news article.

I know, it's not straightforward, but rather than make it too technical, I thought maybe this could still be specified in the same place, but add extra parameters on the end if you want it only available to specific templates:

thumbnail,100,100
portrait,100,150
largethumb,200,200
newsthumb,250,180,news_home,news_article

In the above example, the first three thumb settings would be available to all cropimage fields, and the newsthumb would only be available to the news_home and news_article templates.

Something like that anyway, and it's just a thought (although it might be worth somehow being able to specify fields as well as templates?).

Share this post


Link to post
Share on other sites

I have had the exactly same thought when using this and I will probably implement that when first client project comes which requires this.

Or actually I was thinking about making it work with specific fields, but that template option seems to be even better. Thanks for the suggestion!

Share this post


Link to post
Share on other sites

No problem :)

My first thought was making it something you can set per-template in the template settings, but that sounded too difficult and you would have to write some code when editing a template to check it has a cropimage field and then have a setting just for that. It also seemed too detached from the field itself.

My second thought was to define it per cropimage field as it would be a bit more intuitive editing it there, but I don't like creating duplicates of the Images field just for things like this where you'll only ever define different settings once or twice in a website's lifetime I think.

Which brings us back to the module configuration itself - seems to be the most sensible place and certainly the easier option to code!

Share this post


Link to post
Share on other sites

Just a question.

How about making it possible to insert cropped images in tinymce too? Would it be possible?

Share this post


Link to post
Share on other sites

Antti, thanks for such great module! I've used it a couple of times and it's a great time-saver!! I've just found a strange error and I can't tell what's wrong. I have a laptop and a desktop both running Mac Os and MAMP (for a localhost environment). Recently I've exported my working PW site from the desktop to the laptop (via a mysql dump). Both machines are running the same files (via dropbox) and now have the same data in each of the local databases.

In my laptop local site I get the following error (debug on):

Fatal error: Exception: Fieldtype 'FieldtypeCropImage' does not exist (in /Users/......./....../....../wire/core/Field.php line 200) #0

The log shows the following:

: Unknown User:/?/:ProcessWire Error:Exception: Fieldtype 'FieldtypeCropImage' does not exist (in /Users/..../...../wire/core/Field.php line 200)  #0

.... and it goes on

The desktop machine keeps running the site just fine. Am I missing something here?

Share this post


Link to post
Share on other sites

For me it seems like your install doesn't know about cropImages. Please try clicking check for new modules and removing modules cache. I am pretty sure problems are in how you have transferred the site? Do you have any other 3rd party modules installed?

Share this post


Link to post
Share on other sites

It seems that way. The problem is that the site is blocked by the error (white screen with error message) this is the only module installed (3rd party) is there a way to uninstall the module like this? So then I can install it again.

Share this post


Link to post
Share on other sites

Try removing files from /site/assets/cache/ There are modules.*.cache files that are safe to remove. Not sure if this helps...

Share this post


Link to post
Share on other sites

Yes! that was it! Now I know that I have to clear the cache when migrating! :-[ thanks a lot!

Share this post


Link to post
Share on other sites

Hey Antti - I just tried creating a CropImage field on the latest version of PW (2.2) and while the field shows up, the "Crop Setups" section (under the field where you can preview and define the crop area for the image) does not show up. Basically, it looks like a standard image field on the edit page.

I tried the following code in my template anyway:

echo $page->my_photo->eq(0)->getThumb('thumbnail');

And I get the following error:

Error Exception: Method Pageimage::eq does not exist or is not callable in this context

Any ideas? Anyone else had the same problem with this module in the latest version of PW?

Share this post


Link to post
Share on other sites

I've just encountered the same thing.

It displays as a normal image field as you say and I get none of the crop links for my configured crops next to the images.

Share this post


Link to post
Share on other sites

Fixed it. This just needs tidying up and putting into the source, but if you open InputfieldCropImage module and find the relevant function below and replace it with the code below:

protected function renderItem($pagefile, $id, $n) {

       $out = parent::renderItem($pagefile, $id, $n);

       $crops = $this->modules->get('ProcessCropImage')->crops;
       if (strlen($crops)>3) {
           $cropUrl = "../image-crop/";
           $cropStr = "\n\t\t\t<div class='ui-widget-content crops'><p class='description'>Thumbnails (hover to preview, click to crop)</p>". $this->_getCropLinks($crops, $cropUrl, $pagefile) . "</div>";
       }

       // We add our crop string at the end of the list item that holds image
       $out .= $cropStr;//str_ireplace('</li>', $cropStr, $out);

       return $out;
   }

Share this post


Link to post
Share on other sites

Hey Antti (and others) - I went ahead and made it so that the module can now accept comma-separated lists of templates per thumbnail config.

For example, in the module config, enter a new crop setup called bigthumb like this:

bigthumb,320,240,home,search

The two extra parameters on the end are templates that this is applicable to. You can keep adding templates to the list to your hearts' content, and in this case it won't show you a thumbnail option for the images field on the basic-page template since you narrowed it to a specific list.

If you want the thubmnail to be available to all templates, simply don't add any more parameters after the first three :)

The code, oddly enough, is in the same function as my last post, so change that entire function in InputCropImage.module to the following:

	protected function renderItem($pagefile, $id, $n) {

	$out = parent::renderItem($pagefile, $id, $n);

	$crops = $this->modules->get('ProcessCropImage')->crops;
	if (strlen($crops)>3) {
		// If we've defined one or more templates for specific crops, we need to check the current page's template to see if we actually have any applicable crops to show to the user
		$page = $this->pages->get($this->input->get->id);
		$applicableCrops = array();
		$cropArray = explode("\n", $crops);
		foreach ($cropArray as $k => $v) {
			$cropItems = explode(',', $v);
			if (count($cropItems) > 3) {
				if (in_array($page->template, array_slice($cropItems, 3))) {
					$applicableCrops[] = $cropArray[$k];
				}
			} else { // Any non-template-specific crops are automatically added to the list for all cropimage fields
				$applicableCrops[] = $cropArray[$k];
			}
		}
		$applicableCrops = implode("\n", $applicableCrops);

		if (!empty($applicableCrops)) {
			$cropLinks = $this->_getCropLinks($crops, $cropUrl, $pagefile);
			if (!empty($cropLinks)) {
				$cropUrl = "../image-crop/";
				$cropStr = "\n\t\t\t<div class='ui-widget-content crops'><p class='description'>Thumbnails (hover to preview, click to crop)</p>". $this->_getCropLinks($applicableCrops, $cropUrl, $pagefile) . "</div>";
				// We add our crop string at the end of the list item that holds image
				$out .= $cropStr;
			}
		}
	}

	return $out;
}

If no crops are applicable to a particular template, it simply doesn't render the thumbnails box below each image.

  • Like 1

Share this post


Link to post
Share on other sites

Ryan did send me an email and warned that there might be problems with Thumbnails module on latest build. Haven't had the time yet to see what is needed to fix it, but it seems that Pete have done the hard work and more.

Pete: if possible can you send me an pull request in Github? This way you get proper mention on your contribution.

Share this post


Link to post
Share on other sites

Happy to help :)

I'll do it tomorrow when I'm back at my computer (and can figure out GitHub again - I don't use it often enough to remember how it works ;)).

Share this post


Link to post
Share on other sites

You rock, Pete! Thanks for the fix and for adding functionality to allow for crops for specific templates. Totally handy! :)

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 Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory (alpha version only available via GitHub) SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By d'Hinnisdaël
      Happy new year, everybody 🥬
      I've been sitting on this Dashboard module I made for a client and finally came around to cleaning it up and releasing it to the wider public. This is how it looks.
      ProcessWire Dashboard

      If anyone is interested in trying this out, please go ahead! I'd love to get some feedback on it. If this proves useful and survives some real-world testing, I'll add this to the module directory.
      Download
      You can find the latest release on Github.
      Documentation
      Check out the documentation to get started. This is where you'll find information about included panel types and configuration options.
      Custom Panels
      My goal was to make it really simple to create custom panels. The easiest way to do that is to use the panel type template and have it render a file in your templates folder. This might be enough for 80% of all use cases. For anything more complex (FormBuilder submissions? Comments? Live chat?), you can add new panel types by creating modules that extend the DashboardPanel base class. Check out the documentation on custom panels or take a look at the HelloWorld panel to get started. I'm happy to merge any user-created modules into the main repo if they might be useful to more than a few people.
       Disclaimer
      This is a pre-release version. Please treat it as such — don't install it on production sites. Just making sure 🍇
      Roadmap
      These are the things I'm looking to implement myself at some point. The wishlist is a lot longer, but those are the 80/20 items that I probably won't regret spending time on.
      Improve documentation & add examples ⚙️ Panel types Google Analytics ⚙️ Add new page  🔥 Drafts 🔥 At a glance / Page counter 404s  Layout options Render multiple tabs per panel panel groups with heading and spacing between ✅ panel wrappers as grid item (e.g. stacked notices) ✅ Admin themes support AdminThemeReno and AdminThemeDefault ✅ Shortcuts panel add a table layout with icon, title & summary ✅ Chart panel add default styles for common chart types ✅ load chart data from JS file (currently passed as PHP array) Collection panel support image columns ✅ add buttons: view all & add new ✅
    • By Robin S
      This module is inspired by and similar to the Template Stubs module. The author of that module has not been active in the PW community for several years now and parts of the code for that module didn't make sense to me, so I decided to create my own module. Auto Template Stubs has only been tested with PhpStorm because that is the IDE that I use.
      Auto Template Stubs
      Automatically creates stub files for templates when fields or fieldgroups are saved.
      Stub files are useful if you are using an IDE (e.g. PhpStorm) that provides code assistance - the stub files let the IDE know what fields exist in each template and what data type each field returns. Depending on your IDE's features you get benefits such as code completion for field names as you type, type inference, inspection, documentation, etc.
      Installation
      Install the Auto Template Stubs module.
      Configuration
      You can change the class name prefix setting in the module config if you like. It's good to use a class name prefix because it reduces the chance that the class name will clash with an existing class name.
      The directory path used to store the stub files is configurable.
      There is a checkbox to manually trigger the regeneration of all stub files if needed.
      Usage
      Add a line near the top of each of your template files to tell your IDE what stub class name to associate with the $page variable within the template file. For example, with the default class name prefix you would add the following line at the top of the home.php template file:
      /** @var tpl_home $page */ Now enjoy code completion, etc, in your IDE.

      Adding data types for non-core Fieldtype modules
      The module includes the data types returned by all the core Fieldtype modules. If you want to add data types returned by one or more non-core Fieldtype modules then you can hook the AutoTemplateStubs::getReturnTypes() method. For example, in /site/ready.php:
      // Add data types for some non-core Fieldtype modules $wire->addHookAfter('AutoTemplateStubs::getReturnTypes', function(HookEvent $event) { $extra_types = [ 'FieldtypeDecimal' => 'string', 'FieldtypeLeafletMapMarker' => 'LeafletMapMarker', 'FieldtypeRepeaterMatrix' => 'RepeaterMatrixPageArray', 'FieldtypeTable' => 'TableRows', ]; $event->return = $event->return + $extra_types; }); Credits
      Inspired by and much credit to the Template Stubs module by mindplay.dk.
       
      https://github.com/Toutouwai/AutoTemplateStubs
      https://modules.processwire.com/modules/auto-template-stubs/
    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.60
      Composer: rockett/jumplinks
      ⚠️ NOTICE: 1.5.60 is an important security patch-release for an XSS vulnerability discovered by @phlp. It's HIGHLY RECOMMENDED that all Jumplinks users update to the latest version as soon as possible.
      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 Robin S
      Add Image URLs
      Allows images/files to be added to Image/File fields by pasting URLs.

      Usage
      Install the Add Image URLs module.
      A "Paste URLs" button will be added to all image and file fields. Use the button to show a textarea where URLs may be pasted, one per line. Images/files are added when the page is saved.
       
      https://github.com/Toutouwai/AddImageUrls
      https://modules.processwire.com/modules/add-image-urls/
×
×
  • Create New...