Jump to content
MadeMyDay

Module: PageTableExtended

Recommended Posts

7 hours ago, Robin S said:

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.

 

Sorry, I should have been more specific. What I meant to ask was: It would be interesting to hear how other people manage their PTE pages when they're not direct children.

In my case choosing a custom (hidden from the client) parent for the layout would indeed be less confusing, but it would also mean that under the custom parent, all layout blocks (hundreds) from all projects would be listed without any context right? Not that the context is needed there, just need to get the OCD in check I guess..
 

Share this post


Link to post
Share on other sites
42 minutes ago, phil_s said:

In my case choosing a custom (hidden from the client) parent for the layout would indeed be less confusing, but it would also mean that under the custom parent, all layout blocks (hundreds) from all projects would be listed without any context right? Not that the context is needed there, just need to get the OCD in check I guess.

Yeah, I don't worry about that. No different to Repeater items in that respect. If you're concerned about orphaned pages you can set PageTable pages to be trashed or deleted if their parent page is deleted.

  • Like 3

Share this post


Link to post
Share on other sites

A tipp for your setup.

If you choose a parent page that is not under the /admin/ page you could use this snippet at the start of every block_template to hide pages from frontend access via url:

<?php
// the pageurl is hit this template file directly.
if ($page->url == $_SERVER["REQUEST_URI"]) {
  throw new Wire404Exception(); // show 404 page
}

But put everthing under admin is better solution...i don't read the docs to deep at start, too ;)

I use this module as kind of WYSIWYG blockbuilder on most installations and the largest amounth of blocks is ~ 300 for now....pages are scaling very well in PW. Some drive sites with several thausand pages under one parent...

regards mr-fan

  • Like 2

Share this post


Link to post
Share on other sites

How do u implement a "text column" in pagetable field ?

processwire template allowed unique type field in a template. That's you cannot add three body textfield on the same template ?

I'm thinking of, are you create three separate text fields for the "text column" pagetable field ?

 

Share this post


Link to post
Share on other sites

I created two pagetable fields used for content layout to replace the free text wysiwyg editor.

By clicking the button, no modal window popup

 

BaiduShurufa_2016-11-16_12-32-23.png

 

Share this post


Link to post
Share on other sites

As said on GitHub:

Compatibility should be given up to newest PW3. Look in the dev tools, if there is a JS issue. Never encountered something like this. "textblock" has a template associated? Without template there will no render in PTE. But shouldn't prevent modal though. Please show Console Output.

 

Share this post


Link to post
Share on other sites

Hi,

I'm storing all my  layouts under the "Repeater" page. Is it possible to get the parent page, I mean the page which is containing the specific pagetableextended via API?

E.g.: When I'm trying to call 

$page->parent->name

in lay_columns.php (one of files to render the output) it returns "repeater" wich is obviously because the repeater page is the parent. But I want to get the "original" parentpage where the pagetableextended field is stored.

I'hope you understand me.

 

Many greets!

Share this post


Link to post
Share on other sites

I figured out a new problem:

I'm using repeaters in the layout template in order to give the editor the possibility to define some "same looking" boxes. Inside the repeaters there is amongst other things an image field. When I'm trying to resize it via the API like

foreach($page->rep_imgTitleBody as $item) {
	$img = $item->sing_img->size(600,400)->url;
	$out = "<img src=\"{$img}\" alt=\"{$item->title}\">";
};

 

though it works on the frontend but in processwire backend I'm getting an error:

Quote

Method Pageimages::size does not exist or is not callable in this context

 

Any ideas?
 

2017-07-04 22_21_14-Edit Page_ Home • vieregg-design.de.jpg

Share this post


Link to post
Share on other sites

Sorry for the question, FieldtypePageTable is requested. Is that the Pro Field or is it for free?
 

Share this post


Link to post
Share on other sites

The name is a bit misleading. Just look in the modules section in your backend under "install". It's distributed with every core version, not installed though.

Modules • ProcessWire • ir.schustermann-borenstein.de 2017-07-11 23-15-03.jpg

  • Like 2

Share this post


Link to post
Share on other sites
On 4.7.2017 at 10:22 PM, DV-JF said:

I figured out a new problem:

I'm using repeaters in the layout template in order to give the editor the possibility to define some "same looking" boxes. Inside the repeaters there is amongst other things an image field. When I'm trying to resize it via the API like


foreach($page->rep_imgTitleBody as $item) {
	$img = $item->sing_img->size(600,400)->url;
	$out = "<img src=\"{$img}\" alt=\"{$item->title}\">";
};

 

though it works on the frontend but in processwire backend I'm getting an error:

 

Any ideas?
 

2017-07-04 22_21_14-Edit Page_ Home • vieregg-design.de.jpg

@DV-JF

I came across a similar issue. I'm using a page reference field to select several pages containing just 1 image per page. As Ryan describes in this post.
I haven't checked for the frontend yet, but in the backend I'm getting the same error.

So even though the image field in the referenced pages is set to contain just 1 image, I have to loop through it as if it's a WireArray.

I changed your code in way that worked for me:

foreach($page->rep_imgTitleBody as $item) {
	foreach($item->sing_img as $image) {
    		$img = $image->size(600,400)->url;
    		$out = "<img src=\"{$img}\" alt=\"{$item->title}\">";
	}
};

@MadeMyDay

Is this an expected behaviour? I'm using ProcessWire 3.0.77 and PageTableExtended 2.3.3

  • Like 1

Share this post


Link to post
Share on other sites

