horst

No, it means: you cannot upload the same image to different imagefields on the same page! You can upload the same image to different pages because each page has its own subfolder under site/assets/files/.

@Martijn: I have tested it with PW 2.5.19 from this afternoon (14:00). I cannot replicate all of what you have reported. WHen I take a basename.png and use your code example from above I get the right output: // original => variation basename.png => pim_bright_basename.jpg // URL /site/assets/files/1/pim_bright_basename.jpg BUT it recreates it everytime new, also if I set the second param to false: $options = array('outputFormat' => 'jpg'); // Call PIM $pim = $image->pimLoad("bright", FALSE)->setOptions($options)->contrast(100)->brightness(100)->pimSave(); This is a bug or inconveniance by design, but If you call it this way it works as expected, without recreating it everytime: $options = array('outputFormat' => 'jpg'); // Call PIM $pim = $image->pimLoad("bright", FALSE, $options)->contrast(100)->brightness(100)->pimSave();

Hey Bea, this is so cool! You have released it! The Blog Post is nice too.

There were changes from Ryan to the core image field with the commits to PW 2.5.18. I need to look to this but am not able before tommorow evening. @adrian: have put it on my todo. @martijn: regarding your PM, I try to add this within the init method from InputfieldCroppableImage.

I have downloaded 2.5.18 already an hour ago or so. So, cool to be able now to read everything here what is new! Thanks Ryan.

Have updated Pia to 0.2.2 because she also was affected by the same issue as CroppableImage. Recent PW versions now (can) log modules API actions into logfile modules.txt. This is suppressed now. If you use Pia and a recent PW dev version, please update to 0.2.2. http://modules.processwire.com/modules/pageimage-assistant/

This one is fixed now: The PW $config with recent dev versions now contains or can contain a variable logs: /*** 9. MISC ************************************************************************************/ /** * Additional core logs * * All activities from the API functions corresponding with the given log names will be logged. * Options that can be specified are: pages, fields, templates, modules * * @var array * */ $config->logs = array( 'modules', ); Per default it is set to include "modules". I have changed the croppableimage module to suppress loggin if this is enabled. If you use it with a recent dev version please update: https://github.com/horst-n/CroppableImage And I have tested it with PHP 5.3 and it works, so the requirements are updated too.

@Alfred: Now I can confirm that this is a new behave from PW. With PW 2.5.11 I have not have this messages in modules.txt, but after updating to version 2.5.17 I get this too. You said you run PW 2.5.16, so it is something between 2.5.12 and 2.5.16. I remember that there were many changes with the notifier and log functions in PW, so I will post an issue at Github to tell Ryan about it.

@Tyssen: yes, the pixelated ones are cached versions from before you specified upscaling = false. If you want to override them you can use one of the following methods: add a $image->removeVariations() before creating the new ones! Attention: don't forget to remove this once you are ready! since PW 2.5 you also can add 'forceNew' => true to your options array, this forces recreation of the variations every time a page loads! so please be careful and remove it after wards!! you may load Pia, Pageimage Assistant module. She has an option in the modules config page for forceNew that works sitewide if you are in debug mode and logged in as superuser. This way you do not need to alter your template codes and also it does not slow down your page for guest visitors if you forget to disable it.

Yep, FF has this too under developer tools since the last #n? major versions, but I need to click three times until I get this native tool. The other ones I use since FF before version 2 ! and I need to click only once to open it. Therefore I said / thought "something like that". But you are right @Lostkobrakai, - @pwired: you only need to open the network monitor from FFs developer tools and have a look to the response headers of your ogg-page.

@pwired: you need something like Live HTTP headers add on for firefox. It shows you all HTTP headers on a request:

Looks good!

@Alfred: OMG! I will have a look to this very soon. Also I already know where I have to look at first, I believe. I will come back to this ASAP with a result or with further questions. Thank you.

I like this one very much: http://pik.peterkroener.de/?_escaped_fragment_=/presentations/Pik/@1#!/core/welcome.html@1 It has a presenter mode too: http://pik.peterkroener.de/presenter.html#!/presentations/Pik/@1

@mike1: thanks for finding that. I have removed this line with eval() in @joes code example.

Hi Peter, thanks for reporting that. I have looked into that, but it seems it is related to PW core, not croppableimages fields in special, or maybe I have to transform the fieldname to lowercase at some point in the modules code. I have created a new field of type text and given it a capitalized name: My_New_Field The table was created as: field_my_new_field In the fields table it is registered with name = My_New_Field I will further test it with core images field and others and look how it is handled there. So, when creating a new field you can read in the description of the Name* input: But one can enter uppercase letters. Is this intended or should it be sanitized by PW to a-z_0-9 ?

@Martijn: I cannot replicate this. I have no errors in the logs and I have no error outputs. Error display is set to strict all. I'm on PW 2.5.11 Which version of WiremailSMTP do you use? Do you have set a smtp- hostname, user and pass? Or do you have left one / some fields empty?

This is on the ToDo already. But we ("we" == "Martijn" in this case) haven't had time to rebuild the UI of the editor. It is still how it was in Thumbnails just with the two selects for quality and sharpening added.

I know from hosts where it comes to timeouts with around 10 images in 30 seconds. So with your host it seems to be 5 images in 60 seconds, what is super lazy processing.??

That's what google says, but don't know if IIS7 is noted somewhere there. IIS is noted.

You should take out the debug code snippets, now after we have solved that path thingy. How many images are in the pipe for processing? around 10 or more?

AH, it says file does not exist!!! So, we have to use path instead of url, I think. // not ->urls $AlphaImageUser = "{$config->urls->assets}images/authorwmk/swmb-{$username}.png"; // but ->paths $AlphaImageUser = "{$config->paths->assets}images/authorwmk/swmb-{$username}.png";

Oh, so does you have differences between your path and the output from realpath: echo "<pre>" . $AlphaImageUser . "\n"; echo realpath($AlphaImageUser) . "\n"; ?? ..., and what does it say here with this tests: echo "<pre>with realpath:\n"; // test with realpath echo (file_exists(realpath($AlphaImageUser)) ? 'file exists' : 'file do NOT exist!') . "\n; echo (is_readable(realpath($AlphaImageUser)) ? 'is readable' : 'UHM, is NOT readable!') . "\n"; // test without realpath echo "\nwithout realpath:\n"; echo (file_exists($AlphaImageUser) ? 'file exists' : 'file do NOT exist!') . "\n; echo (is_readable($AlphaImageUser) ? 'is readable' : 'UHM, is NOT readable!') . "\n"; echo "</pre>";

Ah, sorry. I'm in hurry. Haven't read thoroughly. So, 24 bit photoshop png should be fine. The error is triggered here: https://github.com/horst-n/PageImageManipulator/blob/master/ImageManipulator.class.php#L1651 It is only triggered when the file isn't existing or isn't readable: https://github.com/horst-n/PageImageManipulator/blob/master/ImageManipulator.class.php#L2437 It has nothing todo with the PNG type at this point here. Are you sure the filename is correct? You can test it in your code here before passing it to the pim: echo "<pre>" . $AlphaImageUser . "\n"; echo realpath($AlphaImageUser) . "\n"; echo (is_readable(realpath($AlphaImageUser)) ? 'is readable' : 'UHM, is NOT readable!') . "\n</pre>";

Hey, I think you simply need to respect the scope here in Line 26: $config->urls->assets ... Try it with: wire("config")->urls->assets $AlphaImageUser = wire("config")->urls->assets . "images/authorwmk/swmb-{$username}.png";