Leaderboard

For our final dev branch version of 2017, we've added a couple new features that I think you'll find useful. For starters, we've added drag-and-drop (and paste) image upload support to our richtext editor (CKEditor), which is really handy. We've got all the details and a short screencast here as well. https://processwire.com/blog/posts/pw-3.0.87/

I'm quite impressed by https://canadabusiness.ca/ They built a full-blown REST server with ProcessWire: https://canadabusiness.ca/developer/docs/ And widgets too: https://canadabusiness.ca/developer/widgets/ Does anybody know who built this site?

Radio Hala96 FM is a radio service that aims to promote the community through presenting a program map with creativity and thought for all groups. On March 15, 2014, Hala began a live broadcast with a unique programming program that brings you daily on a useful and exciting weekend trip. The Website Is Developed By I&S Group & Powered By The Great ProcessWire & It's Awesomeness That We All Love. .

here is a screenshot of a dashboard, i'm using a simple grid framework + a free admin theme (AdminLTE 2) + masonry for the 'widgets'; i use 3-4 types of widgets, one is a set of shortcuts which is configurable to show on different users, or access levels; this allows individual users to have their own custom set of shortcuts if needed. The other types of widgets are a mini lister, and a formbuilder list; The formbuilder list can display recent submissions to various forms, and is helpful for admins who want to see a quick overview of recent submissions.

Access for Process modules is managed using the 'permission' item in the getModuleInfo() array. You can also create the permission and the page for the Process via getModuleInfo(). You'll need to uninstall then reinstall your module for the settings to take effect. See Ryan's ProcessHello demo module. And the comments in the Process class.

I guess @pwuser1 was asking about a code-editor / IDE that supports jQuery autocomplete while typing etc. Just about any code-editor should support it, or at least have extensions. Try Sublime or VSCode.

Did you logout/login the client user?

@nickngqs, a few more options for executing API code: Tracy Debugger's Console panel Tracy Debugger's Snippet Runner panel Admin Actions module

Yeah, I think this belongs in @pwuser1's other thread about IDE autocompleting in general. While you might find one editor better for jquery code completion and a different one that's better for php code completion, are you really going to switch editors depending on what you are working on? Just find a good editor and download a plugin for jquery code completion - all the big ones will have one.

You have three possibilities. The first one, you can write the code in a template file inside your site/template folder, the second you can write the code in a bootstrapped script in the root directory (or where you want, you just have to adjust the path of the index.php). The thrid, inside a module. Read the whole thread, you should find what you need. What are you trying to achieve ?

I wish Wasn't me, but it's great having an official government site on PW.

All, I intend to give this module some love soon. As part of this, I'm considering how to allow custom names for Columns and Rows (i.e. other than pages).

Ahh! Thanks! Managed to get this working guys! You'll need to login and log out again

