horst

updated to version 0.1.3 fixed a bug with ignoring outputFormat when send as $options with method pimLoad found by @titanium added support for php versions with buggy GD-lib for sharpening and unsharpMask added support for the coming module PageimageNamingScheme into pimVariations()

Ok, your first post is wrong, because the second and third param is processed by the function. But you are right with the post regarding outputFormat. The options passed as 2 or 3 param gets processsed but not assigned to $outputFormat if it is a key in options, and unfortunately $outputFormat overrides $options['outputFormat'] at the end of the function. It is in the todo now. But as a quick workaround for you, you may completly bypass sending the $options together with pimLoad(). Insteed use it this way: pimLoad('prefix'[, true | false])->setOptions($options)-> ... ->pimSave(); This works as expected. (I will rewrite the pimLoad to use this internally the same way) Sorry for the inconvenience.

titanium, please can you provide the code line for that with pimLoad? At line 13 there is only comments. Also without need to test, param 2 definitely work, because I often use it to force recreation of a variations. So you cannot be right with this. Your post regarding outputFormat, have you tested this or do you see this just by reading the code?

I cannot tell what threads or posts I best like, it would end up in a list greater than 20 or more. But I can share a little trick I use to quickly find some of them via google: site:processwire.com/talk (one or more names of users that took part of the conversation) AND ("wordphrase that was in a post there, at best a long one", but need to exact!) OR (a very individual word, if there was any) OR (common keywords) So when I need to know how to setup an apache server for best caching / compression I search for buttock (top, not buttock!) with or without willyc: search->buttock Yesterday gebeer needs to know from where a page->render() function was called. My remembered keyword was "caller", and I know that it isn't talked very often about that: search->caller A search for younger + foxes do result in a single thread, where as the terms old + foxes is a little bit more common

Wow, good find! The ratio is stored as extended info for the image and not used further, so a very good find. (and a very stupid bug, info[2] holds the mimetype ) I will fix this with the next update.

I like to work with spex! (yet another approach) The actual version also makes usage of AIOM already.

Hi gebeer, don't know if it is what you are looking for: https://processwire.com/talk/topic/3660-what-page-was-the-caller-of-render/ If you get the page, you can ask for its template. So no direct solution here, but a solution.

You never know for sure. (Maybe in 10 or 20 years, - or later?) Nice! If you are ready with it, you can post it under showcases and / or add an entry in the sites directory.

