bfncs

I think this sounds like a good idea and might also make exchanging stuff except complete prebuilt templates easier. There was a discussion about continous integration in this thread and I think mindplay.dk is working on it. If we have a reasonably stable thing here, I think it wouldn't be too hard to have something like a "migrations" file including all needed changes to "install" a template.

I haven't heard of plans for an official book, but there once was some chatter about on this forum already so maybe someone else has? Meanwhile, have you already tried reading through the API section of the Processwire site? While not made out of paper, theses pages are still very bookish to read. You can go through them from one chapter to the other, slowly advancing through all important concepts. It doesn't cover PHP itself, so you will have to learn at least the basics of PHP before. Afterwards, the default site that you see right after installing Pw is a great and simple project walkthrough. Just look at the templates and fields in the backend and check out the commented code of the templates. If you do understand what is going on there, you are ready to do simple project. That being said, I doubt that there is something like "the one way" to do a project in Processwire. That pretty much relies on what you want to archieve which is a strength for the system but makes it harder to pick up best practices.

This thread has gotten quiet old but I still think there has been no approach to solve the problem until now. Any news on this one?

Very nice, I also played a little with Angular lately and it's a pretty neat tool, so it's very nice to have it packaged up as a Processwire module already. I'm definitely looking into FieldtypePoll later, looks really promising.

MarcC, thanks a lot for the link to SQL Buddy! I already knew about Adminer and used it sometimes, but SQL Buddy looks much more appealing and is very quick and easy to use, too. I think both of them would make a really nice backend module.

Thanks for the link, this really is an interesting approach. The idea is quite simple, but I've never seen this implemented and it really makes sense to me. I can imagine that this would make a great addition to apeisas great Thumbnail module. This behavior might lead to a more sensible default crop than just cropping from the center. It would have to be optional though, ideally on a per Field basis, because as already pointed out, it may not make sense for all types of images and I also think that it might use up quite a lot of resources on the server.

I think grunt is close to the most interesting thing happening around the organization of frontend projects. While it is certainly great that it can do the dirty and boring work for you, it also really looks like us web developers finally have an open, stable and really flexible way of sharing our process. I have the feeling that with all the projects on Github that use it now, grunt had really come to stay, so it's definitely worth a look for everyone working with the web stack.

I was getting along fine using gedit with some plugins tailored to web development for quite some time. After compatibility issues with the plugins on one of the occasional Ubuntu updates I tried a lot of different stuff and finally bought PHPStorm. This has probably been the best invested money in the last few month. It's an unbelievably feature rich IDE that has all the things I ever wanted and things I never knew I would want but am using on a day to day basis now (file watchers, zen coding, etc). What is amazing: this stuff really doesn't get in your way if you don't want to use it. But enough gushing praise, this wasn't supposed to turn into a commercial... Ryan, how exactly do you configure PHPStorm to behave like Vim? Are you using the IdeaVim-Plugin? This sounds like a really useful combination because Vim is so ubiquitous. You nearly can't get around it if you have to work on servers via SSH (and don't want to use nano), so it's great if you can use the same stuff in your IDE.

Congratulations and all the best to you and your family!

Absolutely right, the first thing you should do when you want to develop your own templates is reading through all of the template files of the default site profile. Afterwards, be sure to also checkout Soma's Markup Simple Navigation module that makes rendering a really usable navigation really easy while still providing a lot of flexibility.

Edit: somehow I overlooked, that teppo already found the exact same thing ages ago... Don't mind, I just have to (!) get something done with Typo3 and try to make it standable by surfing through the Processwire forums... While directly linking to the URL in your menu is certainly the better idea, I think you just have a small error there: Should have been: <?php $session->redirect($page->redirect); I've been using this approach for quite a long time without any problems. It's nice if you want to provide a link to an external URL that may change over time.

I second Soma's argument, it really is a problem if your URLs are dying fast, and already constructing it with a massive amount of URL direction is also not a really good idea. The approach with a page field should be working out nicely in your use case. You might write a smallish module that hooks into Pages::___save() and checks whether a saved page is newly created and a child of your archive page and if yes adds it to the pages field on your front page automatically to keep it comfortable for the editors. That being said, I also think, it would be great to have the possibility to add new pages with manual sorting on top in the backend. Can't imagine a simple and scalable way to do this without any slowish kind of indirection, though.

Thanks a lot for this Ray, it is a really good read and something you can point your customers to, if they are in doubt because they've never heard of Processwire before. I would really like to see a case studies area on the main Pw site if there are some more of these.

