pideluxe

In his latest blog post, Ryan annouces his works on the ProDraft-module for handling publishing workflows. While this is really great news, there is, at least in my opinion, the drawback that this module is a Pro-module. I really appreciate the tons of work Ryan puts into PW and see the need for getting some money back not being able to do work for some clients. I also like the idea of the Pro-modules, where advanced functions not needed by anybody is sold at a moderate price, i myself have bought some Pro-modules already. But such fundamental functionality like draft-versioning or defining a workflow for publishing should be in the core and made open source. I would like to raise a discussion about this, how it could be solved or what other developers think. All other major open source CMS have versioning integrated, so this a field where pw lacks behind and the chance with making that in core would open more opportunities for attracting more people using PW. But then getting this functionality only by paying a decent amount could draw them immediately back without getting the beauty of PW: Some solutions to solve this that cross my mind: Sponsoring: Already Avoine has sponsored some other modules being developed by Ryan, so maybe they or other companies that need drafting could stepin. Crowd-Sponsoring: If there is not one company or individual taking over the sponsoring, why not community fund this like a kickstarter-project? I think, most of us could spent at least the amount the Pro-module would cost or even more to make it open for public. Making only support Pro: Now all the Pro-modules get higher priority support by Ryan. Not only being the only person doing this, but maybe the only individual capable of supporting all the modules at moment, this can become a bottleneck in the future. Being open source, others can work on adding functionality and bug tracking and Ryan could concentrate on supporting. Other CMS are already doing this more or less (i.e. Acquia for Drupal). What do you think, should fundamental functionalities stay available in core for all or only being available as Pro?

Hi Caelan, at the moment i think the easiest way would be to disable the site while updating, make changes to fields and templates and upload your local template-folder to your live-folder. But to really answer your question, we need some more infos from you : Why do you want to copy the live DB to local DB? Do you need pages from the live DB to be backuped? Especially the users, why do you need to import them in the local DB? There a some articles in the forum which deal with this issue, the topic is continious integration or something like this.

You are saying that building custom applications in PW with the "everything is page"-mantra has its limitations - and that's right! No one has said, that every possible application can and should be built with PW-pages. PW is a Content Managment Framework, and for most of the contents you need for the web, its possibilities are more than enough. I think it is not fair by judging over PW while developing an ecommerce-application as your first application. Look at most of online-shopping suites like Magento or Prestashop, how difficult they were to develop just with php(-frameworks). Some applications are not best suited for PW (or any other CMS), at least with not building some helping modules or components, which could make it easier for plug the application together. Just another thought: would you have considered any other CMS with its built-in editing & API to develop an ecommerce solution on top of that?

Thanks for the replies, so this has not to be on the wishlist, it is already there! Maybe we could build an integration into the backend.

Would it be possible to configure a different path to the templates for different users/roles? E.g. for the user admin the templates reside in the folder /site/dev-templates/ and for all others users the templates lie in the folder /site/templates/? With this, you could have a production-version of your templates and when logging in as a special user you can work on your development-version simultaneously. Maybe there could be a function to check-in ready templates to the production-version.

First of all, you should link to the original image in the a-tag, not using the same url as the thumbnail. Next thing to check is that all UIKit-specific things like css and js are loaded correctly. Do you use the full UIKit or a customized version? If that is ok, it should work...

Just saw this announcement in my favourite german computer magazine c't. In the next issue on March 7th, there will be an article about our favourite CMS processwire. Anybody knows who is writing this article, someone from the forum? And be prepared for some traffic... For all non german speaking people, the text reads as follows: ProcessWire instead of Joomla, WordPress and others A modular content managment system, which adapts to the needs of web developers - instead of contrary. ProcessWire promises much freedom without ballast. Whether blog, club site or a complex business site - the free CMS handles it all.

There is the module JSON Installer by Peter Beulque, which lets you add templates, fields and pages via JSON files. This may be very helpful for fast creation or reusing typical scenarios.

