Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by fruid

  1. just curious, what framework does this very proccesswire.com community forum use? First I though it's some from scratch side project by processwire but then I came across https://forum.affinity.serif.com Hi there, I can answer that 😄 https://invisioncommunity.com/
  2. I will look into that and post my code eventually. thanks!
  3. I ran the first query, it says @@character_set_database utf8mb4 @@collation_database utf8mb4_german2_ci so that setting doesn't solve my problem after all… should I try with utf8mb4_german2_ci ?
  4. yes it is in the list. Actually I don't know anymore where to set the CharSet at all (let alone that I didn't find utf8mb4 in the list). I think mixed it up with the dropdown in the import tab. So how to set the CharSet to begin with? And then, I thought I changed the collation for one specific database but it seems like that's a setting that applies to the whole server? Not good…
  5. I cannot find the MySQL version. It's not in the database settings in the host and there's no Database server widget when I click on the home icon in phpMyAdmin and also I do not have SSH access. Something so simple, so far…
  6. I tried that. First of all, I don't see utf8mb4 in the list of charsets, as suggested in the stackOverflow answers, so I cannot select it. Then, trying to change the collation to utf8mb4_unicode_ci or utf8mb4_german2_ci doesn't help, I think it requires the charset to be set to utf8mb4 as well. If I check "Change all tables collations" and "Change all tables columns collations" I get an error like so The behaviour in the frontend of my project doesn't change anyway. I'm not very knowledgeable in that area anyway, so thanks for help!
  7. thanks, ->selectorValue seems good BUT it breaks when the value contains Umlaute (äöü) It puts the value in between double quotes "" which breaks the rest of the selector and whatnot. 😞
  8. I have an issue with selectors, whenever there is a comma in the selected value… $foo = $item->foo; // "what, ever, with, commas" $bar = pages()->get("template=foo_template, title=$foo"); then I get Fehler: Exception: Unknown Selector operator: '[empty]' -- was your selector value properly escaped? (in wire/core/Selectors.php line 222) Because it thinks that what ever is after the comma is the next selector. Though the value in question is not expected to have commas, this shouldn't happen. How can I escape it properly? And then, also, even though I'm NOT in config debug mode, Tracy Debugger is NOT active and I am NOT logged in, i.e. not superuser, I still get the error in the frontend, breaking the entire output script, showing me no CSS (I use markup regions). That's of course not a good user experience. Shouldn't it show a white page instead? Do I have to use a try-catch code block?
  9. need to pick this up, as new issues arose. with PW 3.0.207 the pagination seems to work fine on admin templates, but for ProFields Table, the pagination neither works in .207 nor in .200 though the behaviour is slightly different. I guess I need to update, i.e. buy the newest update of that module then?
  10. this works like a charm! thanks a lot @gebeer
  11. Thank you all a lot for your efforts, at least I'm not alone here… One more thing, in the process module, I'm trying to amend the $results->getPaginationString() I have: 'count' => count($results), 'start' => $results->getStart(), 'limit' => count($results), 'total' => $results->getTotal() But I would like to use a specific field of the first and last result in the array on any given page, much rather than what ever $results->getStart and count($results) returns. I cannot just do 'start' => $results->first->someField;
  12. 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/
  13. 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.
  14. 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
  15. 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.
  16. 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.
  17. 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.
  18. 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
  19. …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.
  20. 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.
  21. PW 3.0.200 PHP 7.3 MySQL 5.7 if that helps
  • Create New...