Soma

Finally!!! ;-)

Is it insider a repeater or anything you found out? Have you chance to install on different machine that could help further?

It works already. Have you changed an imagr field to a crop image?

Yes its the thumbnail official module thread. On mobile so too lazy to link to

We are trying to find out in the Thumbnails thread. It's not working when setting up a cropimages and not saving the field afterwards. The default settings doesn't get recognized (and saved in db). Only after saving the field again it starts working again. At least for me.

And if you reload the page is there the image ort not? Have you got a empty new line.. I dont know. It is working fine here now. :-/

Try to find czech translation as i think its the most complete regarding files. But youd have to create your own just for knwing which are there. You could also use grep or file search to search for patterns of the __() and $this->_() functions.

Got same issue here. Once I saved the field again it worked. Seems like the default value "thumbnail,100,100" doesn't work when calling it from FIeldTypeCropImage.module #55 https://github.com/apeisa/Thumbnails/blob/master/FieldtypeCropImage.module#L55 returns empty. The error is also from there few lines down.

Got same issue her on my local install with 2.2.13

There was exactly same question 1 week ago... ok again http://processwire.com/talk/topic/2584-numchildren-vs-children/?hl=%2Bnumchildren+%2Bcount $page->numChildren returns ALL children count. count($page->children); //or $page->children->count(); return only viewable pages by the user, which mean NOT: unpublished, hidden or non-accessible pages.

or if($users->get($username)){ // username found } not sure what you're doing exactly as always to give simpler solutions This would also work, foreach ($users as $u){ echo $u->name; } And if in an function scope where $users is not available: foreach (wire("users") as $u){ echo $u->name; }

Maybe still no the best, but you can also use this great module by Nico to add a delete action to page tree. http://modules.processwire.com/modules/process-page-delete/ Open admin tree and browse to users, delete one after another. BTW I think this module doesn't belong to Process module but Admin Helpers, Nico?

Use wire("page")->title if inside scope of a sn.. ERR function. Or with giving it through function call.

First there was an object. It was so lonely and had no home so we gave him an url. It was very happy and lived long until someone came and deleted it.

localSidebarText($firstline);

Memory? Have you changed the field from image to crop image?

http://processwire.com/api/cheatsheet/#page 5th entry in that list. $page->url is something so basic and covered all over the place on processwire.com. It's all under API, as it's the only thing you need to know to build templates/pages http://processwire.com/api/what/ http://processwire.com/api/templates/ http://processwire.com/api/variables/page/ http://processwire.com/tutorials/quick-start/navigation/ Or of course http://wiki.processwire.com/index.php/Main_Page. If not, there's even a basic site when you install PW which also is something you want to study first when starting with PW and come ask question if you don't understand something here. I think that's quite good and there's many people think PW has exceptional documentation for a OS project. For some strange reason we still have to figure out why some people think the opposite. There's also the forum which has tons of examples (might use google search to search) and simple questions get answered here mostly immediately.

Sorry to correct you here diogo, but <a href="/disclaimer">Disclaimer</a> works for all levels as it's absolute starting from "/" root. Still better in PW is <a href="/disclaimer/">Disclaimer</a> as it would do a redirect to add trailing slash which is default in PW. You could also use id of the page, so even if you move the page it still get's the right url to the page. <a href="<?= $pages->get(1023)->url ?>">Disclaimer</a>

It can be better explained with this: result = ifonething==something ? iftrue : iffalse;

My code example would be if you have the categories as the navigation/page structure to display the products assigned to them. $page would be the category page and categories is the page field used to select the category on the products. So in simple this find find all products that have the current category page selected. I'm on category page: Boys Nightware show me all products that have Boys Nightware selected. The question you have to ask is do I need multiple categories or not.

I'm officially very confused of what you both trying to archive. It all doesn't make sense to me and it seems hard to explain. You guys seem to be wired very different Either use categories structure you use as the navigation to navigate the categories, then show the products that has the current category selected. OR use categories with the products already inside and simply render them out with $page->children(), which is what NooseLadder is doing and using this approach doesn't make sense to have categories separate again. (I don't see where they would come into play when he already renders them out from the structure which already holds the categories).

Ah now I get it, the PagePaths module by Ryan to query page paths. Still same as above holds true.

@Jorge, I don't understand, are you making a module PagePaths that stores page paths in db? For what usage? Well unfortunately it wouldn't be useful, as the localized paths aren't same as page paths in PW but translated for each language.

Why have you categories tree, and then again a product tree which has the categories again? Do you really need that? Or do you need multiple categories? The way you have it now you already have the products categorized through structure. In your example using page field you would do it like this. // on $page Boys Nightware $prods = $pages->find("template=product, categories=$page"); if (count($prods)) { foreach($prods as $product){ // output prod } }

Unless you have not thousands of child pages in one branch I dont see much speed issues. Also theres options to add id to name which will allow even some more. Ive never used cacheing in pw and have some heavy sites I did not notice getting slow. Pw is fast and allows for scaling you might think it needs cache as with other systems.