Jump to content
MadeMyDay

Module: PageTableExtended

Recommended Posts

This looks like a fantastic piece of work, great job! But like Pete, I hadn't even noticed PageTable field yet :P, I got it from Reno's tweet!

Share this post


Link to post
Share on other sites

I'd noticed the field and used it, just not the bit where you can add multiple templates in order to be able to drop in different content editor "blocks" (I hate that term, but it fits here) in whatever order you like.

Share this post


Link to post
Share on other sites

It would be nice if the required `title step` can be avoided when using multiple templates. But maybe this is out of scope of this module as it is a thing ProcessWire could handle. 

  • Like 1

Share this post


Link to post
Share on other sites

Only works if there's one template allowed or do I miss something ?

Ahh, it's a setting in the PageTable field. 

Edited by Martijn Geerts

Share this post


Link to post
Share on other sites

Hey Martijn,

I managed this by using the automatic naming option and by setting the title field to hidden and not required in the template context settings (so it doesn't affect other templates) and that seems to be working ok.

The one thing I am really missing (and maybe this is just me) is for the PageTable sub pages to be stored in some sort of hierarchy when using an alternate parent page. I can see a complete mess of hundreds of pages ending up in there, with various -n name appendices. Maybe it would be unnecessary extra cruft, but what if sub parent pages (named to match the actual page that uses the PageTable field) were made to store the PageTable pages. e.g.:

Home
----About (has a PT field called Sections)
----Portfolio (has PT field called Jobs)

PageTableItems (hidden)
----About
-------Sections
-----------Section 1
-----------Section 2
-----------Section 3

----Portfolio
-------Jobs
-----------Job 1
-----------Job 2

instead of the current situation of:

PageTableItems (hidden)
Section 1
Section 2
Section 3
Job 1
Job 2

I know the latter looks simpler, but I can see it becoming a mess and confusing when page names were automatically changed to avoid conflicts.

Anyone agree, or am I on my own :)

  • Like 3

Share this post


Link to post
Share on other sites

@adrian,

I managed the title thing now with making the title not global. ( Gonna try your thing, think thats better :-) )

Yesterday, I played the first time with the pageTabeExtended and didn't even looked at the parent where the subpages are stored.

Building a small website for a friend so storing isn't an issue right now.

Your example looks way better IMHO, but I would go for page id instead of page name (uniqueness insured)

Just to throw one more option in:

PageTableItems (hidden) 
----1234		         // page id (where tablefield is used)
-------sections		         // fieldname
-----------template-timestamp    // name of the template used + timestamp date-created
-----------template-timestamp
-----------template-timestamp

----2345
-------jobs 
-----------template-timestamp
-----------template-timestamp
Edited by Martijn Geerts
When using ID it's not unique when using multiple pageTable field per page

Share this post


Link to post
Share on other sites

Adrian,

I have about 8,000 pageTable pages under a single parent (invasive plant species database). I just consider it a closet that I'm never going to look in. :)

So far I haven't had any issues.

  • Like 2

Share this post


Link to post
Share on other sites

Adrian,

I have about 8,000 pageTable pages under a single parent (invasive plant species database). I just consider it a closet that I'm never going to look in. :)

So far I haven't had any issues.

Maybe you're right - maybe I shouldn't worry about it - maybe it really doesn't matter how messy it gets in there :)

  • Like 1

Share this post


Link to post
Share on other sites

I think we need an option "don't ever display children here" as a template setting. At least for editors. Even I am a bit confused when I accidentally open a folder in the tree where all this data crap is in ;)

  • Like 5

Share this post


Link to post
Share on other sites

When I found out about ProcessWire I missed a configurable Repeater right from the start. The new PageTable module is nice but not quite there. Your module is a step in the right direction. If it wasn't required to enter a title for every added block it would be perfect!

Share this post


Link to post
Share on other sites

Does anyone know why I would be having trouble updating this module? I have tried to update it manually and through PW's interface, but I keep getting version 0.0.8. ModuleManager keeps telling me there is an update to 0.1.0 available, but when I go through the updating process, it still says I have 0.0.8. I am just working on a local wamp setup, so it isn't a matter of life and death; I'm just wondering if I am doing something wrong.

Share this post


Link to post
Share on other sites

Try "check for new modules" to clear things out. The update should show then.

Share this post


Link to post
Share on other sites

That didn't work. The weird thing is, when I open the module files, the version number is version=>010. Everything in the admin persists on listing it as 0.0.8.

Share this post


Link to post
Share on other sites

Hmm. If "check for new modules" didn't clear it up, you can try deleting the module cache files in /site/assets/cache/.

Someone else might have a better explanation as to why that's happening. I feel like I've run into it before, but can't remember exactly what I did to resolve it.

Share this post


Link to post
Share on other sites

Thanks for your help. I may put this on the back burner for a bit and see if I can't get some of the same functionality from Hanna codes.

Share this post


Link to post
Share on other sites

I guess it just depends on what you need. Hanna codes are great, but nearly as robust a solution as pageTable(Extended).

I'm sure someone else will chime in with more details, but good luck whatever route you take.

Share this post


Link to post
Share on other sites

I was seeing the same thing. I went in to the two .module files and changed the version numbers from "010" to "10" and refreshed the modules list and voila. Not sure if that really was the issue, but it worked for me. Ryan mentions this:

"The module version number shouldn't have preceding zeros, as this starts PHP thinking it's an octal number or something else (I don't recall). So version number should be 10 rather than 010."

PS The module files were actually already the correct version - just the reporting that was off.

  • Like 1

Share this post


Link to post
Share on other sites

Good to know! Thanks, guys. The correct version number is probably a trivial thing in this regard, but I appreciate your help and the clarification.

Share this post


Link to post
Share on other sites
"The module version number shouldn't have preceding zeros, as this starts PHP thinking it's an octal number or something else (I don't recall). So version number should be 10 rather than 010."

didn't know that. Updated the version number. Thx!

  • Like 1

Share this post


Link to post
Share on other sites

I have a couple more issues. I'll add, let's say, a block of text using the PageTableExtended field. When I hit the publish button in the modal window, it does not publish. I check the settings panel in the modal box, and it consistently has the box checked for "Unpublished." When I uncheck that box and go on about my business, everything works out wonderfully, but I cannot get it to publish the "regular" way. Am I doing something incorrectly?

Also, I have noticed that when I make changes to one of the PageTableExtended blocks on a page and save the page it is a part of, I get a warning about a "Missing required value" under the Title label. I assume it means I'm missing a title somewhere, but the page has a title and the PageTableExtended blocks have automatic titles. Anyone have any guesses?

Thanks!

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