Leaderboard

My list of favorite CMS with custom fields: 1.- Processwire 7.- Simphony 8.- Mod-x 9.- Bolt 10.- Couch The first 6 are processwire.

Ever since my last experience with 1&1, their infamous “support” and their horrible performance in smaller hosting packages, I have explicity banned certain (German) providers. I will decline new clients which insist on staying with those hosters, and I can only advise to adopt that policy. Most clients don't understand the technical limitations that come with bad hosting, and the result will always fall back on you. It's just not worth it.

I've gone to bed last night after the regular gametime, as it's just sad to see a game, where both teams try to not loose the ball. While the Dutch seem to have a fine team, I'm just not impressed with this ultra-save backpassing strategy, and Argentina did almost the same yesterday.

I would do the segments to keep it DRY. In my opinion there are less management issues, since the data is in only one place. I don't see any problem for SEO if you go this way, just create the site map accounting with those pages and for the crawlers the pages will be as real as with the other method. I also can't think of a performance issue created by this, would probably be worse with Hanna code.

Dynamic Roles are a powerful access control tool for ProcessWire. They pick up where traditional roles leave off, and allow you to assign permissions at runtime based on any factor present with the user. Once a user receives one or more dynamic roles (at runtime), those dynamic roles then specify what pages the user can view, edit, or add children to. If traditional roles are a sledgehammer, Dynamic Roles are a scalpel, allowing nearly any finely tuned access control scenario. Traditional ProcessWire roles are limited to assignment of view/edit/add access on a per-template basis. Dynamic roles go outside those limitations and enable you to assign that access based on any factors present with a page (i.e. match any field values). Dynamic Roles assign new access, but do not revoke existing access provided by traditional roles. As a result, Dynamic Roles can be used together with traditional roles, and the two work beautifully well together. Though Dynamic Roles can also replace all situations where you would use traditional roles for access control assignments. If using Dynamic Roles to assign page-view access, you would typically want to use traditional roles to revoke view access from at least the "guest" role at the template level. Then use Dynamic Roles to assign view access to those pages in a more granular manner. This module directly affects the results of all page getting/finding operations by applying the access control directly to the database queries before pages are loaded. As a result, it is fast (regardless of scale), pagination friendly, and requires no further intervention by the developer other than configuring the dynamic roles as they see fit. Because it relies upon new features present only in ProcessWire 2.4.6+, it requires the current dev branch. Sponsored by Avoine Concept by Antti Peisa Code by Ryan Cramer PLEASE NOTE: This module is in pre-release state (like the PW dev branch it requires) and is not recommended for production use just yet. Though we do appreciate any testing and/or feedback that you are able to provide. While not required, this module benefits from ProFields Multiplier. If you have ProFields Multiplier installed before installing this module, it will make this module more powerful by making all of your access control selectors have the ability to use OR-group conditions. Depending on your access control needs, this enables you to accomplish more with fewer Dynamic Roles. How to install Make sure you are running ProcessWire 2.4.6 (dev branch) or newer. Download from GitHub (we will add this module to the Modules directory later). Place all files from this module in /site/modules/DynamicRoles/. In your admin, go to Modules > Check for new modules. Click "install" for the Dynamic Roles module (ProcessDynamicRoles). Click to Access > Dynamic Roles for the rest (see example and instructions below). Example and instructions Lets say you ran a Skyscrapers site and wanted a role enabling users with "portmanusa.com" in their email address to have edit access to skyscrapers designed by architect John Portman, with at least 40 floors, and built on-or-after 1970. Yes, this is an incredibly contrived example, but it is an example that also demonstrates the access control potential of this module. 1. In your admin, you would click to Access > Dynamic Roles. 2. Click "Add Dynamic Role". Enter a name for the dynamic role, like: "skyscraper-test-editor" and save. 3. Under "Who is in this dynamic role?" section, click "Add Field" and choose: Email => Contains Text => "portmanusa.com". This will match all users having "portmanusa.com" in their email address. 4. Under "permissions" check the boxes for: page-view and page-edit. 5. For this contrived example, we will assume the user already has view access to all skyscrapers, so we will leave the "What can they view?" section alone. 6. For the "What can they edit?" section: Click "Add Field" and choose: template => Equals => Skyscraper. Click "Add Field" and choose: architect => Equals => John Portman. Click "Add Field" and choose: floors => Greater Than Or Equal => 40. Click "Add Field" and choose: year => Greater Than Or Equal => 1970. 7. Click Save. Now users matching the conditions of your dynamic role will be able to edit the matching pages, but not any others (unless assigned by traditional roles).

