adrian

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.

Hey @szabesz - I have fixed the issue with the page specific settings not being populated to the CSV export interface (new version now available), but I can't reproduce the problem you are having with an empty CSV file. Make sure you do a hard reload of the page to ensure the update JS file in this module isn't being cached. If that doesn't help, we'll try again I am not sure I understand this - are you wanting a way to filter which pages will be exported? I guess I could add an InputfieldSelector field to the export options to limit the child pages that are exported to the match selector. Is that what you are looking for?

Thanks for figuring that all out! I have just committed a new version which supports a new option for choosing "hidden" or "all" for the child pages to be exported. I have also fixed the missing fields (when child pages are hidden/unpublished). And, I have also fixed the export button in the Reno admin theme. Please let me know if it works ok at your end now.

Hey @szabesz - I just did a check of everything here and I can't reproduce any of these issues (although #3 is probably a Reno specific thing which I'll check in a minute). Could you perhaps help me debug - firstly the missing child page template fields - those are collected here: https://github.com/adrianbj/BatchChildEditor/blob/fe93376a2846df53eba4b102bc5d5ba89f52e09f/BatchChildEditor.module#L938-L943 It would be great if you could add: bd($allFields); at line #944 and check the names of each of the contained fields in the array or let me know if this is empty for some reason. Once we figure this out, we'll get onto why the CSV might be empty.

You should know that this site brings my late 2011 Macbook Pro to its knees. I really love the story you are telling and it's definitely a great way to show clients how working with you would be a great experience, but I would also be worried that if your site crashes a potential clients machine, it might not give the best impression. Also, a 4MB payload for your homepage is pretty steep for someone on a slow connection. SpeedTest shows my download at 163 Mbps and it still takes 9-10 seconds to load your homepage. Please don't take offense at this, because I really do like the message and the way the story is presented, although I could do without the sound effects

Actually just found an easy solution for these, eg: replace: Shortcuts to templates and fields(SuperUser only) with: Shortcuts to templates and fields (SuperUser only) Note that it has to be a   - an ordinary space won't work.

@tpr - nice job on the AddNewChildFirst functionality - very cool! A couple of minor things: 1) This sentence needs the "of" added: "Add new page as first child instead of last" 2) There are several locations where the PW file compiler is causing problems in your text, eg: This is due to this bug: https://github.com/processwire/processwire-issues/issues/98 I have come across this in my own modules and I just end up re-wording things to avoid parentheses near PW variable names, but of course it would be great if this could be fixed properly, but I don't think it's high on Ryan's priorities.

My apologies - yes, I see that those vendor libs are also PHP 5.4+ (https://github.com/lesaff/ProcessWire-Sassify/blob/edbbc4dad1a2a38e64a084638cf69aa9c663abe4/vendor/leafo/scssphp/scss.inc.php#L3) I might really be time for PW to dump support for 5.3. Just looking around, Drupal stopped supporting it 3 years ago!

If I understand the needs correctly, I think this is a perfect use case for WtireCache (https://processwire.com/blog/posts/processwire-core-updates-2.5.28/#wirecache-upgrades). I use this to store the results of a complex set of selector queries that serve JSON to an AngularJS app.

If you can't upgrade your PHP version you could simply replace: public static function getModuleInfo() { return [ 'title' => "Sassify", 'version' => "0.0.5", 'summary' => "Compile SASS/SCSS/Compass and use it in your project.", 'author' => "Rudy Affandi", 'href' => "https://github.com/lesaff/ProcessWire-Sassify", 'icon' => "css3", // use autoload if module is to be called each load, if it is only needed to setup something set to false 'autoload' => true, 'singular' => true, 'page' => [ 'name' => 'sassify', 'parent' => 'setup', 'title' => 'Sassify Settings', ], 'requires' => "ProcessWire>=2.5", ]; } with: public static function getModuleInfo() { return array( 'title' => "Sassify", 'version' => "0.0.5", 'summary' => "Compile SASS/SCSS/Compass and use it in your project.", 'author' => "Rudy Affandi", 'href' => "https://github.com/lesaff/ProcessWire-Sassify", 'icon' => "css3", // use autoload if module is to be called each load, if it is only needed to setup something set to false 'autoload' => true, 'singular' => true, 'page' => array( 'name' => 'sassify', 'parent' => 'setup', 'title' => 'Sassify Settings', ), 'requires' => "ProcessWire>=2.5", ); } Note that PW only requires PHP 5.3.8, so in general modules should be written to use the syntax supported by that version.

I've just pushed a new version of the Create Users Batcher which adds proper CSV parsing (so you can have commas, quotes, spaces etc in other user fields) - thanks to @Rudy for noting this deficiency. I have also added the option to use JSON instead of CSV in case that is easier for your needs. Creation now also supports image fields so you can use a URL to an image to have that added to the user's page.

@hellomoto - sorry you are having trouble. I honestly don't understand what you are seeing there. It doesn't seem like an error message. How/where is this appearing? Could you maybe send a screenshot of it? What version of ProcessWire and PHP are you running?

Glad you got it working that way. As for the approach you are using - honestly not sure - I haven't worked with PayPal for a few years, so I am probably out of date on the latest practices, but at the time IPN was the way to go, but maybe now there is a better approach to verifying a payment as being legit and not a spoofed POST to your form.

More improvements to the Captain Hook panel which I think now makes it the definitive source for browsing and understanding what each hook does. You have always been able to click the line number to open the file to the line of the method in your code editor (if you have things set up correctly), but this new version adds the following two new features: 1) Inline documentation for each hook - click method (last column) to expand/collapse the docs: 2) Direct link to PW API reference (from the Class::method link in the first column), eg clicking on "Pages::saved" will take you directly to this page:

It sounds to me like things are being lost in the redirect to Paypal and back. Paypal should return most things back to you so you can grab them again. What I do is create and populate a PW page with the user's details, submit them to Paypal for payment, and then on return I can look up the user by an ID that I assign to them (stored in their page and also sent to Paypal). With that I can update their page with the payment details (verification of payment, etc). This of course does result in some entries which weren't finalized - sometimes people choose to back out at the last minute, but at least you have more info on this. Also, getting OT here, but are you making use of Paypal's IPN system (https://github.com/paypal/ipn-code-samples/blob/master/php/PaypalIPN.php) to verify payment?

I am not sure how you are getting from the page that sets the $_SESSION into PW. Are you using a header redirect from one to the other? Maybe you could bootstrap PW in the non PW page that collects the $_POST data. Then you could make use of $session in that non PW page. Maybe you could use a cookie instead?

Not sure why that isn't working, but the PW API has it's own $session variable: https://processwire.com/api/ref/session/ at you can use.