Leaderboard

Too bad, WilllyC missed the 50'000th massages. Congrats PW!

PW has very flexible UA management. Most of the sites can get the exact needs fulfilled after little clicking. But when you need to scale it in horizontal way: ie. adding ten different news sections, each with same templates but managed by different group of people, PW doesn't make it too easy (since UA is tied to templates). Also roles&permissions&template access is a combination, that at least we cannot leave to our clients (it's way too complicated for your average editor) - it means that UA management have to be done by us. This is fine on small scale, but some of our sites are pretty heavy on UA: biggest site has over 800 user groups and many times we do have something like 50 000 users importet (these sites are not build on pw today, but hopefully they will be). So we need to have simpler UA that our clients understands and can use on daily basis. That will also mean less granular control, but easier to manage. Lucky for us, PW has hook system in place, that is flexible enough to allow hooking to UA also. Few months ago I started building module to add two features for PW: -user groups (user can belong to more than one group) -page based permissions based on groups (so you can say: this page and it's children can be edited by groups A + B and viewed by groups A + B + C I first thought that I should release this as a paid module, but after showing this current early version to Nik and Teppo (I knew they had similar needs) and when they showed interest in development I wanted to make this a community project (this is gonna be thousand times better than just me building it alone). So lot's of progress is coming and of course everyone is invited to collaborate. Be it ideas, comments, testing, use cases etc.

I think something like this should do what you want: echo date("j. F Y", $pages->get("sort=-modified")->modified); It finds the last modified page. You can of course change this to created and also limit to various templates, parents, etc if you want.

I've been working on this one for a few months and just launched it this morning: http://villasofdistinction.com I also did the previous iteration of this site, 5 or so years ago (which was running ProcessWire 1.0). The new site is powered by ProcessWire 2.4 (2.3 dev). The site is responsive and designed for a good experience on both desktop and mobile. While I did all the development, the site's design/look and feel was created by the client (they have their own internal design agency). Most of the work in this project was actually not anything you can see on the front end. Instead, most of the work went towards back-end management, workflow and web services. The client has a large number of editors and agents that needed various capabilities, workflows, feeds and such. So there's a lot more going on here in terms of a management platform than in the previous iteration... and that's mostly what kept me busy for so those few months. Modules used here: Foundation 4 Profile All In One Minify (AIOM) FieldtypeMapMarker (with MarkupGoogleMap) Pro Cache Form Builder Hanna Code Redirects Selector test Changelog Version Control for Text Fields Batcher Admin Template Columns CKEditor Select Multiple Transfer CollagePlus And a few custom modules

Hi Alec, Welcome to the forums. The simple answer is yes.... the realistic answer is: Such sites will most likely require significant amounts of custom code. As you rightly stated, PW is a framework It will give you the necessary tools to build the site but you will have to get your hands dirty...Having said that, there will be some things you will be able to get with PW right out of the box, e.g. pagination... Maybe you can expound on the specs of your travel site to get better answers... These sites built with PW may be of interest: http://www.villasofdistinction.com/ http://www.goaroundeurope.com/ http://processwire.com/skyscrapers/ More here: http://processwire.com/talk/forum/9-showcase/

Hi Folks, I just added a small module that keeps track of search keywords encoded in http referrers from common search engines leading to your site. See the README for a full documentation of features. Please let me now, if you have found any issues, feature requests or opinions by leaving your comments here in the forum or on github. Regards from Hanover, Germany, Marco

More importantly, that Type Wonder site looks awesome - what a great idea!

Not especially related to programming, but I just learned of Finnish band Ultra Bra, and considering I speak no Finnish whatsoever and understand not one word of their lyrics, they sound wonderful. I'm just a few years late... (The only other band I really enjoy even though I don't speak the language is Runrig, who sing in Gaelic.)

Thank you very much! Yes I do. Please see my answers below. I'd love to further discuss the topics I brought up though. Yup. That's the reason I'm currently waiting for 2.4 to be finished (I said that in another thread about writing blog articles, too). Otherwise I'd propably have to refactor all of the stuff on a daily basis. There currently is too much (very positive!) change going on. Apart from that there is a lot of other work to do. We're currently building about 6 websites in parrallel (all driven by processwire - yay!) which is good for our business but bad for doing sideprojects like this theme. WOW. I didn't read that until now. Thanks for the hint