just ignore the buggy php version for the moment. Replace the ImageSizer.php from your current local pw installation, (you find it under wire/core/), with the attached one and PW will work fine and do no harm to your images. After that, you need to read on under the link others have provided here already. This is essential for you! BTW: My personal opinion is, that the default settings in site/config.php for $config->imageSizerOptions are very well set for the rest of the world, but not for photographers or photography sites. I leave the default settings unchanged for all other sites, but for photography sites I use: $config->imageSizerOptions = array( 'upscaling' => false, // upscale if necessary to reach target size? 'cropping' => false, // crop if necessary to reach target size? 'autoRotation' => true, // automatically correct orientation? 'sharpening' => 'soft', // sharpening: none | soft | medium | strong 'quality' => 94, // quality: 1-100 where higher is better but bigger ); And than in the templates have to pass an individual options array to size() if I need cropped images. PS: on your site under about you are showing a really nice collection of toys On the third tripod from left, is it a Bronica? With films I have used 4x5 and 13x18 cm large formats or 6x6 all the times. Now mostly using a phaseone digital back together with large format arcaswiss or adapted to a modified Bronica SQAi.

Hey PhotoWebMax, here are some photography sites build with pw: http://processwire.com/about/sites/categories/photography/ According to some points here in the posts it sounds to me that it would be the best way for you to upload your photoshop images in the size you want to show them in your gallery. This way you can call the original images and resizing isn't needed. The other thing is, if you use Thumbnails module together with PageImage Manipulator, you have visual control over the quality and sharpening of the thumbnails.

We need to know the path to convert (or ImageMagick) and on some hosts you can choose from different versions like: Pfad zu ImageMagick 4.2.9: /usr/bin/ImageMagick_4.2.9/ (für Typo3) Pfad zu ImageMagick 5.5.4: /usr/bin/ Pfad zu ImageMagick 6.2.6: /usr/bin/ImageMagick_6.2.6/bin/ In this case here, we would test 5.5.4, but Imagick is bound to 6.2.6. Weird, even if we would compare the version from information got through Imagick and the exec call, I don't like to poke around that way. Showing a cmyk without conversion and showing it after trying to convert. Looks good? - YES : NO If 'NO', we can add a short explanation on how to get more information through exec.

But now we know why icc conversion is not working on your server. We can ask the user to run a simple test during module installation that he should answer with yes or no. Trying to convert a cmyk to sRGB or something. If it looks better after conversion, lcms seems to be available.

@Martijn: no, thats confusing. With this option I want to keep all variations, but want to recreate only this single image.

@Adrian: I remember you can use the exec() method on your server. You may check if you have the lcms library used by ImageMagick. To check this you may run the code snippet below and look under cofigure -> delegates if it is listed, and in the delegates output if it is bound to something what isn't the default. [15] => DELEGATES bzlib freetype jpeg jp2 lcms png tiff x11 xml wmf zlib Also it would be good if we can get this information via Imagick extension or something else, if exec() is unavailable. Do you have an idea? <?php $path2convert = '/usr/bin/'; $cmds = array( 'convert -list configure', 'convert -list delegate', //'convert -list format' ); function runExec($cmd) { global $path2convert; exec("{$path2convert}$cmd 2>&1", $out, $result); if(0!=$result) { echo "Returncode: " .$result ."<br>"; echo "<pre>"; print_r($out); "</pre>"; } else { echo "<pre>\n"; print_r($out); "\n\n</pre>"; } } foreach($cmds as $cmd) runExec($cmd);

@Pete: we are on the same side (in german: "Du rennst bei mir offene Türen ein") +1 for implementing cc, bcc and attachment into the WireMail base class! Regarding attachments: https://processwire.com/talk/topic/5704-module-wiremailsmtp/#entry56631

Hi, I have experimented with naming of images. For people who want try out different settings with images, the current naming scheme isn't of good usage. I have added some code to the Pageimage::size method, Pageimage::isVariation, and to the Imagesizer to make it work like here: http://images.pw.nogajski.de/new-naming-convention/ It is open for discussion --- Additional to that I like to implement a new temporary option on a per image base to force recreation of the requested image also if a cached version is available. I don't like to use all the time $image->removeVariations(). What is a useful option name for that? forcenew recreate forcecreate forcerecreate ...? $options = array( 'cropping' => true, 'quality' => 80, 'forcenew' => true ); $img = $image->size(120, 160, $options); --- And for the naming convention I am unsure if a short custom appendix should be enabled too, or if this would be to much? $customappendix: a-z0-9 strlen max 10 ?

I think Ryans initial intention was to support the common basic usage and give us an easy to use possibilty to cretae submodules that can _extend_ the base class. But I am definitly not against extending the base class with cc, bcc and attachment

@Pete: you can ask Teppo directly. He (technically *) can implement it in SwiftMailer without any change in WIreMail base class. I have done it for bcc and cc. It is not more than to add these two as public functions to the SwiftMailer module and make them handle the according SwiftMailer calls for that headers. Simple! * don't know about his time budget nor if he ever want it

Glad you have found it Could you mark the thread as solved / answerded? There must be a button for you as thread author in the lower right, near [MultiQuote]

Have send a pull request that solve it for cropped and uncropped variants: https://github.com/horst-n/ProcessWire/commit/2876bf6568e1bcc1efdee5e1f926f9f618493a52 But there is a need for more naming conventions: https://processwire.com/talk/topic/6028-regenerate-images/

Adrian, the usage of all RGB files are good. To upload and use cmyk for web display is not what is used in real life. We test it here to see how it works in general. But the grayscales are not handled too. Also this may not a problem if you are the one that uploads images to that server. You should prepare your images all the same (gamma 1.8 or 2.2), not mixing different versions. That way you can work with the 6.6.7 without problems. You can have a look to the other tests, especially to sharpening with Imagick. It is very fast compared to GD! Also resizing without sharpening is not that blurry like with GD. But best of all: we can sharpen transparent PNGs with it! You can run it on your installation too, these test and images are also included.

Thanks Adrian, but the cmyk and grayscales don't look as expected, also not with the new tests. Maybe the ImageMagick version 6.6.7 is to old. Lets collect some more infos during the next two weeks, hopefully. @all: Hey, download it and send us a test result

I have updated the Siteprofile ZIP: look in the first post You now first must install the Imagick Resizer module. Also it is more robust and check if you have installed Imagick on your server also on the frontpage when trying to read the version numbers. @Adrian: I have added new/changed tests for icc-cms. Now the usage of ICC-files is reflected in the search result for every single image! Please drop the old profile and run the new one from scratch. (remember first to edit the includes in config.php) Read the slightly new instructions in the first post here in this thread.

Hi Pravin, unfortunately I don't know how the upload via ckEditor works. We need to wait for someone to come in here with more knowledge about that. But due to the fact that only portrait oriented images are effected, I guess that there is something used related to the width of the images only for displaying them. How do the CSS for the images look like? Can you provide an online link to a testpage?

You can simply use a textfield for an URL and also you do not need to use the WireUpload if you finally want to use the image(s) within an pw images field. For that you simply can use $page->images->add('URL_from_text'); But remember to not use $input->post->your-text-field without first validating it. You need to make sure you only got an URL!