Jump to content
apeisa

Release: Thumbnails

Recommended Posts

Sorry, I am lying, it is NOT working.

I have two image fields right next to each other, and I was trying with the wrong one.

So, whatever I try, it is not uploading images - they are just registering as deleted, or something.

Sorry!

Joss

Share this post


Link to post
Share on other sites

And if you reload the page is there the image ort not?

Have you got a empty new line.. I dont know. It is working fine here now. :-/

Share this post


Link to post
Share on other sites

No, reloading just shows an empty field - and nothing in assets. 

So, it is actually not getting uploaded at all.

I am just going to try and create a new field with just the default setting and see what happens.

Share this post


Link to post
Share on other sites

Okay, update.

Created a new field. Save

Left all settings as default.

Added it to template.

It did not work.

===========

Saved new field - leaving the settings as default.

It now works.

Changed settings.

Still works.

Not sure why I cannot get the other field to work, however. Something odd has happened during set up, I suppose, some combination that I have done.

Share this post


Link to post
Share on other sites

A quick note unrelated to the above.

There is an issue with Twitter Bootstrap (and probably other responsive frameworks) that the max width of 100% messes up Jcrop.

However, this can be solved by adding:

#bd img {
  max-width: none !important;
}
 
To somewhere. :)
 
And it is all better again.

Share this post


Link to post
Share on other sites

Downloaded the latest version from Github. Installed it on PW 2.2.14 (2.3) on a fresh installation running with PHP 5.3 - It works so far until I want to edit the crop area. Click on it just opens the new tab saying 

Unrecognized path

Hope you can come up with a working version for PW 2.3. This module is so useful. 

Share this post


Link to post
Share on other sites

It works already. Have you changed an imagr field to a crop image?

Share this post


Link to post
Share on other sites

Yes. Now I have created a new field (named it again images,deleted the old one?) and the error still occurs.

Share this post


Link to post
Share on other sites

Is it insider a repeater or anything you found out? Have you chance to install on different machine that could help further?

Share this post


Link to post
Share on other sites

Nothing. Just the basic-page template with a field called images or "bilder". 

Activating the Debug mode displays the full error:

 

TemplateFile: Unrecognized path

I've first checked the admin.php in the templates folder - it's there.

Older versions of PW with the module are running on the same server without any problems. Could try to install it on the machine here.

EDIT:

Ok, strange but known behaviour:

I've uninstalled everything and installed it again. Now I'm stuck at the upload with the error as Joss.

EDIT 2:

Works now. Just followed the steps Joss described. 

Share this post


Link to post
Share on other sites

A complete aside:

Just working on a blog profile and I am thoroughly enjoying the plugin! So thanks!

Thought I would just say that.

Joss

  • Like 1

Share this post


Link to post
Share on other sites

I'm running into a small issue with the Thumbnails module where a client is uploading an original image which has the exact dimensions of the configured thumbnail size for the CropImage field... It's a case where the client knows the image dimensions used on the website, and tries to upload an original with the right dimensions (even though he doesn't have to) ...but he doesn't know enough to compress it.  

Strangely, the thumbnail is created as normal (I can use it in my templates), but compression is never applied if the dimensions of the original match the thumbnail dimensions.  So we're ending up with a lot of bloated jpegs slowing down the site.

It works fine, of course, if I click the 'thumbnail' link to custom-crop the image (with the jcrop interface), and just select the whole image as the cropping zone. But I don't want the client to have to do that. Better to just drag the file into the field, save the entry, and let ProcessWire work it's magic ;-).

Can I somehow tweak the module to force the compression of images in this case? Any pointers would really be appreciated...

Thanks for your time,

-Brent

Share this post


Link to post
Share on other sites

Hi bcartier,

I think this is currently only possible with a little hack.

I took a look at the source of Thumbnails and if I'm right, you need to uncomment the if on line 91 here:

https://github.com/apeisa/Thumbnails/blob/master/FieldtypeCropImage.module#L91

//if ($this->w != $sizer->getWidth() || $this->h != $sizer->getHeight()) {
  $this->_copyAndResize($img, $imgPath);
//}
  • Like 1

Share this post


Link to post
Share on other sites

Thanks Wanze!

That's really helpful. The ProcessWire community comes through again!  :-)

  • Like 1

Share this post


Link to post
Share on other sites

This would be a nice preference to have on the module settings Antti.

Share this post


Link to post
Share on other sites

This would be a nice preference to have on the module settings Antti.

Maybe. Not sure. I hate settings :)

  • Like 1

