Jump to content
apeisa

Release: Thumbnails

Recommended Posts

I wonder about change configuration to the JSON format.

In this way, we could provide more options for the site administrator. But the configuration becomes more difficult :/


[
  {
     "name": "my new thumb",
     "template": [ "basic-page", "home" ],
     "aspectRatio": 1,
     "minSize": [100,100],
     "maxSize": [  200,200 ]
  },
  {
     "name": "small thumb",
     "aspectRatio": null
  },
  {
     "name": "thumbnail2",
     "width": 100,
     "height": 200
  }
]

What do you think about this?

Share this post


Link to post
Share on other sites

I do like the idea of Min and max size as it is currently possible to create a small crop that is actually enlarged on the site.

I'll have a think about config later and see if I can come up with a suggestion.

Share this post


Link to post
Share on other sites

I do like the idea of Min and max size as it is currently possible to create a small crop that is actually enlarged on the site.

This is something else.

jCrop Documentation

jCrop allows you to specify the dimensions of graphics that you cut.

You can allow for example 100x200px MIN or 100x500px MAX for images in siebar. This way you can cut the picture of a different height but fixed width 100px.

Share this post


Link to post
Share on other sites

Back when I played with it a few years ago, you could set the crop box to be the actual crop size (so if you uploaded a 1600x1280 image and your image is to be cropped to 320x200, it can give you a starting box that size that you can't make any smaller, but could make bigger proportionally - that's what I was talking about (although I suspect you already worked that out ;)).

If accidentally uploading images that are smaller than the crop the crop box could just scale down so it uses up as much of the image as possible or something.

Just an idea - it all works fine as it is and I'm looking forward to playing with the per-field settings later today/tomorrow :) Just out of interest, to the per-field settings work in the new per-template settings that ryan introduced recently for things like naming the same field differently for different templates? Being able to have just one "images" field and set the settings for that field in the many templates I use it in would be awesome :)

Share this post


Link to post
Share on other sites

If accidentally uploading images that are smaller than the crop the crop box could just scale down so it uses up as much of the image as possible or something.

I think we should have "Min Image Dimensions" as we have "Max ImageDimensions". You should get a message that the image is too small.

Just an idea - it all works fine as it is and I'm looking forward to playing with the per-field settings later today/tomorrow :) Just out of interest, to the per-field settings work in the new per-template settings that ryan introduced recently for things like naming the same field differently for different templates? Being able to have just one "images" field and set the settings for that field in the many templates I use it in would be awesome :)

I looked at these new features and I do not think it was possible for now.

I do not know how to add a field to be visible in chosen context. Maybe Ryan knows how :].

But you can do this right now in this way:

thumbnail,200,200,basic-page,home
big_thumbnail,500,500,other_template_name
medium_thumbnail,300,300,post_template

Share this post


Link to post
Share on other sites

I wonder about change configuration to the JSON format.

In this way, we could provide more options for the site administrator. But the configuration becomes more difficult :/

Well, if we keep adding options, then JSON is soon much easier than current method :)

Also, if we ever build nicer UI, then JSON is much easier to have at backend than our current method. Also we might think about using YAML, since that is pretty nice to look at and write, but not sure. Seems simpler to go with JSON.

PS: Thanks for the pull request. I will test and merge it soon.

Share this post


Link to post
Share on other sites

Also, if we ever build nicer UI, then JSON is much easier to have at backend than our current method. Also we might think about using YAML, since that is pretty nice to look at and write, but not sure.

I would totally go with YAML Parsing here :) There is also a neon, which looks like some sort of 'YAML' with few fixes. Are you interested in YAML? I'm thinking about creating a module, which would some more advanced configuration (I'll talk about it more later, when at least readme would be done:) ), So I'm thinking we could do module named e.g. 'CodeYAML', which would add support for YAML parsing (so you would not have to parse it manually in code or distribute it, you'd have only one dependency). What do you think?

Share this post


Link to post
Share on other sites

Also we might think about using YAML, since that is pretty nice to look at and write, but not sure.

Hi,

A thought on YAML: whilst it is a very nice format (I use it for test fixtures) please be aware that it is whitespace intolerant as it uses leading indentation/spacing to delimit structures a bit like Python or HAML do. You need to configure your editor carefully to preserve existing leading space if you are to work with YAML files. If it is just you going to be editing these then that might not be a problem, but once users of your system start editing them you could be in for some extra support work if they don't configure their editors well.

