Jump to content
interrobang

ImageFocusArea

Recommended Posts

How stable is this with the current dev (2.6.22). 

Share this post


Link to post
Share on other sites

New bug?

If the image field is loaded via Ajax then the click of the focus-link will be redirected to the homepage instead of opening the image in modal frame.

For explaination:

I have an image focus area field inside a fieldset. I have decided to show the content of the fieldset only if i click on the fieldset and the content will be shown afterwards via Ajax. In PW you can choose under the fieldset setting tab when to show the content (open, open only if there is content inside,...).

If I choose to show the content via Ajax the image focus area field doesnt allow to set a focus area. After clicking the link I will be always redirected to the homepage.

If I change the fieldset status to something without Ajax (fe always open) the image focus area field work as expected.

Maybe this could be a bug if other users have the same problem.

Best regards

Share this post


Link to post
Share on other sites

Sorry, I have not tested this module in any recent version, but I recommend using the dev version in the thumbnails branch, some minor issues might be fixed there: https://github.com/phlppschrr/ImageFocusArea/tree/thumbnails

I have not looked into these new ajax features. Does anybody know of any thread here how to support ajax editing and loading for your own fields?

Please continue to report any issues and improvement ideas here (or even better at github). 

PS: Sorry, for being a bad module maintainer. I still have some plans with this module, but not enough time - too much customer work and a newborn baby at home.

  • Like 2

Share this post


Link to post
Share on other sites

and a newborn baby at home.

Congrats! (and take all the time you can get for beeing with the baby) :)

Share this post


Link to post
Share on other sites

Hi again.

In case anyone is wondering... this module doesn't currently work with the new image field upgrade in 3.0.17  :-(

As Ryan points out here https://processwire.com/blog/posts/major-images-field-upgrade

Note that other modules that extend the old images field (like those that provide additional crop functions) may not work with the new one. If that turns out to be the case, we'll likely move the old images field to a 3rd party module so that it can continue to be used for these cases.

Many thanks

Nik

  • Like 2

Share this post


Link to post
Share on other sites

Hi,

i had the problem today as Nik, when i tried to upgrade an old 2.6 installation to PW3.

Would be really great if this module could be upgraded to work with the new Imagefield.

Thanks!

Share this post


Link to post
Share on other sites

Hi Interrobang - hope you are well

Have you had any thoughts on how this module might become usable in PW 3.x?

I'm trying to work out a way forward for sites reliant on this module, and it would be useful to know if there is any prospect of future development, so I can make an informed decision.

Kind regards

Nik

Share this post


Link to post
Share on other sites

Hi Nik,

thanks, I am well :) Honestly I have not used my module myself for a long time, and I still have not looked into what has to be done to migrate this module to PW3 and its new image field. I plan to release a new version eventually, but can't say how long it will take. But seeing somebody still uses it at least motivates me to test it myself in PW3.

Sorry, that I cant give you a more satisfying answer. I will post back here after testing.

 

Share this post


Link to post
Share on other sites

Thanks Interrobang.  Your module was mentioned in the thread for Horsts Croppable image module.  Using the focus of an image would be my preferred method for retaining flexibility, but I guess I'm in a minority.

Regards

Nik

Share this post


Link to post
Share on other sites
On 10/10/2016 at 2:56 PM, NikNak said:

Using the focus of an image would be my preferred method for retaining flexibility, but I guess I'm in a minority.

i'm still voting for a solid and core solution of image cropping. using either an exact crop, or predefined ratios, or using a focus area and make it possible to get the right image for the right spot on your template/design and allowing different ratios!

but i guess we 2 are in a minority... 😉

  • Like 5

Share this post


Link to post
Share on other sites

Hi Bernhard

I don't think many people could have seen how useful this approach is. 

Fingers crossed for the future.

 

  • Like 2

Share this post


Link to post
Share on other sites

+1

Until the change in PW3 image module it was my prefered solution for image cropping. Just let the user define the important part of the image and do the cropping in the templates. 

One solution for this would be the approach Ryan mentioned https://processwire.com/blog/posts/major-images-field-upgrade

Quote

If that turns out to be the case, we'll likely move the old images field to a 3rd party module so that it can continue to be used for these cases.

 

But i think it would be way nicer, if we had the ImageFocusArea function and all the the new features of the new image field.

Share this post


Link to post
Share on other sites

I am really missing this module in version 3, are we any closer to an update?

