dragan

Did you check your browser JS console as well? Keep an eye on the network tab as well (you can filter by XHR).

Did you try custom (field / value) and then "modified>=today" ? (modified=today for some reason doesn't work) (manually entering modified>2018-01-01 14:00 worked for me too)

Do you mean MarkupPagerNav? I never tried to use this inside a custom admin page, I'm not even sure it's supposed to work in the backend too. Looking at the docs (filed under "frontend")... did you do step 2? Enabling Pagination Determine what template(s) you want to use pagination with. Go to Admin > Setup > Templates > [Your Template] > URLs, and check the box for: Allow Page Numbers. Save. Most likely, your template is "admin" (?), so I'm not sure if this possible at all.

What's your relevant code in your template file? That's not an image/file URL, i.e. not $imagefieldname->url What's inside this array? I guess the images? Or is it empty? Looking at your screenshot, why is there a visible <img src=... in the middle of nowhere? Did you inspect that?

Can you show us some code?

There are a few settings under module/edit?name=SessionLoginThrottle

I'll gladly do so and try to find a pattern that might help to isolate/identify the root cause. Alas, this week I'm short on time ?

Yes. PageType with template service. title: PageTitle! Field with the type of FieldtypePageTitle It's listed in the config under "legalFields" (showing as "title (system)"). However, I can't choose it from legalPageFields, i.e. the dropdown doesn't list it.

No, they all have a template assigned (most though without a physical file - don't think that should matter). I only ever just use the system-field title. Is that not included? Strange thing is that if I replace title with name in the query, it works. But (again, just for some PR fields) if use title, I get errors.

@dadish Thanks for the quick update / fix. I tried it again today, and while empty int fields are no longer a problem, I get some other strange issues: I can query some page reference fields, but not others. The error shown is like: Unlike with the integer issue, the output stops, i.e. there is no additional data output shown. I compared a pageref field that doesn't throw GraphQL errors with another one that does: The one that works shows this in the documentation explorer panel: (when searching with the field-name) ProductPageArray ProductPage ProjectPage.product ProjectCreateInput.product ProjectUpdateInput.product While others just show: ProjectPage.industry ProjectCreateInput.industry ProjectUpdateInput.industry (project = template, product + industry = page reference fields) Does that give you a hint what's happening behind the scenes?

I never used Hanna Code myself, but can't you just do $buttons = $hanna->render("[[subscribebuttons]]"); and then $out .= $buttons; ? Don't know if you gotta have $hanna = $modules->get('TextformatterHannaCode'); inside or before your function definition though...

Since @ryan most likely won't read this thread, maybe someone should open an issue (with label "enhancement") here: https://github.com/processwire/processwire-requests/issues?q=is%3Aopen+is%3Aissue+label%3Aenhancement Most probably, this would mean a huge refactoring of lots of core-code, but hey, we would all profit from a performance boost in situations mentioned in this thread.

Yes, just a regular integer field. I was just thinking... Most fields in the pages / template I'm querying are optional. Granted, I didn't do extensive testing so far, but I guess it throws errors each time when there is no value in a field. (hence, the selector "only show if images.count > 0" was working fine). Could that be? Earlier it just outputted empty nodes or null instead (which I would expect and is totally fine).

I finally found some time to install the brandnew version and do some tests. I made sure I cleared the modules cache, and cleared file compiler cache. But I get some strange behaviour in the test-tool (pw-admin/setup/graphql/) : Did anything major change in regards to query syntax? This used to work previously: Now I get lots of errors. Even something smaller throws errors: If I remove "budget" field, it works. I double-checked it's in the allowed fields in the module config. Something similar happens when I include images, and some pages don't have images. i.e. With this selector it works as expected: project(s: "industry%=verwaltung, images.count>0, sort=-year, limit=3") If I just do project(s: "industry%=verwaltung, sort=-year, limit=3") { I get stuff like this: Funny thing is, the output at the bottom after "data": { "project": { "list": [) still looks OK to me. Do I see these error messages only because the site is in debug-mode? Or because I do this in the backend as superuser?

My only concern would be that a lot of page references can slow down page-loading in edit-mode in the admin. But just for updating / creating / reading such values, I don't think performance would suffer. You can always completely hide these PR fields in the admin (or choose to only load via AJAX when opened).

https://superuser.com/questions/7327/how-to-add-a-custom-search-engine-to-firefox https://addons.mozilla.org/de/firefox/addon/custom-search-engine/ Or just bookmark my Google Custom Search Engine (or create your own): https://cse.google.com/cse?cx=013706179141317928628:dendm4c3gpq The nice thing about GCSE is that you can freely configure several domains/sites where it should search: As you can see... it's been used quite frequently :-)

To increase the chance that Ryan even sees your suggestion, I'd create a post in the Lister Pro forum (feature request). Who knows, maybe with a hook it can be already done somehow today...

Yeah, well in that case it really seems impossible. Can't you narrow it down with some other condition? has_parent, template, or similar? I know you said you want something future-proof, but certainly you are not adding new templates every day? Field dependencies let you write your own logic in plain PHP (one of many options), I guess Ryan has a reason he didn't allow such freedom when it comes to Lister (Pro or not) - probably security concerns. You might want to take a look at @bernhard's RockGrid module instead. A bit more work initially than just creating a new Lister Pro instance, but you're totally free to list / select / query whatever you like.

grumble... sorry, but my first example doesn't indeed work. It seems that this (quite surprisingly) does seem to work: page.fieldname= At least in my test-environment, it lists all pages (my field only exists in only one template)

Try it with include=all as another filter.

Well, there's no selector "if template / page has field_x", so a workaround could be two custom selectors: custom (field=value) 1 = meta%= custom (field=value) 2 = meta!= Make sure to check the checkbox on the right (make it OR rather than AND)

well, whatever field-name it is - "body" or whatever you've named it.

Do you mean you place that class in CKEditor? You have to enable inline classes, otherwise the richtext editor strips it away when saving. Admin => Setup => Fields => Your field => Input => Extra allowed content Enter something like a[*]{*}(*) config / syntax examples: https://ckeditor.com/docs/ckeditor4/latest/guide/dev_advanced_content_filter.html#custom-mode

Maybe you need to add a getForPage() in there? https://processwire.com/talk/topic/18880-getting-one-repeater-items-as-content-for-other-repeater-item-on-the-same-page/ Try to use Tracy Debugger and see what dumps you get. https://adrianbj.github.io/TracyDebugger/#/debug-methods?id=bardump

@dadish Great news indeed! Big thanks for this rewrite. Can't wait to try it out (probably not before the weekend).