Leaderboard

Markup Simple Navigation Module While there was a lot of people asking how to make navigation, and there were many examples around already (apeisa, ryan...) I took the chance to sit down 2-3 hours to make a simple navigation module. It has even some options you can control some aspects of the output. Installation: 1. Put this module's folder "MarkupSimpleNavigation" into your /site/modules folder. 2. Go to your module Install page and click "Check for new modules". It will appear under the section Markup. Click "install" button. Done. Technically you don't even need to install it, after the first load call ( $modules->get("MarkupSimpleNavigation") ) it will install automaticly on first request if it isn't already. But it feels better. However, it will not be "autoloaded" by Processwire unless you load it in one of your php templates. Documentation: https://github.com/somatonic/MarkupSimpleNavigation/blob/master/README.md Modules Repository processwire.com https://processwire.com/modules/markup-simple-navigation/ Download on github https://github.com/somatonic/MarkupSimpleNavigation Advanced example with hooks creating a Bootstrap 2.3.2 Multilevel Navbar https://gist.github.com/somatonic/6258081 I use hooks to manipulate certain attributes and classes to li's and anchors. If you understand the concept you can do a lot with this Module.

https://github.com/apeisa/Thumbnails Template usage: echo $page->cropImages->eq(0)->getThumb('thumbnail'); Better docs coming soon. Development sponsored by: http://stillmovingdesign.com.au/

Hi, I'm trying to build a search function using selectors but when "sanitizing" a string, containing a comma, with Sanitizer::selectorValue it sometimes removes the comma. Here are some test runs (first row is input, second is selectorValue output) : 'test' 'test' "test' "test" ,test, ' "test '" ' '' ','test' "'test" guns n' roses, mötley crüe "guns n' roses mötley crüe" ','test "'test" "''" "" , "" test, test2 "test, test2" Also in the documentation for selectorValue it says: does this mean you can't search for all characters (comma)?

So here we go: http://siebennull.com/PWfileReference/ I hope it gets clearer ;-)

Hi Guys, I have read through other topics on using PW for multisite setups and am a bit none the wiser unfortunately. Let me explain my scenario: I have a potential client project whereby they want to have 3 websites all as separate websites in terms of: content look & feel domain names Users However, for me to setup up the websites for them it makes no sense for me to be managing 3 separate hosting accounts and them to be paying for all of that. Also, 1 of their websites will be a primary site with a few thousand visitors per month, but the 2 more secondary websites will only have a couple of hundred visitors. Perfect for a multisite install to my mind which wouldn't tax server resources too much. This to me seemed a perfect opportunity to setup a multisite under one hosting environment whereby domains are mapped to subdirectories or whatever setup I would need. My problem is that I have no idea as to how I go about setting all of this up in PW. I have done this before with WordPress using the domain mapping plugin under a multisite install. All without dealing with symlinks or much code at all. However, I would really like to use PW for this as long as it's not too complex. With PW I can deliver a client user experience in the admin area that is much more streamlined for their particular use case.

Which direction you go largely depends on whether you want the sites to use independent databases or share the same one (perhaps for communicating to one another). If you want them to be technically separate, independently running sites on the same account, then use the built-in multi-site functionality that Diogo mentioned. Here are the docs for that: http://processwire.com/api/modules/multi-site-support/ If you want them to share data, then use Apeisa's great multisite module:

I'm using this system sucessfully on my host

Count me in for contributing to the manual.

Thanks very much onjegolders - I'm glad you found it useful. I hope to get more people contributing Case studies and I plan to write one for my next client site with PW coming up soon. I hope the case studies will highlight the strengths that PW has in real life scenarios (it has many) and help people to decide on using it.

I've merged the 2.2 dev branch into the 2.1 master branch, making 2.2 the current stable version. I've been switching my own sites between the two branches for weeks without issue, and I've not had any reports from others about compatibility issues, so believe it's safe to merge. However, there are a lot of changes between the two so use caution when pulling in the latest commit. By that I mean backup and test everything out to ensure all still works as expected. Of course, this is something you should always do, but especially so in this case (it merged more than 50 commits from the dev branch). Language Support The LanguageSupport modules are now included in the ProcessWire stable branch, but they are uninstalled by default. These LanguageSupport modules are still considered beta, as I think we need more people using and testing them before we can consider them non-beta. To install them, just click "install" on the LanguageSupport module in your Admin > Modules. It will install everything else. You can also uninstall the LanguageSupport modules just as easily as installing them by just uninstalling the LanguageSupport module (and it will uninstall the rest). I will be adding a Language Packs section to the Download page soon. Thanks to all those that have helped with making translations. In the coming weeks, we will also be making more and more of the core modules translatable, so we'll need continued help from our translators. Special thanks to Avoine (http://avoine.fi) for being a sponsor of ProcessWire 2.2. You will see their name start to appear elsewhere on the site as a thanks for them helping to make the Language Support possible in ProcessWire. Other changes The LanguageSupport modules are the major drive of this version. However, there are several other changes and additions, including: Add module dependencies support. Add module auto install and uninstall support, to correspond with dependencies. Add 'page-create' permission to Setup > Templates > Template > Access. Update to latest version of TinyMCE (3.4.7) Add new Page Clone module to core (may be installed from Admin > Modules) Update error log file to include hostname. Made tab delimited rather than colon delimited. Added built-in multi-site/multi-domain support optiona via config file /wire/config.index.php Addition of several new hooks, especially in the $pages API var and files Inputfield. Add new 'Site' link in default admin theme. Numerous other bug fixes and optimizations, see the commit log for details. Upgrading an existing installation There is no formal upgrade process for going from ProcessWire 2.1 to 2.2, so all you need to do is pull in the latest commit (when you have time to adequately test it). If you aren't tracking the source on GitHub, then you'll want to download the latest ZIP and then do the following: Replace your existing /wire/ directory with the new one in the ZIP. Replace your existing /index.php with the new one in the ZIP. Replace your existing /.htaccess file with the htaccess.txt file included in the ZIP. That's all you need to do. However, I suggest renaming or backing up your existing /wire/, /index.php and /.htaccess files just in case you need to revert for any reason. This is standard procedure with any upgrade. Please let me know how everything works for you. After installing, there is one change that may affect you if you are using multiple non-superuser roles with page edit access. A user must now have page-create permission on a Template in order to create a new page that uses that template. You'll see this setting on any template that is defining access, on its access tab. So if you have non-superuser roles with edit access, go in and add that page-create permission for any templates that they should be allowed to create new pages from.