Module: PageTableExtended

[felted]

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

[MadeMyDay]

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.

[cstevensjr]

Go to /Modules/Core:

[felted]

Thank you.

[Roych]

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

[Roych]

bump 

thank you

R

[MadeMyDay]

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?

[Roych]

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

 

[MadeMyDay]

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.

[Roych]

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 

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

[mr-fan]

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

[MadeMyDay]

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?

 

[jploch]

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?
 

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;
}

 

[jploch]

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?

[Robin S]

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();

 

[jploch]

@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();

 

[Robin S]

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();

 

[jploch]

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!

[Michkael]

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

[jploch]

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

[jploch]

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?

[MadeMyDay]

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.

[jploch]

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 ?

[MadeMyDay]

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!

[jploch]

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)