...and Pete, you're right about the hardware aspect, didn't think about that. So, either you could get your hardware to do something web-compatible (like emulating keyboard inputs) or you might go bleeding edge and use something like a chrome packaged app that supports serial, usb, etc. If this doesn't suffice, you might install an instance of node.js on your local pos machine to read your hardware (I remember this was quite easy to do on a linux system) and connect it to your app with web sockets. None of this ways will enable you to use custom hardware on mobile devices, though, so probably the route to go there would be a native app (which could still communicate with a backend built with Processwire). Please keep us posted about which way you go, sounds quite interesting.

What you're doing there sounds interesting. Are you going to have Processwire itself online then or will you copy the created JSON files to be delivered by your node server? In the first case, you might try whether it isn't already sufficient to employ site caching to archive your desired performance. In the latter case you might install Processwire locally, make proper JSON templates for your data as if you wanted to just normally display them and build an index with links to all of your JSON files. Afterwards you can use a website scraper (Wget with the recursive option would be sufficient) to generate all your content, save it and copy it to your node server afterwards. You might even use some toolset (Cronjobs or the likes) that automatically transports your files to the server. The other possibility would be to write a Processwire module ("Static website exporter") that iterates the trees, renders each page with it's proper template and saves it to some folder on disk. You will probably have to deal with saving the export state and using some extent of asynchronous building to not run in a PHP timeout. You might even go crazy and build a small PHP CLI application, that includes Pw and does everything with a shell command. If you're really planning not to regenerate the files very often, I would definitely go with the second method because what you will have to do is a one-liner on your console.

Have you looked for any in-browser errors? What browser are you using (I had some problem once with a really old version of IE)?

I imagine what you want could be archieved nicely by some kind of offline-capable Javascript MVC app built with something like Angular.js, Ember.js, Backbone.js or similiar frameworks. This way you can make it feel very quick and at least do some meaningfull stuff, when the server is offline. You could still use Processwire for managing the data and quickly build a JSON API to communicate with.

Hi there, very interesting discussion with good arguments going on here. I think while all the possible solutions pointed out already will work, what this kind of content editing really needs to be user-friendly is be a nice editor. I imagine something like the usual WYSIWYG editors that has an added area with predefined drag-and-drop content blocks. You can then drag each one at a place in your existing content where it's content (and look) is editable. Probably this is done most easily with a grid-based approach. The hard part of this would be building the editor then, integrating it into Processwire should be quite easy. I would be really glad if this kind of thing exists, because it might come in handy at some point, i.e. for custom marketing landing pages.

Ah, thanks so much, that was what I was looking for! That day had too much staring at code which makes you blind eventually. I'll try to work out the main question tomorrow, then, should be easier now.

Hi there, I'm currently writing a module that needs a Process action to generate some previewable HTML+CSS Code. In my code I'm doing something that boild itself down to this, to generate the preview: public function executePreview() { $p = new Page(); $p->template = $this->get('template'); // configurable module variable return $p->render(); } Would be fine if this wouldn't render inside the default admin template (that I need for other actions of the same controller). This inserts a lot of CSS and JS that I can't use here. The Preview action will be embedded into another action as an iFrame and I already tried calling it with ?modal=1 which get's rid of header, footer and sidebar, but still loads the CSS and JS. What I'd like to do know is to programmatically change the template of this view, but I wasn't quite successful. I inserted this in the above code to make it render another inside my module folder, but it still renders inside the default admin template: $this->page->template->set('filename', $this->config->paths->MyModule . 'my-blank-template.php'); While this would be pretty hackish, it also doesn't work... but I really hope that someone of you has a better answer to this problem? With kind regards, Marc Edit: While stepping through the code I wondered, where exactly the $page->render() function is?

Thanks a lot for answering, Ryan! This is exactly how I feel about it, but experience shows the average user doesn't get it. You're completely right about the fact that every form on the whole wide web works like this, it's still better to be prepared That sounds just great!

I don't feel good about capturing this thread, but I wanted to ask for exactly the same: Even with the great Form Save Reminder in place, it would be great to open all "View" links in the backend in new tabs/windows. Any ideas on how to archieve this the clean way?

About Gravatar: This is also pretty easy to do in PHP, just have a look at their documentation. No need to request data from their API upfront, you can calculate a hash and assemble the image's src by yourself on the server. This might be something that would be nice to have as a simple module though.

Hi Aren, Joss should have pointed out nearly everything you need to know about the image slider integration in the backend. The rest should be pretty straightforward, just add fields for all kinds of information you want to add for your project: Project Title (Text) Project Description (Textarea, maybe with TinyMCE) Tags (Page with Autocomplete, have a look at this thread for more information on how to implement it) Project date (Date)

This module is really working great, thanks a lot for your work on this, Ryan! While using it I stumbled upon a smallish bug with uppercase chars in field names, but to fix this probably needs changes in core. Please share your thoughts on this one.