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

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.56
      Composer: rockett/jumplinks
      Jumplinks is an enhanced version of the original ProcessRedirects by Antti Peisa.
      The Process module manages your permanent and temporary redirects (we'll call these "jumplinks" from now on, unless in reference to redirects from another module), useful for when you're migrating over to ProcessWire from another system/platform. Each jumplink supports wildcards, shortening the time needed to create them.
      Unlike similar modules for other platforms, wildcards in Jumplinks are much easier to work with, as Regular Expressions are not fully exposed. Instead, parameters wrapped in curly braces are used - these are described in the documentation.
      Under Development: 2.0, to be powered by FastRoute
      As of version 1.5.0, Jumplinks requires at least ProcessWire 2.6.1 to run.
      View on GitLab
      Download via the Modules Directory
      Read the docs
      Features
      The most prominent features include:
      Basic jumplinks (from one fixed route to another) Parameter-based wildcards with "Smart" equivalents Mapping Collections (for converting ID-based routes to their named-equivalents without the need to create multiple jumplinks) Destination Selectors (for finding and redirecting to pages containing legacy location information) Timed Activation (activate and/or deactivate jumplinks at specific times) 404-Monitor (for creating jumplinks based on 404 hits) Additionally, the following features may come in handy:
      Stale jumplink management Legacy domain support for slow migrations An importer (from CSV or ProcessRedirects) Feedback & Feature Requests
      I’d love to know what you think of this module. Please provide some feedback on the module as a whole, or even regarding smaller things that make it whole. Also, please feel free to submit feature requests and their use-cases.
      Note: Features requested so far have been added to the to-do list, and will be added to 2.0, and not the current dev/master branches.
      Open Source

      Jumplinks is an open-source project, and is free to use. In fact, Jumplinks will always be open-source, and will always remain free to use. Forever. If you would like to support the development of Jumplinks, please consider making a small donation via PayPal.
      Enjoy! :)
    • By BitPoet
      As threatened in Ryan's announcement for 3.0.139, I built a little module for sliding toggles as a replacement for checkboxes. Styling of the input is CSS3 only (with all the usual caveats about older browsers), no JS necessary, and may still be a bit "rough around the edges", so to speak, since I didn't have much time for testing on different devices or brushing things up enough so I'd feel comfortable pushing it to the module directory. But here's the link to the GitHub repo for now:
      InputfieldSlideToggle
      Fieldtype and Inputfield that implements smartphone-style toggles as replacement for checkbox inputs. The visualization is CSS-only, no additional JS necessary.
      Status
      Still very alpha, use with caution!
      Features / Field Settings
      Size
      You can render the toggles in four different sizes: small, medium, large and extra large.
      Off Color
      Currently, "unchecked" toggles can be displayed either in grey (default) or red.
      On Color
      "Checked" toggles can be rendered in one of these colors: blue (default), black, green, grey, orange or red.
      Screenshots

      Some examples with checkbox label


      View all Size and Color Combinations
      Small toggles Medium toggles Big toggles Extra big toggles  









    • By Orkun
      Hi Guys
      I needed to add extended functionalities for the InputfieldDatetime Module (module is from processwire version 2.7.3) because of a Request of Customer.
      So I duplicated the module and placed it under /site/modules/.
      I have added 3 new Settings to the InputfieldDatetime Module.
      1. Day Restriction - Restrict different days based on weekdays selection (e.g. saturday, sunday) - WORKING

       
      2. Time Slots - Define Time slots based on custom Integer Value (max is 60 for 1 hour) - WORKING

       
      3. Time Range Rules per Weekday - Define a minTime and MaxTime per Weekday (e.g. Opening Hours of a Restaurant) - NOT WORKING PROPERLY

       
      The Problem
      Time Slots and Day Restriction working fine so far. But the Time Range Rules per Weekday doesn't work right.
      What should happen is, that when you click on a date, it should update the minTime and maxTime of the Time Select.
      But the change on the select only happens if you select a date 2 times or when you select a date 1 time and then close the datepicker and reopen it again.
      The time select doesn't get change when you select a date 1 time and don't close the picker.
      Here is the whole extended InputfieldDatetime Module.
      The Files that I have changed:
      InputfieldDatetime.module InputfieldDatetime.js jquery-ui-timepicker-addon.js (https://trentrichardson.com/examples/timepicker/) - updated it to the newest version, because minTime and maxTime Option was only available in the new version  
      Thats the Part of the JS that is not working correctly:
      if(datetimerules && datetimerules.length){ options.onSelect = function(date, inst) { var day = $(this).datetimepicker("getDate").getDay(); day = day.toString(); var mintime = $(this).attr('data-weekday'+day+'-mintime'); var maxtime = $(this).attr('data-weekday'+day+'-maxtime'); console.log("weekday: "+day); console.log("minTime: "+mintime); console.log("maxTime: "+maxtime); var optionsAll = $(this).datetimepicker( "option", "all" ); optionsAll.minTime = mintime; optionsAll.maxTime = maxtime; $(this).datetimepicker('destroy'); $(this).datetimepicker(optionsAll); $(this).datetimepicker('refresh'); //$.datepicker._selectDate($(this).attr("id"),date); //$.datepicker._base_getDateDatepicker(); // var inst = $.datepicker._getInst($(this)); // $.datepicker._updateDatepicker(inst); /*$(this).datetimepicker('destroy'); InputfieldDatetimeDatepicker($(this), mintime, maxtime); $(this).datetimepicker('refresh'); */ // $(this).datetimepicker('option', {minTime: mintime, maxTime: maxtime}); } } Can you have a look and find out what the Problem is?
      InputfieldDatetime.zip
       
      Kind Regards
      Orkun
    • By teppo
      This module tracks changes, additions, removals etc. of public (as in "not under admin") pages of your site. Like it's name says, it doesn't attempt to be a version control system or anything like that - just a log of what's happened.
      At the moment it's still a work in progress and will most likely be a victim of many ruthless this-won't-work-let's-try-that-instead cycles, but I believe I've nailed basic functionality well enough to post it here.. so, once again, I'll be happy to hear any comments you folks can provide
      https://modules.processwire.com/modules/process-changelog/
      https://github.com/teppokoivula/ProcessChangelog
      How does it work?
      Exactly like it's (sort of) predecessor, Process Changelog actually consists of two modules: Process Changelog and Process Changelog Hooks. Hooks module exists only to serve main module by hooking into various functions within Pages class, collecting data of performed operations, refining it and keeping up a log of events in it's own custom database table (process_changelog.) Visible part is managed by Process Changelog, which provides users a (relatively) pretty view of the contents of said log table.
      How do you use it?
      When installed this module adds new page called Changelog under Admin > Setup which provides you with a table view of collected data and basic filtering tools See attached screenshots to get a general idea about what that page should look like after a while.
      For detailed installation instructions etc. see README.md.
       


    • By Gadgetto
      Status update links (inside this thread) for SnipWire development will be always posted here:
      2019-08-08
      2019-06-15
      2019-06-02
      2019-05-25
      If you are interested, you can test the current state of development:
      https://github.com/gadgetto/SnipWire
      Please note that the software is not yet intended for use in a production system (alpha version).
      If you like, you can also submit feature requests and suggestions for improvement. I also accept pull requests.
      ---- INITIAL POST FROM 2019-05-25 ----
      I wanted to let you know that I am currently working on a new ProcessWire module that fully integrates the Snipcart Shopping Cart System into ProcessWire. (this is a customer project, so I had to postpone the development of my other module GroupMailer).
      The new module SnipWire offers full integration of the Snipcart Shopping Cart System into ProcessWire.
      Here are some highlights:
      simple setup with (optional) pre-installed templates, product fields, sample products (quasi a complete shop system to get started immediately) store dashboard with all data from the snipcart system (no change to the snipcart dashboard itself required) Integrated REST API for controlling and querying snipcart data webhooks to trigger events from Snipcart (new order, new customer, etc.) multi currency support self-defined/configurable tax rates etc. Development is already well advanced and I plan to release the module in the next 2-3 months.
      I'm not sure yet if this will be a "Pro" module or if it will be made available for free.
      I would be grateful for suggestions and hints!
      (please have a look at the screenshots to get an idea what I'm talking about)
       




×
×
  • Create New...