I've used a single file library called spyc before and found it very effective at meeting my YAML processing needs.

Share this post


Link to post
Share on other sites

A thought on YAML: whilst it is a very nice format (I use it for test fixtures) please be aware that it is whitespace intolerant as it uses leading indentation/spacing to delimit structures a bit like Python or HAML do.

It also doesn't support tabs, AFAIK - that's why I mentioned neon (if you like YAML, neon seems the way to go):

NEON is very similar to YAML.The main difference is that the NEON supports "entities" (so can be used e.g. to parse phpDoc annotations) and tab characters for indentation. NEON syntax is a little simpler and the parsing is faster.

Share this post


Link to post
Share on other sites

Hi Adam,

Sorry, I totally blanked on your initial reply to apeisa so I missed your link to Neon. I'll check it out.

Ok, took a look and you're right. Neon looks more flexible regarding leading tabs / spaces but lacks a lot of YAMLs more complex features -- which may well be fine for this application -- and it gives you good error reports. However, I think my general point may still hold true if people who aren't familiar with the leading whitespace requirements end up editing those files, and especially if the parser errors are not exposed fully to the user.

Edited by netcarver

Share this post


Link to post
Share on other sites
Just out of interest, to the per-field settings work in the new per-template settings that ryan introduced recently for things like naming the same field differently for different templates?

With the new field-template context, you can name it differently with labels and descriptions. But changing the actual 'name' of a field is something you can't do. Though even if we could, I think I might find that a bit confusing. :)

Being able to have just one "images" field and set the settings for that field in the many templates I use it in would be awesome

Being able to change the other field settings (beyond label, description, columnWidth, visibility) is actually supported in the core, but I've got the system blocking it right now because I'm worried about side effects here. I figured we'd open this up in advanced mode soon, and then roll it out for everything once we're sure it's not creating major new issues or complexity. But it made my mind hurt just thinking about all the possibilities it could open up (good and bad). So decided to make field-template context contain only known variables to start, and then jump into the rest after marinating a bit. :)

Share this post


Link to post
Share on other sites

Before adding any more features (:P) can someone have a test with thumbnails in repeater fields? I doesn't seem to work, as the opening page to make the thumbnails isn't showing any image (just empty) but the layout is there. Previously I even had at some point showing an error that the page can't resolve. I think I posted this issue already elsewhere but can't remember as I thought it was here. :)

Share this post


Link to post
Share on other sites

Haven't played with repeater yet, but will test this right after when I found time.

Share this post


Link to post
Share on other sites

Thanks apeisa, I'm currently again testing with repeaters and there seems an issue with cropimages (not sure if images suffer the same) when I add a new repeater element on page with an cropimage field and upload an image, after saving the page the added element dissapears. Though after adding an element again there's still the image uploaded before (already reported issue on repeater thread, but think not solved yet). But after saving the page again then, it stays there and when clicking the "thumbnail" link a new window opens with this error:

Fatal error: Call to a member function get() on a non-object in /Applications/XAMPP/xamppfiles/htdocs/pw-dev/site/modules/Thumbnails/ProcessCropImage/ProcessCropImage.module on line 50

Share this post


Link to post
Share on other sites

Thanks Soma. Can you post the link href that produces that error?

Share this post


Link to post
Share on other sites

Thanks. I understand the problem now. That link will turn into this selector later on:

$img = wire('pages')->get(1002)->images_repeater1122->get("p1000242.jpg");

Problem is, that the page 1002 doesn't have the field images_repeater1122, but the underlying repeater page has that. Not sure what would be the best fix, but it doesn't feel like very difficult to solve.

Share this post


Link to post
Share on other sites

PawelGIX: I merged your pull request. It works great.

Others: updating is little "nasty", since you need to put your thumb-config to the field settings. Not sure how this is best done in live site.

Share this post


Link to post
Share on other sites

Maybe you should put my update to the dev branch. I work on it to make the upgrade painless.

Share this post


Link to post
Share on other sites

I noticed when adding a new page with 15 images yesterday that it creates thumbnails for each crop config as soon as the page is saved. In my case I have 3 different crops so I ended up with 6mb of images for one page.