ok guys, there have been some major updates to the boilerplate. Check it out at https://github.com/fixate/pw-mvc-boilerplate, and take a look at my original post for a few details on the updates. Things are far neater

Thanks Matthew! I'm always interested in the cause when someone's got a problem with a selector. Well at least when it's not an obvious one . Often it's a misunderstanding of some kind or a structure complex enough to get anyone dizzy, but then there are those few cases where someone's actually hit a bug or some other kind of bad behaviour. And those are the cases I'm always willing to try and solve. So, wilsea, I wouldn't say your issue has been fixed. That's only a workaround. Of course it may be one good enough for your particular case, but at least I'm still wondering what's the reason. You checked the code lengths from the original table if I'm not mistaken? Could you run the check against the data in the "field_code" table (if the field is called "code" then that would be the table with the code strings in a field called "data")? Just to rule out the possibility of some inconsistency there. I'm guessing you've generated the pages in PW using a script and there just might be something wrong there. If everything seems fine there also, could you give a couple of example codes (working and not working ones)? There really has to be some explanation why you've run into this behaviour. Don't get me wrong - I'm glad you got the expected results and you're probably just fine using this approach. Just being curious .

Very, very smart. This is the kind of site that should be used as a long case study (small ebook, to be honest) going through details such as why dedicated work-flows are so important (and how to define them) the importance of rigidly defining the brief, the necessity of being able to recreate ideal workflows in the back-office for the editorial/site management reasons, the creation of an editorial hierarchy and managing it the level of expertise required to attack such a project the importance of a consistent and understandable API to have a chance of a) creating the site and b) modifying and developing the site over a sustainable period why developing such a site within a rigid structure such as Joomla or Wordpress would undermine most of the above, underlining the importance of being able to create a dedicated application And the finally, why ProcessWire made all the above not only possible, but delivers a fast, effective, enterprise class solution. So, a big PW advert, basically. ProcessWire needs such a write up.

after reading this article http://www.searchenginejournal.com/why-arent-you-paying-attention-to-apis-for-your-cms/41155/, I started looking a bit deeper on what it means and how hard would it be for PW to have such an API... I didn't come to a conclusion, as would be expectable from such a noobie in such things but still, I wanted to post here some of the documents I stumbled on to tease you people to have a thought on this. http://ecmarchitect.com/archives/2009/11/23/1094 http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=cmis http://rest.elkstein.org/ http://docs.fuelphp.com/general/controllers/rest.html http://wiki.alfresco.com/wiki/CMIS http://drupal.org/project/cmis http://www.elefantcms.com/wiki/RESTful-APIs http://mambo-manual.org/display/dev/Interacting+with+the+RESTful+API

Of course I hope all the best for ProcessWire also in this contest, and it would be a shame to scrap all of our hard work too! ... I just was a bit disappointed with Bitnami's decisions. They could have made it so that votes last since they are voted. I think then the ordering of packages would be more according to the actual size of the community, and they would then be worked off by Bitnami in a reasonable order ... promoting a good prioritization rather than bloodshed competition ... much like how StackOverflow got so incredibly successful. As it is now, it just encourages the respective communities to turn themselves inward-out and do massive campaigns to try to break the patience of the others ... and if you fail, all your time is wasted - worth zero. I think it will bite back at them in the end. But of course, for us others, we just have to live with it :|

Thanks for your reply and about cookies. I have now something to workout in the week-end and see how far it will get me. Thanks.

Thanks for the info, then I know! BAD decision by Bitnami, just to get more shares ... But anyway ...

You can use PHP's default mail function: $to = 'nobody@example.com'; $subject = 'the subject'; $message = 'hello'; $headers = 'From: webmaster@example.com' . "\r\n" . 'Reply-To: webmaster@example.com' . "\r\n" . 'X-Mailer: PHP/' . phpversion(); mail($to, $subject, $message, $headers); But personally I would recommend installing the free SwiftMailer class (swiftmailer.org). It is incredibly powerful and can easily send mail using SMTP, can include both HTML and plain text versions in the one send, allow you to add attachments which is great if you are using a PHP PDF generating class to automatically generate a receipt, and lots more!