Hi, just wanted to say hello to PW. Some former WebsiteBaker users made me aware of PW, so I decided to give it a trial this weekend. From my past CMS experience, I decided to convert an existing SilverStripe template into PW from scratch. This way you will quickly get a feeling about the system itself, the backend, template system and available documentation. After watching two videos and reviewing the API documentation, I started over and had a clone of my SilverStripe site running in less than two hours. I started with WebsiteBaker back in 2006, did some sites with ModX and Contao (formerly known as TypoLight) and was even forced to deal with WordPress by one client, before I finally switched to SilverStripe around 2009. My first impression of PW was: cool little CMS with easy backend, awesome API. Somehow feels a bit like a mixture of WebsiteBaker, Contao and SilverStripe to me, taking the best from all of them while skipping the bad parts. Respect. Looking forward learning more about PW. Cheers cwsoft

Tested. This should work... $p_user = wire('user')->name;// set user name $p_page = wire('pages')->get("title=$p_user");// try to get page with the same with user name $p = $this->modules->get('ProcessPageList'); $p->set('id', $p_page->id);// setting the parent page to user name page Edits: Edited code above to show class/module use context... Also edited some typos in your original code (which I also subsequently copy pasted )

Well the cool kids use remote control, Airplane bahh... Glad you found it. I have no idea why.

What do you mean by no success? I also see that you haven't rendered your form...i.e. echo $form->render();//or return if in a function...

Hello, @totoff: Tried to install the Modesta theme, but I somehow fail to "activate" it. Downloaded it from the link you provided and copied the content of the ZIP file to: /site/modules/AdminThemeModesta. Then I went to "Modules -> Check for new Modules" and clicked the "Install" button. The Modesta theme showed up. However, I seem to be too stupid to get the theme activated. Tried to logout, cleared browser cache, nothing happened. Any advice? Cheers cwsoft @blad: First time I heart about the CMS listed at postion 9 and 10 in your list

There is definitely issues with last commit and module requirements. I opened discussion about that in GitHub (see the last commit in dev). For now I suggest using second latest commit.

Did you know that a lot of ex-modx'ers found refuge in processwire ? You can find them here in the forum.

Very tense game that was. Commiserations my Dutch friends..... As for Argentina (or the Dutch for that matter)....I don't see them going past the Germans. Barring the impossible, the Germans have it! Best team of the tournament IMO.

http://modules.processwire.com/categories/admin-theme/

It has PHP and one SQL DB. Chances are good. But the offer is very poor compared to other hosting companies. If you don't need 1&1 for a particular reason better check out other offers.

Blender - Gimp - Photoshop ?

Wow! No words - thanks Avoine and Ryan

kongondo, thank you, man! It worked like a charm! Wow, another great advance in my project. Can't thank you enough! And it was not too much of a puzzle, as it seems to me now One small note for those who would like to use this trick in a ProcessPageEdit-based module: if you construct your own form for ProcessPageEdit, then put the rendered ProcessPageList in an InputfieldMarkup (and append it to an InputfieldWrapper field if you want to): $form = $this->modules->get('InputfieldForm'); // prep the form $wrapper = new InputfieldWrapper; // a wrapper $wrapper->attr('value', 'List of available articles'); $p = $this->modules->get('ProcessPageList'); // kongondo's code goes here $p->set('id', 9999); // setting the parent page $pageTree = new InputfieldMarkup; // the placeholder $pageTree->value = $p->execute(); // fill the InputfieldMarkup form field... $wrapper->add($pageTree); // put inside the wrapper... $form->append($wrapper); // append the wrapper Because Process<something> modules do not append directly to forms, you know

It would be correct: $sanitizer->pageName("Größen", Sanitizer::translate); No it's not dependent on special thing. It's used to translate titles to the name. Nothing to do with translations. This was added at some point around 2.3 after lots discussion and isn't documented on API section (yet) but on cheatsheet http://cheatsheet.processwire.com/?filter=pagename.