Shouldn't it be making thumbnails when requested by the templates on page view rather than trying to make all options for a page? This seems a bit wrong to me as some of the crops will only be used by one image in my case.

Also, does it do any tidying up after itself if you change a crop size in the config? I don't think it does, but I realise it might be hard to add this as well.

Share this post


Link to post
Share on other sites

It doesn't yet any cleaning up, even if you delete the images on page or even the field the images stay there. Only if you delete the page itself, they will get deleted.

Share this post


Link to post
Share on other sites

Hi! First of all, thank you for this wonderful module.

I am, however, experiencing some difficulties on using it properly. I experience the same issue some users reported back in the thread but while I've tried to apply the fix, it even got worse. So, here's what happening:

post-550-0-95596500-1337956047_thumb.png

Anyone has any clue on what may be going wrong?

Thank you!

Share this post


Link to post
Share on other sites

Have you created an image field and then set the inputfield (on field input settings tab) to "cropimage"? Or changed an already setup image field to use cropimage inputfield? If so, it won't work, you have to create a field using fieldtype "cropimage" from the start. I recently ran into this problem.

Share this post


Link to post
Share on other sites

Is there any way for this to be integrated with the TinyMCE image chooser? In other words an option in the image choosing screen to choose a 'thumbnail' instead of the main image and have all the thumbnail features in the page?

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
      TrelloWire
      This is a module that allows you to automatically create Trello cards for ProcessWire pages and update them when the pages are updated. This allows you to setup connected workflows. Card properties and change handling behaviour can be customized through the extensive module configuration. Every action the module performs is hookable, so you can modify when and how cards are created as much as you need to. The module also contains an API-component that makes it easy to make requests to the Trello API and build your own connected ProcessWire-Trello workflows.
      Features
      All the things the module can do for you without any custom code: Create a new card on Trello whenever a page is added or published (you can select applicable templates). Configure the target board, target list, name and description for new cards. Add default labels and checklists to the card. Update the card whenever the page is updated (optional). When the status of the card changes (published / unpublished, hidden / unhidden, trashed / restored or deleted), move the card to a different list or archive or delete it (configurable). You can extend this through hooks in many ways: Modifiy when and how cards are created. Modify the card properties (Target board & list, title, description, et c.) before they are sent to Trello. Create your own workflows by utilizing an API helper class with many convenient utility methods to access the Trello API directly. Feedback & Future Plans
      Let me know what you think! In particular:
      If you find any bugs report them here or on Github, I'll try to fix them. This module was born out of a use-case for a client project where we manage new form submissions through Trello. I'm not sure how many use-cases there are for this module. If you do use it, tell me about it! The Trello API is pretty extensive, I'll try to add some more helper methods to the TrelloWireApi class (let me know if you need anything in particular). I'll think about how the module can support different workflows that include Twig – talk to me if you have a use-case! Next steps could be a dashboard to manage pages that are connected to a Trello card, or a new section in the settings tab to manage the Trello connection. But it depends on whether there is any interest in this 🙂 Links
      Repository on Github Complete module documentation (getting started, configuration & API documentation) [Module directory pending approval] Module configuration

    • By MoritzLost
      Process Cache Control
      This module 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) Clear the ProCache page render cache (if your site is using ProCache) 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.
      Plans for improvements
      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 CHANGELOG in the repository Screenshots


    • By Macrura
      PrevNextTabs Module
      Github: https://github.com/outflux3/PrevNextTabs
      Processwire helper modules for adding page navigation within the editor.
      Overview
      This is a very simple module that adds Previous and Next links inline with the tabs on the page editor. Hovering over the tab shows the title of the previous or next page (using the admin's built in jqueryUI tooltips.)
      Usage
      This module is typically used during development where you or your editors need to traverse through pages for the purpose of proofing, flagging and/or commenting. Rather than returning to the page tree or lister, they can navigate with these links.
      Warnings
      If you are using PW version 2.6.1 or later, the system will prevent you from leaving the page if you have unsaved edits.
      For earlier versions, to avoid accidentally losing changes made to a page that might occur if a user accidentally clicks on one of these, make sure to have the Form Save Reminder module installed.
      http://modules.processwire.com/modules/prev-next-tabs/
    • 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-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 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 Multi currency support Custom order and cart fields 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 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 ----
       
×
×
  • Create New...