Jump to content

Module: PageTableExtended


MadeMyDay

Recommended Posts

Honestly I have no clue what is happening there. Just out of curiosity, could you try to autoload the module? So in FieldtypePageTableExtended.module try 'autoload' => true (perhaps same for PageTable). Doesn't make that much sense but I have no idea why FieldtypePageTable isn't ready since it is already present. The modal injects its changes via ajax, I guess somehow there could be the problem with your referenced PTE template block. But its just wild guessing.

  • Like 1
Link to comment
Share on other sites

15 hours ago, MadeMyDay said:

Honestly I have no clue what is happening there. Just out of curiosity, could you try to autoload the module? So in FieldtypePageTableExtended.module try 'autoload' => true (perhaps same for PageTable). Doesn't make that much sense but I have no idea why FieldtypePageTable isn't ready since it is already present. The modal injects its changes via ajax, I guess somehow there could be the problem with your referenced PTE template block. But its just wild guessing.

Thanks for looking into it!
I set autoload to true, but its not fixing my issue.

After testing I found out that the issue is caused by this line in my templates for the blocks that being referenced:

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

So I removed it and its working fine. but now my PTE blocks that are stored under admin–>siteparts are viewable on the frontend for everyone.
I don't want these pages to show up in search results, are there any other things I ca do to prevent that?

Link to comment
Share on other sites

Could you try something like this?

// only allow access to the page if logged in with editing permissions
// otherwise throw a 404 if viewed directly
if(!$page->editable() && (!count($options['pageStack']))){
  throw new Wire404Exception();
}

 

  • Like 3
Link to comment
Share on other sites

On 5/3/2019 at 7:38 PM, gmclelland said:

Could you try something like this?


// only allow access to the page if logged in with editing permissions
// otherwise throw a 404 if viewed directly
if(!$page->editable() && (!count($options['pageStack']))){
  throw new Wire404Exception();
}

 

That worked! Thank you!

Link to comment
Share on other sites

  • 3 weeks later...

I've found this module really useful, and thought I'd share an interesting use case I've come up with for it.

I had a client who wanted both the functionality of pageTable, and PageTableExtended, ie they wanted a tabular summary like PageTable provides, but with the option to expand or collapse to display rendered detail from a template like PageTableExtended allows.

It turns out, I was able to provide the desired functionality using PageTableExtended, and built in UI-kit classes in the template file I provided to PageTableExtended.

 

<!--
This is the summary section, like displayed by PageTable
-->
<table class="AdminDataTable AdminDataList uk-table uk-table-divider uk-table-justify uk-table-small">
    <thead>
        <tr>
            <th>BOM</th>
            <th>Cases to produce</th>
            <th>+/- or exact</th>
            <th>Notes</th>
        </tr>
    </thead>
    <tr>
        <td><?= $bom->title ?></td>
        <td><?= $page->cases ?></td>
        <td><?= $page->exact ?></td>
        <td><?= $page->notes ?></td>
    </tr>
</table>
<!--
Toggle to display detail section
-->
<a herf="#" class="toggleRenderedLayout">
    <i class="toggle-icon fa fa-angle-right"></i>
</a>
<span class="renderedLayoutTitle">BOM Details</span>
<!--
Detail section, hidden by default, using built in ui-kit css.
-->
<div class="renderedLayout hiddenOnStart">
    <div uk-grid uk-margin-small-top>
        <div class="uk-width-1-3 uk-margin-small-top"><strong>Wine Variety </strong><?= $bom->wineVariety->title ?></div>
        <div class="uk-width-1-3 uk-margin-small-top"><strong>Brand </strong><?= $bom->brand->title ?></div>
        <div class="uk-width-1-3 uk-margin-small-top"><strong>Market </strong><?= $bom->market->title ?></div>
        <div class="uk-width-1-1 uk-margin-small-top"><strong>Orientation </strong><?= $bom->orienation->title ?></div>
		...
    </div>
</div>

Screenshot, showing the tabular summary, with the detail section expanded.

image.png.21db5447082979c21abbb7dc237e67e0.png

 

  • Like 5
Link to comment
Share on other sites

  • 3 months later...

Hey! Its me again 🙂
Iam currently experimenting with this module, to make the pagetable block items draggable and resizable (with some JS) and output them with CSS Grid.
My setup works already, but to save the item positions I need fields to store the data in (like Y=10 X=6 Width=4 Height=8). 

So my question would be:
How can I add fields to the rendered Items that don't get rendered and that i can access with javascript?

Changing the module files would be ok.
My goal is to make a new inputfield with this, so I made a new version/copy of the Page Table Extended Module.
@MadeMyDay I hope it is ok for me to build that on top of this module.
Thanks in advance!

