Leaderboard

@all I just pushed a waaaay overdue update to the Textile textformatters that brings in the latest version of Textile (now at 3.5.5 compared to 2.4.1 before.) If you want to see what new features Textile picked up along the way then browse the changelog. Please be aware that this new version requires PHP 5.3.0 or higher as it uses namespaces. This release also introduces a new formatter: TextformatterTextileField. This is a very lightweight formatter that only applies Textile's span and glyph handers to a single line input and does not wrap the result in paragraph tags - making it suitable for formatting fields for use in PW templates without having to resort to stripping paragraph tags.

So I created a little python script. https://gist.github.com/anonymous/10001724 create a new file and give it execute permissions chmod +x ./pw You can fetch the lastest PW code from git an start a new project. ./pw <new-project-name> Also if you want a specific version ./pw <new-project-name> dev 2.4.0 Will create a new folder with your project name if you need help ./pw help Tested in my Linux machine.

Hi t2t2 You can also do this: like this if you like: $t = new TemplateFile("/path/to/your/template.php"); echo $t->render();

First PW-meetup in Finland will take place at Tampere, Friday 2.5.2014, 12:00. I'll give you exact address when it's confirmed, but it will be walking distance from Tampere railway station. It will be free event for everyone. Avoine will offer some coffee and if we get really lucky, some cookies also. I think we will have something between 5-10 people coming, so it will not be that formal event. If you have anything you want to talk or show, please get in touch with me (antti@avoine.fi / 041-4383991). Anything goes - showcase something you have build, tell us about the great idea for module, propose plan that will help PW to spread in Finland etc.. After the 3 or 4 hours we can change location to pub and continue the world changing plans. No registration required, but always to happy to hear if you are coming (here or email).

You better re-read this answer to your previous question: https://processwire.com/talk/topic/6013-difference-select-aka-dropdown-vs-page-field-type/?p=58768 Hint.... $page->myselect->title; $page->myselect->template; $page->myselect->id; $page->myselect->child->name; $page->myselect->headline;//custom field $page->myselect->othercustomfield;//custom field $page->myselect->this; $page->myselect->that; $page->myselect->that->and->and->and;//you get the picture... Here's your other homework...will the above work in a function?

Btw, there seems to be no folder limit on ext4 filesystem. We are running pw installations with well over 100000 folders already.

Hello guys, long time listener, first time caller (or something like that) Night Attack is the new independant version of the NSFW show podcast hosted by Brian Brushwood and Justin Robert Young. And I'm sure you'll all be happy to hear it's powered by ProccessWire. The quick feature list: Processwire 2.4.0, nginx + php 5.5.9 with cloudflare in the front Includes 3 different quality podcast feeds (all based on the data on episode pages) Uses the alternate template filename for render, wrapper has this at the top: // Get the page content ob_start(); include "{$page->template}.php"; $content = ob_get_clean(); and then content is output with <?= $content; ?>. This way the templates can even be just html Made in less than a week (might had started 4~5 days before going live, can't remember) Modules: AIOM+, Page Edit Soft Lock, Piwik Analytics and a custom module to ensure rss feeds have correct content type when cached I mainly focused on the code side while the design was done by sebgonz.

Hi rusjoan, Sorry you're having a bad experience at the moment, but I don't think it helps to get angry at PW. Just having a quick look, I see a couple of issues with your code. $config->paths will be empty because when you're inside a function you need to use wire('config') or $this->config depending on how you are using it in the module. This is because of PHP variable scope - there are lots of posts about this. Same goes for your use of $user and $input->get Try fixing those and see where you are at. I think there are probably more things amiss, but let us know what happens with those changes first. If you are calling the module on a use specific basis in your templates, which I think is what you are doing, then autoload false makes sense.

Just an FYI: Been running on MariaDB for most of my installations PW ( 2.2, 2.3, 2.4) with no issues to report. That does not mean you should migrate a production site with out testing it however.

@Mats No problem - I forgot I could add that PHP dependency as a requirement in the plugin info. I'll fix that. Edited to add: Updated the module to require PHP>=5.3.0 which should stop this occurring again.

5.2.17. Sorry, should have checked the version. Too many hosts to keep track of...

That looks good. What version of PHP are you using?

@Mats Thanks for the report - I'll try a fresh install via the Module manager and see if I can reproduce this. Updated to add: Worked fine for me using the PW dev branch and PHP 5.5.11. Could you paste-bin/gist the content of your TextformatterTextile.module? Sounds like it might have been corrupted.

All those pages are a good read. And if read well, at least half the questions you asked would not have been asked.

@bytesource I just pushed an updated TextformatterTextile module that adds a new formatter: TextformatterTextileField that should do just what you need without you having to hook things or use the P stripper.

a good read

Looks like Angular might start making use of polymer elements, which would be really cool. Ember might be getting involved too. So much cool stuff happening - hard to decide which way to go. Throw Meteor in the mix as well and app development is starting to get really fun

foreach($page->pagefieldmulti as $selected) echo $selected->title; // worked excellent if($page->pagefieldmulti->has(1001)) echo "option page with ID 1001 is selected"; // worked not So I took the first code. foreach($job->check as $selected) { echo $selected->title; echo $selected->body; } So in pagefieldmulti I chose the parent page (for selectable childs) that will function as checkboxes. I then made a separate template for these child pages which have a title and body field. Now when I output these 'selected' pages, it will display those two fields as a title and description. Never once seen a cms that display multiple same fields (body in my case) in one article. Amazing what you can do with processwire - so many possibilities! And lucky there are many friendly people on this forum to help eachother. More will turn to PW for sure. Because these type of things would be weeks or maybe months on other cms.

The index.php file goes into where ever you've put you main website directory, so if my website directory is called "mywebsite" and it's in the "public_html" directory of the server you would put the index.php file: public_html/ mywebsite/ index.php //here is where you would put it Are you using shared hosting or do you have root access? I guess I should ask: are you using Apache or IIS? BTW, I like the duck... birds of a feather, code together

The goal is that there would be no difference from our perspective. But the reality is they are two totally different things behind-the-scenes, so there are sometimes minor differences. In time, hopefully there won't even be minor differences. But either way, it's good to know the difference just because database-querying selectors are more expensive to execute in terms of resources. Any function that accepts a selector and returns pages from the $pages or $page API variable is a database-querying selector. Whereas in-memory selectors are primarily used by PageArrays, as they represent a group of pages already loaded in memory and selectors are used to filter through them. $results = $pages->find("selector"); // database-querying $results = $results->find("selector"); // in-memory $children = $page->children; // database-querying $children = $page->children("selector"); // database-querying $children = $children->filter("selector"); // in-memory $children = $page->children->find("selector"); // database AND in-memory (just use children w/selector instead)

Session fingerprint also keeps track of useragent. So if your useragent or IP is changing, then the session is considered no longer valid. This can help to prevent session hijacking. But it can be a nuisance if your IP and/or useragent are changing for a valid reason. In that case, you should disable session fingerprint from your /site/config.php file. Locate this line and changed it to 'false' as shown below: /** * sessionFingerprint: should login sessions be tied to IP and user agent? * * More secure, but will conflict with dynamic IPs. * */ $config->sessionFingerprint = false;

Mmmmm... donuts.