Jump to content
MadeMyDay

Module: PageTableExtended

Recommended Posts

Just use the labels of templates to name them more descriptively. The buttons below pagetables will always show the label and fall back to the name of the template if no label is defined.

For the "add new" buttons, there are a lot of them in processwire. Most of them are there, because either the context provides the information about what will be added or the cms can not tell ahead of time what will be added. You can edit them with hooks, different ones dependent on which one you'll want to edit, but not via the admin backend. But this is not the thread to take about this in detail.

  • Like 1

Share this post


Link to post
Share on other sites
Just use the labels of templates to name them more descriptively. The buttons below pagetables will always show the label and fall back to the name of the template if no label is defined.

Labels! This Label-Field in Template was never catching my Eye.

Thank you.

Share this post


Link to post
Share on other sites

Look for template label on the template settings. The field is closed when empty, look well.

Share this post


Link to post
Share on other sites

git2.jpg

From the screenshot, there are three different page content, Text block with headline, text columns and image gallery could be added.

How to do something like that with this module?

Edited by kongondo
Edited for clarity

Share this post


Link to post
Share on other sites

Hi,

I'm using this module to display some different sections on the homepage of a webseite like in this example: https://processwire.com/talk/topic/7459-module-pagetableextended/#entry71793

My home template file looks like this:

$page = $pages->get(1021); // This is a Site for storing all sections of the homepage

foreach($page->children as $child) {
	require($child->template .'.php');
};

$mainContent = $out;

Here's an example of one of my child-templates:

<?php 

/* section-slider.php  - Template File for a Slider*/

// Check if Back- or Frontend

if(isset($options['pageTableExtended'])){
    $useMain = false;
    $out = "";
    $addJS = "";
}

// Check if is in frontend	
else {
    $page = $child;
};

// Starting output

$images = $page->images;

$mini =   320;
$small =  640;
$medium = 900;
$large =  1200;
$xlarge = 1680;

$out .= "

	<section id='{$page->name}' class='slides'>";
		
		foreach($images as $img) {			
			$out .= "<img src='{$img->width($mini)->url}' srcset='{$img->width($mini)} {$mini}w, {$img->width($small)} {$small}w, {$img->width($medium)->url} {$medium}w, {$img->width($large)->url} {$large}w, {$img->width($xlarge)->url} {$xlarge}w' alt='{$img->description}'>";
		};
		
$out .= "
	</section>";

// Load JS and CSS Files

$inlineJS .= "
	<script>
		$(function() {
			$('.slides').slidesjs({
				width: 1200,
				height: 900,
				navigation: {
					effect: 'fade'
				},
				pagination: {
					effect: 'fade'
				},
				effect: {
					fade: {
						speed: 3000
					}
				},
				play: {
					active:true,
					auto: true,
					swap: false,
					effect: 'fade',
					pauseOnHover: false,
					interval: 5000
				}
			});
		});
	</script>";

array_push($cssFiles,"css/slides.css");
array_push($jsFiles,"js/jquery.slides.min.js");
	
// Check if backend

if(isset($options['pageTableExtended'])){
    echo($out);
}

Two questions:

1. I'm wondering if it's possible to redirect the children of the site to the parent-site or to the homepage, when a user tries to visit the childpage directly, so that it's not possible to visit the child-page directly.

2. How are the child-pages sorted? When I try to sort them via drag&drop here:

post-889-0-31901100-1433844880_thumb.jpg

this don't effect the frontpage.

I've to sort the child-pages to get the correct sortorder here:

post-889-0-02600700-1433845111_thumb.jpg

Where can I change it, so that the childpages are sorted correctly?

Many greets, DV-JF alias Jens.

Share this post


Link to post
Share on other sites

1. I'm wondering if it's possible to redirect the children of the site to the parent-site or to the homepage, when a user tries to visit the childpage directly, so that it's not possible to visit the child-page directly.

2. How are the child-pages sorted? When I try to sort them via drag&drop here:

1. Something like this should work:

