MadeMyDay

omg. OMG.

Well, then you have to think about some other approaches. Everything is possible. Scenario 1: Duplicate all news: - Use url segments. On subsite's overview list all news from main site and don't link to their url but to /subsite/news/$news->name. The /subsite/news/ overview page has url segments activated. You identify the news, include it the same way described above and you're done. Scenario 2: Only selected news: - Use a checkbox on the original news template and list only the news that are checked on the subsite. Rest as described in 1. Another approach would be to use RSS for the import. As I said: Everything is possible, you only have to identify the approach which is less work for you and your client.

exactly. Since I assume you want an 1:1 copy (regarding content) of your main site's page in a different template.

Define a field type "page", name it like "includePage" or something like that and add it to your subsite's template. If you wish to include an other page, just select it in your subsite's page. In your subsite's template just add something like this on the top: <?php if(count($page->includePage)>0){ // is there a page to be included? $page = $page->includePage->eq(0); // overwrite page fields with the included page } Now the $page object is overwritten with the included page object.

Usually they don't break but display the mobile version if a "mobile first" approach is applied. If IE8- should be supported, I would rather polyfill the media queries for them. But I think this is a more a religious question

Well, browsers always try to fix invalid markup themselves. You have to check the generated source code (Right click -> view source code), not the "live" source code from FireBug. Hm. I don't understand why one should offer a responsive version to a browser which cannot handle media queries. Also IE8 and IE7 are not used on mobile devices, so the only group you target are people with a very small desktop screen. Or am I missing something?

Soma, thank you. As always: Easier than I even dreamed of.

Struggling on a problem with the new PageTable field. If the field is set to a custom page holding the entries, I don't know how to define the original page where the PageTable field is included. Say I have a page with id 1040 and my entries are stored under a page with id 1020: If I render $page->parent->id, I always get 1020 (of course). How can I access the id where the PageTable field is originally included (here: 1040)?

You don't close the <ul> of your blog posts (2nd error). 3rd error is a following error because of that. 1st error is a common html5 boilerplate thing which shouldn't concern you. One thing in general: Put the Javascript to the bottom and I don't know the CSS framework underlying, but using CSS expressions for responsive web design seems a bit outdated ;-) Besides that: The site looks good and does fit to the topic. I know your struggling with given font and colors, but you made the best out of it!

Unobtrusive support at it's best

I want to like this post multiple times but the forum software doesn't allow me to do that. So: Like. Like. Like. Like. Like. Like. Like. Like. Like. Like. Like. Like. Like. Like. Like. Like. Honestly: It's comparing apples to oranges. PW is strong. It is the most intuitive, the best designed (in terms of API and UI) CMS out there with the smallest footprint possible. I recently used again the multi language support. I mean, look at the API. Look at the solution for a problem each CMS has. It is just beautiful. You have several ways to solve that problem (as always with PW). But it is there, written in the core, well documented on one(!) API page, because it just works intuitively, it is just simple. Every addition to the core is an addition which solves general problems and the way Ryan solves them is just genius. There is no addition you have to scratch your head when reading the new API. You always think: "wow, clever". And this is the way to go with the core. Make it simple, make it smart, make it beautiful! Regarding themes, profiles and such: It is already possible. It is out there. Provide a custom profile for a real estate agent: Give him a set of modules, fields and templates to handle his offers. This is no problem! This is even easier and more flexible than it ever will be in WordPress, because it goes way beyond a custom theme and can be installed with one click. But: Nobody will care at the moment, because ProcessWire has no own category in theme/template websites, because ProcessWire has not the attention of other plug&play systems. And this is totally okay! Think of TYPO3, a widely spread system, mostly used in enterprise environments and even on small sites (dunno why), but the point is: Everyone (at least in Europe) knows it, it is one of the most used systems in the business sector (not on private children soccer club websites). But: this is the goal! Be the system developers use. Don't be the system every idiot wants to use. Concentrate on performance, flexibility and most of all: beauty of the API! The rest will follow.

Aren't site profiles exactly made for all this? Why are there so few profiles made yet? I think because PW was never intended for plug&play and everyone learns that (after perhaps 60 minutes time if 30 are too short). And this was and ever will be a good decision.

Well, I always use Cycle2 because it is very open configurable and nearly everything is possible. For your thumbnails for example look here: http://jquery.malsup.com/cycle2/demo/pager.php If you don't want to build your own full size background, just use this on top of cycle2: http://www.aaronvanderzwan.com/maximage/

Can you provide a link to that said slideshow? Seems very limited.

Also no hidden pages in the result ;-)

That would change nothing since the children() needs the selector. and include=all would also include unpublished children which I guess is not desired.

Should be: $pages->get("/about-us/meet-the-team/")->children("include=hidden"); since the children are hidden and not the parent. And also I prefer to get the parent by id since changing the page name would make your selector return nothing. For example if your team page has id 1020: $pages->get(1020)->children("include=hidden");

I totally agree. It's not even my own wish, but I hear it more often in the past year since more and more people are considering PW as an alternative. I think such a feature would be a good reason for CMS switchers and/or a good marketing thing. You know, like "look how flexible it is, you can build your page even in the backend very individual with drag&drop and eye candy and such stuff... blah blah" ;-) PageTable is great, repeaters are great, all the new pro fields and of course all your modules are great. The flexibility is endless. You know that, I know that, every experienced PW user knows that. But - as I said - for marketing reasons such at a first glance flexible features or on the other hand the learned and for several years used solutions like a central media manager would be nice. They could be built on top of the PW core without losing the PW paradigms. People are not interested in how something works as long as it works for them

Can't remember my test two weeks ago. But it isn't inpage, is it? It's more a usual page layout in a lightbox, right? What I have in mind (and others, too) is an integrated repeater-like way with choosable layouts. But honestly: This is no deal breaker, but it is something (perhaps the only thing) PW can't do out of the box.

Yes, kind of. But then you get a row of a PageTable which isn't the same (of course) as a individual repeater template, whose layout you can control. The other systems (I've been told, don't know actually, would never cheat on PW) allow a more visual approach than just a row of different data fields.

I think the main "click" you need in your head is understanding the concept. Everything is a page with fields. See it as data container. You need to reuse pages or their fields? Put them somewhere hidden and reference them where needed. You need some kind of repetition of content? Use repeaters or sub pages. Or take a look at this differentiation from our master: Comparison of Repeaters, PageTables etc. The only thing ProcessWire cannot do (yet): A kind of repeater where you can define the kind of content block you insert (like TYPO3 or Contao does). But also this can be done with a clever combination of repeaters and PageTables and... whatever. There always is one or more ways

There is no central media management in PW by design. Images and other media are always tied to a page. If you want to reuse them, build a central image/media folder and use a page selector for selecting/referencing them. Also use the Page List Image Label module for a better visual selection.

Why not maintain two branches according to the PW branches? stable and development?

I am not sure that the problem are passwords only. I still have one installation where I can only login via the development sub domain and not with the live domain. This is exact the same installation in the same folder with both domains pointing to it, http hosts are both set. The error message also is not "wrong password" but this one: Saying "Login failed".

Same here. Since 2.4. this happened two times, but I can see no pattern. Sometimes it works, sometimes not.