Link to comment
Share on other sites

  • 2 weeks later...

Hi. This module looks really promising for a current job, didn't know about it til now.

Does anyone have it working with TemplateEngineFactory / TemplateEngineTwig v2?

Eg if a template to be rendered in the admin does either of the below:

if($options['pageTableExtended']){
	$factory = $modules->get('TemplateEngineFactory');
	$controller = $factory->controller('controllers/content-gallery.php', 'content-gallery.html.twig');
	$controller->execute();
}
if($options['pageTableExtended']) {
	$factory = $modules->get('TemplateEngineFactory');
	$factory->render("content-gallery");
}

Only way I can get output in the admin is to change the render method in this this line from:

$parsedTemplate->render()

to:

$parsedTemplate->page->render()

Does this make sense, or should i try to hook TemplateFile::render with TemplateEngineFactory for this use case?

Link to comment
Share on other sites

Can someone help me with this?
How can I add input fields to the rendered Items that don't get rendered and that i can access with javascript?
I need to also save these fields into the database when the page is saved.

Would be awesome if someone more experienced could point me in the right direction.

Link to comment
Share on other sites

Ok, figured it out partly, don't need to change the $parsedTemplate->page->render() call in PageTableExtended since that has lots of sideffects.

Just need to capture and return the twig output like so:

if($options['pageTableExtended']) {
	$factory = $modules->get('TemplateEngineFactory');
	$out = $factory->render("content-gallery", ["p" => $page]);
	echo $out;
}

Now I am having trouble using twig filters / php functions in this context, but I believe that is more a TemplateEngineFactory / TemplateEngineTwig issue.

Link to comment
Share on other sites

9 hours ago, jploch said:

How can I add input fields to the rendered Items that don't get rendered and that i can access with javascript?
I need to also save these fields into the database when the page is saved.

Hi @jploch, not sure exactly what you are doing, but can't you have hidden fields either on the main template or sub-templates inside the PageTable that you save data to on a hook?

Link to comment
Share on other sites

9 hours ago, Mikie said:

Hi @jploch, not sure exactly what you are doing, but can't you have hidden fields either on the main template or sub-templates inside the PageTable that you save data to on a hook?

Hi! Thanks for answering! For my drag/resize page builder module I need simple text fields to store position data for every PageTable item/page (like Y=10 X=6 Width=4 Height=8).
I have to change these values dynamically with javascript. Adding these directly to the 
sub-templates renders them, so they are not accessible with javascriptWhat do you mean by hidden fields? I could add a field to my main template, where the PageTable lives and store the item positions as one big JSON array. But I would prefer to have the fields added to the sub-templates for the PageTable items/pages, so its easier to output the positions. Iam still very new to module development (this is my first attempt) and not very good with php. So I feel much more comfortable with Javascript/jQuery but Iam learning. 

I tried to modify the PageTableExtended Module code to add my fields like this (before I added the fields to my sub-templates)

<?php
foreach($pagesToRender as $p){
              $itemID++;
				$layoutTitle = $p->template->$label ? $p->template->$label : $p->template->name;
				$ext = "." . $this->config->templateExtension;
				$template_name = $p->template->altFilename ? basename($p->template->altFilename, $ext) : $p->template->name;
				$templateFilename = $this->config->paths->templates . $this->pathToTemplates  . $template_name . $ext;

				$parsedTemplate = new TemplateFile($templateFilename);
				$parsedTemplate->set("page", $p);
				$parsedTemplate->set("isAdmin", 1);
				$parsedTemplate->options = array('pageTableExtended' => true);
				$p->of(true);

				$iconClass = "fa-angle-down";
				$activeClass = "pte-open";
				$statusClass = "";
              
              //get input fields for grid item positions (they are part of the sub-template)
                $data_gs_height = $p->getInputField('data_gs_height');
                $data_gs_width = $p->getInputField('data_gs_width');
                $data_gs_x = $p->getInputField('data_gs_x');
                $data_gs_y = $p->getInputField('data_gs_y');
               
            //how to set input fields for grid based on html data attribut? I would normally do this with JS..

				if($p->is(Page::statusUnpublished)) $statusClass .= " pte-unpublished";
				if($p->is(Page::statusHidden)) $statusClass .= " pte-hidden";
				if($p->is(Page::statusLocked)) $statusClass .= " pte-locked";

				if($this->collapseUnpublished && $p->is(Page::statusUnpublished)){
					$iconClass = "fa-angle-right";
					$activeClass = "hiddenOnStart";
				}

				$layout .= '
	        				<div data-id="item-'.$itemID.'" class="'.$statusClass.' grid-stack-item" data-gs-height="' .$p->data_gs_height. '" data-gs-width="' .$p->data_gs_width. '" data-gs-x="' .$p->data_gs_x. '" data-gs-y="' .$p->data_gs_y. '">
                            
                            <div class="grid-stack-item-header">
                            <a href="#" class="toggleRenderedLayout">
	        							<i class="toggle-icon fa '.$iconClass.'"></i>
	        						</a>
	        						<span class="renderedLayoutTitle '.$activeClass.'">'.$layoutTitle.'</span>
	        						<a class="InputfieldPageTableEdit" data-url="./?id='.$p->id.'&modal=1" href="#">
	        							<i class="fa fa-edit"></i>
	        						</a> 
	        						<a class="InputfieldPageTableDelete" href="#">
	        							<i class="fa fa-trash-o"></i>
	        						</a>
	        					</div>
                            
	        						<div class="grid-stack-item-content renderedLayout '.$activeClass.$statusClass.'">
                                    <div class="grid-stack-item-content-inner">
                                    '.$parsedTemplate->render().'
                                    <div class="grid-stack-inputs">
                                    '.$data_gs_width->render().'    
                                    '.$data_gs_height->render().'
                                    '.$data_gs_x->render().'
                                    '.$data_gs_y->render().'
                                    </div>
                                    </div>
	        					</div>
	        				</div>';
			}
			$out = '<div class="grid-stack">'.$layout.'</div>';
