adrian

Yes, you will need to create it. Basically any code in that file will be run when ProcessWire is "ready". You can read more about it here: https://processwire.com/blog/posts/processwire-2.6.7-core-updates-and-more/#new-core-files-for-site-hooks

Sorry for the delay - I got sidetracked. You can fix this easily with a little hook magic. Place this in your /site/ready.php file: $this->addHookAfter("InputfieldRepeater::renderRepeaterLabel", function($event) { $return = $event->return; $event->return = str_replace('#', '', $return); });

Sorry, ignore the stupidity in my last post - I did #1 instead of #n I'll look into it and get back to you in a minute

It works for me. Is that what you are looking for?

Have you checked the console's Network tab - of course make sure this is open before you upload the images, and start by clearing any existing items to make it easier to see - sorry if this is obvious to you already. Do you have PW's debug mode turned on? Also, installing Tracy Debugger might show some otherwise missed errors.

Is it always 2 images that work? Do you maybe have Max files set to 2 for the image field? eg:

My guess is that it's Apache's mod_security module blocking those filenames. What happens if you upload 5 images with other filenames?

Storing form/quiz/survey data in PW pages is great idea. I would even use the fields from the template that stores the data as the way to build the form that users will access on the frontend. After each question has been answered, add that answer to the appropriate field on the page and then reload with the next field/question. Obviously you could delete the page when you get to the end of the process, but honestly I would keep them - why not keep the data - you never know when you might find it useful As far as naming pages, I would go with the ID of the new page as the name and title.

Yeah, it's a bug in the file compiler: https://github.com/processwire/processwire-issues/issues/98 As a workaround, replace the space with a &nbsp;, eg: <label for=pass2>New Password&nbsp;(Confirm)</label>

$image = $page->images->get("name=myimage.jpg"); $image->width();

Sorry

Yep - another Captain Hook update. Often hookable methods for a class are derived from a parent class. Take the "Roles" class for example. It lists add, delete, & save as the hookable methods that are available. But because it extends the "PagesType" class, its hookable methods are also available from the "Roles" class, eg: Roles::deleted. To make these derived methods easier to find, I have added a new: ClassName extends ParentClassName line to each file section. Both names are also linked directly to the API docs so you can find out more info there as well.

@benbyf Have you installed this module from @horst - http://modules.processwire.com/modules/image-animated-gif/

Thanks @flydev and @kongondo Github issue posted: https://github.com/processwire/processwire-issues/issues/360

Hi @noelboss - you might want to consider the issue of triggering a login attempt when there is no user for the entered email address:

I am convinced I must be tired and that is why I can't get several of them to work, but would someone else mind testing please. In my testing: These work Roles::deleteReady Roles::deleted Roles::saveReady Roles::saved but these don't work Roles::add Roles::delete Roles::save Roles::added Except for Roles::added, all the ones that work are hooks that work are those derived from the PagesType class, so I thought maybe that was the reason, but this one screws up that idea. Anyone see the same problem and have any ideas why those other ones don't work? Thanks!

I would love to see your mockup of a GUI for it. No promises though I'm afraid - there is a LOT going on in Edit mode and I am not really sure how that would fit in with Lister, but if it looks doable and others here sound interested, I'd be willing to give it a go.

Another small update for Captain Hook. Now if you have Ryan's ProcessWire API Explorer module installed, the Class::method link will take you to the appropriate page of the API Explorer interface, rather than to the processwire.com API docs page. This means it will work offline, and of course also means it will be updated to the version of PW running on your site.

Have you played around with "Lister" mode - maybe that would suit your needs already, rather than me adding a selector to "Edit" mode. I know the Lister mode isn't perfect, but it's pretty useful in the way it lets you define and adjust columns to show and the inline edit mode (if you have Lister Pro installed). Anyway, just an idea.

I could easily add it as a config setting on each individual configurable page, but I am guessing that this is something you would want to change potentially each time you visit the children tab - this might make for some complex ajax/js, but I'll take a look. The settings I save from the parent configurable page (both Pages to Include and Fields to Export) are working fine where when I go to export they are pre-selected. Are they saving on the page's settings when reloaded and just not appearing in the BCE interface on the children tab, or are they not saving at all? Any chance I get access this site online somewhere?

Not suggesting to trust it, just using it to give you a quick idea of what happens with various characters. Depending on how you are doing things regarding the password, you might find these useful for automatic password generation and emailing the user with their username and temporary password: http://modules.processwire.com/modules/email-new-user/ http://modules.processwire.com/modules/password-force-change/

Usernames are also sanitized in real time via JS - try adding an uppercase letter or a $ or @ and they will be converted/removed as soon as you unfocus the field. I agree that when adding a user or normal page (both are effectively the same) it should note that periods are allowed. OT a little - if you are adding users by a batch import, be sure to check out the Create Users Batcher action in the AdminActions module.

@Neeks - could you please post this as an issue on Github so that Ryan will definitely see it?

I decided to go ahead to do this so now you can specify exactly which pages will be exported. Hopefully others will find this useful also:

@chrisbourn - welcome to the ProcessWire forums. I am not sure if you meant to post here as it doesn't appear that your site is actually built with ProcessWire. Please correct me if I'm wrong, but perhaps you'd do better on the prettyphoto forums.