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 bernhard
      --- Please use RockFinder3 ---
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory (pending approval) If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
    • By Craig
      I've been using Fathom Analytics for a while now and on a growing number of sites, so thought it was about time there was a PW module for it.
      WayFathomAnalytics
      WayFathomAnalytics is a group of modules which will allow you to view your Fathom Analytics dashboard in the PW admin panel and (optionally) automatically add and configure the tracking code on front-end pages.
      Links
      GitHub Readme & documentation Download Zip Modules directory Module settings screenshot What is Fathom Analytics?
      Fathom Analytics is a simple, privacy-focused website analytics tool for bloggers and businesses.

      Stop scrolling through pages of reports and collecting gobs of personal data about your visitors, both of which you probably don't need. Fathom is a simple and private website analytics platform that lets you focus on what's important: your business.
      Privacy focused Fast-loading dashboards, all data is on a single screen Easy to get what you need, no training required Unlimited email reports Private or public dashboard sharing Cookie notices not required (it doesn't use cookies or collect personal data) Displays: top content, top referrers, top goals and more
    • By daniels
      This is a lightweight alternative to other newsletter & newsletter-subscription modules.
      You can find the Module in the Modules directory and on Github
      It can subscribe, update, unsubscribe & delete a user in a list in Mailchimp with MailChimp API 3.0. It does not provide any forms or validation, so you can feel free to use your own. To protect your users, it does not save any user data in logs or sends them to an admin.
      This module fits your needs if you...
      ...use Mailchimp as your newsletter / email-automation tool ...want to let users subscribe to your newsletter on your website ...want to use your own form, validation and messages (with or without the wire forms) ...don't want any personal user data saved in any way in your ProcessWire environment (cf. EU data regulation terms) ...like to subscribe, update, unsubscribe or delete users to/from different lists ...like the Mailchimp UI for creating / sending / reviewing email campaigns *I have only tested it with PHP 7.x so far, so use on owners risk
      EDIT:
      Since 0.0.4, instructions and changelog can be found in the README only. You can find it here  🙂
      If you have questions or like to contribute, just post a reply or create an issue or pr on github, thanks!
    • By MoritzLost
      Sorry for the convoluted title. I have a problem with Process modules that define a custom page using the page key through getModuleInfo (as demonstrated in this excellent tutorial by @bernhard). Those pages are created automatically when the module is installed. The problem is that the title of the page only gets set in the current language. That's not a problem if the current language (language of the superuser who is installing the module) is the default language; if it isn't, the Process page is missing a title in the default language. This has the very awkward effect that a user using the backend in the default language (or any other language) will see an empty entry in the setup menu:

      This screenshot comes from my Cache Control module which includes a Process page. Now I realize the description sounds obscure, but for us it's a common setup: We a multiple bilingual sites where the default language is German and the second language is English. While the clients use the CMS in German, as a developer I prefer the English interface, so whenever I install a Process module I get this problem.
      As a module author, is there a way to handle this situation? I guess it would be possible to use post-installation hooks or create the pages manually, but I very much prefer the declarative approach. The page title is already translatable (through the __ function), but of course at the time of installation there is no translation, and as far as I'm aware it's not possible to ship translations with a module so they are used automatically. Could this situation be handled better in the core? I would prefer if the module installation process would always set the title of the Process page in the default language, instead of the language of the current user.
×
×
  • Create New...