I am having to make do with Croppable Image 3, but the crop settings require both width and height values, not allowing either to be flexible.

  • Like 3

Share this post


Link to post
Share on other sites

Without this module, I am now struggling to find a way to get an image cropped to a particular ratio, that retains the full resolution of the original image. ie - have a cropped image that is as good as it can be at a particular ratio. From that master, i would then make variants. 

Using CropableImage3 this is not possible - as all defined crops are pixel based rather than ratio based - and not dependent on the original size image. This therefore restricts the flexibility of generating a subsequent scaling of the image from the best master possible.

Horst's suggestion of uploading a large image to start with and cropping it to the right proportion at high res and then scaling, is impractical in day to day situations for my use, as you can't always impose that kind of restriction on your client's images. 

I had hoped that if I turned upscaling off, then perhaps I would be able to set a very large crop setting, and the cropping would just be made as large as possible. 

Anybody managed to find alternatives to the conundrum this has left, if you want to retain maximum flexibility in the automated scalings of your images. ?

Cheers

Nik

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
      --- Please use RockFinder3 ---
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory (pending approval) If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
    • By Craig
      I've been using Fathom Analytics for a while now and on a growing number of sites, so thought it was about time there was a PW module for it.
      WayFathomAnalytics
      WayFathomAnalytics is a group of modules which will allow you to view your Fathom Analytics dashboard in the PW admin panel and (optionally) automatically add and configure the tracking code on front-end pages.
      Links
      GitHub Readme & documentation Download Zip Modules directory Module settings screenshot What is Fathom Analytics?
      Fathom Analytics is a simple, privacy-focused website analytics tool for bloggers and businesses.

      Stop scrolling through pages of reports and collecting gobs of personal data about your visitors, both of which you probably don't need. Fathom is a simple and private website analytics platform that lets you focus on what's important: your business.
      Privacy focused Fast-loading dashboards, all data is on a single screen Easy to get what you need, no training required Unlimited email reports Private or public dashboard sharing Cookie notices not required (it doesn't use cookies or collect personal data) Displays: top content, top referrers, top goals and more
    • By daniels
      This is a lightweight alternative to other newsletter & newsletter-subscription modules.
      You can find the Module in the Modules directory and on Github
      It can subscribe, update, unsubscribe & delete a user in a list in Mailchimp with MailChimp API 3.0. It does not provide any forms or validation, so you can feel free to use your own. To protect your users, it does not save any user data in logs or sends them to an admin.
      This module fits your needs if you...
      ...use Mailchimp as your newsletter / email-automation tool ...want to let users subscribe to your newsletter on your website ...want to use your own form, validation and messages (with or without the wire forms) ...don't want any personal user data saved in any way in your ProcessWire environment (cf. EU data regulation terms) ...like to subscribe, update, unsubscribe or delete users to/from different lists ...like the Mailchimp UI for creating / sending / reviewing email campaigns *I have only tested it with PHP 7.x so far, so use on owners risk
      EDIT:
      Since 0.0.4, instructions and changelog can be found in the README only. You can find it here  🙂
      If you have questions or like to contribute, just post a reply or create an issue or pr on github, thanks!
    • By MoritzLost
      Sorry for the convoluted title. I have a problem with Process modules that define a custom page using the page key through getModuleInfo (as demonstrated in this excellent tutorial by @bernhard). Those pages are created automatically when the module is installed. The problem is that the title of the page only gets set in the current language. That's not a problem if the current language (language of the superuser who is installing the module) is the default language; if it isn't, the Process page is missing a title in the default language. This has the very awkward effect that a user using the backend in the default language (or any other language) will see an empty entry in the setup menu:

      This screenshot comes from my Cache Control module which includes a Process page. Now I realize the description sounds obscure, but for us it's a common setup: We a multiple bilingual sites where the default language is German and the second language is English. While the clients use the CMS in German, as a developer I prefer the English interface, so whenever I install a Process module I get this problem.
      As a module author, is there a way to handle this situation? I guess it would be possible to use post-installation hooks or create the pages manually, but I very much prefer the declarative approach. The page title is already translatable (through the __ function), but of course at the time of installation there is no translation, and as far as I'm aware it's not possible to ship translations with a module so they are used automatically. Could this situation be handled better in the core? I would prefer if the module installation process would always set the title of the Process page in the default language, instead of the language of the current user.
×
×
  • Create New...