Ovi

The solution is here: https://processwire.com/talk/topic/12375-urgent-will-pay-help-debugging-image-fields/

I love you man! I've been waiting for something like this for soooo long. My clients are going to love this. I found a CSS bug by the way. In PixlrEditor.css you should change: .pixlr-menu-bar{ position: absolute; top: 1em; right: 1em; background: transparent; } to: .pixlr-menu-bar{ position: absolute; top: 1em; right: 1em; background: transparent; z-index:9999; } This prevents the button from being un-clickable because it sits underneath the image thumbnail on the back-end of the page. Great work and thanks again!

Hi Apeisa, I've found a bug. When using a cropimage field inside of a repeater field, the description of the image does not save. The puzzling part is that I think it used to at some point, since I have images with descriptions still there in the install. But now I've run into this problem on any install I try (they are all on the same server and I haven't changed the server config). I tried a fresh install of 2.5.2.8 and 2.5.2.9 (dev), as well as 2.5.3 (master) and it also happens on 2.3.0. The bug happens with even just the default install and the Thumbnails modules installed, nothing else, on a clean install. Debug mode is enabled but shows no errors or warnings. Console is clean. Normal image fields' descriptions still do save, but if I switch them to CropImage they stop working. I can give you access to an account on the server if you can't reproduce the bug for some reason, just let me know. Thanks!

Yes, seriously unfortunately I am working on just such a site right now. It's for a business that has 10 separate locations (pseudo-franchises, which are more or less independent) and they will all need to have their own separate blogs with their own URLs and their own tags, categories and archives. So far I've used a method where all the blogs have different templates in PW which all point to the same template file (which is based on Ryan's blog profile) but I've made the template file dynamic so the names of all the fields are built at run-time based on a naming convention. For example: tags-location1-name, tags-location2-name... etc. instead of just having 1 tags field. And all those suffixes are stored in a special hidden field in the root page of each location. Don't mean to derail this thread, just wanted to point out a situation where more than 1 individual blog is needed and how much work it can take to set up something like that. Again, big thanks for your work, it's going to save me a lot of time on many projects!

Awesome work! Now, what if i needed to have 10 separate blogs like this on the same site?

OMG. Found the error! This needs to be a cautionary tale to others. I had this code in the head section: <?php if ($page->template = "typical-day"): ?> <!-- some files get added here--> <?php endif ?> As you can see there is a "=" sorely missing there (i miss-typed or was just tired, have no clue how it happened). So it ended up changing the template of the page instead of just checking if it was set to "typical day". The "typical-day" template obviously did not even have the "homepage_slideshow" field assigned to it. On the bright side That is something very cool to be able to do (changing the template on run-time), which might have some interesting applications. Is that something one should do or should we stay away from it?

This is driving me nuts. It's such a simple thing, I've done it 100s of times before, but right now it's not working. It's either: an obvious mistake on my part Processwire broke (hope not) I'm trying to do the simplest thing: list the images in an image field, like this: <?php if (count($page->homepage_slideshow)): ?> <ul class="campHpSlideshow"> <?php foreach ($page->homepage_slideshow as $slide): ?> <li><img src="<?= $slide->url ?>" alt="<?= $slide->description?>"></li> <?php endforeach ?> </ul> <!-- /.homepageSlideshow --> <?php else: ?> <img src="http://placehold.it/1024x400&text=no+images" alt=""> <?php endif ?> The count($page->homepage_slideshow) returns false, even though there are images in the field. The field name is spelled correctly. I triple-checked. Also, I could swear this was working before. Any ideas what I can do to fix this? Would re-installing help?

Figured it out finally: Servint bungled things up and installed APC and Eaccelerator together No wonder things got screwy. Thanks for all your help Ryan, you rock.

Yep I'm running on DSO right now, but the issue's still there... Working with Servint support but it's an uphill battle.

Did just that, wiped the wire directory, re-uploaded from a freshly downloaded copy of PW 2.3.0 - still the same behavior. All the sites on that server have this problem. Maybe the switch from suPHP to FastCGI caused this? That was my best guess. So i asked Servint to switch to DSO - which should be what you're using too, Ryan, since you told me in another thread that you're not using FastCGI, and DSO is the only other alternative that allows APC. Still no luck, even with DSO (i of course i changed the attributes of the /site/assets/) folder to 777 to account for PHP running as 'nobody" - but the error still appears after creating an image field. My sites are so much faster with APC though, and i really don't want to go back to suPHP. I even did a fresh install of PW on a new account on the server, and i still get this issue appearing. That's just weird. Maybe there's some obscure stuff in my server config that Servint screwed up...

Hi Ryan and thanks for your help! I cleared the APC cache (even put <?php apc_clear_cache(); ?> in the header of the site, with no conditions, to make sure it clears. The fields did start working once i manually created the missing table, but each time i create a new image field, it get the error again. For some reason the table for that field never gets created, and i get this error when trying to create a new field: Error: Uncaught exception 'WireDatabaseException' with message 'Table 'dap_pw.field_testimage3' doesn't exist' in /home/dap/public_html/wire/core/Database.php:118 Stack trace: #0 /home/dap/public_html/wire/modules/Fieldtype/FieldtypeFile.module(261): Database->query('SHOW COLUMNS FR...') #1 /home/dap/public_html/wire/core/Fieldtype.php(321): FieldtypeFile->getDatabaseSchema(Object(Field)) #2 [internal function]: Fieldtype->___createField(Object(Field)) #3 /home/dap/public_html/wire/core/Wire.php(271): call_user_func_array(Array, Array) #4 /home/dap/public_html/wire/core/Wire.php(229): Wire->runHooks('createField', Array) #5 /home/dap/public_html/wire/core/Fields.php(203): Wire->__call('createField', Array) #6 /home/dap/public_html/wire/core/Fields.php(203): FieldtypeCropImage->createField(Object(Field)) #7 [internal function]: Fields->___save(Object(Field)) #8 /home/dap/public_html/wire/core/Wire.php(271): call_user_func_array(Array, Array) #9 /home/dap/public_html/wire/core/Wire.php(229): Wire->runHooks('save', Arr (line 118 of /home/dap/public_html/wire/core/Database.php) This error message was shown because you are logged in as a Superuser. Error has been logged. So far it only happens with image fields.

What i get is this error message, whenever i create a new image field, on a page with the URL sitename.com/processwire/setup/field/save Error: Uncaught exception 'WireDatabaseException' with message 'Table 'dap_pw.field_testimage' doesn't exist' in /home/dap/public_html/wire/core/Database.php:118 Stack trace: #0 /home/dap/public_html/wire/modules/Fieldtype/FieldtypeFile.module(261): Database->query('SHOW COLUMNS FR...') #1 /home/dap/public_html/wire/core/Fieldtype.php(321): FieldtypeFile->getDatabaseSchema(Object(Field)) #2 [internal function]: Fieldtype->___createField(Object(Field)) #3 /home/dap/public_html/wire/core/Wire.php(271): call_user_func_array(Array, Array) #4 /home/dap/public_html/wire/core/Wire.php(229): Wire->runHooks('createField', Array) #5 /home/dap/public_html/wire/core/Fields.php(203): Wire->__call('createField', Array) #6 /home/dap/public_html/wire/core/Fields.php(203): FieldtypeImage->createField(Object(Field)) #7 [internal function]: Fields->___save(Object(Field)) #8 /home/dap/public_html/wire/core/Wire.php(271): call_user_func_array(Array, Array) #9 /home/dap/public_html/wire/core/Wire.php(229): Wire->runHooks('save', Array) # (line 118 of /home/dap/public_html/wire/core/Database.php) This error message was shown because you are logged in as a Superuser. Error has been logged. However, the field does get created, and i can use it, and i can save any configurations i make, but i can't rename or delete it (i get the same type of database error message). This started happening after asking the Servint support team that manages my VPS to install APC and PDO on my server. Any ideas how these things can be related, or what can i do to fix this? Thanks, Ovi EDIT: Now i'm seeing that when trying to create a new page that uses an image field i get this error: Error: Uncaught exception 'WireDatabaseException' with message 'Table 'dap_pw.field_event_image' doesn't exist' in /home/dap/public_html/wire/core/Database.php:118 Stack trace: #0 /home/dap/public_html/wire/modules/Fieldtype/FieldtypeFile.module(261): Database->query('SHOW COLUMNS FR...') #1 /home/dap/public_html/wire/core/Fieldtype.php(460): FieldtypeFile->getDatabaseSchema(Object(Field)) #2 /home/dap/public_html/wire/core/Fieldtype.php(415): Fieldtype->getLoadQuery(Object(Field), Object(DatabaseQuerySelect)) #3 [internal function]: Fieldtype->___loadPageField(Object(Page), Object(Field)) #4 /home/dap/public_html/wire/core/Wire.php(271): call_user_func_array(Array, Array) #5 /home/dap/public_html/wire/core/Wire.php(229): Wire->runHooks('loadPageField', Array) #6 /home/dap/public_html/wire/core/Page.php(651): Wire->__call('loadPageField', Array) #7 /home/dap/public_html/wire/core/Page.php(651): FieldtypeCropImage->loadPageField(Object(Page), Object(Field)) #8 /home/dap/public_html/wire/core/Page.php(558): Page->getF (line 118 of /home/dap/public_html/wire/core/Database.php) This error message was shown because you are logged in as a Superuser. Error has been logged.

Thanks Ryan, I just realized i was using suPHP as a PHP handler, and so eaccelerator wasn't even working. I did some reading and i just put in a ticket to Servint to switch to FastCGI and install APC. Are you using FastCGI as well?

Hi everyone, I'm currently wondering what would be an optimal configuration to use on a VPS or dedicated server running Processwire. I'm referring to configuring Apache and PHP so that they offer the best environment for running Processwire with best performance while keeping the security as tight as reasonably possible. I hope we can make a guide out of this for people like me who are not server administration veterans and just know how to compile Apache using EasyApache and tweak the PHP settings in WHM. I'll take care of writing out the guide if you guys can supply the info. I'm obviously hoping that the man himself Ryan will pitch in and help out with this. Thanks in advance you awesome people!

It's working! I was missing $page->setOutputFormatting(false); and $page->save(); Working module: <?php class PageAverageRating extends WireData implements Module { public static function getModuleInfo() { return array( 'title' => 'Copy average rating into hidden field', 'version' => 100, 'summary' => 'Copies the average rating to another field', 'singular' => true, 'autoload' => true, ); } public function init() { $this->addHookAfter("CommentFormWithRatings::processRatingInput", $this, 'copyAverageRating'); } public function copyAverageRating() { $page = wire('page'); // get access to the page $page->setOutputFormatting(false); // without this we can't save the page later on // we're interested in product pages only: if($page->template->name != 'product') return; // use the existing averageRating method to get the average rating and store it in the field // we created called average_rating: $page->average_rating = $page->product_comments->averageRating; $page->save(); } } Many thanks Antti, Soma and of course Ryan, you guys rock. This is finally starting to make sense for me. I think i will write a guide to help people like me get started with module development.