Jump to content
MadeMyDay

Module: PageTableExtended

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

Share this post


Link to post
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?

Share this post


Link to post
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

Share this post


Link to post
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!

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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!

Share this post


Link to post
Share on other sites

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?

Share this post


Link to post
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.

Share this post


Link to post
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.

Share this post


Link to post
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?

Share this post


Link to post
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>';
?>

 

Share this post


Link to post
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

Share this post


Link to post
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

Share this post


Link to post
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

Share this post


Link to post
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 🙂

Share this post


Link to post
Share on other sites

Hey @jploch sorry I missed this. How’d you go? I am not 100% sure on the above, creating a hidden admin page with a Process module is the simplest way to do it, but i think you can use Ajax with inputfields, like talked about here:

 

  • Like 1

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 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 Pip
      Hi everyone!
      I'm trying out the Login/Register module for my site. Noted that the module assigns the newly registered user to login-register role. 
      Once you modify the login-register role's permissions, particularly adding page-edit, the new member role will be set to guest. 
      Thing is I'd like to grant my new users the power to create their own pages. Any advice? 
      Thanks. 
    • 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');
×
×
  • Create New...