Don't know if I am getting ahead of myself but the custom code option to get the selectables could be like this (this code can be placed in site/ready.php as per the field's instructions): $wire->addHookAfter('InputfieldPage::getSelectablePages', function($event) { if($event->object->hasField == 'page_reference_field') { //the page instance where the field exists, in this case, Item 4 for example $page = $event->arguments('page'); //the reference to the project $currentProject = $page->parent('template=project'); //has_parent sets the parent limit for the find() $event->return = $event->pages->find("has_parent=$currentProject,template=subitem_template"); } });

@Federico, There were a number of issues in Version 004 of VPS (the one you got) when used in ProcessWire 3, especially if using the default theme. All those issues have been ironed out in Version 005. It is currently being beta tested. I hope to release it next week. If you cannot wait until then, I am happy to send you the pre-final Version 005 to use instead.

Hi guys, I am working on a blogpost to convince customers in doubt that ProcessWire is right for them. The article is almost ready, but first only in german and will be published on my website soon. It will be translated after publishing. One question that would be answered is "You have heard that ProcessWire is relatively unknown or not widely used" and I want to bring up some well-known brands as examples, that are using PW. Right now I have this list, but they are not so well-known: BMW Test Drive BMW Dealersites Die Höhle der Löwen Produkte Maxim Markenprodukte Jentschura´s Regenata KF Interactive Werbeagentur Dojo Werbeagentur FriendChip Verband österreichischer Banken und Bankiers Metasystems Informatiktage Captiva Writer Relocations So, do you know any big names, that use ProcessWire as their CMS?

Hi Guys It would be awesome when all the resource about processwire (tutorials, docs, cheatsheet, recipes, videos, api, faq etc...) would be unified on one documentation website called "docs.processwire.com". The new site would gather infos & data from these resources: https://processwire-recipes.com/ http://processwire.tv/ https://www.pwtuts.com/ https://processwire.com/docs/ http://cheatsheet.processwire.com/ and would unified it on the final site https://docs.processwire.com. I think It is far more better to have one endpoint for all the processwire resources & wisdom then mutliple sites. This way it is far more easier to get into the processwire world and choosing processwire as the next main cms for further projects. The Documentation Site could perhaps look like this (it is just a mockup, so don't expect to much from me ):

I get a fatal error, when I want to edit a page that has no image field. Well, actually there are image fields, but they are part of repeaters or matrix-repeaters, or some other fields. btw: this refers to the wire module file, not site The template of this page has the following fields/field-types: I feel kinda bad for posting all these issues... I'm sure the community can wait till 2018 until these things are ironed out. Enjoy your well-deserved holidays!

Hi Eugene, This is now sorted in version 022. Thanks.

Update: Menu Builder 0.2.2 As of today and this version onward, ONLY ProcessWire 3.x is supported. Changelog Support for namespaced ProcessWire only (ProcessWire 3.x). Various bug fixes to getMenuItems(), breadcrumbs and saving menus in multi lingual environments (thanks for all reports in GitHub and the forums). Available now in the modules directory. Please note that this version does not address any PHP 7.x issues. Screen: Menu Builder in UiKit

You might want to remove that NatGeo India site - unfortunately it is now on WP

With Firefox, I can drag and drop, but copy+paste does nothing. If I drag and drop, and right click on "image properties", I get the same errors I posted above... Once I save the page, the image stays in the WYSIWYG editor, but it hasn't been added to the images-field. And right-clicking again only shows the same errors... checking the HTML source code, I see the image src is still the remote (source) URL. I don't know if this is related, but my JS console is showing the following error: 17:27:24.227 ckeditor.js:253 Uncaught Error: [CKEDITOR.resourceManager.add] The resource name "mystyles" is already registered. at CKEDITOR.resourceManager.add (ckeditor.js:253) at /site/modules/InputfieldCKEditor/mystyles.js?nc=1512242401&t=2015030801.160:9 the contents of mystyles.js: /** * mystyles.js * * This file may be used when you have "Styles" as one of the items in your toolbar. * * For a more comprehensive example, see the file ./ckeditor-[version]/styles.js * */ CKEDITOR.stylesSet.add('mystyles', [ {name: 'Inline Code', element: 'code'}, {name: 'Inline Quotation', element: 'q'}, {name: 'Left Aligned Photo', element: 'img', attributes: {'class': 'align_left'}}, {name: 'Right Aligned Photo', element: 'img', attributes: {'class': 'align_right'}}, {name: 'Centered Photo', element: 'img', attributes: {'class': 'align_center'}}, {name: 'Two Columns', element: 'p', attributes: {'class': 'columns-2'}}, {name: 'Three Columns', element: 'p', attributes: {'class': 'columns-3'}}, {name: 'Justify', element: 'p', attributes: {'class': 'justify'}}, {name: 'Small', element: 'small'}, {name: 'Deleted Text', element: 'del'}, {name: 'Inserted Text', element: 'ins'}, {name: 'Cited Work', element: 'cite'} ]);

Hey @arjen. This is a list I published in my blog article Why ProcessWire is the best choice for your website (not always, but in most cases) to convince people, that ProcessWire is not so unknown.

That's a nice one to end the year Unfortunately, the new CKEditor image feature doesn't quite work as expected. (Win 8, latest Chrome). I can copy + paste, and drag and drop. But when I right-click on the image and select "image settings", I see this in the modal: ProcessWire: ProcessPageEditImageSelect: No page specified DEBUG MODUS ABLAUFVERFOLGUNG ($config->debug == true): #0 /home/mysite/public_html/dev.mysite.ch/wire/core/Modules.php(607): ProcessWire\ProcessPageEditImageSelect->init() #1 /home/mysite/public_html/dev.mysite.ch/wire/core/Modules.php(1288): ProcessWire\Modules->initModule(Object(ProcessWire\ProcessPageEditImageSelect), Array) #2 /home/mysite/public_html/dev.mysite.ch/wire/core/ProcessController.php(168): ProcessWire\Modules->getModule('ProcessPageEdit...', Array) #3 /home/mysite/public_html/dev.mysite.ch/wire/core/ProcessController.php(259): ProcessWire\ProcessController->getProcess() #4 /home/mysite/public_html/dev.mysite.ch/wire/core/Wire.php(380): ProcessWire\ProcessController->___execute() #5 /home/mysite/public_html/dev.mysite.ch/wire/core/WireHooks.php(714): ProcessWire\Wire->_callMethod('___execute', Array) #6 /home/mysite/public_html/dev.mysite.ch/wire/core/Wire.php(442): ProcessWire\WireHooks->runHooks(Object(ProcessWire\ProcessController), 'execute', Array) #7 /home/mysite/public_html/dev.mysite.ch/wire/core/admin.php(113): ProcessWire\Wire->__call('execute', Array) #8 /home/mysite/public_html/dev.mysite.ch/wire/core/admin.php(113): ProcessWire\ProcessController->execute() #9 /home/mysite/public_html/dev.mysite.ch/wire/modules/AdminTheme/AdminThemeUikit/controller.php(15): require('/home/mysite/...') #10 /home/mysite/public_html/dev.mysite.ch/site/templates/admin.php(15): require('/home/mysite/...') #11 /home/mysite/public_html/dev.mysite.ch/wire/core/TemplateFile.php(287): require('/home/mysite/...') #12 /home/mysite/public_html/dev.mysite.ch/wire/core/Wire.php(380): ProcessWire\TemplateFile->___render() #13 /home/mysite/public_html/dev.mysite.ch/wire/core/WireHooks.php(714): ProcessWire\Wire->_callMethod('___render', Array) #14 /home/mysite/public_html/dev.mysite.ch/wire/core/Wire.php(442): ProcessWire\WireHooks->runHooks(Object(ProcessWire\TemplateFile), 'render', Array) #15 /home/mysite/public_html/dev.mysite.ch/wire/modules/PageRender.module(514): ProcessWire\Wire->__call('render', Array) #16 /home/mysite/public_html/dev.mysite.ch/wire/modules/PageRender.module(514): ProcessWire\TemplateFile->render() #17 /home/mysite/public_html/dev.mysite.ch/wire/core/Wire.php(383): ProcessWire\PageRender->___renderPage(Object(ProcessWire\HookEvent)) #18 /home/mysite/public_html/dev.mysite.ch/wire/core/WireHooks.php(714): ProcessWire\Wire->_callMethod('___renderPage', Array) #19 /home/mysite/public_html/dev.mysite.ch/wire/core/Wire.php(442): ProcessWire\WireHooks->runHooks(Object(ProcessWire\PageRender), 'renderPage', Array) #20 /home/mysite/public_html/dev.mysite.ch/wire/core/WireHooks.php(808): ProcessWire\Wire->__call('renderPage', Array) #21 /home/mysite/public_html/dev.mysite.ch/wire/core/WireHooks.php(808): ProcessWire\PageRender->renderPage(Object(ProcessWire\HookEvent)) #22 /home/mysite/public_html/dev.mysite.ch/wire/core/Wire.php(442): ProcessWire\WireHooks->runHooks(Object(ProcessWire\Page), 'render', Array) #23 /home/mysite/public_html/dev.mysite.ch/wire/modules/Process/ProcessPageView.module(205): ProcessWire\Wire->__call('render', Array) #24 /home/mysite/public_html/dev.mysite.ch/wire/modules/Process/ProcessPageView.module(205): ProcessWire\Page->render() #25 /home/mysite/public_html/dev.mysite.ch/wire/core/Wire.php(383): ProcessWire\ProcessPageView->___execute(true) #26 /home/mysite/public_html/dev.mysite.ch/wire/core/WireHooks.php(714): ProcessWire\Wire->_callMethod('___execute', Array) #27 /home/mysite/public_html/dev.mysite.ch/wire/core/Wire.php(442): ProcessWire\WireHooks->runHooks(Object(ProcessWire\ProcessPageView), 'execute', Array) #28 /home/mysite/public_html/dev.mysite.ch/index.php(55): ProcessWire\Wire->__call('execute', Array) #29 /home/mysite/public_html/dev.mysite.ch/index.php(55): ProcessWire\ProcessPageView->execute(true) #30 {main} Der Prozess hat keinen Inhalt ausgegeben. (the process didn't return any content) Once I save the page and do the same thing again, those errors are gone. Do I have to adjust my settings somewhere?

Yes, thanks. @rafaoski added a site profile using Bootstrap 4 updated there :

Nice one Canada should be adrian's territory - I hope they hired him

Bootstrap 4 is in beta now and there are some differences. Most important: It uses Popper.js instead of Tether.js https://medium.com/@lukaszholeczek/how-to-upgrade-bootstrap-4-alpha-6-to-bootstrap-4-beta-d43b4210f2a3 Just for information.

elabx, many thanks! Your solution does it. Works perfectly! Many thanks to all of you! Happy new year!

For the "Selector string" option I think the correct syntax is: has_parent=page.parent

I use a dashboard for most big sites, and shortcuts on there to all of the major interactions; i have clients who interact with their content only through the dashboard and lister pro listers, and some settings pages that have shortcuts to edit on the dash...

Depending on how much you want to change, you can always do CSS overrides. Put this line in /site/templates/admin.php, above the line that brings in controller.php: $config->styles->append($config->urls->templates."admin.css"); Make a file in templates called "admin.css". Now let's say you want to change the navbar color: #pw-masthead { background: #666 !important; }

Just do this: $pages->find("template=files, include=hidden");

Hi @Hurme $pages->get() returns Page or Null https://processwire.com/api/ref/pages/get/ I guess that what are you looking for is $pages->find() https://processwire.com/api/ref/pages/find/

@bernhard , thank You ! It's nice to see that i can do something useful for the community. I clearly understand that anyone can have his own preferred colors, but the convenience and positive UX can be achieved if we will accept some simple design rules. Consistency. Any color, any font variation should have the same meaning across the whole app. E.g. every link should be blue, every visited link should be grey and so on. The current AdminThemeUIKit has no major drawback of this kind. The link and button colors should mean what they mean in common. The blues and greens are the metaphor of something positive, greys are neutral, light greys are about something disabled and/or inaccessible. As for reds -- they're commonly threated as a sign of risk and a metaphor for dangerous actions. Here lies one of the important drawbacks of current AdminThemeUIKit . Every link is red -- why? The "positive" buttons like "Add new something" become red when hovered -- what is the reason? Okay, we humans are able to quickly adaptate to almost everything. But adaptation always means discomfort and perplexion. High contrasts and bright colors are for wow effect only. Admin interfaces need the light, moderate-contrast and calm appearance. The current color scheme of AdminThemeUIKit has the major drawback of high contrast and bright colors. Details are below. The bigger area we fill with color the less bright and less saturated this color should be. Just imagine the AdminThemeUIKit's header totally filled with red: it will be extremely annoying. The current almost-black header fill is also far from being ideal. Too dark, too saturated, too much contrast with the rest of the page. This big area needs a light, low-brightness, low-saturation filling. On the other hand, the textual links deserve the bright and highly saturated colors (but not reds please, at least for "positive" links). Hope this will help. And thanks again for a perfect product!

Maybe I am incorrect, but it seems like you are trying to WP'ize PW. I think that it makes more sense to educate the client that in PW the page tree is hierarchical and this makes much more sense than having Posts and Pages listed at the same level, with Home below Pages. Maybe if you need Posts, Categories, Media, etc to stand out you could make use of icons in front of those parent pages? It might give the visual cues that the client needs to find these easily amongst the other top level pages?

Might sound a little insignificant to mention, but I have found myself using the GOTO Page ID feature a lot but it was annoying me that there was no way to open the View/Edit links in a new tabs. Well, now you can - just use your standard "new tab" shortcut: middle-click, right-click > new tab, CTRL+left-click, 3-finger click, etc - really handy!

Continuing on from yesterday's Console enhancements: 1) History stack now supports the state of text selection and the scroll position, so now much easier to run different versions without reselecting. 2) This selection and scroll position state is also recorded as you edit so it is also available if you reload your browser, etc so everything will be as you left it. 3) The editor window within the console should now always get focused when the panel itself is made visible (by hover or click). Previously this wasn't reliable. This makes running code much easier because the keyboard shortcuts for running will work without needing to click into the editor window to focus it. Unrelated to the Console panel - I have made the "Show debug bar in backend" checked by default on module install. Of course you can always uncheck this, but I find the debug bar just as useful in the backend, especially the Request Info panel when editing a page, template, field, or module settings. So consider this an attempt to enlighten new users to the benefits of it in the backend because I am sure many never bother to enable it. Please let me know if you find anything amiss with the new Console functionality.

Sorry for the quick follow up. The latest version now supports non-contiguous and partial line selections, so now you can do this: Note the partial line selections in this example:

This is a minor change, but I am actually really excited by it The Console panel now supports running just the selected code. I often find myself using the Console panel to test variations of code to see which is faster / more efficient. The time and memory usage is displayed after each request, but it's often a bit of a pain to keep commenting out some of the code, testing it, and then uncommenting that and commenting out the other, etc. Now you can have multiple functional bits of code and just run one at a time. You can see in these examples that I am selecting different chunks of code to be run and I can clearly see which one uses more time and memory.

Hi everyone, Relatively major new version just released: 1) New run on init, ready, finished option in Console panel I am not sure how popular this will be, but it lets you inject code from the Console panel into the PW process at init, ready, or finished. This lets you test hooks and other code that you would normally add to the init.php, ready.php, or finished.php files without having to edit files, and also without affecting anyone else viewing or working on the site. This screenshot should give you the idea: As you can see, I have added a hook to change the page title on saveReady. The way it currently works is that you: enter your code click Run to "register" the code for the next page request select "init", "ready", or "finished" as the place to have it injected In this example, you would then save the current page and the hook would be injected into init() and the page title will change If you don't switch back to "off" when you are done testing, it will expire in 5 minutes. The Console panel icon will also change to a red color to provide a visual indicator that you have an injection running on each page request. Please give me feedback on this feature - if you guys are annoyed by having those options visible and you never plan on using this, I'll make it an option that can be turned off completely. 2) Make User Switcher available without setting to "DEVELOPMENT" mode When I initially built the User Switcher I was a little paranoid about the possible security implications so went a little overboard by making it only available when hardcoded to DEVELOPMENT mode. But in reality this didn't make any difference and just made it more difficult to use, so now you'll find it easier to use - it's such a great feature! If you haven't used it, give it a go! 3) Options to hide debug bar from Form Builder iframe Having the debug bar in a Form Builder iframe can be useful, but also a visual annoyance so now you can disable if you want. 4) Hide User Bar from Form Builder iframe This is automatic as there is no reason for the User Bar to appear in a Form Builder iframe and it is confusing for users and ugly. 5) Restricted panels now works with "tracy-restricted-panels" role as well as permission (needed due to recent PW core change) Due to a recent change in the PW core, it is no longer possible to edit the permissions for the superuser role, so I have now added support for assigning a "tracy-restricted-panels" role to a user. The "Restricted Panels" defined will then be applied to users with this role. The permission option will continue to work for other non-superusers. 6) ACE editor update 7) Other bug fixes / tweaks

