adrian

@Saugatdai - if I have the module correct, you're probable better off posting your issue over here: https://processwire.com/talk/forum/62-padloper/

I recently extended PrivacyWire (via hooks) to handle opt-in and opt-out models and during my research the one key thing I discovered is that the province of Quebec also requires the opt-in model, so I also use Maxmind's region_code to allow support for specifying which model is used at the region, and not just country level. I also added support for showing a "Opt out request honored via privacy signal" temporary toast message when the browser has set a Global Privacy Control (GPC) policy, rather than either of the opt-in or opt-out banners. @maximus - does the module support these options?

Claude is always asking me to test things via Tracy console. This is why I added to the copy MD for agent, including the Copy All button at the bottom. It lets it understand the file/template/data structure and also to run comparisons on the data retrieved when refactoring code or adding new features. I much prefer this to giving Claude direct access to the site DB - this way I can check each query it's about to make and to choose whether I provide it with the complete results or not. Not that it is a real lock, but Tracy does have a setting to prevent all access to superusers with another role so if they don't know about Tracy then you could keep them out. Best bet would be to define this setting via $config>tracy rather than in the module settings so it's harder for them to override.

Hi @Robin S - sorry for delay in responding, but thanks for the follow up. I haven't used that module regularly in so long. Anyway, glad you figured out an approach that works for you. Cheers.

This is exactly why I tweaked mine to look like this with the top/bottom border (box-shadow) on hover. You get the definition you need with a nicer grey (IMO). with: .PageList .PageListItem:hover { box-shadow: inset 0 0.5px 0 0 #ccc, inset 0 -0.5px 0 0 #ccc; border-radius: 0 !important; }

But don't all elements have the grey border which helps to separate them from the background - I think that is why #fbfbfb works.

I agree with @Peter Knight - I set --pw-main-background: #fbfbfb; on all my sites, but I am sure#f5f5f5 would also be a better default.

So does that mean that 2.0 fixed all the issues that you just reported as being present in 1.4.1? Can I make 2.0 the new master version?

FYI - latest commit fixes that bug.

Just a note for everyone to be aware of this critical bug in this version if you have any save hooks: https://github.com/processwire/processwire-issues/issues/2269

My reasoning for wanting a download is so it's easy to get it, modify it in a local image editor and upload it again as the replacement for it. I feel like this is a good and valid use case. I do use RockAdminTweaks to add a download button to an image in the page editor, but without that, downloading the fullsize version of any image in PW is actually very fiddly. Thanks for the explanation about the replace restricting the extension. I didn't realize just how it worked, keeping the same filename etc. I am related note, does renaming a filename in the interface also replace all references to it in RTE fields?

Sorry, I just noticed the column ordering options - I know it explains what to do, but I think a move icon next to each one would make it clearer. I also do feel like there needs to be an option to set the default order in the settings because site editors will likely not realize they can reorder them.

Sorry @Mikel - the page column was staring me in the face, but because of the order my columns are appearing it was right next to the image and I think I sort it felt it was an image label or something. But I am curious how you are changing the column order? I also can't get the Used In column to appear. Should there be a checkbox to check here: Another request, but could you add a download button to each thumbnail? Also, when I use the "Replace" button, it won't let me upload an image with different extension to the existing image - is this intended? It feels off - surely any extension supported by the image field should be allowed?

Hi @Mikel - what do you think about having a column that lists (and links to: edit and view) the page that the image is uploaded to? Obviously the parent page, not repeater item pages. Also, I am seeing an issue where editing an image that is on a user page and on separate tab (not the main content one) doesn't strip out all of the other fields - I actually get the full page edit interface. I haven't tested, but I expect it's the user page issue, rather than the separate tab.

Awesome, thanks!