Share this post


Link to post
Share on other sites

Bringing Wanze's small change into the module works for me  ;-)

No settings!

Share this post


Link to post
Share on other sites

I have a strange thing happening here.

I ported a PW 229 site with this working plugin from a development server to another server and when I upload a new image it shows just the same image in one size for all the thumbnail versions.

When I click on one image to crop, it shows the extra window and then I can select the crop section allright, I then click on crop and go and get the page that says:

wow that looks great, but no image shows up, when I click on wow that looks great I return to the image and when I now hover over the just cropped image, it shows an empty little hover screen where before it showed the uncropped image, if I then click save article I get the following error:

small_xxxx.jpg is an unsupported image type and then the whole page is not accessible anymore.

When I go into site/assets/files/files/1023 it shows small_xxxx.jpg with a filesize of 0, once I delete that I can access the page again.

When I check the log file it says:

2013-03-02 21:37:55    guest    http://www.xxx.xxx/    Error    Exception: small_xxxx.jpg is not a recogized image (in /xxx/xxx/xxx/xxx.xxx/public_html/wire/core/ImageSizer.php line 92)

I then upgraded to pw 2.2.15, same story.

I also tested on a new site (PW 2.2.15) on this same server and after uploading I went into the site/assets/files/1081 dir and see

featured_3145-xl.jpg     173.068 size

homefeatured_3145-xl.jpg     same 173.068 size

page_3145-xl.jpg  same 173.068 size

reference_3145-xl.jpg  same 173.068 size

So the module does replicate the files upon upload, but does not resize.

And after crop it changes the images size to 0 and prevents the page from showing in the front end AND the backend, I can only access the page in the backend again after deleting the 0 size image

Both sites now on PW 2.3 (=2.2.15?), but I took one site back to 2.2.9 stable and same issue.

Only difference between servers is OS, dev server was ubuntu (I think) new server is FreeBSD.

Share this post


Link to post
Share on other sites

Hi, - sorry, I might not of great help in this, but it maybe that this behave not only target the module but also the ImageSize-core:

you should post or reference in this Topic too:

http://processwire.com/talk/topic/1448-proper-image-type-checking-instead-of-extensions-for-imagesizer/

The new site on the same server is pw 2.2.15 too?

Share this post


Link to post
Share on other sites

Hello Horst,

Thanks for posting in the other thread, yes I think it might have something to do with the resizer, but I am not familiar enough with how it all works under the hood so to speak.

The new site is on 2.2.15 as well, I reverted one to 2.2.9 and that did not make any difference either.

I wonder if anyone can say what dependencies the cropping feature needs for php extensions etc, I am almost inclined to believe it has to do with that.

The plugin itself seems to work partly, as in:

- after upload it makes different named versions of exact the same sized image, no cropping applied whatsoever

- when forced to do a manual crop it ends up making a new 0 sized version of the image, which freezes the page in the back end and the front end.

thanks

Share this post


Link to post
Share on other sites

OK, so I see that ImageSizer.php needs gd2, and on my server phpinfo says:

gd GD Support enabled GD Version bundled (2.0.34 compatible) FreeType Support enabled FreeType Linkage with freetype FreeType Version 2.4.11 GIF Read Support enabled GIF Create Support enabled JPG Support enabled PNG Support enabled WBMP Support enabled XBM Support enabled

So it looks liek I have the extension I need for this to work, yet it does not work, any ideas?

Share this post


Link to post
Share on other sites

One step further...

I uploaded a png file and now the module works as it should, it correctly creates all the right sized images.

So it seems the trouble lies with jpg files.

Any ideas?

Share this post


Link to post
Share on other sites

OK fixed!

I had to reinstall a few things on my server, so it had nothing to do with this plugin.

Just for anybody's information, I am on a freebsd server, using directadmin and had to go to:

/usr/ports/graphics/jpeg and make deinstall, then I had to make reinstall

then I went back into :/usr/local/directadmin/custombuild and run ./build php to rebuild php with all options, I chose to reinstall all options to get php compiled with GD supprt for jpeg

This module is truly awesome!

 

  • Like 1

Share this post


Link to post
Share on other sites