?>

 

Link to comment
Share on other sites

Hi, @jploch . Can you explain the workflow, or maybe do a diagram.

What I think you want is:

- Admin interface uses gridstack.js
- In this context (ie your module building on PageTableExtended), each item in the grid contains the child page preview, and the page that is being previewed is where the data for gridstack.js is stored / set

If you want to save the data after dragging / resizing an element, I'd probably leverage events from the api here https://github.com/gridstack/gridstack.js/tree/develop/doc and set the data via ajax. To do that you just need an endpoint to send the data to, eg /pw/setgriddata/. Below code is not tested, just an example as I haven't used gridstack..

In the module js file:

$('.grid-stack').on('gsresizestop', function(event, elem) {
	var $elem = $(elem);
	var data = {
		width: $elem.data('gs-width');
		height: $elem.data('gs-height');
		x: $elem.data('gs-x');
		y: $elem.data('gs-y');
		id: $elem.data('id');
	}
	$.ajax({
		url: "/pw/setgriddata/",
		data: data,
	}).done(function( msg ) {
		console.log( msg);
	});
});

At /pw/setgriddata/:

if ($config->ajax && $input->post) {
	if ($p = $pages->get("id={$input->post->id}") {
		$p->data_gs_width = $input->post->width;
		// etc
		$p->save();
		return "Updated page: " . $p->title;
	} else {
		return "Could not find page: " . $input->post->id;
	}
}

You probably don't want to do this on all resizes however. If you want to do it on page save, again I would probably use gridstack events to populate the input fields you are rendering. Again, very quick... 

$('.grid-stack').on('gsresizestop', function(event, elem) {
	var $elem = $(elem);
	$elem->find(".grid-stack-input#data-gs-width")->val($elem.data("gs-width"));
	// etc
});

 

  • Like 2
Link to comment
Share on other sites

On 9/30/2019 at 7:06 AM, Mikie said:

- Admin interface uses gridstack.js
- In this context (ie your module building on PageTableExtended), each item in the grid contains the child page preview, and the page that is being previewed is where the data for gridstack.js is stored / set

This is exactly what I want to do 🙂
I will try to do it with ajax, thanks for your suggestions!!
Right now Iam busy with other projects, but I will try this as soon as I can get back to it.

I will keep you posted.

  • Like 1
Link to comment
Share on other sites

On 10/2/2019 at 7:39 PM, jploch said:

I will try to do it with ajax, thanks for your suggestions!!

Cool. Just an FYI in case you aren't aware... modules can create and remove admin pages on install / uninstall, which is where that ajax url would live.

  • Like 1
Link to comment
Share on other sites

On 10/7/2019 at 12:58 AM, Mikie said:

Cool. Just an FYI in case you aren't aware... modules can create and remove admin pages on install / uninstall, which is where that ajax url would live.

Looking at other modules, I think I have to create a process module that would create a page under admin at module install (e.g. admin->setgriddata). The process module would have the code to save the ajax request in the pageTable Item/page. Or is there better way to do this? Sorry for all the noob questions! Iam new to module development 🙂

Link to comment
Share on other sites

  • 1 month later...
  • 1 year later...

Hey folks!
Iam exited to finally show you a preview of my pagebuilder fieldtype I'm working on for quite some time now.
It's based on PageTable and takes a lot of inspiration from PageTableExtended.

@MadeMyDay Thanks for your work on PageTableExtended, it helped me a lot in figuring this out!

Let me know what you think

Link to comment
Share on other sites

  • 2 months later...

I copied the module folder to /site/modules:
/site/modules/PageTableExtended-master
Downloaded from:
processwire.com/modules/fieldtype-page-table-extended/
When I go to "modules" and "search for new modules" I get an:

Server Error
We're sorry! The server encountered an internal error and was unable to complete your request. Please try again later.
error 500

After that, an access to Modules is no longer possible in Admin. So I delete the folder, and everything is okay. What could be the reason for this?

Link to comment
Share on other sites

Try this...

  1. Enable $config->debug in /site/config.php
  2. FieldtypePageTable (or how it is called) is installed? I guess but better check this.
  3. Check if the module has the ProcessWire namespace in it. Maybe that's an issue here.
  4. If you are running PHP 8 maybe try PHP 7.4 instead.
  5. Use the latest stable version of ProcessWire

 

Link to comment
Share on other sites

@wbmnfktr 

PW 3.0.165, PHP 7.4, PageTableExtended 2.3.3 Beta
Debug-Mode is already activated.

But: I can't install the module. The moment the PageTableExtended folder is dropped, the administration is dead. Therefore I can't check it via Debug.

Link to comment
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 Robin S
      This module lets you add some custom menu items to the main admin menu, and you can set the dropdown links dynamically in a hook if needed.
      Sidenote: the module config uses some repeatable/sortable rows for the child link settings, similar to the ProFields Table interface. The data gets saved as JSON in a hidden textarea field. Might be interesting to other module developers?
      Custom Admin Menus
      Adds up to three custom menu items with optional dropdowns to the main admin menu.
      The menu items can link to admin pages, front-end pages, or pages on external websites.
      The links can be set to open in a new browser tab, and child links in the dropdown can be given an icon.
      Requires ProcessWire v3.0.178 or newer.
      Screenshots
      Example of menu items

      Module config for the menus

      Link list shown when parent menu item is not given a URL

      Advanced
      Setting child menu items dynamically
      If needed you can set the child menu items dynamically using a hook.
      Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); if($menu_number === 1) { $colours = $event->wire()->pages->findRaw('template=colour', ['title', 'url', 'page_icon']); $children = []; foreach($colours as $colour) { // Each child item should be an array with the following keys $children[] = [ 'icon' => $colour['page_icon'], 'label' => $colour['title'], 'url' => $colour['url'], 'newtab' => false, ]; } $event->return = $children; } }); Create multiple levels of flyout menus
      It's also possible to create multiple levels of flyout submenus using a hook.

      For each level a submenu can be defined in a "children" item. Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); if($menu_number === 1) { $children = [ [ 'icon' => 'adjust', 'label' => 'One', 'url' => '/one/', 'newtab' => false, ], [ 'icon' => 'anchor', 'label' => 'Two', 'url' => '/two/', 'newtab' => false, 'children' => [ [ 'icon' => 'child', 'label' => 'Red', 'url' => '/red/', 'newtab' => false, ], [ 'icon' => 'bullhorn', 'label' => 'Green', 'url' => '/green/', 'newtab' => false, 'children' => [ [ 'icon' => 'wifi', 'label' => 'Small', 'url' => '/small/', 'newtab' => true, ], [ 'icon' => 'codepen', 'label' => 'Medium', 'url' => '/medium/', 'newtab' => false, ], [ 'icon' => 'cogs', 'label' => 'Large', 'url' => '/large/', 'newtab' => false, ], ] ], [ 'icon' => 'futbol-o', 'label' => 'Blue', 'url' => '/blue/', 'newtab' => true, ], ] ], [ 'icon' => 'hand-o-left', 'label' => 'Three', 'url' => '/three/', 'newtab' => false, ], ]; $event->return = $children; } }); Showing/hiding menus according to user role
      You can determine which menu items can be seen by a role by checking the user's role in the hook.
      For example, if a user has or lacks a role you could include different child menu items in the hook return value. Or if you want to conditionally hide a custom menu altogether you can set the return value to false. Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); $user = $event->wire()->user; // For custom menu number 1... if($menu_number === 1) { // ...if user does not have some particular role... if(!$user->hasRole('foo')) { // ...do not show the menu $event->return = false; } } });  
      https://github.com/Toutouwai/CustomAdminMenus
      https://processwire.com/modules/custom-admin-menus/
    • By tcnet
      This module for ProcessWire sends a notification email for each failed login attempt. Similar modules exists already in the module directory of ProcessWire. However, this module is designed to notify, even if specified user doesn't exist.
      Settings
      The settings for this module are located in the menu Modules=>Configure=>LoginFailNotifier.
      Notification email
      Specifies the email address to which the notification emails should be sent.
        Email subject
      Specifies the subject line for the notification email.
        Post variables
      Specifies the $_POST variables to be included in the notification email. Each variable must be separated by a comma. For example: login_name,login_pass
        Server variables
      Specifies the $_SERVER variables to be included in the notification email. Each variable must be separated by a comma. For example: REMOTE_ADDR,HTTP_USER_AGENT
      Link to ProcessWire module directory:
      https://processwire.com/modules/login-fail-notifier/
      Link to github.com:
      https://github.com/techcnet/LoginFailNotifier
    • By Fokke
      ProcessWire 3.x markup module for rendering meta tags in HTML document head section. Note that this module is not a full-blown SEO solution, but rather a simple tool for rendering meta tags based on module configuration. Adding custom meta tags is also supported.
      Built-in meta tags
      The following meta tags are supported out-of-the-box:
      Document title consisting of page title and site name Character set Canonical Viewport Description Keywords Hreflang tags Open Graph og:title og:site_name og:type og:url og:description og:image og:image:width og:image:height Twitter meta tags twitter:card twitter:site twitter:creator twitter:title twitter:description twitter:image Facebook meta tags fb:app_id The full documentation with configurable options can be found here: https://github.com/Fokke-/MarkupMetadata
       
      Requirements:
      ProcessWire>=3.0.0 PHP >=7.1 Installation using Composer
      composer require fokke/markup-metadata Manual installation
      Download latest version from https://github.com/Fokke-/MarkupMetadata/archive/master.zip Extract module files to site/modules/MarkupMetadata directory.
    • By m.sieber
      ITRK-Service for ProcessWire
      Module for the automated transfer of imprint, data protection declaration and terms and conditions from IT-Recht Kanzlei to your ProcessWire installation
      What is ITRK Service for ProcessWire?
      ITRK-Service for ProcessWire is a free module for ProcessWire CMS. It provides an interface to the update service of IT-Recht Kanzlei, via which the legal texts of your online presence are automatically updated. In this way, the texts remain legally secure and warning-proof in the long term. Imprint, data protection declaration, revocation and general terms and conditions are currently supported.
      You can find our documentation (in german language) here: https://www.pupit.de/itrk-service-for-processwire/dokumentation/

      Download: https://www.pupit.de/itrk-service-for-processwire/
      Github: https://github.com/pupit-de/pwItrkServiceConnector
    • By LuisM
      Symprowire is a PHP MVC Framework based and built on Symfony using ProcessWire 3.x as DBAL and Service-Provider
      It acts as a Drop-In Replacement Module to handle the Request/Response outside the ProcessWire Admin. Even tough Symfony or any other mature MVC Framework could be intimidating at first, Symprowire tries to abstract Configuration and Symfony Internals away as much as possible to give you a quick start and lift the heavy work for you.
      The main Goal is to give an easy path to follow an MVC Approach during development with ProcessWire and open up the available eco-system.
      You can find the GitHub Repo and more Information here: https://github.com/Luis85/symprowire
      Documentation
      The Symprowire Wiki https://github.com/Luis85/symprowire/wiki How to create a simple Blog with Symprowire https://github.com/Luis85/symprowire/wiki/Symprowire-Blog-Tutorial Last Update
      16.07.2021 // RC 1 v0.6.0 centralized ProcessWire access trough out the Application by wrapping to a Service https://github.com/Luis85/symprowire/releases/tag/v0.6.0-rc-1 Requirements
      PHP ^7.4 Fresh ProcessWire ^3.0.181 with a Blank Profile Composer 2 (v1 should work, not recommended) The usual Symfony Requirements Features
      Twig Dependency Injection Monolog for Symprowire Support for .env YAML Configuration Symfony Console and Console Commands Symfony Webprofiler Full ProcessWire access inside your Controller and Services Webpack Encore support Caveats
      Symfony is no small Framework and will come with a price in terms of Memory Usage and added Overhead. To give you a taste I installed Tracy Debugger alongside to compare ProcessWire profiling with the included Symfony Webprofiler

      So in a fresh install Symprowire would atleast add another 2MB of Memory usage and around 40ms in response time, should be less in production due to the added overhead of the Webprofiler in dev env
       
×
×
  • Create New...