Wikizone - Benutzerbeiträge [de]

ProcessWire - Pagination

2018-08-22T05:55:45Z

79.219.79.191: Die Seite wurde neu angelegt: „Seitenbrowser / Pagebrowser in ProcessWire https://processwire.com/api/modules/markup-pager-nav/ * Im Template erlauben Beispiele Kindseiten auflisten <syn…“

Seitenbrowser / Pagebrowser in ProcessWire

https://processwire.com/api/modules/markup-pager-nav/

* Im Template erlauben
Beispiele

Kindseiten auflisten
<syntaxhighlight lang="php">
$options = array(
'listMarkup' => "<ul class='uk-list uk-list-striped'>{out}</ul>",
'pagerOptions' => array(
'listMarkup' => "<ul class='uk-pagination'>{out}</ul>",
)
);
$content = $page->children("limit=10")->render($options);
/*
* Note that the render() method above is from the MarkupPageArray plugin module.
* It does nothing more than iterate through the provided pages and make an unordered list,
* optionally with pagination.
</syntaxhighlight>

ProcessWire - Selectors

2018-08-21T16:57:09Z

79.219.79.191:

== Operatoren ==
http://cheatsheet.processwire.com/selectors/selector-operators/

== Beispiele ==
=== Selektoren in Option Fieldtypes ===
<syntaxhighlight lang="php">
$optionsfield // return id (string)
$optionsfield->id; // return id (int)
$optionsfield->title; // return string USE THIS or
$optionsfield->value; // return empty string or value (if your option settings like '1=value|title')

// dot syntax in selector string
$pages->find('optionsfield.id=2');
</syntaxhighlight>
=== Seiten finden ===
<pre>
$skyscrapers = $pages->find("template=skyscraper, sort=-modified");
foreach($skyscrapers as $skyscraper) {
echo "<li><a href='$skyscraper->url'>$skyscraper->title</a></li>";
}
</pre>
=== Page Reference auf diese Seite ===
https://processwire.com/talk/topic/1071-page-fieldtype-two-way-relation/
echo $pages->find("field1=$page")->render();
If the page isn't part of the front-end site, then I'll remove view access from its template. Or if it is part of the front-end, but I don't want to show the relations, then this:

if($page->editable()) echo $pages->find("field1=$page")->render();

Though I almost always integrate these relation-revealing pages into the site structure, as it's rare that this information doesn't have some value to the site's users too. This is an example of one that locates all pages referencing it in a field called 'country':
https://www.tripsite.com/countries/croatia/

=== Punkt Syntax ===
$architects = $pages->find("template=architect, city.title=Chicago");
$buildings = $pages->find("architect=$architects");
That's easy enough, but wouldn't it be nicer if you could just do this?
$buildings = $pages->find("architect.city.title=Chicago");

$buildings = $pages->find("architect.city.state.abbr=IL");
Broadening further, perhaps we want buildings from all architects in the USA:

$buildings = $pages->find("architect.city.state.country.abbr=USA");
Or perhaps both USA and Canada:

$buildings = $pages->find("architect.city.state.country.abbr=USA|CA");

=== User ===
http://cheatsheet.processwire.com/users/users-methods/users-find-selector/
Find all users whose email address ENDS with processwire.com and create a link to email them
<pre>
$items = $users->find("email$=processwire.com");
foreach($items as $item) {
echo "<li><a href='mailto:{$item->email}'>{$item->name}</a></li>";
}
</pre>
Find all users who have "fred" anywhere in their name

$items = $users->find("name*=fred");
Find all users who have the "superuser" role

$items = $users->find("roles=superuser");

ProcessWire - Selectors

2018-08-21T16:49:04Z

79.219.79.191:

== Beispiele ==
=== Selektoren in Option Fieldtypes ===
<syntaxhighlight lang="php">
$optionsfield // return id (string)
$optionsfield->id; // return id (int)
$optionsfield->title; // return string USE THIS or
$optionsfield->value; // return empty string or value (if your option settings like '1=value|title')

// dot syntax in selector string
$pages->find('optionsfield.id=2');
</syntaxhighlight>

=== Page Reference auf diese Seite ===
https://processwire.com/talk/topic/1071-page-fieldtype-two-way-relation/
echo $pages->find("field1=$page")->render();
If the page isn't part of the front-end site, then I'll remove view access from its template. Or if it is part of the front-end, but I don't want to show the relations, then this:

if($page->editable()) echo $pages->find("field1=$page")->render();

Though I almost always integrate these relation-revealing pages into the site structure, as it's rare that this information doesn't have some value to the site's users too. This is an example of one that locates all pages referencing it in a field called 'country':
https://www.tripsite.com/countries/croatia/

=== Punkt Syntax ===
$architects = $pages->find("template=architect, city.title=Chicago");
$buildings = $pages->find("architect=$architects");
That's easy enough, but wouldn't it be nicer if you could just do this?
$buildings = $pages->find("architect.city.title=Chicago");

$buildings = $pages->find("architect.city.state.abbr=IL");
Broadening further, perhaps we want buildings from all architects in the USA:

$buildings = $pages->find("architect.city.state.country.abbr=USA");
Or perhaps both USA and Canada:

$buildings = $pages->find("architect.city.state.country.abbr=USA|CA");

ProcessWire - Selectors

2018-08-21T16:40:43Z

79.219.79.191: /* Beispiele */

ProcessWire - Fields

2018-08-18T16:26:28Z

79.219.79.191:

[[ProcessWire - Field Types]]
[[ProcessWire - Field Rendering]]
[[ProcessWire - Profields]]
[[Processwire - Field Types Usage]]
http://www.flamingruby.com/blog/anatomy-of-fields-in-processwire/