Jump to content
MadeMyDay

Module: PageTableExtended

Recommended Posts

On ‎01‎.‎09‎.‎2014 at 2:44 PM, MadeMyDay said:

Extends the Processwire PageTable field for rendering table row layouts

Where can i find the PageTable field?

Thanks, Felted

Share this post


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

Where can i find the PageTable field?

Thanks, Felted

Should be in core distribution. But you have to install it first. It is called "ProFields: PageTable" afair.

  • Like 2

Share this post


Link to post
Share on other sites

Hello,

first time using PageTableExtended so far so good. I've created three diferent layouts with three diferent template files and I'm showing a list of all items on a parrent page with

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

So what I would like to do is open each item in a different template (same template for all items) like (read more button) , can this be done somehow? Not in a layout given in PTE.

one of my layouts looks like this, expl.:

<div class="col-lg-5 col-xs-12">
   <div class="ro-service-1-item ro-service-1-v clearfix">
     <div class="ro-image ro-left"><img src="<?=$page->images->first->url?>" alt="service" class="img-responsive"/></div>
       <div class="ro-content">
         <h3 class="ro-hr-heading"><?=$page->title?></h3>
           <div class="ro-bgc-trans-5"><?=$page->body?><a href="<?= $page->url ?>" class="ro-more"><i class="fas fa-arrow-right"></i></a></div>
      </div>
    </div>
</div>

So my <?= $page->url ?> links to this template, I'd like to use diferent template for this. Hope you understand. Something like blog opening a detail page.

Thank you

R

Share this post


Link to post
Share on other sites

Sorry, I don't get it. You three different layouts for PTE, so far so good. Now you wanna do what? The read more link to a different page should point to a different template? Why not? For that URL the detail page template is used, isn't it?

  • Like 1

Share this post


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

Sorry, I don't get it. You three different layouts for PTE, so far so good. Now you wanna do what? The read more link to a different page should point to a different template? Why not? For that URL the detail page template is used, isn't it?

hello,

with:

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

I'm showing all my pages in one template like teasers. Just some small teaser text. I have some other fields added in PTE that are not shown here. So in the bottom of every item (layout) I have read more button with link "<?= $page->url ?>" wich opens the templates assigned to TPE that I don't want. I need to create another template (services-details) wich will fetch all the fields from this specific page (layout), hope u unerstand.

Here is the link to the site so you wil know what I mean.

LINK

You will se the "Beri več ->" link ... that should point to diferent template but would fetch fields from only that layout.

Thank you

R

 

Share this post


Link to post
Share on other sites

Could you explain the use case for me? Why are those fields not filled in the details template and you just pull them to the PTE template? So the PTE template for example just consists of a page select field. You select a page and the PTE template renders the information pulled from that page.

Share this post


Link to post
Share on other sites
8 minutes ago, MadeMyDay said:

Could you explain the use case for me? Why are those fields not filled in the details template and you just pull them to the PTE template? So the PTE template for example just consists of a page select field. You select a page and the PTE template renders the information pulled from that page.

not sure I follow, what you need here :undecided:

I want link to point to new "detail" template but contans fields from clicked page.

Share this post


Link to post
Share on other sites

I think you mix up things and usecases.

You wanna have a overview page like in your link - and you wanna details pages for every entry?

So you even don't need a PTE setup here.

just use a pagetree for this elements and set the templates for /storitve/ and /storitve/detail_what_ever/ and you are ready.

Editor only have to add pages under this tree - the short teaser is generated automagically no need for PTE here....this time.

regards mr-fan

if you wanna stick to your way you could check if you are on the overviewpage or on the PTE element page itself (check for $page->parent or page->id)...

Share this post


Link to post
Share on other sites

I guess you are talking about the

Quote

Pri nas si lahko pričeske uredijo vsi željni profesionalnega videza. Gospe, gospodje ali otroci, dobrodošli so vsi, ki dajo kaj nase. Imate željo po pričeski iz fotografije? Prinesite fotografijo in domov boste odšli s popolnoma enako, morda še lepšo. Dobrodošli! ;)

block and the corresponding detail page.

You seem to put the text in the pte template. Why not put a page select field to the pte template and put the content of that textblock where it belongs, to the detail page (let's call it "summary"). Assuming your detail template is "detail" and the pte template is "pte_textblock".

Add a page select to pte_textblock named "linkedPage". So in your pte_textblock template you have access to the fields of the detail page via

$page->linkedPage->summary and also to the read more destination via $page->linkedPage->url.

 

Ring a bell? ;)

 

  • Like 1

Share this post


Link to post
Share on other sites
On 7/4/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

I have the same problem when resizing images with the api.
Doing this, did not solve it for me:

$item->block_image->first()->size(100)->url

edit: it works when I set the image field as an array and loop through it.
but this is not ideal in my use case.

I would like to keep the field as an single image field, so the client can simply change the image by replacing an existing one.
This was also a suggested solution, but Iam not sure where I have to put this (inside my template for the pagetable items?):

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

I have managed to build a pagebuilder with blocks using PageTableExtended.
Its working well and the customer is very happy with the look and usability.