Really great effort, thanks pete! Maybe we can bundle some more community functions into one starting page, like Ellis Labs is doing it for EE: https://ellislab.com/community. On their community page you can search for developers, look at showcases, hire someone for a job and have links to more community-driven content like the forum or blogs about the cms. I also like their developer-directory with more services being listed and the budget for the target customer. But i do not think the budget is a clever idea to let customers estimate the budget, thats the task for the developer. I would go instead for the size of the staff, freelancer, mid-sized agency or something the like, so that customers get an idea, how much manpower stands behind it. Also the dropdown with countries may be an side-by-side alternative for the map, when the count of developers gets bigger. This may be just cosmetic, but i think marketing the brand "ProcessWire" is becoming more and more essential. Bundling all the community efforts in one page is showing the power that stands behind the project and can convince uncertain customers or developers to go for processwire.

What is you best practice for preventing web browsers from loading contents of newly generated or static sites from their cache, so that the visitor always gets the newest version? I tried the following, but not with the desired results: Meta-Tag "expires" with date in the past .htaccess-method described here (german) Any suggestions?

Lisandi, i think you are mixing things up... A end-user in my opinion is someone who logs in the backend, changes text, images, data, inserts pages, moves them and deletes them. He doesn't have to care which modules are making his pretty website, he's just filling in the forms with his data. Maybe he updates modules or the core, but won't install any modules himself. A website-developer cares about how the data is brought together to form a decent website. He decides which modules he is integrating or he has to tailor for the specific needs for his client. Sometimes these two fall together (nearly everyone can install WordPress) and i think this is the point you are trying argue about. For end-users, who like to dive more into the systems, the steep in Processwire is still higher than for Drumlapress. If more such people are attracted to Processwire, the community will grow and also more people will actually develop modules for this system. The problem with the apps you mentioned is that maintaining, debugging, updating und error-checking is very time-consuming and most people don't make many with modules, but with the websites they build. If a core-update is breaking a module it is most likely not the fault of the developer of the module, but for changes in the API or the way ProcessWire does certain things. And before building big monolithic apps we should focus on building smart parts of software, which can than be glued together and expanded on the client/end-user wishes. Take a forum for example, there is the discussion module from apeisa which mimicks the essence of a forum, but is not such a beast like phpBB oder IP.Board, the same goes for e-commerce, blog, ... Sure, it would be great to have e.g. a working prebuilt e-commerce just after installing. Many man-years of developing stand behind such applications like Magento. I don't see the infrastructure for this at the moment for ProcessWire. Behind TYPO3 or Drupal for example stand firms which employ core developers, so they can concentrate on this and not on making money with actually building websites. For really end-user usability i would now go for different profiles, that are choosable at install. See my earlier post from me on this (also a great discussion about usability!)

I don't think a website-builder-tool for frontend is the way to go for processwire. Processwire is about structuring your data, making connections between that data and query that with the API. This is the work done in processwire for a developer or designer, to enable his clients (or himself) being able to collect the data and have it output in a proper way for a website or something else. If you use a builder for frontend-editing, the end-user has control of the formatting and arranging of the data, which sometimes is not desired. In my opinion, a CMS has to make constraints for the data to ensure the integrity and applicability, the PW-backend is very useful for this. E.g. a user wants to have three featured items on the homepage, you can easily do this with a website-builder as well using three equal-width blocks. But what if the user wants four or more items? If the developer was clever he thought about this in advance and made a slider if more items are added. (You can argue that you maybe can also add a slider element in website-builder... well, then this is example is not the best, but i hope you get the point) In conclusion, the developer of the website makes decisions for the end-user that his data is presented in the way the developer has supposed it to be. He is the expert in making the website usable for the visitor, the end-user is expert in his business and over his data. Btw. don't get me wrong, i like some of your ideas and i think themes should being brought into PW in any way former or later.

My brother produces custom textiles, so if there is a need for textile merchandise, let me know, i'll ask him for a quote.

You are requesting not to load any template file, thats breaking the backend functionality. So why bother breaking any others? Btw. which backend functionality was broken by doing that? Yes, thats true! Many germans here!

Set the alternative template file in the settings to a php-file (e.g. null.php) which only contains <?php

Why are you using the delegate approach, if you don't want to manage all templates with one file? That's the reason for this approach, you have only to manage one file for all (or some) templates.