if($page->url ===  $_SERVER['REQUEST_URI']) {
	$session->redirect($page->parent->url);
}

2. How are the child-pages sorted? When I try to sort them via drag&drop here:

2. From https://processwire.com/api/selectors/

foreach($page->children('sort=sort') as $child) {
	require($child->template .'.php');
};

Share this post


Link to post
Share on other sites

Do I just miss something?

On the Details tab of a field of type PageTableExtended you can Select a parent for items.
But when done, you can't switch back to the option no parent is selected.

Is there a way to do it?

Share this post


Link to post
Share on other sites

Thanks @adrian, hadn't seen that. It's a smart solution - but not easily found...

Share this post


Link to post
Share on other sites

I am trying to understand if I should use the new ProFields Repeater Matrix or PageTableExtended. Does PageTableExtended have any distinct benefits? I haven't had a chance to test thoroughly enough to make the decision yet.

Share this post


Link to post
Share on other sites

I haven't tested the new matrix field for now.

PTE renders the selected templates/blocks for the editor. So the dev could create a simple visual blockeditor with drag and drop the blocks and prerender them like it looks on frontend or in a other way that fits in the backend like teammembers, slideimages and so on.

Some things to mention:

- Care for the used templates to render in SEO things - access the single parts are possible if you don't handle this (for example you have all PTE elements under a hidden parent the elements are accessable on frontend, too)

- The CSS for prerendering is sometimes a little tricky since it could be that it crashes with the admin styles (only some special classes and maybe fontsizes and so on)

  you could use .renderedLayout Class on such elements in your special CSS file for PTE.

I'm running PTE for pretty much every repeating element that is more complex like contentblocks, sliderimages with text and settings, teammembers, grouping documents and so on...all things that elements in summary are under a rage from 10 to maximum 40. If i need more elements like events or something i'll stick to pages.

best regards mr-fan

  • Like 4

Share this post


Link to post
Share on other sites

In posted screenshot, the text column pagetable isn't fixed in 3 cols ? or it can be in any number of colums, 2, 3 or 4

Share this post


Link to post
Share on other sites

@MadeMyDay

What about the compatibility of PageTableExtended with PW 3.0.x devns?

Share this post


Link to post
Share on other sites

Is working here on a massive setup for blockbuilding....no affect so far.

  • Like 2

Share this post


Link to post
Share on other sites

@all: Was kind of out of business for a while. Will come back and check everything in September! Also some new ideas for this module ;-)

  • Like 8

Share this post


Link to post
Share on other sites

@MadeMyDay

Looking forward indeed! Such an amazing module.
Running smoothly on ProcessWire 3.0.30 devns here btw.

One small quibble: How would you get the sort order from the drag and drop view of the module to correlate to the child pages in the tree view? As Jens pointed out, it seems there is currently no possibility to sync these two up or render/access the module's custom sort order?

Cheers!
Phil

Share this post


Link to post
Share on other sites
1 hour ago, phil_s said:

One small quibble: How would you get the sort order from the drag and drop view of the module to correlate to the child pages in the tree view?