I still have a problem with the output of PageTableExtended (PTE) in the backend. I took some screenshots to demonstrate it.

My configuration looks like this: In my PageTableExtended field I have a template containing a PageReference field. That reference field allows only one reference. The pages I then reference to contain just one image per page. That way I can reuse images on different pages. But also, with just one page allowed per reference field, I have the ability to reorder the images on my page in a visual manner. Mainly that for I have PTE in use.

The empty PTE field in the backend looks like this:
59d8d257731a6_1empty.jpg.d1b0b9249707f349c062b35538d9441f.jpg

In the backend I add an image by clicking on the +Image button, respectively I create a new page with a template containing a page reference field. The modal window opens and I reference a page with an image named "sample-image". Then I hit save and the modal window closes. The PTE field now looks like this:
59d8d3c2f044d_2beforesafe.jpg.934b1ef1a2ed7aa81c23fbfff2bd095c.jpg

The template of the reference field in the PTE echoes the url of the image in the referenced page. Just as I would do to display the image, but for demonstrating purposes without the surrounding <img> tags.

Pause for a moment. Right now everything is as expected. BUT...

 

Now to the strange behaviour of PTE: After I hit Save on my actual page, where the PTE field lives in, I get this:
59d8d3c4f0e98_3aftersave.jpg.deaffe42dafeed1308686172a4dd3828.jpg

As you can see, the url of the referenced image is incomplete, the [name].[ext] part is missing. So it's not possible to display the image in the backend!

But on the frontend everything is fine:
59d8d6db2f978_4frontend.jpg.6a35ec14d8d439892b9fd37d4cd18c24.jpg

 

@MadeMyDay Is this behaviour expected?

Has someone the same problems? Can anybody suggest a solution?

 

Thanks in advance!

 

Below are my .php files for the basic-page containing the PTE field and the subtemplate for the media_pagereference.

// basic-page.php
<?php namespace ProcessWire;

$out = "";
if (count($page->pageTableExtended)) {
    foreach ($page->pageTableExtended as $pte) {
        $out .= $pte->render();
    }
}
?>

<main data-pw-id="main" class="main">
    <?php echo $out; ?>
</main>
// media_pagereference.php
<?php namespace ProcessWire;

if ($page->pageReference) {
    $refPage = $page->pageReference;
    $img = $refPage->image;
    echo $img->url;
}

 

Share this post


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

As you can see, the url of the referenced image is incomplete, the [name].[ext] part is missing.

For one reason or another, output formatting must be off when the PTE inputfield is rendered. To work around this, try...

// media_pagereference.php
<?php namespace ProcessWire;

$refPage = $page->getFormatted('pageReference'); // value will vary depending on "Page field value type" setting
if ($refPage->id) {
    $img = $refPage->image;
    echo $img->url;
}

...or more reliably (since it will work regardless of the "Page field value type" setting)...

// media_pagereference.php
<?php namespace ProcessWire;

$refPage = $page->getUnformatted('pageReference'); // always a PageArray
if ($refPage->count) {
    $img = $refPage->first->image;
    echo $img->url;
}

 

  • Like 1

Share this post


Link to post
Share on other sites

I got a solution for my problem described above.

I canged the settings for the image field that is allowed to contain just 1 image. Instead of returning a single element it now returns always an array of elements (hope the description is correct in english). Therefor I definitely need to either loop through the returned array (which is way too much, as there is just one image in it). So as szabez pointed out, a short and clean way is to use ->first()

@Robin SThank you for your suggestion, you where literally a few moments too late ;) But I'll give it a try!

Share this post


Link to post
Share on other sites

@Robin S sorry, your code didn't work for me, I had to change it that way:

// media_pagereference.php
<?php namespace ProcessWire;

if ($page->pageReference) {
    $refPage = $page->pageReference;
    $img = $refPage->getUnformatted('image')->first();
    echo $img->url;
}

Now it's possible to set the configuration of the 'image' field to return a single element instead of an array.

A second way next to the workaround I described above and a good opportunity to learn more about output formatting...

  • Like 1

Share this post


Link to post
Share on other sites

It is currently not actively under development but I use it as it is on several sites (I guess a lot of others do so, too). So I am wondering about this line:

<?php echo $page->pagetableextended->render(); ?>

The parts are just pages (see PageTable docs) . So with your code you just get an array of pages and PW is so kind to show you which. What you wanna do is:

<?php 
foreach($page->pagetableextended as $pe){
  echo $pe->render(); 
}
?>

 

  • Like 1

Share this post


Link to post
Share on other sites
Just now, Donald said:

Question: Can you recommended to use for bigger projects related to the fact that I would like to use it as an "content block builder" or like Lego for the frontend?

Sure, why not? I am using it on more than ten websites. Some of them have thousands of visitors each day, but that is not the crucial thing since the module doesn't do anything different than the PageTable module itself. It "just" renders the templates also in the admin. There can be some glitches (as this thread shows) but as long it works for you in the admin area, it will also work for your visitors ;-)

 

  • Like 2

Share this post


Link to post
Share on other sites

See it as an alternative to the Repeater Module. For the repeater you define (the same) input fields for each item. The PageTable module is technically pretty similar as both store the items in own pages somewhere. But with the PageTable module you have the opportunity to use different templates as input field sets to choose from. The PageTable module shows those (sub)pages as a table with each page as a row. PTE extends that functionality for rendering the items as they are rendered in the frontend.

Share this post


Link to post
Share on other sites

I would say the PageTable module by Ryan is close to his repeater matrix ;-) I only extended the functionality of the former.

  • Haha 1

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...