@nico: i saw your module right after submitting my post, great effort! @pwired: I know all this already, i'm already in love with processwire! But what is about the devs who don't want to invest that much time in processwire to estimate its power? You could dive in the forums or use tuts, not everybody has the time or desire to achieve this at first look. So why not give them one more possibility? And after discovering the power of processwire, you could use the other ressources to answer upcoming questions for further customization of the website and using the api yourself. My suggestions would make possible to establish a basic theme groundwork for using different themes together, nothing more. It shouldn't been considered as the default way for theming or integrating this in the core. It's just another way one can go to processwire put in use.

I agree with OrganizedFellow, that templates and themes should be separated from core. But it should be made easier for a not so tech-savy webmaster/developer, to install profiles (= themes) and to customize them to their needs. To accomplish this, i would suggest the following: develop ready-to-use profiles (maybe these could be named "PROfiles"?) for the most demanded website-types, e.g. coprorate site, blog, gallery, portfolio, shop, ... make it possible to install PROfiles side-by-side and as easy as installing modules, so that a corporate site could easily extended with a blog by installing the blog-profile proceed the fields/templates for each profile with a separate tag, e.g. all fields for a corporate site are prefixed with "corp_" + field name (except title-field or maybe others) all these PROfiles should be based on the same css-framework, i would suggest foundation, as ryan used it already for a profile. this makes it easier to use different PROfiles together with consistent styling PROfiles should use minimal styling. But maybe different CSS-styles could be made available for color-schemes or similar the templates should contain layout-files for special parts of a page (think of widgets or partials), so that developers could easily reuse these parts to create their own templates (e.g. on a corporate site display a list of the lastest blog-entries in the sidebar) PROfiles settings should be made available on one admin-page, maybe each Profile get its own tab (or whatever ui fits best), where the respective settings are shown As one conclusion, this makes it necessary, that markup is generated by the PROfile for outputting the content. I already hear the complaints about that this is not what is processwire intended for, thats right. But this is totally optional, not in core and you mustn't use it at all, you still could use your own code. It only would make it easier, even for developers, to get started with processwire by installing already tested and optimised profiles by processwire pros. There should be a PROfile-team for maintaining and ensuring consistency of things throughout the distinct PROfiles.

Today i found a new, at least for me, kind of PHP-framework, which does look very promising. It may be a bit off topic for processwire, but for all programmers here that were using a framework like symfony or laravel, it could be a very interesting alternative. The project is called Phalcon and here is what they are saying about it: I have not used it myself, but not only the perfomance does look promising (from two to four times faster than every other PHP-framework), also the framework is feature-rich. It does not make assumptions about directory-structure. Have a look and tell me what you pros here think about it.

Another way to return all children including grand-children is to use has_parent: $all_children = $pages->find("has_parent=$parent, ...");

You can use PageEditPerRole from pogidude, which is based on Ryan's PageEditPerUser, but works on roles.

There is no shop at the moment. It's all running with processwire.

My younger brother runs a business for textile finishing and custom textiles in germany: http://meridian-gbr.de Based on foundation 5, which it really made easy to realise the layout. Modules used: Page Image Manipulator by Horst

As being a active member of this sports club, i've been asked to take over the website-development, so i'm developing this site in my spare time. http://tbe1844.de Developed first with Twitter Bootstrap v.2, but then converted it to version 3, which went comparatively smooth and easy. Every section could be managed by the staff from this section by restricting admin access for paths to users. This is still in development, especially the event managment needs some engagement. It is planned that it should be easy to generate a view of events distinct to a section or team and display this in a calendar or list... I implemented also a ranking list for the beach volleyball teams. It is based on the ELO-system used by chess or table soccer, the ranking points you get for a win or loss are calculated based on the points for both teams before the game. The ranking list is private, so if you wanna take a look, send me a pn. Modules used: Image thumbnails Fredi Hanna Code (you can insert tooltips to persons and locations in the editor) Page edit per user Map Marker

Lately i've put together this rather standard website for a german beer brewery manufactory: http://schwarzwald-gold.com Design is all by me, except the logo, which was done by a graphic designer. The new Foundation 5 was used as base. For the slideshow i used layerslider, the client could create his own slideshows and assign it to every piece of content. The client wished to have configurable blocks of content, which i realised with repeaters that can be adjusted to display just text, text with a left or right aligned picture and can choose to include a slideshow at the end of the block. The contact form is based on the code from Soma.