Here are a few links to check out for PW calendars. I'm not recommending a solution here, just signposting. These are in the official PW module repository... https://github.com/ffub/MarkupiCalendar (iCalendar feeds anyone?) https://github.com/netcarver/PW-ProcessGcalEmbed (My old module) http://www.99lime.com/modules/recurme/ (Premium) These aren't (a.f.a.i.k.)... https://github.com/plauclair/Calendar https://github.com/ryancramerdesign/MarkupLoadGCal (Ryan's module) https://github.com/decadeofdefeat/church-website-processwire (Has a calendar implementation in it) https://github.com/lindquist/processwire-calendar https://github.com/UF-Asq-Fab-Lab/Scheduler Hope that helps!

Thanks @Samc and @maxf5, you gave me an idea about the future of my AdminOnSteroids module, rewriting it as an admin theme. This has been come up earlier too but there was no Uikit theme then, now it's perhaps more easy to do this.

OK, after a long struggle I manage to find the solution. First, I had problems to add the domain in the App settings. Solved thanks to this post https://stackoverflow.com/questions/8769238/app-domain-is-not-a-valid-domain Then I changed these settings as described here and finally it worked! full post here https://stackoverflow.com/questions/37063685/facebook-oauth-the-domain-of-this-url-isnt-included-in-the-apps-domain

