adrian

Looks like @ryan just upgraded the modules site from PW 2.x to 3 and that has caused something to break. I no longer have access to the admin so I can't see what the cause of the error is, but hopefully he'll read this ?

This is the version I am experiencing the issues with. I actually assumed (wrongly now that I look at that Maria page) that I was running a version that was compatible with MySQL8. Maybe the issues I've been having are not specific to "8" but rather default settings that come with MariaDB that don't come with MySQL? Not sure at this point. The main issues that have shown up are cases where PW was not setting the value for the table's sort field or other similar instances where a value is required. Maybe it's even just the way Maria throws errors - maybe it throws errors where MySQL doesn't bother. Really not sure without spending more time which I don't have at the moment - sorry!

@MoritzLost I am running: MySQL Server: 5.5.5-10.3.22-MariaDB-0+deb10u1 This is the default version with Debian these days, although the reported numbers for these are always a bit confusing - I have no idea why there is 5.5.5 before the 10.3.22. Honestly I think hosts should be upgrading - these versions of MySQL have been the stable release for a couple of years now - I think Ryan is lagging behind on this so having hosts upgrade might prompt him to also upgrade his environment.

@michelangelo - the AdminActions module also has an action for this:

@Craig - thanks for your work on this. If a cronjob is run it throws this error: PHP Notice: Undefined index: HTTP_USER_AGENT Would you mind disabling this module when called via the CLI, eg. PHP_SAPI !== 'cli' Thanks!

There have actually been quite a lot of issues. Ryan has fixed several of them, but there are still some outstanding issues and I expect more will continue to surface and AFAIK Ryan still hasn't upgraded his dev environment so he's not seeing them and not being able to replicate so there has been some guesswork and back and forward with me on them. That said, I do have several sites running on MySQL 8 / MariaDB 10 so I am reporting new things as they come up. Not ideal, but hopefully they'll all be sorted sooner than later. However if I were you, I wouldn't upgrade yet.

Have you had a look at alpinejs - a good option if you are already familiar with Vue

@Kola - glad you figured it all out ? The key thing here is that it's not really the ASMSelect inputfield, but rather the Page Reference fieldtype that's behind it - because you have that set to store multiple values you need to use the add() method. Same would go for checkboxes etc.

@gmclelland - looks like you have upgraded from a very old version of Tracy - just go to the module settings page and save it and the error will be gone.

I did mention that above ?

I've had issues with MySQL passwords with special characters before. I hadn't thought about which character was causing the problem, but I agree with @horst that the $ is the likely problem.

@digitex - I agree that there are still some big issues with this. Setting widths to use percentage-based widths in the Uikit theme settings seems to help with many of the issues, but definitely not all. Have you seen this mammoth issue thread: https://github.com/processwire/processwire-issues/issues/480 (linked above by Robin). The default admin theme definitely works better than Uikit on this front.

Hi all, I just added the ability to restrict access to custom FieldsetTabs which makes it easier to block certain user roles from having edit access to entire sets of fields (in the selected tabs). I also added a new "Exempt Roles" setting that makes it easy to make sure certain roles are not affected by this module - particularly useful if you use the "View" permissions approach.

This works for me: $store->getUnformatted('products');

Yeah, that version is 3 years old ?

What about ditching the "3" ? IIRC there wasn't an API variable for the first version anyway, was there? Wouldn't this be cleaner going forward?

Just to clarify, are you do a Modules > Refresh? It also works fine for me. But. again, please don't use this technique for CSS tweaks - it will result in lots of unnecessary pain when the core version of the module is updated.

Ok, but overriding CSS doesn't require creating a new copy of the module. Just inject the CSS you want into the PW admin - I use AdminOnSteroids for this, but there are other ways.

Hi @Mike-it - I have updated the module to fix this. I have also done a lot of code cleanup and a few improvements. Let me know how it goes.

Deprecated, not yet removed, so no need to totally panic, although there are a few problematic bugs with PW and MySQL 8 that I have discovered and am notifying Ryan as I find them. Keep in mind that v8 has been the stable release for 2 years now.

Just an FYI for anyone who reads this - this is deprecated since MySQL 8: https://dev.mysql.com/doc/refman/8.0/en/information-functions.html#function_found-rows I have told Ryan here: https://github.com/processwire/processwire-issues/issues/1146#issuecomment-629428382

https://docs.gravityview.co/article/626-google-maps-error-referernotallowedmaperror Looks like you haven't set up your Google account to allow access from your site's domain.

Firstly, are you sure you need to modify the module for "style editing"? In case you haven't read already: https://processwire.com/docs/modules/guides/comments/ Secondly, if you do find you need to modify, I would consider upgrading to the very latest dev as there have been some major changes to the comments field and an important bug fix. Consider those before worrying about why the approach you are taking isn't working yet.

@gornycreative - https://github.com/rolandtoth/AdminOnSteroids/issues/118

Hey @bernhard - do you have support for getting fields from a page reference field? Something like: addColumns(['title', 'pagefield.title']) I feel like this should be fairly easy if the page field is a single item only. Not sure the best approach if it is set up to store references to multiple pages though. I guess this is similar to your support for the Options fieldtype where you use: "OptionsValue:sex" in the docs example. Any thoughts on whether this could be supported? I guess I could add it myself via the "columnTypes" folder, but I feel like this will be a common enough need that it should be included. Nevermind - I really should RTFM ?