All the pages that are created with my PageTable are living under
admin–>siteparts

Now I tried to make the blocks reusable on other pages using the PageReferenceField.
The problem is, the parent, where the pages from my PageTable are living, is set
to not be viewable by guest users to prevent these pages from being viewable on the frontend. 
Now they only show up on the Frontend when Iam logged In.

How can I prevent those pages to be accessed by URL, but
still be able to include these pages with the PageReferenceField?

Share this post


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

How can I prevent those pages to be accessed by URL, but
still be able to include these pages with the PageReferenceField?

When a page is rendered by another page PW populates a "stack" of pages that called render in an $options variable. See Ryan's comment:

So if a page is accessed directly and not rendered by another page then the page stack will be empty (in fact the $options variable will not be set). So you can put the following at the top of template files that should not be directly viewable but only rendered as part of another page:

if(empty($options['pageStack'])) throw new Wire404Exception();

 

  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites

@Robin S
Thanks you are the best! works great!! 

Edit:

While these pages now redirect to a 404 page,
all pages using my pagetable block with the redirect stopt showing up in admin.
showing a red error message saying The process returned no content.
And the whole page is empty with nothing to edit. 😞
–––––



The next cool addition would be a way to clone block items.
Even nicer if these could be cloned to different pages as well and still be able to get edited on every page.

this is also discussed here:
But Iam not sure if I understand where to put LostKobrakai code or how to adapt this.

On 9/24/2014 at 4:30 PM, LostKobrakai said:

PageTables are handled the same as other pagefields. So you can just use something like this:


$selected_page = $pages->get("something"); // Get the Page
$selected_table_entry = $selected_page->table->eq(0); // Get the PageTable entry
$clone = $pages->clone($selected_table_entry); // Clone the entry

$new_page = $pages->get("something"); // Get the page to copy to
$new_page->table->add($clone); // Add the clone to the PageTable
$new_page->save();

 

Share this post


Link to post
Share on other sites
7 hours ago, jploch said:

While these pages now redirect to a 404 page,
all pages using my pagetable block with the redirect stopt showing up in admin.
showing a red error message saying The process returned no content.

I've never actually used this module, but looking at the module code I think this will work:

if(empty($options['pageTableExtended']) && empty($options['pageStack'])) throw new Wire404Exception();

 

  • Thanks 1

Share this post


Link to post
Share on other sites
6 hours ago, Robin S said:

I've never actually used this module, but looking at the module code I think this will work:


if(empty($options['pageTableExtended']) && empty($options['pageStack'])) throw new Wire404Exception();

 

That worked! Thanks for your help!

  • Like 1

Share this post


Link to post
Share on other sites

Hey Guys, first of all thanks for the awesome module!

I have two questions:
1) Do I have to create a php file for each template I integrate in the field or can I code it in the php file where I put the PTE field?
2) If I have a folder with many CSS like you can see in the picture, how should I proceed?

Thank you.
Have a nice day,

Michael

Capture.JPG

Share this post


Link to post
Share on other sites

My PTE is not working with markup regions

This post can be deleted.
My markup regions are working fine with PTE, I made a mistake in my code..

Share this post


Link to post
Share on other sites

I managed to render blocks from page reference fields inside PTE.
In my template for the page reference block I render the page like this:
$page->block_page->render();

But when I save the modal after I add/change a block I get the error and the changes only appear after I save the page with the regular Save button from the page:
Failed to ready module: FieldtypePageTable

This only happens if the PTE has a page reference block.
Any Ideas why this error is happening?

Share this post


Link to post
Share on other sites

Sorry, I never saw that error. 

Quote

This only happens if the PTE has a page reference block.

You mean a page reference field? I also use page reference fields a lot so this shouldn't be the root cause. Do you have an another PTE field active in that template? I know there might be problems if there is more than one PT/PTE field in one template.

Share this post


Link to post
Share on other sites
15 minutes ago, MadeMyDay said:

Sorry, I never saw that error. 

You mean a page reference field? I also use page reference fields a lot so this shouldn't be the root cause. Do you have an another PTE field active in that template? I know there might be problems if there is more than one PT/PTE field in one template.

Yes I mean page reference field.
There is only one PT/PTE field on the page.

When I remove the $page->block_page->render(); from the template for that block (with the page reference field), everything is working fine.
I use the page reference field to add blocks that where added to another page with PTE, so that the blocks can be reused on another page.
Hope that makes sense to you 🙂

Share this post


Link to post
Share on other sites

could you share some more code, esp. how you render the blocks in your template and how that specific block with the page reference looks like. Thanks!

Share this post


Link to post
Share on other sites

template for block with page reference field:

if($page->block_page) echo "{$page->block_page->render()}";

And on my template to render the site with PTE:

$content = "";
if(count($page->pagebuilder)>0){
     foreach($page->pagebuilder as $l){
         $content .= $l->render();
     }
}

include("./_main.php");

$content is a variable in _main.php where the whole markup for the site is rendert.

(All blocks for PTE are stored under admin->siteparts.
They are configured to automatically get a title)

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