Curious what everyone else thinks. Maybe it won't be a huge deal in most cases, but I can see sites with certain header and footer content being cutoff with this design. Have a read of their developer guidelines - yet another thing to consider in our designs: https://developer.apple.com/ios/human-interface-guidelines/overview/iphone-x/ Honestly I think more square corners for the device itself look better and I think the screen should be completely square - I feel like this is stepping back to old TV rounded corners: Note that I don't like the edge of the Samsumg Galaxy S8 either - I feel like it looks weird and I am sure your hands would end up covering the edge of what you are trying to view. Sorry for rambling, but I am curious what everyone else thinks they should be aiming for both esthetics and functionality?

Great selling point for wp theme coders "iphone x compatible"

Okay, so it turns out I was wrong, but only for the bottom, which kinda makes sense for them, but may not work nicely in a range of scenarios. Edit: landscape mode crops both sides.

Just one more thing. Personally I will not give a damm about the guidelines you linked to. I want to adhere to standards only. If Apple (aka Jony Ive) wants to cut off part of my design then it is his choice. I will tell my clients that it is Apple's fault. They should stick to industry standards but they deviated. I'm strong with the Force in this Either way, it is good to know Apple has gone mad, thanks for the post!

Hey! This is a very early/experimental/alpha not for production environments release of a new module I'm working on. Just testing the possibilities and the interest that might be for such a thing. The idea is to be able to quickly create fields while working inside the template files without having to go to the admin. For example, in an early stage of development when creating a layout, insteading of putting a placeholder headline and then going to the admin to create the headline field where the real content will be, you can create the field directly from the template file by doing: <h2><?=$page->field("A nice headline", "headline", "text")?></h2> This will create a new "headline" text field when it doesn't exist in the system and add it to the the template of the page you're working on and add "A nice headline" value to it. On a second run the module will recognize that the field already exists on that template and will simply return it's value. The method accepts three string parameters in the order ( value, field name, field type ). Value and name are required but field type will assume "text" when omitted. $page->field("A nice headline", "headline"); // creates a text field $page->field("A nice paragraph", "body", "textarea"); // creates a textarea field The method also accepts a boolean parameter in any position: TRUE forces the value to be saved into the field on that page, FALSE (or omitted) sets that value to the field when it adds it to the template, but leaves it how it is when the field already exists in the page. This is the only situation when this module can be destructive, and it's only concerning the value of the field on that page: $page->field("Another nice headline", "headline", TRUE); // will create or add a text field and add the value to the page even if the field already exists there The method also accepts an array as parameter. This array will be used as options for the creation of the field. The options array will override the string parameters when they clash. $page->field("A nice headline", "headline", array( 'name' => 'subtitle', 'label' => 'Subtitle' )); // will ignore the name "headline" and use "subtitle" instead As soon as the fields are created and added to the template, all the method will do is return the value, just like if using $page->headline, unless you use the TRUE parameter which will override the value of the field by the value in the first parameter. -- With this module you can, for instance, convert an existing HTML template quickly, just by pasting the html into a template with no fields created yet, and going through all the code, replacing the content by calls to my field() method. In the end you should have a working page with all the fields created in the template. Now you just need to go to the fields and adjust their preferences. So, just download it > install it > test it > tell me what you think! dynamicPageFields.module.zip -- Edit: Multilanguage fields threw an error but they don't now. You can create a multi lang text by doing: $page->field("A nice headline", "headline", "textlanguage"); that third parameter is just a case insensitive simplification of input field names to make it easier to write. You can still use the original input field name like "FieldtypeTextLanguage" if you prefer.

Removing the session_start() from the AutoFbPost.module at the beginning solves this problem

@Lance - I think you'll find that for the most part it is easiest to keep the pagetable pages as children of the page, but it will also depend a lot on your structure, and whether that page has children already, in which case put them somewhere else.. some examples of where i've use pagetables, and i think it will make sense: | Page | PageTable Children | |-----------|--------------------| | Album | Tracks | | Slide | Captions | | Portfolio | Images | | Vignettes | Vignette | i think if you use the reno theme and also lister pro, it actually won't matter that much where you put them; but in a lot of cases having them as children keeps things tidy and you can always get the relation of a pagetable item by calling it's parent. and you can add pages not through the page table, and it will pick them up and ask you if you want to add them. For PDFs, depending on the amount on one page, i might still consider good old repeaters