froot

We recommend downloading the dev version if you are using it locally for development, while we recommend downloading the master version if it will be immediately used in a live/production environment (like if you are upgrading an existing installation). It is also generally safe to use the dev version in production after thorough testing in an non-production environment. – https://processwire.com/download/core/

OK I just tried something else… upgrading to dev branch 3.0.207 (newest dev branch), replacing master branch 3.0.200 THAT WORKED!! Now that's not to say there won't be any other issues that I'm not aware of at this point because, you know, it's the dev branch but at least that tells us something, right? Not sure what it tells me but it just seems to be a bug that has been fixed? So when is the next master version coming? Needless to say I would like to avoid using the dev branch for a live site.

OMG this is so frustrating. here's some other stuff I tried uninstall all modules delete all modules delete all unused field delete all unused templates empty the trash (actually deleted the modules from the file system first and then under "missing" deleted all modules one by one from the database) delete the cache table in the database delete the cache folder in the file system mess with the .htaccess file switch the admin theme turn on and off javascript for this browser use other browsers absolutely nothing helps and no error whatsoever. What else is left to try? What would you do next? uninstall PW start over? Are there some phpmyadmin settings that I'm not aware of? thanks for help

what else can I try? It must be the database. I uninstalled all modules and the file system is like from a new installation. All I did was import the /log/ folder from an older installation so that I'd have enough data to paginate through. That's it but still cannot use the pagination.

didn't help but thanks

I can rule out the effects of ready.php and init.php, I didn't try yet with all other template files but will do so today, I think that's the next logical step. But then also, in the second attempt I described, where I just use the same database and none of the files from the file system, it doesn't work either. So if you think about it, the files couldn't be the problem either. That's why I have to assume that the issue lies in the database, but I wouldn't know how to go about finding the problem let alone repairing the database. Like I said, the diagnostic tool says it's fine. I clicked on it, but not much seems to happen other than that the warning disappears. But it returns eventually. Can't say for sure what table it is in the db (cause right now the warnings are gone) but often times it's a some cache. Some pages of a certain template amount to 4 digits, if I filter anything that has an ID it amounts to 8000 something, so that can't be it either.

I feel like I tried everything at this point. Install a fresh PW (200) with new database and one by one install the same modules as in the broken installation and test if at some point the pagination stops working. But it always works. And I tried the other way around. I duplicated the broken installation's database and pointed the new installation to that database. As expected, the pagination doesn't work then. Then I UNinstalled all the modules one by one. But pagination never works. Uninstalling the modules, deleting the modules, clearing cache, compiled files. Deleting unused fields, unused templates, deleting all modules that require an update according to the diagnostics module. Uninstalling and deleting the diagnostics module, uninstalling and deleting Tracy Debugger. Nothing helps. Tried in different browsers too. Cleared cookies, cache, all the good stuff. The only issue I ran into when uninstalling all fields and template that used some special module was this: Dangit… Fatal Error: Uncaught Error: Call to a member function set() on null in site/modules/FieldtypeColorPicker/FieldtypeColorPicker.module:46 I must have uninstalled some field or module that is required to edit the field in question. Don't know what though and I think I can assume that that's not the issue. Now I cannot edit the field, thus cannot delete it. Anyway, I'm again, out of ideas. Is my database corrupted? Diagnostics says it's fine. Are there too many entries for PW to handle? BTW, what does that mean? (ProcessDiagnostics) P.S. This is what I dislike about this work/job/career. I can handle and enjoy logical errors because that just requires thinking and reasoning. But Debugging is basically searching for a needle in a haystack, it takes hours, days or weeks until you solve the problem and when it's done, the work that went into it is pretty much invisible to the client so it's hard or impossible to put a price on it, after all, I chose the tool that I would work with.

