formmailer

You can use the status "Hidden" for this. It's on the settings tab of the page. /Jasper

I just checked that and that's correct but if (which is very unlikely, but still...) a user wants a password with no other letters than öäå, or maybe just 2334164Å it is not accepted, even though it is a correct password according the description.

Same here!

I know that you can can use them in the translation, but having å in the pagename gives some strange effects (it will be replaced with a -) and I am not sure how passwords react on these characters. (haven't tried) Of course you have the ö ä ü and even the Eszett (ß) in German, but they are not the last character in the alphabet and aren't that important in the translation: if it doesn't work, a user can try something else. But if the instructions say (a-ö A-Ö) the Ö and ö characters need to work in that field, otherwise it would be very strange. But obviously it would be good to know which foreign letters are allowed and which aren't. (not even speaking about Chines, Japanes, Arabic and so on....) /Jasper Edit: Just tested the following password: öäå1öäå1 and got following error: the password doesn't contain any letters.

Here comes the first draft in Dutch. It's a very rough translation and I probably need to work a while with the Dutch admin to find all my mistakes. But I know there are more Dutch users here, so I guess others will find pretty quickly. I'll upload the Dutch files to Github, so others can play with them as well and send a pull request if they like. https://github.com/f...-nl-Processwire /Jasper Edit: added Github link

I have the same issue here (using xammp, both on Windows 7 and XP). /Jasper

I actually thought about this, but since I only used a date field in this release, it didn't seem necesary to run more than once a day. But I will add (half)hour support as well. Just for those who don't like LazyCron, it's also possible to run this plugin from a specific template, with the following: <?php $SchedulePages = $modules->get("SchedulePages"); $SchedulePages->RunSchedulePages(); This would allow you to set-up a real cron job using wget or curl, just to activate the scheduling function. But just now this doesn't add antything since the date fields are set to midnight. As I can see the current date picker doesn't support times, or does it? This would almost be a requirement for adding time support to this module. That would be great! I tried to find out how to do that, but gave up after a while. And while you are at it: would it be possible to create a FieldsetTab (called Schedule) as well and add this with a single click (or drag-n-drop) to a template? It would be great if these scheduled dates alway would appear in their own Schedule tab without having a user creating the FielssetTab field and add the date fields in it. Good points. I changed the name, both for the module and the function. /Jasper

I started working on the Dutch translation. I might be able to do the Swedish translation as well, although I am not a native speaker (but I live in Sweden). /Jasper

I understand, although I am not legal minded either. I noticed that Tinymce is licenced under LGPL 2.1. As far as I understand things, this would mean that it's possible to use GPL v3 for PW. http://www.gnu.org/licenses/gpl-faq.html#AllCompatibility I beleive WordPress has GNU v2 or later. Note: I am not saying that you should change the licence. /Jasper

Hi, I just uploaded the first version of the SchedulePages module to Github: https://github.com/f...r/SchedulePages This plugin module allows you to schedule (un)publication of pages. I hope you guys will like it. //Jasper Usage: ====== Place the SchedulePages.module file into the site/modules folder and install the plugin from the admin area. Install/activate the LazyCron module (if you haven't already). This module is part of the Processwire core, but it isn't activated by default. Add the following date fields to your template: publish_from publish_until Note: the fields are already created during the installation of the module That't all. LazyCron will run take care of (un)publishing your pages that have a the publish dates set. It will run on every hour. Please note: LazyCron hooks are only executed during pageviews that are delivered by ProcessWire. They are not executed when using ProcessWire's API from other scripts. Edit: Changed the name of the module and function as Ryan suggested below. Edit 2: Updated instructions. Required fields are now automatically created and from now it runs every hour. Edit 3: Added module dependency. The updated module is on Github

Thanks Ryan! As you probably understood I am writing a module for scheduled posts and I thought everyting worked, but suddenly I realised that you easily can have pages with a start date but without an end date, so I need to take care of these as well. Just ignoring the end date actually works, but causes expired pages to be activated and be deactivated directly afterwards by the "unpublish rule". I'll try your options out and I am sure they will work. /Jasper

Hmmm... I need to make the find query more complex and I am not sure how I can fix this. I have: wire("pages")->find("status=unpublished, publish_from<" . time() .", publish_until>" . time()); The above works, but I also need the the pages without a publish_until date (publish_until = empty). How can I do that ? Is it possible? /Jasper

Thanks guys, that did the trick! /Jasper

Hi! I am probably thinking totally wrong, but I would like to run the following $pages->find query directly in a module's function $pages->find("status=unpublished"); I don't want to run it in the template and pass the PageArray to this function, but when I am trying this I get the following error: Is it possible to do this in some way or does it require a totally different approach? /Jasper

I am a little bit curious about Ryan's reasons to licence ProcessWire under GNU/GPL v2 and not under the newer GNU/GPL v3. Is there a special reason for this choice? /Jasper

Cool, just missing one cheat sheet on your site This one: the Processwire Cheat Sheet by Soma (http://somatonic.github.com/ProcessWireCheatsheet/) /Jasper

Keeps getting better and better, Soma. Great work! Would it be an idea to add a link to the online docs with examples for each "group", eg. http://processwire.com/api/variables/page/ for the $page section. Maybe something like: $Page (Online documentation and examples) I think the examples are very useful, especially for new users. /Jasper

Thanks guys! I think I'll try out Ryan's suggestion and will do the same for the page expiry date. I'll try to make it as general as possible, so others can use this as well. Would it be useful to create a module for this? /Jasper

Hi, I need to schedule some posts/articles (both start and end date). What would be the best approach for this? I was thinking about a (lazy)cron job calling a page that changes the status of the page based on the current date. Would this be a good solution or is there a better way? /Jasper

You're right. Fixed that in my post.

Very useful! Great work, Soma!

Antti, is the above still true? /Jasper

As for the Twitter module. Did you take a look at the screencast in this topic: http://processwire.com/talk/index.php/topic,281.0.html ? If you want the module to show in your sidebar, you can call the module using the following code into the sidebar section of the tempate. (in the default example section, this is in the head.inc file.): $page->renderTweets("/url/to/page/you/just/created/"); /Jasper

I am glad you like it. I started using Piwik a few months ago and I was very impressed. The day after I installed it, I figured that I wouldn't need Google Analytics anymore, but I used them together just to see if there were some major differences in tracking. It turned out that the stats were almost the same (a few minor differences occured, but that could have been caused by my own visits, that Piwik ignored and GA tracked). Now I stopped using Google Analytics on most of my sites and I am only using Piwik instead. Jasper

Installed it in my test environment and it looks very nice and usefull. Good job!