There we go! But do you, or anyone else, know if they start from scratch every month? Would not be fun to scrap the hard work of the ERPNext guys gathering all those votes, if that happens ... Hope that anyone being #2 will at least make it next round. After all we're all in open source, and it'd be nicer to have friendly and mutually spurring and promoting relation with other projects, than die hard winner-takes-it-all competition ...

equal! yippieh!!! Now once ERPNext activates its community, we must stay strong !!!!

but there's 15 days to go....

Probably should've mentioned in my last post that it's, of course, possible to support both $db and $database simultaneously. Ryan posted an example of this in the first post of the thread linked above. That would make sure that your module works now and in the future releases, though I must admit that I still haven't added this to any of my own modules either.. Oh, and by the way: this module seems very useful. Had a quick look and so far I'm liking it very much

Ooh look! We are only 13 votes off first position ....

@adrian: Thank you! that worked like a charme! i thought there must be an easier way than to add a date field to every single page next time i'll come up with a more complex question

Minor clarification: Since current master doesn't yet support PDO and according to Ryan 2.4 will be backwards compatible with earlier versions (thus supporting $db and MySQLi) "in near future" might be a bit of an overstatement here. If this module needs to work with current master (stable) branch of ProcessWire, $db is a requirement.

These are the kinds of answers you want when brevity is key! Thanks apeisa

Regardless of a CMS/CMF for sites like these you need to have decent knowledge of scripting. Next, the preparation before you even can start building sites like these takes awful lot of time. As Kongondo stated, those sites require significant amounts of custom code. 1) When you're new to ProcessWire and want to build this you need to have a good understanding of PHP/ OOP. 2) Accept the extra time it takes finding out `best practices` for PW. 3) Very, very good preparation. If you want to do it with PW, it's all in there. ps, I don't want to build anything not build on top of PW.

1. yes 2. yes and no

Oh, there are plenty. Finding them awake, sitting upright and facing front is another matter, however.

@soma here are some upgrades for strings (translatable). Maybe better use some variables for repeating strings (like: 'more', 'installed: ') ? line 239: $status = $this->_('found: ') . $local_version; line 248: $status = '<span class="ui-state-installed">' . $this->_('installed: ').$local_version.'</span><br/>'; $status .= '<span class="ui-state-update">' . $this->_('new version available!').'</span><br/>'; line 254: $status = '<span class="ui-state-installed">' . $this->_('installed: ').$local_version.'</span>'; line 284: $pretext = '<p>'.$this->_('Modules found on modules.processwire.com (').$count.') </p>'; line 498: return $this->_('(uninstallable)').'<br/><a href="'.$module->url.'" target="_blank" title="'. $this->_('Uninstallable with Modules Manager').'">'. $this->_('more').'</a>'; line 541+1: $actions = "<button name='install' value='{$module->class_name}'>" . $this->_("install") . "</button>"; line 543+1: $actions = '<a href="'.$module->url.'" target="_blank" title="'.$this->_('No download URL found').'">'. $this->_('more').'</a>';

This thread has become quiet unfortunately. I wonder if you (Felix) have any plans do continue with your admin theme? It's definitely outstanding ...

I found the command line the easiest way to work with sass. Basically you need only one command: sass --watch. If you open the command line via windows file explorer from the directory where your .rb file lives you don't even have to navigate to the right directory. Btw. I don't know very much about Foundation, but doesn't it integrate Compass (http://compass-style.org/)? If so, Compass is a very convenient way of working with sass. Here is a short summary on working with sass from the command line: http://www.hongkiat.com/blog/getting-started-saas/

