horst Posted October 8, 2016 Author Share Posted October 8, 2016 No this is not intended. The original image never is changed in PW, at least 99%. The original uploaded image never is touched and should be in high quality (best 100%). Also, my opinion, it never should be outputed to the frontend. It is the source or master for all variations needed in a site. To be short, your suggestion can't work at least, as you can specify multiple crop settings, and how should they all be able to update the original image? But you can and should call every defined crop variation by its name everywhere you like it. Also you can call every other variation derived from Pageimage, incl. the original image. Does that make sense for you? 1 Link to comment Share on other sites More sharing options...
DL7 Posted October 8, 2016 Share Posted October 8, 2016 Hi Horst, I totally understand the concept and process. What I dont under however is that after installing the module the first image I cropped the cropped image was visable in the backend under "homepage afbeelding" as being the sole image to be used in the front-end. The cropped overwrote the uploaded image. Of course the orginal image was still available (in the folder structure). No problem, but just wanted to let you know that I had two seperate behaviour using the plugin. I'll try this evening to replicate the first behaviour. 1 Link to comment Share on other sites More sharing options...
Macrura Posted October 8, 2016 Share Posted October 8, 2016 @DL7 no i think you may be confused about the standard cropping built into the core. this module allows you to define various crops and you have to call those by name in the api output code. It does not replace or affect the original image at all. 2 Link to comment Share on other sites More sharing options...
DL7 Posted October 9, 2016 Share Posted October 9, 2016 Hi Cacrura, Perhaps I did the first image indeed via the natice cropped function. My apologies for the confusing. 1 Link to comment Share on other sites More sharing options...
ukyo Posted October 11, 2016 Share Posted October 11, 2016 @horst thanks for your great module. Today i installed your module via module panel by class name and changed my image field with croppableimage field and i setted a size (full-width,1425,434) for this field. After click this size from images field i have below errors on opened modal box, i can see image and preview image. Notice: Undefined property: stdClass::$manualSelectionDisabled in /Users/user/Sites/site-folder/site/modules/CroppableImage3/ProcessCroppableImage3/ProcessCroppableImage3.module on line 47Notice: Undefined property: stdClass::$useImageEngineDefaults in /Users/user/Sites/site-folder/site/modules/CroppableImage3/ProcessCroppableImage3/ProcessCroppableImage3.module on line 48Notice: Undefined property: stdClass::$manualSelectionDisabled in /Users/user/Sites/site-folder/site/modules/CroppableImage3/ProcessCroppableImage3/ProcessCroppableImage3.module on line 120 I am using ProcessWire 3.0.36 version, I made fresh module installation. Link to comment Share on other sites More sharing options...
ukyo Posted October 13, 2016 Share Posted October 13, 2016 @horst also can you check this error : I can't use croppable image 3 module with custom upload names module together. Link to comment Share on other sites More sharing options...
horst Posted October 15, 2016 Author Share Posted October 15, 2016 On 11.10.2016 at 3:50 PM, ukyo said: @horst thanks for your great module. Today i installed your module via module panel by class name and changed my image field with croppableimage field and i setted a size (full-width,1425,434) for this field. After click this size from images field i have below errors on opened modal box, i can see image and preview image. Notice: Undefined property: stdClass::$manualSelectionDisabled in /Users/user/Sites/site-folder/site/modules/CroppableImage3/ProcessCroppableImage3/ProcessCroppableImage3.module on line 47Notice: Undefined property: stdClass::$useImageEngineDefaults in /Users/user/Sites/site-folder/site/modules/CroppableImage3/ProcessCroppableImage3/ProcessCroppableImage3.module on line 48Notice: Undefined property: stdClass::$manualSelectionDisabled in /Users/user/Sites/site-folder/site/modules/CroppableImage3/ProcessCroppableImage3/ProcessCroppableImage3.module on line 120 I am using ProcessWire 3.0.36 version, I made fresh module installation. On a side note: You cannot use - in your names, because - is the devider for suffixes in image variation names. Please change full-width to fullwidth or fullWidth! But back to your issue: I wasn't able to recreate it. What exactly have you done to install it? Passing in the class name here: Admin > Modules [ NEW ] -> ModuleClassName Which classname have you passed? Link to comment Share on other sites More sharing options...
ukyo Posted October 15, 2016 Share Posted October 15, 2016 @horst I used class name from this module page : http://modules.processwire.com/modules/croppable-image3/. Also yesterday i downloaded the module files directly from github repo. I corrected suffix, renamed it "fullwidth" deleted old created files, result not changed (have error). I applied these : if(property_exists($globalOptions, 'manualSelectionDisabled')) if(property_exists($globalOptions, 'useImageEngineDefaults')) to error lines like @adrian advice for my other issue with this module. I don't have error for the moment, but I don't know is this a really solution ? For the moment continue to work just applied quick fixes. 1 Link to comment Share on other sites More sharing options...
horst Posted October 15, 2016 Author Share Posted October 15, 2016 Do you have opened the FieldtypeCroppableImage3 config screen once or never after install? Link to comment Share on other sites More sharing options...
ukyo Posted October 15, 2016 Share Posted October 15, 2016 Yes, after installation I opened FieldtypeCroppableImage3 config screen but didn't make any changes on this screen. Do you offer to disable quality selector ? With this settings i don't have error when i open modal cropper. Link to comment Share on other sites More sharing options...
horst Posted October 15, 2016 Author Share Posted October 15, 2016 Maybe the setting is not relevant, but saving it one time before open the cropper modal? I need to test this. Link to comment Share on other sites More sharing options...
ukyo Posted October 15, 2016 Share Posted October 15, 2016 I unchecked checkbox and saved module settings, tested to open crop modal there is no error. Its look like need to go FieldtypeCroppableImage3 settings and click to save button before use module. 1 Link to comment Share on other sites More sharing options...
hheyne Posted October 17, 2016 Share Posted October 17, 2016 Hi horst, thank you for your work on this modul. Is there a problem when I use it within a repeater? When I define an image-field like this: slider,1280,480,home_final the slider-croping-button don't appear on the page. If I define it without the template it works. 1 Link to comment Share on other sites More sharing options...
horst Posted October 17, 2016 Author Share Posted October 17, 2016 Ah, I think this is a bug, or at least it is not obvious for the user, how to define the template for a repeater. If you define a template, it checks if the current page has this template. I believe "home_final" is the template of the page that contains the repeater? The repeater item itself is a page too, but its template isn't "home_final". As a quick workaround: determine what is the template name of the repeater items and set this, (maybe additionally), into the fields setup. For example, if I have a repeaterfield named topmenu, I will find its items under Admin -> Repeaters -> topemnu -> ..., and their template is repeater_topmenu For the long term, i will see, if this can be done by the module behind the scences. But it will take some time that is currently not available for me. Link to comment Share on other sites More sharing options...
hheyne Posted October 17, 2016 Share Posted October 17, 2016 Hi horst, thank you very much for explaining this. I tried it but it's the same thing. My repeater-field ist named slider_repeater and the corresponding template is also named slider_repeater. Under it there are subpages which are named home like the pagename of the page which contains the slider field. My line is slider,1280,573,slider_repeater,home_final Only if I write it without any of the to template-names the button will be shown on the page home. It doesn't matter if I use only one of the. Only none of them works ;-) In this project it's not critical. But I think this could be something people are desire for. Best Regards Link to comment Share on other sites More sharing options...
horst Posted October 17, 2016 Author Share Posted October 17, 2016 These subpages named home, etc, didn't they have a template called repeater_slider_repeater ? I'm not totally sure, but to a great extend, that the repeater items always have a template name with prefixed repeater_ 2 Link to comment Share on other sites More sharing options...
lenoir Posted October 19, 2016 Share Posted October 19, 2016 Hey there, This module is great. Just wondering, what's the best way to have the user choose which cropping to use in the frontend? The way I understand the README file, the programmed template decides which cropping to use. But what if the user wants a vertical image for an image, and a panorama for another? Thanks for clarifying. PS: Currently working for architects, so I'm glad there are "serious" labels now too ;-) Link to comment Share on other sites More sharing options...
horst Posted October 19, 2016 Author Share Posted October 19, 2016 Hi lenoir, the designer / developer decides which format is displayed at the frontend, as he embedds the API code for the output into the template files. For example, if you define two formats (landscape and portrait), the user has the possibility to select the relevant crop section for both formats, but in a regular / simple setup, the output is defined in the template files with $image->getCrop("portrait")->url at places where a portrait image is required. If you want to give the user the possibility to choose from different formats for one single place, you need a special setup with e.g. pagetable or the ProFields Repeater Matrix wrapped around the image field. Link to comment Share on other sites More sharing options...
lenoir Posted October 19, 2016 Share Posted October 19, 2016 4 minutes ago, horst said: If you want to give the user the possibility to choose from different formats for one single place, you need a special setup with e.g. pagetable or the ProFields Repeater Matrix wrapped around the image field. I was also thinking about a repeater. Pagetable would also make sense I guess. Thanks Horst! I thought there might be a secret weapon I didn't know of Link to comment Share on other sites More sharing options...
hheyne Posted October 19, 2016 Share Posted October 19, 2016 On 17.10.2016 at 6:44 PM, horst said: These subpages named home, etc, didn't they have a template called repeater_slider_repeater ? I'm not totally sure, but to a great extend, that the repeater items always have a template name with prefixed repeater_ Hi Horst, thank you for the hint. Yes with repeater_slider_repeater it works like a charm. 1 Link to comment Share on other sites More sharing options...
horst Posted October 19, 2016 Author Share Posted October 19, 2016 @lenoir Maybe, as a simple way, you also can add a select field near to the croppable image field and let the user select which format he want to be displayed on that page on the frontend. 2 Link to comment Share on other sites More sharing options...
Matcha Posted October 28, 2016 Share Posted October 28, 2016 Hi, I am on ProcessWire version 3.x and just installed this module. It works fine on my superuser account but not on any other roles I have made. When I click on a crop size it brings up the site structure as pictured below instead of the image editing screen. I've also included a screencap of the permissions given to the user. Why it works perfectly fine for my superuser any of my other accounts is doing my head in. Have I overlooked something? Link to comment Share on other sites More sharing options...
horst Posted October 28, 2016 Author Share Posted October 28, 2016 @Matcha The module installs a permission: "croppable-image-3". Have you given that to the roles that should be able to work with it? Link to comment Share on other sites More sharing options...
cappuccino Posted October 29, 2016 Share Posted October 29, 2016 Hi, I'm using PW 3.0.33 and would like to crop some images. If I publish the page I have always this error: Error: Exception: Method Pageimage::getCrop does not exist or is not callable in this context (in ../wire/core/Wire.php line 410) #0 [internal function]: ProcessWire\Wire->___callUnknown('getCrop', Array) #1 ../wire/core/Wire.php(348): call_user_func_array(Array, Array) #2 ../wire/core/WireHooks.php(548): ProcessWire\Wire->_callMethod('___callUnknown', Array) #3 ../wire/core/Wire.php(371): ProcessWire\WireHooks->runHooks(Object(ProcessWire\Pageimage), 'callUnknown', Array) #4../wire/core/Wire.php(372): ProcessWire\Wire->__call('callUnknown', Array) #5 ../wire/core/Wire.php(372): ProcessWire\Pageimage->callUnknown('getCrop', Array) #6../site/templates/home.php(63): ProcessWire\Wire->__call('getCrop', Array) #7 template-file: $bild = $neuigkeit->images->first()->getCrop('news'); $content .= "<figure> <img src='{$bild->url}'> <figcaption>{$bild->description}</figcaption> </figure>"; Does anybody know why i keep on getting this error? Thanks for your help. Link to comment Share on other sites More sharing options...
horst Posted October 29, 2016 Author Share Posted October 29, 2016 The error says, that you finally have no pageimage object in $neuigkeit->images->first() So, at first you need to check / debug what is in $neuigkeit, what is in $neuigkeit->images and if there are images available in the field on the current page. Your field setup looks good! incl. setup for cropsetting. Calling it looks good too, but something in your chain isn't what it should be: $neuigkeiten should be a page (with a template and with fields). Please check this in your code at exactly the point that throws the error: echo "<pre>\n<hr />"; echo "$neuigkeiten->id \n $neuigkeiten->template->name \n"; // if the above is not id == 0 and has a valid template name, go on and check the fields in that page: foreach($neuigkeiten->feilds as $f) { echo "$f->name \n"; // if the images field is in, check if it has images available if('images' == $f->name) { echo " count: " . count($neuigkeiten->images) . "\n"; } } // if all above is ok, at list the ->first() image should be a pageimage, you can check this too $testobj = $neuigkeit->images->first(); if(is_object($testobj)) { echo $testobj->className() . "\n"; } echo "\n<hr /></pre>\n"; Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now