Leaderboard

I'm excited to announce that the ProcessWire Form Builder is now available from the DesignIntelligence bookstore: http://store.di.net/...re-form-builder I'm initially giving a 20% discount on the prices there (coupon code PWFB-BETA) because I'm still adding new things to it at a rapid pace, and feel it should still be called "beta test" (and not full price) until it's been out in the wild for a bit. However, a few of us here have been using the Form Builder on production sites for awhile already, and it's working great. But if you don't mind using a pre-release version and giving me feedback or suggestions where appropriate, then there's a nice discount for now (which will expire when we reach version 1.0). If you are wondering what the DesignIntelligence bookstore is, they are one of my long time clients and have agreed to let me provide the Form Builder through there. I actually setup and manage this online store already for them (and have for years), so feel very comfortable putting the Form Builder here. But when we grow big enough, we'll setup our own. When you get Form Builder, you'll also get access to the new Form Builder Support board (in this forum). This is where regular software updates are posted (ZIP files), among other things. So PM me when you do so that I can add you to it. Thanks for your support of ProcessWire and Form Builder!

Current status → [growing a beard, just to be difficult]

Doesn't look like I will get the time for at least a few weeks, but what I had in mind for making an awesome newsletter module for ProcessWire is things like this: Building templates in PW's template system (duh) Being able to reference content from elsewhere on the site (like check out X amazin product/service) - essentially a repeater field for Service Title (if you want to override the page title you're referencing) short description (again, only if you want to override that page's summary), image from that page and then being able to drag and drop that sort of content quickly into any order. And so on It's really exciting when you think about all the possibilities of what you can do just by creating each newsletter content as a normal page and template combination, so I think that any such module should leave that completely separate and just focus on: Subscribes/unsubscribes - a default system to store subscribers as users with a guest and newsletter role (I think it should be this anyway) and make the class so it can easily be extended to add/remove/deal with subscribers any other way someone can think of Sending mail Dealing with bounces (from systems like Mandrill, although if you read the info it deals with a lot of this itself if you forget to remove bad addresses - it just won't send to them again to keep you compliant and will notify you, which is nice) These are the basics and I think it could just be a case of keeping it this basic - everything else is a case of PW pages and templates then, plus a bit of a headache in terms of making all your styles inline once again like back when you didn't know what a stylesheet was For that reason alone, perhaps it should ship with a default page, some fields and a template as an example? It could well be that this is complex enough to warrant another paid module, especially when you start thinking about shipping it with a selection of templates, or considering ways to make it easy to download new templates from within the module (probably a version 2 feature!).