I'm positive it has nothing to do with Lister Pro per se because like I said, the pagination doesn't work for any module that uses pagination in this installation. Also pretty sure it has nothing to do with the PHP version, it's the same PHP version for all other projects with no issues elsewhere. (MAMP sets one version for all projects) PW version is 200 which is the master version. MySQL version is also 5.7 for this and all other projects, so I guess I can rule this out too. Other things I've tried: exclude ready.php (maybe some hooks are messing up the admin) – no changes exclude init.php (probably pointless cause that's just for frontend?) – no changes I'm out of ideas

…with that in mind, does that look weird to you? also, whenever I echo anything outside the <content></content> tag, it's echoed twice. I'm using markup regions BTW. It might not seem related, but I think it's worth mentioning in this context.

I thought about that too, but I doubt that solves the bug or what it is. Also, it's not like the admin template is listed among all other templates for me to edit.

PW 3.0.200 PHP 7.3 MySQL 5.7 if that helps

in one PW project of mine, none of them work. I mean name any module that shows a pagination in the admin backend and the pagination doesn't work, core or site module. My guess is it has to do with some sort of redirect somewhere though I cannot make out where and why. Lister Pro module for example at least shows an error: {"error":false,"message":"Unknown Lister action"}

but why don't the links work? And what about other modules that use pagination in the admin backend, why does their pagination not work either and do they not use Process class?

OK but does it work when you click on 2, 3, 4… ? Cause I get it to look as in your demo but the links don't work. What are you doing differently?

I'm having difficulties paging/paginating an array of pages inside a process module. (template "admin") In the frontend, this seems to be more straightforward, but in admin, it seems to not know the segments. It shows the pager, it limits the results, however when I click on the next or any page it says "ProcessWire: Unrecognized path" and "Der Prozess hat keinen Inhalt ausgegeben." or something. The URL adds the segment /Seite2/ I thought I'd just have to allow pagination and segments in the settings of the listed pages's template, like I'm used to, but no, there must be more to it. Has anyone been there? Also, in other modules (not mine) I can see the pagination not working either. If I click on another page inside the pager, it reloads the same page.

thanks @gebeer that sounds promising, will give this a try. Follow-up question: Is there a way to switch the email sender method by API? (I very much guess so) Once the quota is reached, I’d like to try sending over the web server. So far couldn’t accomplish that.

just curious, how is a InputfieldCheckbox field different to a FieldtypeOptions field with only one option?

I need to just set it once for an array of pages because the checkbox field would be new to them. After that the checkbox field would be set upon page creation. I'll give the Tracy Debugger option a try then. Thanks @gebeer!

a checkbox field cannot be checked by default? also: Admin Action "Field Set or Search and Replace" cannot batch set a checkbox field's value? ?

thanks but no other service should be used. I just want to know if it's technically possible to know if an email was actually sent. I thought ->getResult() or the like would return an object of some sort.

my SMTP-server has a limited amount of emails that it can send per day. Is there a way to find out if an email was actually sent or not?

I have a field of type float and when I populate it with say 12.34 and save, the value changes to 12,34 In the frontend, it also outputs 12,34 which is NaN What to do? Weirdly, the same setup works on my localhost (outputs a float 12.34 in the frontend) but NOT on the remote server.

if ($item->$field >= 0 && $item->$field !== '') { this did the trick, thanks a lot for the input @Jan Romero

this is simply not true, for floats at least, it does NOT make a difference between 0 and empty value ?

And then also, there's one scenario where the value IS indeed 0, and NOT empty. So I need the condition to be true if the field value is literally 0 and not true if the field is actually not populated. if ($item->$field >= 0) { … } // this is true even if the field is not populated – not expected if ($item->$field >= 0 && $item->$field != '') { … } // this is false even when the field value is actually 0 – not expected if ($item->$field != '') { … } // this is false even when the field value is actually 0 – not expected It seems like which ever way I twist and turn it, I can't get it right. (I realise this is now off topic because I'm not even using the ->parent() API with selector anymore, because it seems to make this matter even harder)