This thread is for the new PW admin theme being developed for 2.4. Zahari and WillyC, I'm sure you guys both have good intentions, but this is not the right thread to promote other admin themes and such. We're now focused on wrapping up and fixing bugs in the new theme, not redesigning it. This is in preparation for the very soon upcoming 2.4 release. Zahari–please do keep up the good work on your theme, post to the directory, and start a thread for it, as I'm sure many of us will enjoy using it too. WillyC–please don't let that one go beyond the sketch stage. I hope you can appreciate that there's no way one could ever get everyone to have the same viewpoint on subjective things, so that is kind of pointless. The goals here have always been more about the system. Then taking that system and reducing it to the most minimal, easy-to-use implementation. All while still incrementally improving on the old theme. The consensus has been that's what we've done, even if we're still working out some bugs. We'll let others take it and run with it in creating stuff more tailored towards their own preferences and other scenarios. The biggest complaints with the old admin theme were: 1) the colors don't have broad appeal; 2) the header area used entirely too much space; 3) the fields layout was too boxes-in-boxes with excessive linework, emphasizing the containers over the inputs; 4) the type was too small. The consensus and the math has been that the new admin theme solves these issues, while appealing to a broader audience than the old theme. Keep in mind there's no way to make everyone happy, so it's entirely expected to have a hater or two (I'd be more concerned if there weren't). Also keep in mind the old admin theme has a consensus of haters, among those that don't use it every day. So it's a bottleneck when it comes to new users. Is the new theme meant to be some kind of design masterpiece? Absolutely not–it is intentionally trying to avoid making design statements, and focused on reduction to essentials (though not to the point of looking like Craigslist). When it comes to the bigger design project (PW 3.0), we'll hand this off to Felix and Phillip (and perhaps others), who have already nailed the concept. That's my opinion, but we'll seek the input of the community to decide. My experience has been that small team design=good results, community/committee design=bad results. But that's another conversation. We'll move onto talking more about that once we've got 2.4 final. Regarding the Inputfield containers: yes there are still situations where the boxes-in-boxes (emphasizing the containers over the inputs) might suit an individual installation or preference better. But there are more where it doesn't. As a result, it's not as well suited as a default (and we've already been through this to excess), but it is something we always want to offer as an option. The new admin theme system allows for configurable spacing between the Inputfield containers via a setting provided to the InputfieldWrapper. We may even make it configurable within the default admin theme at some point, but I'd rather see other themes focus on things like that. As for the typeface: Arimo vs. Arial. I agree with most with the points about Arial, and I think the arguments presented here against using any webfont make sense. As much as I like Arimo and as good as it looks on my own computer, I think we've got to revert to Arial–it makes more sense with this theme's goals and in the big picture.

Those two projects sound like great ideas to get stuck in to with ProcessWire. I think most people here would recommend using the development version now, and just keep updating as you go along. It's fairly stable right now, and updates are very simple to do (just replace the /wire/ directory, usually). I don't think there's a date scheduled for a 2.4 release - it will be ready when it's ready I started a website using the dev branch in August, and it's almost ready to launch. I've updated the work-in-progress site several times during development and it hasn't been a problem. So I would say go for it

Coding with Revolver and Rubber Soul from Beatles. Amazing albums!

This is a little off topic, but since it involves headphones, it's probably more in topic here than anywhere else in the forum. If you haven't heard 3D stereoscopic sound (I hadn't), you need to try it, it's really quite cool. To experience it, you need to use stereo headphones. Virtual barber shop (this one works best if you close your eyes): Thunderspace (put headlines on and click play on the video): http://thunderspace.me/ What's cool is also how simple 3d stereoscopic sound is to achieve. You just record the sound with two microphones: one where each ear would be on a person. Your mind apparently does the rest in making it 3d/spacial.

Well if it's a busy site they'll be querying Piwik potentially thousands of times an hour (not sure of your visitor numbers) whether they're a search engine spider or not. I think your solution here is to use MarkupCache and just update it once every hour. That way you're not hammering Piwik or slowing things down for your users. Even Google Analytics doesn't give you up-to-the-minute page counts by default (I think they update every 2-4 hours unless you're viewing some live stats). Of course if it's a site with very few visitors then I'm not sure why it would slow it down so much.

Wanze why, you're already here This is correct. Just the hook function would be like this. public function greyscale(HookEvent $event){ $img = $event->object; $arg1 = $event->arguments[0]; // do things with image // return image object for chaining $event->return = $event->object; } Which would allow you to do things like: echo $im->size(10,0)->greyscale('arg1','arg2')->url;

most of the time I end up wearing my earbuds for two hours, but forget to turn any music on *edit: Martijn, love that Lollywood song and video

I lizen to mi sound ofe keybpard wun koding.

You most likely ran out of memory. MAMP and other *AMP installs often come configured with 32 MB memory limit for PHP, which isn't enough to upload largish files via ajax. View your phpinfo to see where your php.ini file is located. Edit it, and change memory_limit to 256M. Also in php.ini, update post_max_size to be the same or larger. Restart server and double check that the changes took effect by finding memory_limit in your phpinfo output.