I've upgraded my 2.2.9 site to 2.2.15 and I can't get cropping to work at all - not with any image type. There's been no changes to my server that I know of.

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 picarica
      so i am trying to put CustomHooksForVariations.module, a custom module, i am placing it into site/modules direcotry yet my modules page in admin panel gives me errors
      so this is the screen show when i refresh modules, i dont know why the shole hook is written on top of the page :||

      and this next image is when i try to install it, i saw that it is not defiuned modules.php but it shouldnt need to be ?, any ways i dont want to edit site's core just to make one moulde work there has to be a way

    • By David Karich
      ProcessWire InputfieldRepeaterMatrixDuplicate
      Thanks to the great ProModule "RepeaterMatrix" I have the possibility to create complex repeater items. With it I have created a quite powerful page builder. Many different content modules, with many more possible design options. The RepeaterMatrix module supports the cloning of items, but only within the same page. Now I often have the case that very design-intensive pages and items are created. If you want to use a content module on a different page (e.g. in the same design), you have to rebuild each item manually every time.
      This module extends the commercial ProModule "RepeaterMatrix" by the function to duplicate repeater items from one page to another page. The condition is that the target field is the same matrix field from which the item is duplicated. This module is currently understood as proof of concept. There are a few limitations that need to be considered. The intention of the module is that this functionality is integrated into the core of RepeaterMatrix and does not require an extra module.
      Check out the screencast
      What the module can do
      Duplicate multible repeater items from one page to another No matter how complex the item is Full support for file and image fields Multilingual support Support of Min and Max settings Live synchronization of clipboard between multiple browser tabs. Copy an item and simply switch the browser tab to the target page and you will immediately see the past button Support of multiple RepeaterMatrix fields on one page Configurable which roles and fields are excluded Configurable dialogs for copy and paste Duplicated items are automatically pasted to the end of the target field and set to hidden status so that changes are not directly published Automatic clipboard update when other items are picked Automatically removes old clipboard data if it is not pasted within 6 hours Delete clipboard itself by clicking the selected item again Benefit: unbelievably fast workflow and content replication What the module can't do
      Before an item can be duplicated in its current version, the source page must be saved. This means that if you make changes to an item and copy this, the old saved state will be duplicated Dynamic loading is currently not possible. Means no AJAX. When pasting, the target page is saved completely No support for nested repeater items. Currently only first level items can be duplicated. Means a repeater field in a repeater field cannot be duplicated. Workaround: simply duplicate the parent item Dynamic reloading and adding of repeater items cannot be registered. Several interfaces and events from the core are missing. The initialization occurs only once after the page load event Changelog
      2.0.0
      Feature: Copy multiple items at once! The fundament for copying multiple items was created by @Autofahrn - THX! Feature: Optionally you can disable the copy and/or paste dialog Bug fix: A fix suggestion when additional and normal repeater fields are present was contributed by @joshua - THX! 1.0.4
      Bug fix: Various bug fixes and improvements in live synchronization Bug fix: Items are no longer inserted when the normal save button is clicked. Only when the past button is explicitly clicked Feature: Support of multiple repeater fields in one page Feature: Support of repeater Min/Max settings Feature: Configurable roles and fields Enhancement: Improved clipboard management Enhancement: Documentation improvement Enhancement: Corrected few typos #1 1.0.3
      Feature: Live synchronization Enhancement: Load the module only in the backend Enhancement: Documentation improvement 1.0.2
      Bug fix: Various bug fixes and improvements in JS functions Enhancement: Documentation improvement Enhancement: Corrected few typos 1.0.1
      Bug fix: Various bug fixes and improvements in the duplication process 1.0.0
      Initial release Support this module
      If this module is useful for you, I am very thankful for your small donation: Donate 5,- Euro (via PayPal – or an amount of your choice. Thank you!)
      Download this module (Version 2.0.0)
      > Github: https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate
      > PW module directory: https://modules.processwire.com/modules/inputfield-repeater-matrix-duplicate/
      > Old stable version (1.0.4): https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate/releases/tag/1.0.4
    • By Robin S
      A new module that hasn't had a lot of testing yet. Please do your own testing before deploying on any production website.
      Custom Paths
      Allows any page to have a custom path/URL.
      Note: Custom Paths is incompatible with the core LanguageSupportPageNames module. I have no experience working with LanguageSupportPageNames or multi-language sites in general so I'm not in a position to work out if a fix is possible. If anyone with multi-language experience can contribute a fix it would be much appreciated!
      Screenshot

      Usage
      The module creates a field named custom_path on install. Add the custom_path field to the template of any page you want to set a custom path for. Whatever path is entered into this field determines the path and URL of the page ($page->path and $page->url). Page numbers and URL segments are supported if these are enabled for the template, and previous custom paths are managed by PagePathHistory if that module is installed.
      The custom_path field appears on the Settings tab in Page Edit by default but there is an option in the module configuration to disable this if you want to position the field among the other template fields.
      If the custom_path field is populated for a page it should be a path that is relative to the site root and that starts with a forward slash. The module prevents the same custom path being set for more than one page.
      The custom_path value takes precedence over any ProcessWire path. You can even override the Home page by setting a custom path of "/" for a page.
      It is highly recommended to set access controls on the custom_path field so that only privileged roles can edit it: superuser-only is recommended.
      It is up to the user to set and maintain suitable custom paths for any pages where the module is in use. Make sure your custom paths are compatible with ProcessWire's $config and .htaccess settings, and if you are basing the custom path on the names of parent pages you will probably want to have a strategy for updating custom paths if parent pages are renamed or moved.
      Example hooks to Pages::saveReady
      You might want to use a Pages::saveReady hook to automatically set the custom path for some pages. Below are a couple of examples.
      1. In this example the start of the custom path is fixed but the end of the path will update dynamically according to the name of the page:
      $pages->addHookAfter('saveReady', function(HookEvent $event) { $page = $event->arguments(0); if($page->template == 'my_template') { $page->custom_path = "/some-custom/path-segments/$page->name/"; } }); 2. The Custom Paths module adds a new Page::realPath method/property that can be used to get the "real" ProcessWire path to a page that might have a custom path set. In this example the custom path for news items is derived from the real ProcessWire path but a parent named "news-items" is removed:
      $pages->addHookAfter('saveReady', function(HookEvent $event) { $page = $event->arguments(0); if($page->template == 'news_item') { $page->custom_path = str_replace('/news-items/', '/', $page->realPath); } }); Caveats
      The custom paths will be used automatically for links created in CKEditor fields, but if you have the "link abstraction" option enabled for CKEditor fields (Details > Markup/HTML (Content Type) > HTML Options) then you will see notices from MarkupQA warning you that it is unable to resolve the links.
      Installation
      Install the Custom Paths module.
      Uninstallation
      The custom_path field is not automatically deleted when the module is uninstalled. You can delete it manually if the field is no longer needed.
       
      https://github.com/Toutouwai/CustomPaths
      https://modules.processwire.com/modules/custom-paths/
    • By teppo
      Hey folks!
      I'm happy to finally introduce a project I've been working on for quite a while now: it's called Wireframe, and it is an output framework for ProcessWire.
      Note that I'm posting this in the module development area, maily because this project is still in rather early stage. I've built a couple of sites with it myself, and parts of the codebase have been powering some pretty big and complex sites for many years now, but this should still be considered a soft launch 🙂
      --
      Long story short, Wireframe is a module that provides the "backbone" for building sites (and apps) with ProcessWire using an MVC (or perhaps MVVM... one of those three or four letter acronyms anyway) inspired methodology. You could say that it's an output strategy, but I prefer the term "output framework", since in my mind the word "strategy" means something less tangible. A way of doing things, rather than a tool that actually does things.
      Wireframe (the module) provides a basic implementation for some familiar MVC concepts, such as Controllers and a View layer – the latter of which consists of layouts, partials, and template-specific views. There's no "model" layer, since in this context ProcessWire is the model. As a module Wireframe is actually quite simple – not even nearly the biggest one I've built – but there's still quite a bit of stuff to "get", so I've put together a demo & documentation site for it at https://wireframe-framework.com/.
      In addition to the core module, I'm also working on a couple of site profiles based on it. My current idea is actually to keep the module very light-weight, and implement most of the "opinionated" stuff in site profiles and/or companion modules. For an example MarkupMenu (which I released a while ago) was developed as one of those "companion modules" when I needed a menu module to use on the site profiles.
      Currently there are two public site profiles based on Wireframe:
      site-wireframe-docs is the demo&docs site mentioned above, just with placeholder content replaced with placeholder content. It's not a particularly complex site, but I believe it's still a pretty nice way to dig into the Wireframe module. site-wireframe-boilerplate is a boilerplate (or starter) site profile based on the docs site. This is still very much a work in progress, but essentially I'm trying to build a flexible yet full-featured starter profile you can just grab and start building upon. There will be a proper build process for resources, it will include most of the basic features one tends to need from site to site, etc. --
      Requirements and getting started:
      Wireframe can be installed just like any ProcessWire module. Just clone or download it to your site/modules/ directory and install. It doesn't, though, do a whole lot of stuff on itself – please check out the documentation site for a step-by-step guide on setting up the directory structure, adding the "bootstrap file", etc. You may find it easier to install one of the site profiles mentioned above, but note that this process involves the use of Composer. In the case of the site profiles you can install ProcessWire as usual and download or clone the site profile directory into your setup, but after that you should run "composer install" to get all the dependencies – including the Wireframe module – in place. Hard requirements for Wireframe are ProcessWire 3.0.112 and PHP 7.1+. The codebase is authored with current PHP versions in mind, and while running it on 7.0 may be possible, anything below that definitely won't work. A feature I added just today to the Wireframe module is that in case ProcessWire has write access to your site/templates/ directory, you can use the module settings screen to create the expected directories automatically. Currently that's all, and the module won't – for an example – create Controllers or layouts for you, so you should check out the site profiles for examples on these. (I'm probably going to include some additional helper features in the near future.)
      --
      This project is loosely based on an earlier project called pw-mvc, i.e. the main concepts (such as Controllers and the View layer) are very similar. That being said, Wireframe is a major upgrade in terms of both functionality and architecture: namespaces and autoloader support are now baked in, the codebase requires PHP 7, Controllers are classes extending \Wireframe\Controller (instead of regular "flat" PHP files), implementation based on a module instead of a collection of drop-in files, etc.
      While Wireframe is indeed still in a relatively early stage (0.3.0 was launched today, in case version numbers matter) for the most part I'm happy with the way it works, and likely won't change it too drastically anytime soon – so feel free to give it a try, and if you do, please let me know how it went. I will continue building upon this project, and I am also constantly working on various side projects, such as the site profiles and a few unannounced helper modules.
      I should probably add that while Wireframe is not hard to use, it is more geared towards those interested in "software development" type methodology. With future updates to the module, the site profiles, and the docs I hope to lower the learning curve, but certain level of "developer focus" will remain. Although of course the optimal outcome would be if I could use this project to lure more folks towards that end of the spectrum... 🙂
      --
      Please let me know what you think – and thanks in advance!
    • By tcnet
      PageViewStatistic for ProcessWire is a module to log page visits of the CMS. The records including some basic information like IP-address, browser, operating system, requested page and originate page. Please note that this module doesn't claim to be the best or most accurate.
      Advantages
      One of the biggest advantage is that this module doesn't require any external service like Google Analytics or similar. You don't have to modify your templates either. There is also no JavaScript or image required.
      Disadvantages
      There is only one disadvantage. This module doesn't record visits if the browser loads the page from its browser cache. To prevent the browser from loading the page from its cache, add the following meta tags to the header of your page:
      <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate" /> <meta http-equiv="Pragma" content="no-cache" /> <meta http-equiv="Expires" content="0" /> How to use
      The records can be accessed via the Setup-menu of the CMS backend. The first dropdown control changes the view mode. There are 4 different view modes.
      View mode "Day" shows all visits of the selected day individually with IP-address, browser, operating system, requested page and originate page. Click the update button to see new added records. View mode "Month" shows the total of all visitors per day from the first to the last day of the selected month. View mode "Year" shows the total of all visitors per month from the first to the last month of the selected year. View mode "Total" shows the total of all visitors per year for all recorded years. Please note that multiple visits from the same IP address within the selected period are counted as a single visitor.
      Settings
      You can access the module settings by clicking the Configuration button at the bottom of the records page. The settings page is also available in the menu: Modules->Configure->ProcessPageViewStat.
      IP2Location
      This module uses the IP2Location database from: http://www.ip2location.com. This database is required to obtain the country from the IP address. IP2Location updates this database at the begin of every month. The settings of ProcessPageViewStat offers the ability to automatically download the database monthly. Please note, that automatically download will not work if your webspace doesn't allow allow_url_fopen.
      Dragscroll
      This module uses DragScroll. A JavaScript available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability in view mode "Day" to drag the records horizontally with the mouse pointer.
      parseUserAgentStringClass
      This module uses the PHP class parseUserAgentStringClass available from: http://www.toms-world.org/blog/parseuseragentstring/. This class is required to filter out the browser type and operating system from the server request.
      Special Feature
      PageViewStatistic for ProcessWire can record the time a visitor viewed the page. This feature is deactivated by default. To activate open the module configuration page and activate "Record view time". If activated you will find a new column "S." in the records which means the time of view in seconds. With every page request, a Javascript code is inserted directly after the <body> tag. Every time the visitor switches to another tab or closes the tab, this script reports the number of seconds the tab was visible. The initial page request is recorded only as a hyphen (-).
       
×
×
  • Create New...