dynweb

When editing a template like this: As long as a template does not define its own access rights, the option "Yes always, regardless of page status or access control" has no effect: it "sticks" in the admin interface, but the folder /site/access/files/XXX is not prefixed with a "-" and access control is not enforced. The file is delivered by Apache. If the template defines its own access right, it works as expected (by me). The file is delivered by PHP. It this expected behavior? Is there some good reason why a template must define its own access rights to enforce access control to files? Thank you for your insights. Edit: Tested on latest PW stable, pristine install.

You can choose on your implementation if you want to charge the user's card immediately ("capture") or only reserve the funds for later capturing (via Stripe admin or API). The only problem is that it doesn't make much of a difference to the user (Stripe event advises that many users won't see a difference on their CC statement between "reserved" and "captured" amounts). Even if an amount is "only" reserved, the client can no longer dispose of these funds.

I would definitely be interested... if some client would ask for a (PW integrated) forum. Must be at least 10 years now that I haven't had such a requirement. So I am not sure that there still exists a sizable market for (new) forum softwares...

if(class_exists('\Tracy\Debugger', false) && Debugger::isEnabled()) return; Works for me. We just tell PHP to skip autoloading, so it will never know about the composer version.

Not really ? At this point, Debugger is probably not enabled, so no output at all. if(class_exists('\Tracy\Debugger')) { \Tracy\Debugger::enable(); return; }; This one works, but the Tracy bar has none of the ProcessWire specific info (as the init() method returns early). if(class_exists('\Tracy\Debugger')) { $this->wire('session')->error('Cannot activate TracyDebugger because another version is already installed, maybe via composer?'); return; }; This kind of error message, however, would be really helpful for people like me who don't remember the stuff they have in their vendor directory...

Seems as if Debugger::isEnabled() returns false after a fresh composer install so it can't prevent double loading. I just have to be careful not to require tracy/tracy via composer (or nette/nette that adds *all* packages), so this shouldn't be a major problem ?

OK, problem solved ? Tracy is working with a pristine PW install. All my "customized" installs have a vendor directory where I (previously) did a composer require nette/nette which also installs tracy in the vendor dir. And this version is loaded first, resulting in the "Cannot declare..." error. Thank you for your help, @adrian !

Thank you, @adrian I can reproduce the error on my local dev server and on the live server(s). I already tried to to refresh modules and to clean the file compiler cache, to no avail. I still have to test it with a pristine processwire install, I will let you know...

Starting with version 4.3.26, I get a compile error after installing/upgrading Tracy: Compile Error: Cannot declare interface Tracy\ILogger, because the name is already in use (line 16 of site/modules/TracyDebugger/tracy-2.9.x/src/Tracy/Logger/ILogger.php) It seems that this commit https://github.com/adrianbj/TracyDebugger/commit/10e1d3a28a2719d120325eaf4559505c3ebd98a9 is source of the error. When removing the line if(class_exists('\Tracy\Debugger') && Debugger::isEnabled()) return; everything is working again. Tested on PW 3.0.184 and 3.0.200. Any input will be appreciated -- I have no idea where to start ?

Download works for me, too. Just in case: Have you checked that you have the correct time on your localhost? That might prevent the cert to validate.

You might want to try $http->download($url, $file, ['verify_peer' => false]); Or maybe additional context options: https://www.php.net/manual/en/context.ssl.php

Sorry to derail this thread, I would like to download the new version from my download link, but it seems to be the same version that I bought in May 2020. It always says v0.1.2 β... Thank you ?

This shouldn't be a problem ?

Have you ever thought about using a repeater field (instead of CKE) for user input? One repeater item for each tab? This would be much easier for the client and certainly less error prone...

This put me on the right track ? I had a Pages::saved hook that set output formatting to true (when it shouldn't). Thank you!