adrian

Thanks @zoeck - seems like the documentation for all this is spread all over the place which I don't think is helping Ryan get renewals. Honesty I would probably have renewed more often if I'd known about the cheaper price.

Thanks @zoeck - that page does show: Renewal Terms $39/year But then (presumably because it's expired), when I click on "Upgrade", it says "ProDevTools (Agency) $170 upgrade charge (the difference in price). Optional $89/year yearly renewal of support and upgrades after first year." I don't think upgrade is the right option, but there are no other buttons/links on that first page that actually work - the others are links to the forum thread which I no longer have access to. I can get to a page that says: "1 x Renew: ProDevTools" but this invoice has expired so I can't pay. I guess if you don't renew before your original subscription expires, you can't get it for the renewal price. I don't know if that's intentional or a limit of the forum store?

@ErikMH - I don't think I have ever seen a discounted renewal option. How do you renew a module for those reduced prices?

I don't get a notice from LRP either. For the backend, I tried both a dash and now an underscore and neither work. I did manage to login via the backend after a few attempts.

Thanks @Robin S - I tried logging in via the backend login form. I couldn't, but I managed to use the password reset which worked, but then I still couldn't login with that new password via the backend or frontend forms still.

@ryan - I can no longer log into the modules directory. I don't get any notification as to why either, but I do see this JS error (which might be unrelated). Uncaught ReferenceError: Inputfields is not defined <anonymous> https://d1juguve2xwkcy.cloudfront.net/modules/WireRequestBlocker/ProcessRequestBlocker.js?v=4-3.0.251:43 fire https://d1juguve2xwkcy.cloudfront.net/assets/pwpc/pwpc-e1739702c839f9ff94bc214b49a3df07d7cbaa03.js:1 fireWith https://d1juguve2xwkcy.cloudfront.net/assets/pwpc/pwpc-e1739702c839f9ff94bc214b49a3df07d7cbaa03.js:1 ready https://d1juguve2xwkcy.cloudfront.net/assets/pwpc/pwpc-e1739702c839f9ff94bc214b49a3df07d7cbaa03.js:1 completed https://d1juguve2xwkcy.cloudfront.net/assets/pwpc/pwpc-e1739702c839f9ff94bc214b49a3df07d7cbaa03.js:1 ProcessRequestBlocker.js:43:2

@Mike-it - sorry, it's not possible at all with the way the module works. A workaround is @teppo's https://processwire.com/modules/admin-restrict-branch-select/ which extends this module. Not quite what you are looking for, but maybe it will suffice.

Worth a read! "The lesson here is to never mix manually constructed SQL fragments and bindings when using PDO emulation. You are opening yourself up to a huge risk by doing so as a single misparse results in SQL injection. If you are a developer: Disable PDO::ATTR_EMULATE_PREPARES if possible; If not, ensure you are on the latest version (PHP 8.4) and you do not allow null bytes in your queries." https://slcyber.io/assetnote-security-research-center/a-novel-technique-for-sql-injection-in-pdos-prepared-statements/

Just a quick note that most of Ryan's pro modules don't appear under paid either.

@Mike-it - the latest version supports the Options field type but note that you need to use the numeric key for the option rather than the label, so 1 or 2 rather than Yes or No, for example.

@Jonathan Lahijani - not sure if this is what you are looking for, but all Tracy's settings can be overridden in config.php like: $config->tracy = [ 'outputMode' => 'development', 'guestForceDevelopmentLocal' => true, 'forceIsLocal' => true, ]; Not sure if those are the exact options you want, but hopefully that approach works for you.

And a JS error is preventing anyone from showing on the map.

Honestly I would find another host - having chmod disabled is likely to continue to cause problems.

@AndZyk @ryan @diogo - also reported here: https://github.com/processwire/processwire-issues/issues/2110

Are you also hosting with lautre.net ? Looks to me like they have disabled chmod() in php.ini

@Kiwi Chris - would it work to use the hook you showed above, but limit it so it's only applied on the frontend so it doesn't break things in the admin? Maybe I am still not understanding full though?

Hi @Kiwi Chris - this module is all about restricting branch access in the admin (so basically viewing and editing in the admin). It does not attempt to prevent viewing on the frontend at all. I honestly find the page-view permission in PW very confusing in certain situations and it has some bugs associated with it - the latest I found is: https://github.com/processwire/processwire-issues/issues/2107 I assume you are attempting to lock things down after the recent security issue that was eluded to (although the implications not really explained as well as they should have been) here: https://processwire.com/talk/topic/31385-pw-30251-–-core-updates/#comment-249810 ?

@Pete - I've just pushed a lot of critical fixes, so just in case you have already started testing, please grab the latest version. I knew there was a good reason I hadn't looked into doing this before :)

Hey @Pete - if you want to try it out: https://github.com/adrianbj/TracyDebugger/tree/namespaced I am not ready to commit to the master branch yet because there were a lot of changes required and I have a feeling I still might have missed some things - most likely core PHP things like DirectoryIterator etc that need to be prepended by \ to get them called from the global namespace.

Hey @Pete - I maintain four different Tracy core versions which are all included and used based on the version of PHP available. I have also made a real effort to ensure PHP 7 compatibility (maybe even 5 - not sure). A Tracy upgrade is basically instantaneous on all my servers/installs so I've never thought of the compiling process as an issue. Adding a namespace is probably more of a big deal with so many panels and reliance on the Tracy core itself - maybe just a matter of lots of backspaces to start loading things from the global namespace. The one other module I namespaced was AdminActions and it was a real challenge but that was mostly due to trying to support installed custom user actions whether they were namespaced or not. Still, it put me off namespacing others. I'll try to find some time to see what's involved sometime soon.

It works here (if you're patient enough), but as noted above it's a pretty useless demo because the admin is so bare - basically useless and a very poor advert for PW.

Hi @Pete - sorry, I haven't used EFS - I have a regular EBS setup on AWS so I don't really know why the file compiler is causing you issues - for me it's been seamless for years so I have never seen the need to add the PW namespace to any of my modules. I do it for all my template files, but figured why break modules for any old PW 2.x installations if I don't need to. For me it compiles it once when the module is updated and then it's just as quick as it would be if it was namespaced because the compiled version is loaded all the time. Is it because your EFS setup is used by multiple EC2 instances and that somehow why it needs to be re-compiled every time? You mention "it compiles otherwise when file compiler is on - which for me is most of the time as there are modules I use that are not in a namespace" - does that mean that if one module isn't namespaced it's making all recompile on every page load?

You're right of course! Contentful has been the leading commerical headless CMS for quite a long time, so they are doing something right. I was asked to build a site with it about 10 years ago - I declined because I loved working with PW and couldn't understand the reason to spend so much on a commercial service like Contentful, but they are definitely successful - there are some very big names on this list: https://trends.builtwith.com/websitelist/Contentful

Ok, but I think it needs an "All" button (as the default) and then "Featured" could be just the featured modules - otherwise I think it's quite confusing.

Can I humbly make an overarching statement on my thoughts about website design. I think there are certain types of sites that should have artsy, flashy, animated content and large fonts - these can make the right impression and be part of the visual experience. But when it comes to technology, I think clean, simple, and free of distractions is needed. Take a look at how clean https://www.contentful.com/ is and compare with https://www.sanity.io/ which is mess of moving stuff that I just want to gloss over. I also think you might have missed a key marketing point - "headless"