Just wondering why you would need to do this. A PageTable field does not necessarily include all the children of a given parent so the contents/order of the field could never match the children in all circumstances. I would have thought that if you create a PageTable field then you interact with its pages via the field (whether we're talking about the API or the admin interface) rather than the page tree. Personally, I always store my PageTable pages under the admin branch so they're not visible/confusing for clients.

  • Like 2

Share this post


Link to post
Share on other sites
8 hours ago, Robin S said:
10 hours ago, phil_s said:

One small quibble: How would you get the sort order from the drag and drop view of the module to correlate to the child pages in the tree view?

Just wondering why you would need to do this...

I use PTE as a visual editor for modular layout blocks in a project page template of a Portfolio website. The client can create and arrange blocks with various configurations to build the individual project pages. The blocks will get added as children of the project page. The page tree thus looks something like this:

home
+ projects
  + first project
    + block-fullwidth
    + block-fullwidth
  + second project
    + block-twohalves
    + block-fullwidth
    ...

In theory the obvious benefit of using PTE here is that the client can do all the arranging (which is more of a try this and that process) directly in the interface, and preview which order they will appear in the page in in a visual way. 

In practice though, when I fill the array and specify a sort order for rendering like this:

 $blocks = $page->children('sort=sort')

..this will render the (manual) sort order from the page tree, not the manual sort order arranged by the client via the PTE interface.
I can rearrange the blocks in both views individually and access the page tree custom sort order e.g. via the above–but can't access PTE's sort order.

So TLDR: I would like to access and render the custom sort order done via the PTE fields, not a custom sort order done via the page tree. 
Am I looking at this the wrong way or missing anything? Should I fill the array with find/get instead?

Cheers guys!

Screen Shot 2016-09-08 at 14.26.44.jpg

Share this post


Link to post
Share on other sites

You don't have to refer to the page tree order or use $page->children. Assuming your PTE field is called "layout"  all you have to do is:

 

foreach($page->layout as $l){
    $layout .= $l->render();
}

The field itself holds the connection to its blocks. No matter where they are in the tree (because that's configurable).

  • Like 1

Share this post


Link to post
Share on other sites
1 hour ago, MadeMyDay said:

You don't have to refer to the page tree order or use $page->children. Assuming your PTE field is called "layout"  all you have to do is:

 


foreach($page->layout as $l){
    $layout .= $l->render();
}

The field itself holds the connection to its blocks. No matter where they are in the tree (because that's configurable).

Oh, nice :)

It seems reading the manual helps as usual. Sorry.

@Robin S How do you keep order without the context of the parent? (assuming you are using PTE for a similar setup)?

Thanks a bunch guys!

Share this post


Link to post
Share on other sites
8 hours ago, phil_s said:

How do you keep order without the context of the parent?

I'm not sure what you mean. It's just as @MadeMyDay explained - the order is stored as part of the field. You just need to get the "block" pages via the field rather than as children of a parent.

Instead of...

$blocks = $page->children('sort=sort');

...do...

$blocks = $page->my_pagetable_field;

 

  • Like 2

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-07-03 -- SnipWire 0.8.7 (beta) released! Fixes some small bugs and adds an indicator for TEST mode 2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  

       
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By Sten
      Hello
      Till now I hacked something with the twig template but it works no more with new PW versions so I look forward to create a module. I am working on a site in multiple languages : French, English, Italian, German, Spanish, Portuguese, Hebrew, Russian. The new posts are entered in any language with a field for language. Till now, I got twig files to get the translations with constants defined for each part of the pages.
      So I'd like to create a module to include theses files added according to the url /fr/en/...
      Have you some observations to do before I begin about the direction to take ?
      Thank you
    • By ukyo
      Mystique Module for ProcessWire CMS/CMF
      Github repo : https://github.com/trk/Mystique
      Mystique module allow you to create dynamic fields and store dynamic fields data on database by using a config file.
      Requirements
      ProcessWire 3.0 or newer PHP 7.0 or newer FieldtypeMystique InputfieldMystique Installation
      Install the module from the modules directory:
      Via Composer:
      composer require trk/mystique Via git clone:
      cd your-processwire-project-folder/ cd site/modules/ git clone https://github.com/trk/Mystique.git Module in live reaction with your Mystique config file
      This mean if you remove a field from your config file, field will be removed from edit screen. As you see on youtube video.
      Using Mystique with your module or use different configs path, autoload need to be true for modules
      Default configs path is site/templates/configs/, and your config file name need to start with Mystique. and need to end with .php extension.
      Adding custom path not supporting anymore !
      // Add your custom path inside your module class`init` function, didn't tested outside public function init() { $path = __DIR__ . DIRECTORY_SEPARATOR . 'configs' . DIRECTORY_SEPARATOR; Mystique::add($path); } Mystique module will search site/modules/**/configs/Mystique.*.php and site/templates/Mystique.*.php paths for Mystique config files.
      All config files need to return a PHP ARRAY like examples.
      Usage almost same with ProcessWire Inputfield Api, only difference is set and showIf usage like on example.
      <?php namespace ProcessWire; /** * Resource : testing-mystique */ return [ 'title' => __('Testing Mystique'), 'fields' => [ 'text_field' => [ 'label' => __('You can use short named types'), 'description' => __('In file showIf working like example'), 'notes' => __('Also you can use $input->set() method'), 'type' => 'text', 'showIf' => [ 'another_text' => "=''" ], 'set' => [ 'showCount' => InputfieldText::showCountChars, 'maxlength' => 255 ], 'attr' => [ 'attr-foo' => 'bar', 'attr-bar' => 'foo' ] ], 'another_text' => [ 'label' => __('Another text field (default type is text)') ] ] ]; Example:
      site/templates/configs/Mystique.seo-fields.php <?php namespace ProcessWire; /** * Resource : seo-fields */ return [ 'title' => __('Seo fields'), 'fields' => [ 'window_title' => [ 'label' => __('Window title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'attr' => [ 'placeholder' => __('Enter a window title') ] ], 'navigation_title' => [ 'label' => __('Navigation title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'showIf' => [ 'window_title' => "!=''" ], 'attr' => [ 'placeholder' => __('Enter a navigation title') ] ], 'description' => [ 'label' => __('Description for search engines'), 'type' => Mystique::TEXTAREA, 'useLanguages' => true ], 'page_tpye' => [ 'label' => __('Type'), 'type' => Mystique::SELECT, 'options' => [ 'basic' => __('Basic page'), 'gallery' => __('Gallery'), 'blog' => __('Blog') ] ], 'show_on_nav' => [ 'label' => __('Display this page on navigation'), 'type' => Mystique::CHECKBOX ] ] ]; Searching data on Mystique field is limited. Because, Mystique saving data to database in json format. When you make search for Mystique field, operator not important. Operator will be changed with %= operator.
      Search example
      $navigationPages = pages()->find('my_mystique_field.show_on_nav=1'); $navigationPages = pages()->find('my_mystique_field.page_tpye=gallery');
    • By Robin S
      This is a module I made as an experiment a while ago and never got around to releasing publicly. At the time it was prompted by discussions around using Repeater fields for "page builder" purposes, where the depth feature could possibly be used for elements that would be nested inside other elements. I thought it would be useful to enforce some depth rules and translate the depth data into a multi-dimensional array structure.
      I'm not using this module anywhere myself but maybe it's useful to somebody.
      Repeater Depth Helper
      This module does two things relating to Repeater fields that have the "Item depth" option enabled:
      It enforces some depth rules for Repeater fields on save. Those rules are:
      The first item must have a depth of zero. Each item depth must not be more than one greater than previous item depth. It provides a RepeaterPageArray::getDepthStructure helper method that returns a nested depth structure for a Repeater field value.
      Helper method
      The module adds a RepeaterPageArray::getDepthStructure method that returns a multi-dimensional array where the key is the page ID and the value is an array of nested "child" items, or null if there are no nested children.
      Example

      The module doesn't make any assumptions about how you might want to use the depth structure array, but here is a way you might use it to output a nested unordered list.
      // Output a nested unordered list from a depth structure array function outputNestedList($depth_structure, $repeater_items) { $out = "<ul>"; foreach($depth_structure as $page_id => $nested_children) { $out .= "<li>" . $repeater_items->get("id=$page_id")->title; // Go recursive if there are nested children if(is_array($nested_children)) $out .= outputNestedList($nested_children, $repeater_items); $out .= "</li>"; } $out .= "</ul>"; return $out; } $repeater_items = $page->my_repeater; $depth_structure = $repeater_items->getDepthStructure(); echo outputNestedList($depth_structure, $repeater_items);
       
      https://github.com/Toutouwai/RepeaterDepthHelper
      https://modules.processwire.com/modules/repeater-depth-helper/
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
×
×
  • Create New...