Soma

Maybe a well build html structure that suites well for theming only through CSS. Like zen garden.

If such a case google search is better... https://www.google.ch/#hl=de&output=search&sclient=psy-ab&q=site:processwire.com%2Ftalk+404+error&oq=site:processwire.com%2Ftalk+404+error

Marty, great work as always. I noticed that the french pages use english titles in the url. Not sure if it's intended or not, but would be easy and make sense to have speaking urls.

This should do it throw new Wire404Exception();

@Nico, the module knows it because you have to enter it. We use the language page title field.

Weird when I tested this with getModuleID, It'd always return 0.

Yes if I disable debugging it works... which means when I turn it on (always on when developing) the multilanguage doesn't work on frontend and admin. :/ And I love debugging enabled when developing. It also breaks the admin, this particular one appears on all pages even frontend. If adding the check wouldn't harm anyone I would be thankful.

Well it seems it only works if you use the process module id. But no idea how to get that. As far as I know the process is handled through names. Look at admin.php in core. Edit: So only solution I see for now is looping and checking for $page->process == "ProcessName".

Not sure, have you tried adding "include=all" ?

Well I tested it quickly. Since the caching seems to be handled by $page->render(), it makes sense anyway to use it for rendering the page instead of the include. $page = $modules->get('LanguageLocalizedURL')->parseUrl(); echo $page->render(); This works with caching pages.

Hi wanze and welcome. Thanks for reporting and testing. We will look into it. This module uses the same sanitizer page name translation as PW internally for pages. I'm surprized that "persönlich" would have been "persoenlich" without changing the replacements beforehand. I think you got tricked somehow.

I got this site on a server from a friend and it has php 5.2.4 latest PW in a subdir. Everything works fine but as soon as I install language module I get this: Warning: Wrong parameter count for debug_backtrace() in /----/pw/wire/core/LanguageFunctions.php on line 32 What is it about? Also can't get translation to work in templates. Edit: When I change the line: $traces = debug_backtrace(defined('DEBUG_BACKTRACE_IGNORE_ARGS') ? DEBUG_BACKTRACE_IGNORE_ARGS : false); to the following it works again. $traces = debug_backtrace();

Hi and welcome to the forums. Or try enter something wrong in the .htaccess like "&djsjoocklsc" and see if it throws a 500 server error.

The prefered, simpler way is to make the user when created via API unpublished: $user->addStatus(Page::statusUnpublished); See cheatsheet addStatus Then the user can't login yet. And the admin can just go and publish the user (same as with pages) in the admin. Users are pages so the page API applies here same way as it is for pages. Or using API to publish $user->removeStatus(Page::statusUnpublished); See cheatsheet removeStatus The different system flags are also on the cheatsheet.

Go on templates, filter to show "system" templates, edit user template.

PageListImageLabel Marty requested and sponsored a new module little while ago. http://processwire.c...t-image-option/ I just wanted to create a separate release thread. Many thanks to Marty for sponsoring and making this possible. This just shows how great this community is. So here it is the Page List Image Label module. It enables you to add thumbnails of images from the pages in the admin page tree. Download: http://modules.processwire.com/modules/page-list-image-label/ Github: https://github.com/somatonic/PageListImageLabel A screenshot of it in production. (old version)

Great work Ryan, already looking very good! What do you plan for supporting themes?

Nope sorry.

Look the posts above....

Just as input... http://processwire.c...eciprocal-data/ I was doing some tests and having fun coding a modules that lists links to selected pages in page fields. https://gist.github.com/2878361 Feel free to take it and do whatever you please. Possible to add a modal to edit pages directly from the link.

I don't see an easy way. *head explodes*

I think you can do it pretty easily with what's there. As already discussed. I don't think there's much performance issues with the approach you mentioned. You could even use markup cache if you got thousand and thousand of pages (PW is very performant). PW is designed to work very performant using page references and inheritly check upwards the page tree, this is where PW excels using the hirachy approach. It would be easily possible with certain modules (ie fieldtypes) to list selected block from a page all up to the root and list them depending if they're falldown or not. There would be some trickery to it UI wise but I can imagine some simple setup. Nonetheless we are here to help and give hints. It's always nice to see what other people come up with.

If what you find in PW using page references and some simple logic of inheritance, maybe using checkboxes is not an option (also ui wise), there's no way to do this out of the box without getting your hands dirty. PW isn't designed to do this very easy. Using page reference won't give you all you want but at least some way. If your block inheritance concept demands functionality that is not there you'll have to code it. And I can imagine, depending what you exactly need, that it would require a lot of complex coding. But maybe I'm wrong Personally I can't think of a way such a system would be easy to implement. Also it would have to be dead simple for editors to grasp it and don't lose control. My experience with such systems is like with inheritance of access control, which can get out of hand quickly.

The solution to your problem is to change it to this: $out = preg_replace($regex, '$1' . $page->name . '/$2', $out);

I'm not really sure without testing and it's damn difficult Not sure if you noticed there's a collaborative module going here Not sure if that would work with your setup (but looks like), it's so far pretty stable, but not tested heavly. But without using it we will never know. If your project isn't that complicated and may be a good canditate to give it a try. There's only very little you have to do to make it work (not like above) and can be disabled without problems. It even works with default install and one additional selector on the navigation to even publish languages on the page separate (checkbox). If you have more questions, put them there in the thread and we can surely help.