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

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

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 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-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 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 (alpha version only available via GitHub) 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 d'Hinnisdaël
      Happy new year, everybody 🥬
      I've been sitting on this Dashboard module I made for a client and finally came around to cleaning it up and releasing it to the wider public. This is how it looks.
      ProcessWire Dashboard

      If anyone is interested in trying this out, please go ahead! I'd love to get some feedback on it. If this proves useful and survives some real-world testing, I'll add this to the module directory.
      Download
      You can find the latest release on Github.
      Documentation
      Check out the documentation to get started. This is where you'll find information about included panel types and configuration options.
      Custom Panels
      My goal was to make it really simple to create custom panels. The easiest way to do that is to use the panel type template and have it render a file in your templates folder. This might be enough for 80% of all use cases. For anything more complex (FormBuilder submissions? Comments? Live chat?), you can add new panel types by creating modules that extend the DashboardPanel base class. Check out the documentation on custom panels or take a look at the HelloWorld panel to get started. I'm happy to merge any user-created modules into the main repo if they might be useful to more than a few people.
       Disclaimer
      This is a pre-release version. Please treat it as such — don't install it on production sites. Just making sure 🍇
      Roadmap
      These are the things I'm looking to implement myself at some point. The wishlist is a lot longer, but those are the 80/20 items that I probably won't regret spending time on.
      Improve documentation & add examples ⚙️ Panel types Google Analytics ⚙️ Add new page  🔥 Drafts 🔥 At a glance / Page counter 404s  Layout options Render multiple tabs per panel panel groups with heading and spacing between ✅ panel wrappers as grid item (e.g. stacked notices) ✅ Admin themes support AdminThemeReno and AdminThemeDefault ✅ Shortcuts panel add a table layout with icon, title & summary ✅ Chart panel add default styles for common chart types ✅ load chart data from JS file (currently passed as PHP array) Collection panel support image columns ✅ add buttons: view all & add new ✅
    • By Robin S
      This module is inspired by and similar to the Template Stubs module. The author of that module has not been active in the PW community for several years now and parts of the code for that module didn't make sense to me, so I decided to create my own module. Auto Template Stubs has only been tested with PhpStorm because that is the IDE that I use.
      Auto Template Stubs
      Automatically creates stub files for templates when fields or fieldgroups are saved.
      Stub files are useful if you are using an IDE (e.g. PhpStorm) that provides code assistance - the stub files let the IDE know what fields exist in each template and what data type each field returns. Depending on your IDE's features you get benefits such as code completion for field names as you type, type inference, inspection, documentation, etc.
      Installation
      Install the Auto Template Stubs module.
      Configuration
      You can change the class name prefix setting in the module config if you like. It's good to use a class name prefix because it reduces the chance that the class name will clash with an existing class name.
      The directory path used to store the stub files is configurable.
      There is a checkbox to manually trigger the regeneration of all stub files if needed.
      Usage
      Add a line near the top of each of your template files to tell your IDE what stub class name to associate with the $page variable within the template file. For example, with the default class name prefix you would add the following line at the top of the home.php template file:
      /** @var tpl_home $page */ Now enjoy code completion, etc, in your IDE.

      Adding data types for non-core Fieldtype modules
      The module includes the data types returned by all the core Fieldtype modules. If you want to add data types returned by one or more non-core Fieldtype modules then you can hook the AutoTemplateStubs::getReturnTypes() method. For example, in /site/ready.php:
      // Add data types for some non-core Fieldtype modules $wire->addHookAfter('AutoTemplateStubs::getReturnTypes', function(HookEvent $event) { $extra_types = [ 'FieldtypeDecimal' => 'string', 'FieldtypeLeafletMapMarker' => 'LeafletMapMarker', 'FieldtypeRepeaterMatrix' => 'RepeaterMatrixPageArray', 'FieldtypeTable' => 'TableRows', ]; $event->return = $event->return + $extra_types; }); Credits
      Inspired by and much credit to the Template Stubs module by mindplay.dk.
       
      https://github.com/Toutouwai/AutoTemplateStubs
      https://modules.processwire.com/modules/auto-template-stubs/
    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.60
      Composer: rockett/jumplinks
      ⚠️ NOTICE: 1.5.60 is an important security patch-release for an XSS vulnerability discovered by @phlp. It's HIGHLY RECOMMENDED that all Jumplinks users update to the latest version as soon as possible.
      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 Robin S
      Add Image URLs
      Allows images/files to be added to Image/File fields by pasting URLs.

      Usage
      Install the Add Image URLs module.
      A "Paste URLs" button will be added to all image and file fields. Use the button to show a textarea where URLs may be pasted, one per line. Images/files are added when the page is saved.
       
      https://github.com/Toutouwai/AddImageUrls
      https://modules.processwire.com/modules/add-image-urls/
×
×
  • Create New...