All Activity

Yep, I just released a new version to fix the issue you just reported. You can download with the PW Upgrade module, or via Github (https://github.com/adrianbj/TracyDebugger) or composer. The older versions are also available on Github under releases: https://github.com/adrianbj/TracyDebugger/releases

Thank you for your swift answer, @adrian . Just to be sure and to avoid the nth trouble with installing/uninstalling: I downloaded the new version last week. Is there a new version since then? (sorry, I don't know in what file inside the module zip I can find the version number) and: where can we find old versions of the modules? (for example, in case the new one rise some incompatibilities with other modules, PHP version, etc.) Once again, thank you for your trouble answering me.

@Jonathan Lahijani - are you talking about the PW Upgrade module, or my old Toolkit module?

Sorry @RuiVP - looks like there was an issue with getNonce() helper in the version of the Tracy core you were using. Please update to the latest version which should fix things for you.

Hello. I used to work with TracyDebugger in my development site (Windows 10 home + Wampserver + PHP 8.0.30). When I tried to update the module, I got error "Call to undefined method Tracy\Helpers::getNonce()" I also get in Tracy's report: From there on, I couldn't access anymore any site page. The only solution to keep working was to delete Tracy's folder in module folder. This means I can't even clear database data from this module. Can you figure out what is going on? Thanks in advance, but please take into consideration that I'm not a programmer.

This looks amazing. Thanks for sharing!

One minor nitpick with this module is that if you're running the dev version of ProcessWire (lets say version 3.0.123) and that version receives additional commits/updates but without a version bump, you can't "upgrade" to it given how this module works. You can only upgrade when 3.0.124 dev version is available. Not a big deal for me since I have a bash script that takes care of pulling the latest from GitHub, however it would be nice to support getting the absolutely latest bleeding edge version with this module.

@MrSnoozles Have you tried this GitHub repository? https://github.com/uiii/processwire 🙂

@ryan One suggestion: What do you think about adding a file field to the engineer for asking questions with files? For example: Create me a page with the contents of this Word file. Also it I noticed that questions that take longer will end in an internal server error because of the long execution time. In this case one would better use the terminal, because I think there is no easy solution around this except for increasing the server time limits? Very interesting development. I just created a homepage and a subpage on a fresh install without writing a single line of code. 😅 One issue Claude Sonnet 4.6 had was the concept of Markup Regions. It had problems with the main-tags and disabled Markup Regions in the end. 😄 But maybe it can understand Markup Regions better with a more precise prompt. I have no tested that yet.

@ryan While you're refactoring the core: I had an idea stuck in mind for a while and I wonder what you and Claudia think about it. Instead of having the core in the "wire" directory it could be by default in the "vendor/processwire" directory. That way we would get much better composer support. The system can then be installed normally by downloading the zip, but also using a composer command.

Thank you very much for your feedback and for your contribution to helping us refine the module! I'll try to make some adjustments in the coming days. The module has been in development since February 2026, so stable operation was paramount. If you have any issues or suggestions for improvement, I'm always happy to help!

Hi everyone, Built this for a financial news site that needed live stock quotes embedded inline in editorial content. Drop a ticker into any text field and it renders as a live badge with price, change, and direction - clicking opens a full detail popup. GitHub: https://github.com/mxmsmnv/Stocks What it does: Live price badges - ticker, price, change amount/%, direction arrow; click opens a popup with open/high/low, 52-week range, P/E, volume, market state Three data providers - Yahoo Finance (free, no key needed), Finnhub, Alpha Vantage TextFormatter with three parse modes: Explicit [stock:AAPL] tags Cashtag/hashtag - $AAPL, #TSLA Auto-detection by company name and aliases in text Company Manager - tracked companies with names, aliases, enable/disable toggles, bulk CSV import Four CSS frameworks - Vanilla CSS (built-in), Tailwind, Bootstrap 5, UIkit 3; auto-detected or manually set File-based cache with configurable TTL and per-ticker clear from admin Circuit breaker - pauses API calls after repeated failures, serves stale cache with ~ marker Custom provider API - add any data source by extending StocksProviderBase $stocks = $modules->get('Stocks'); echo $stocks->renderBadge('AAPL'); echo $stocks->renderBadgeAs('TSLA', 'bootstrap'); Requirements: ProcessWire 3.0+, PHP 8.2+ MIT License.

The Tracy core now supports some new AI agent tools: https://github.com/nette/tracy/releases/tag/v2.12.0 I have included this new version, but also extended it so there is now a new bluescreen panel with the Agent Markdown version for easy copying into your AI deity of choice. I also added a copy MD to clipboard button for those exception files generated by guest users (in production mode):

I'm not sure exactly when, but one of the recent builds of the PW API documentation lost a reference page (that is linked from elsewhere in the documentation; which was linked from the Template's Family tab for "name format" as of v3.0.257): https://processwire.com/api/ref/pages-names/page-name-from-format/ If page URLs are adjusted based on updated documentation, might need to handle auto-redirects and check links in PW's admin as well. When there are such profound changes of pace, sometimes the pace outpaces itself. 😄 That said, nice to see some quick turnaround on things that, I'd imagine, you've wanted to tackle for some time but haven't had the desire to dig through it due to the ROI of time. That's certainly one absolutely huge benefit of AI. Looking forward to checking out the updated versions of the modules and seeing if there are any new fixes in the mix. 🙂

Wonderful, thanks @maximus! I can confirm that these two issues are fixed. I've added a follow-up to my Github issue as the sorting order by date does not seem to work.

https://demo.processwire.com/

Hey @ryan, is this a side effect of your recent restructuring of the /wire/core/ classes?

Hello @Peter Knight To be clear, FrontendForms doesn't send any form data by default – it just checks whether a form is valid or not. Inside the isValid() method, you can send form data — or do whatever you want (e.g., store the values on a page). So it's not a "Email Form" module by default. Informing about what went wrong So in this case, it's a bit more complicated. The validator can only set the form validation to true or false (without sending information to an administrator). Of course, it could happen that a real person uses some characteristics of a SPAM text and the text is therefore declared as SPAM. This risk always exists, but it is very low. For this reason, it is necessary to inform the user about which mechanisms were responsible for the failure of validation. But I agree with you: too much detailed information (e.g., word 1 and word 2 are SPAM words) could give a human spammer too much information. My Opinion: In this case you have to make a compromise. You can't stop SPAMMERS completely. If it's a bot, it should post a fixed text in a text box – it will fail and can't react the way it changes the SPAM text it's going to pass. When you have real human SPAMMERS, it becomes much harder to stop them, because they can react much different than a bot. At the moment, the information in the error message is very general and doesn't contain too much detailed information. Yes the danger is always there, especially with AI - so I guess I leave it general. You can also change the error message to your own by asking the user to call you by phone if the message fails validation. Another option would be to set the threshold lower (e.g. from 50 to 30) so that more SPAM properties are accepted and the entered text is more likely to pass validation. I don't know what the "best practice" scenario is in this case. Maybe someone has an idea how best to deal with messages that have been falsely declared as SPAM, even though they are not.

Hi @jacmaes, thanks for the kind words and for taking the time to test! Both issues you reported are fixed in v1.9.2 (released today). Quick summary: Unix timestamps for start_date / end_date — datetime fields are now auto-detected by field type and formatted automatically, no manual column type override needed. Filter dropdown doing nothing — two bugs were at play: the Apply button wasn't showing up on select change (DOM queried before ready), and the query string was encoding [ / ] as %5B%5D which PHP couldn't parse as an array. Both fixed. Full details in the changelog. Let me know if anything else comes up!

https://github.com/ryancramerdesign/skyscrapers2 this is for PW3, not sure about php version, but most likely not compatible with 8.5...

This might be the best approach, @Hackasacka, thanks.

Hi Peter, Ryan has the 'Skyscrapers' site profile & demo, which may save you time setting up your own test site? https://github.com/ryancramerdesign/SkyscrapersProfile Hope it helps.

Thanks Juergen I guess what I was imagining would be the apparent successful submission of a form. The ProcessWire admin might get the spam notification (or not) to catch any false positives. Is there a danger that by telling spammers or bots what content triggers the spam gate, that we are educating them on how to avoid the system you have in place? Im only coming at this from my own PoV. Looks like a great Module.

Hello @Peter Knight At the moment, it stops the successful form submission like any other validator and an error message will be displayed to the user under the inputfield, that the text looks like SPAM with a hint to prevent using to much links to write to much words in uppercase letters using typical SPAM words and so on If a form has too much failed attempts, it will be logged, with timestamp and IP if this security measure was not disabled manually, but not with detailed information. So at the moment it only stops the successful form submission. Maybe the error message is written generally. This could be improved to give more information of what went wrong. Idea: Could be done only via a session I think but I have to try it.

@maximus Thanks for all your modules, you're on a roll! I've tested this module and opened an issue. It's probably a misunderstanding on my part, but when you get a chance, could you take a look at it? Thanks!