I've been working on an experimental module set that adds 2-factor authentication to ProcessWire with the help of Steve Gibson's PPP one-time-pad system. This is split into two modules; a CryptoPPP library that implements the otp system and a 2-factor authentication module that uses it to add 2-factor authentication to ProcessWire. The 2-factor module adds an additional "Login Token" field to the login page into which the authenticating user will need to enter the next unused token from their one-time-pad. Pages from their pad can either be printed out in advance in a credit-card sized format (with codes being crossed out as they are used as shown here) or the required token can be sent to their registered email address so they don't need to print anything out. This second option requires a good email address be present in the user's account in order for them to be sent the token. Email Delivery To set up email delivery go to the 2-factor module's config page and choose "token delivery via email" and save the settings. Next, make sure that every user who will use the system has a valid email address set up in their account. Upon the first failed user login attempt, the required token will be emailed to the user’s email address and they should then be able to log in. Printing Pages From The Pad If you prefer to print the tokens in a handy credit-card sized format then… Go to your profile screen Expand the “PPP Initialisation Vector” field Hit the “Show Token Cards” button to open a new browser window with the next 3 useful cards Use your browser’s print option to print these out Trim them to size and store ...but make sure you print these out before you enable 2-factor authentication on your account. If you cross out your used codes, you will always know which code to use when logging back in -- and if you forget, the first login attempt will fail and the token field will then prompt you with the location of the correct code to use. Why would I ever want to use 2-factor authentication? If your site is only for you or for people you know use good passwords then you probably never will need a 2-factor authentication system. But it has been shown that many users use passwords that are, well, rubbish not very good and having a second factor can be useful in mitigating poor passwords. As the second factor in this system comes out of a one-time-pad system (meaning it will not be reused) then having the user's password leaked or guessed should not compromise their account nor will having someone spy out the token they are using to log-in as tokens are not re-used (well, not for a very long time.) Known Problems You need to hit the save button after you install the 2-factor module to get it to remember the initial settings. (I guess I'm not setting the defaults correctly at present but pressing the button will allow you to move forward for now) Uninstall of the 2-factor module leads to a lot of warnings. Attachments

I am already sans-beard

Could this be of help: http://processwire.com/talk/topic/648-storing-module-config-using-api/?

Just did my duties, and it took 5 attempts with recaptcha. But once again human was stronger than evil computer.

Hey ho, I wrote a new module: ProcessShortcodes. It brings Wordpress like shortcodes to Processwire. A quick example: <?php $shortcode = $modules->get('MarkupShortcodes'); $shortcode->add('login', function($atts){ return '<form><h3>'.$atts['content'].'</h3><label>Enter password for "'.$atts['name'].'":</label> <input type="pass"></form>'; }); $content = 'Lorem ipsum dolor [login name="user"]Login[/login]'; echo $shortcode->render($content); ?> You can: add a shortcode: $shortcode->add('login', function($atts){ return '<form><h3>'.$atts['content'].'</h3><label>Enter password for "'.$atts['name'].'":</label> <input type="pass"></form>'; }); remove a shortcode: $shortcode->remove('login'); remove all shortcodes: $shortcode->remove_all(); and use them: $shortcode->render('Lorem [ipsum /] hello. [dolor name="nico" /]. Third possibility: [abc def="hij"]a text[/abc]. '); As seen above there are three different possible syntaxes: 1.: [shortcode] or [shortcode /] 2.: [shortcode key="value" /] or [shortcode key="value"] or [shortcode key="value" second="bla" /] 3.: [shortcode]lorem ipsum[/shortcode] or [shortcode key="value"]lorem ipsum[/shortcode] or [shortcode key="value" second="bla"]lorem ipsum[/shortcode] You can download it here: https://github.com/NicoKnoll/MarkupShortcodes I will add it to the module section as soon as possible.

I created a simple module that allows you to log in using your e-mail address rather than username: https://github.com/m...lAuthentication A couple of thoughts: This should be a built-in option in the login module, rather than an add-on - most sites have taught users to log in with their e-mail address. (I tend to forget what my username is - on most sites I don't have one!) The Session and ProcessLogin APIs need to be more extensible - for instance, to allow modifications to the form or fields. Modules like "login via Twitter" etc. will soon be something that people demand. I wish the build...form() methods in PW were more generally open to hooks...

Took me quite some time to find a good solution to this issue, but I think I found one. Just updated module to 0.0.9. 1. It works now, and works much better with "Disable sub-folder for default language" option. 2. Improved some code also with the "Enable multi-langauge domains." setting, which also was suffering similar issue. It might be obvious but these two module options can't be used together. Also added notes in admin to be aware.

Haha, I took it to right. After 15 minutes I thought that I might have better things to do That is pretty amazing though.

Sorry Soma, but It was a cache thing!! Disregard my last post. I'll try to mold some page titles to see if the plugin works for me.

Offtopic: Landitus, just to notice that the correct translation from "Atención al cliente" from ES to PT would be "Atendimento ao cliente" and not "Atenção ao Cliente"

Alan.

Alan, YES!

Still didn't read the article, but the xkcd comic it links to in the beginning is great http://xkcd.com/327/

Forehead. I forgot to add forehead, now it's completely different joke. Dammit

Maybe I'm missing something, but currently in latest PW you can set all fields to "required" built in.

Yep. Everyone in the IRC channel has to have a clean-shaven gravatar

That's good to know Ryan, thanks for testing it. I wasn't aware of the installs property, must have missed that from my reading of the wiki. I separated it in case anyone else wanted to develop modules that use the PPP one-time-pad system (though I don't have any further plans to right now) and also because the code in CryptoPPP is mainly comprised of parts of existing PHP implementations of the PPP system and I wanted to able to credit those folks in the module's information. My contributions are mainly within the 2-factor authentication module. I plan on doing that once there has been some additional testing and I've worked out the two problems I have with it at present (see the Known Problems part of the opening post.)

Congrats Ryan! Awesome Work.

This is really awesome Steve, and a great idea. Just tested out here and it works great! Thanks for your work with this module, it looks really well put together. One question: why is CryptoPPP.module kept separate? Just wondering if this might be simpler for people to install if they could just download 1 zip (or 1 clone) and have everything needed in 1 directory. You could add CryptoPPP to your getModuleInfo 'installs' line, and have it install and/or uninstall automatically with Auth2FactorPPP (ProcessWire will do this for you have you use that 'installs' property). Though if you are planning to make other modules that use CryptoPPP, then I suppose it makes sense to keep them separate. But just wanted to check. I would love to see this in the modules directory if you have time to add it: http://modules.processwire.com/add/ … thanks again for the great work you've done with these modules!

For those that also do this I followed Soma's instructions, so under /site/tinymce/plugins/ I now have two folders: /bramus_cssextras/ and /soma_shortcuts/ and in the field's TinyMCE settings, under 'Third-party plugins', I simply added: soma_shortcuts: /site/tinymce/plugins/soma_shortcuts

There has been a recent change in behavior here (a couple weeks ago), though not one that affect you unless you are trying it for the first time, as there was nothing worthwhile in the previous behavior. PageArray::sort() used to sort by the property value without regard to the page's outputFormatting state. This would mean that it could sort by the formatted date, which would be alpha sorting (of the date string) rather than date sorting. That's really not what you want. So I recently modified it so that it always sorts by the unformatted value, regardless of whether output formatting is on. Meaning, $pageArray->sort('some_date_field'); and $pages->find('..., sort=some_date_field'); should always be consistent. Please let me know if you are up-to-date with your PW version and still experiencing incorrect behavior with this.

Soma to the rescue. Actually I'm not a TinyMCE expert, but working with PW pushed me to get into it, since there were a couple bugs in PW implementation for IE. Having clients that work with IE8-9 made me take care of it even if I didn't wanted. Ok here it comes: I quickly searched and looked at how shortcuts are implemented in TinyMCE, and since 3.+ there's a addShortcut command. http://www.tinymce.c...tor.addShortcut These are the shortcuts currently in TinyMCE: ctrl+z Undo ctrl+y Redo ctrl+b Bold ctrl+i Italic ctrl+u Underline ctrl+1-6 h1-h6 ctrl+7 p ctrl+8 div ctrl+9 address (ctrl on Mac = cmd) I quickly created plugin you can use to define your own. It's different for Mac than Windows, and also Browser dependent I think. Install this plugin as you would for the bramus_cssextras. Same procedure. Here's the plugin code and attached for dowload. For finding commands you can search the tiny_mce_src.js. This plugin will add a shortcut ctrl+e to format a block as a blockquote. // Create a new plugin class (function(){ tinymce.create('tinymce.plugins.SomaShortcuts', { init : function(ed, url) { ed.addShortcut('ctrl+e','Format Blockquote', ['FormatBlock', false, 'blockquote'], this); } }); // Register plugin with a short name tinymce.PluginManager.add('soma_shortcuts', tinymce.plugins.SomaShortcuts); })(); Cheers. soma_shortcuts.zip

SlimeText sounds great Sorry, just had to do it

$user->language = $languages->get('de');

If the request comes in through ajax, ProcessWire will detect it and your Process module can just return the content (JSON or whatever) that you want in the ajax. Basically, you don't need to do anything other than load the page with ajax and you should get what you want.

Thanks to Soma for helping me with module questions via the #processwire IRC channel.

Maybe but if it works, I'm gonna give you big kiss on your hairy … …or not, you know.

For US sites StormOnDemand if you need the power, or lower down the ladder from the same parent company, LiquidWeb's offerings are great too. For me it's all about managed hosting and hardware/software faults being fixed whilst I sleep in about 2 minutes on the rare occasion they occur, as opposed to my experience with UK hosts which is you don't know all your sites have been down for 8 hours until you get out of bed. LiquidWeb and ServInt are just so far ahead of the game in terms of looking after customers that all the awful hosts I've use in the past should be ashamed.

Really loving it!

I would suggest looking into Mandrill from those chaps at MailChimp. It's basically the sending/stats/bounce part of Mailchimp, leaving you to build the newsletter and subscriber database in ProcessWire. Basically it's another alternative to what Antti mentioned above, and one I'm really curious to look into myself if I ever get time! Colour me biased, but the pricing and features in Mandrill might be more appealing too (first 12,000 emails sent per month free).

That idea never occurred to me, so +1 for thinking outside the box

I can happily recommend ServInt - the company ryan uses. I've got a VPS in their Amsterdam datacentre and the service is great, sites load quickly and it's cheaper and better managed than UK VPS hosting (I've found that a lot with the better US hosting). The only drawback thus far is only being able to pay in US Dollars, but if you're fine with the conversion rate being in our favour for the past however many years then you can overlook the fact that pricing therefore fluctuates a little due to the exchange rate. It's all a small price to pay for better service and more cost-effective hosting I think.

I think it's quite telling that there isn't a tag for PW on Stack Overflow.