Soma

Try this $anzeige->save(array("quiet" => true, "uncacheAll" => false)); Any page save clears some cache. I don't know but it was always like this that when you have page saves on front-end templates happening. That might interferer with some methods that are cached previously. Not sure why prev and next are affected here, could be a bug or a side effect of an optimization for these methods that have some overhead. You can also call a $pages->uncacheAll(); before your $page->next and it won't work.

Then your <h1><?php echo $page->title; "Holiday Cottages"; if($page->editable()) echo "<p><a href='$page->editURL'>Edit</a></p>"; ?></h1> also outputs title of cottage and edit link? It's like you overwrite $page somewhere (header.inc?) or just the template like $page->template = "something" instead of $page->template == "cottage" ... Strange, and I don't see what's wrong. Only thing I know is that you're viewing a page that template doesn't have pagination enabled.

Maybe you should show us all template code... You either have a $page = $somethingElse overwriting current page. Or you render the page from another page.

That means that the page you're looking at, its template doesn't have page numbers enabled. Can you change it to this? echo "template: " . $page->template->name . " pagenum: " . $page->template->allowPageNum;

What do you get if you add this to your code just before foreach? echo "pagenum: " . $page->template->allowPageNum;

Location template aren't the items you want to paginated aren't they? Is location template = central-lakes or ambleside ?

Only thing I can say is that /adult/child/?page=2 Actually /child/?page=2 indicates that pagination is NOT enabled on the page you are on doing it, if it was it would be /child/page2

What's the url when you go to page 2? Is there something else special in your setup? Otherwise I would say pagination is not enabled or you have other limit calls previously in your code.

Thanks alot Horst for your time! The lines are hardly visible so not sure. These indized optimized png's I attached do have these lines when resized. When I do convert such an image to normal rgb png and upload it these lines are still there. Now It seems that it depends on the Photoshop version! I'm not sure how, but a png from a coworker saved in CS6 seems to work and has no lines. it's also when I open the optimized pngs in my CS4 the alpha transparency isn't shown and the modus is indized 8bit and the transparent shadow is black pixled, while in CS6 it shows the png correct as rgb and alpha transparency. The agency that does the images sent us unoptimized pngs and they seems to work.

They're attached. Thx

We have transparent product images as pngs. Now resizing them gives us artifact (lines) inside the image. I set sharpening to none and tried different things but no matter what there's lines in the resized thumbs. It even happens on non transparent images (visible on white background), but there it seems it can be avoided at least by setting gamma higher. Here a image showing the artifacts (contrast and darkened in PS to show the effect) It's barely visible but depends on the monitor and I see it clearly on mobile but hardly noticed on desktop. I am a little lost as to if this is possible to avoid.

There's one false too much

I'm the creator of the cheatsheet.processwire.com Searching for "->of" of "of()" works fine. It uses a fuzzy live search clientside with javascript using quicksilver (and some nifty code by jQuery creator John Resig). I remember having some problems with special chars like > but I think some of it was in Firefox but can't recall what. Actually I replace > with a > as this html entity is also used in source. So far I can't reproduce it but maybe you use a sepcial browser or anything else, so please let me know.

It important to know. In most cases if output formatting is on, a field is a string. So you output a property containing a string that is formatted in one way or another or gering the correct language. Either through the field itself or a text formatter. Once you turn of outputformatting it may no longer a property with a string but an object that may has methods or other properties. Most of the times this only matters on frontend context, while in modules and backend output formatting is never on unless it's explicit used or a module deals with pages that come from via a variable from a frontend template that uses a module method. Or if you need a date as timestamp you can try it off or use getUnformatted() method. Setting a field only needs outputformatting off if you do this in frontend context and for fields that are more complex and have outputformatting that turns an array or object into a string ready for output. Input formatting is mostly just used as far as I know for datetime field used for inputs in a form, and has nothing to do with how you set a value via API. Could be wrong though.

Or if inside a string and multiple chains use {} echo "{$page->images->first()->url}..."; If only one chain it doesn't need it like echo "$page->url";

Enjoyed raeding your post rick. What was the case that brought you back to PW exactly?

Ryan already has the module to edit config in backend since 2.5 in his repository. I'm working on a new multisite version but doubt it will be ready anytime soon.

How about multisite reading config.

No you can (with my example) add entries to the $config->httpHosts but it's won't have an effect cause the whitelist is checked before you can do this in a module or template or whatever. I'm not sure why you'd want this. It's not like you change this all the time.

You can also just leave config httpHosts blank. You could update it via API like this $hosts = wire("config")->httpHosts; $hosts[] = "ww.domain.ch"; wire("config")->set("httpHosts", $hosts); This should be in a autoload init(). But I'm not sure it be early enough to work.

Yeah $options is a template var. If you need it you shouldn't overwrite it.