Module: PageTableExtended

[MadeMyDay]

Perfect. Thank you Pete!

/merged

[onjegolders]

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

[Pete]

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.

[Martijn Geerts]

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. 

[MadeMyDay]

No problem. Just define an autoformat:

[Martijn Geerts]

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

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

Edited September 4, 2014 by Martijn Geerts

[adrian]

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

[Martijn Geerts]

@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 September 4, 2014 by Martijn Geerts
When using ID it's not unique when using multiple pageTable field per page

[renobird]

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.

[Martijn Geerts]

(invasive plant species database)

(invasive Page species database) 

[adrian]

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

[MadeMyDay]

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

[bipster]

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!

[renobird]

Hey bipster,

Entering a title isn't required. Have a look at this thread. https://processwire.com/talk/topic/7477-strategy-for-flexible-content-types-in-a-template/#entry72309

[bipster]

Thanks renobird!

[thistimj]

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.

[renobird]

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

[thistimj]

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.

[renobird]

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.

[thistimj]

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.

[renobird]

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.

[adrian]

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.

[thistimj]

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.

[MadeMyDay]

"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!

[thistimj]

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!