wbmnfktr

Ask for browser name, version, and all extensions installed. Even ask if the person is using a VPN or is sitting behind a PiHole or Adguard instance. One coincidence... the user is using an Apple and the page path contains `Apple(s)`. Another thing, the path has a weird prefix in the breadcrumb: `\Apples` Might be nothing, but these are my first thoughts.

@cpx3can you provide me a list of all modules you use and and outline of the template in which that occures, maybe even an export of the template and fields, with the exact versions of ProcessWire and the modules you use. So I can create a similar environment and play around with it? Would reduce the guessing here.

AI, Cursor, Windsurf, Claude Code... you name it. In terms of ProcessWire they all need a strong hand that guides them through different tasks, ways, and whatever its in the way. You need to oultine your part in ProcessWire in great detail. You need to define hooks, the solutions to use - from ZIP to TempDir. You have to outline the forms it needs to render and the fields to use from start to finish. You could give an existing module as baseline, but beware it knows what to do then. But extending existing modules works pretty good - see my fork here of GUID/UUID Generator Whatever tool you use, it knows the baseline I knew 2 weeks into ProcessWire back in 2014 after doing the tutorials and reading the forums. Hint: Let Composer/Cascade finish the tutorials - it's wild! And let them create rules, workflows and memories from it. You will reach a junior-junior grade PW-dev this way. BUT (big time)... it's great and even superior in terms of PHP. Do the outline, from start to finish, do what you know in terms of ProcessWire. Let the AI/IDE/Agents do the PHP part, including docs, and you will be happy. Sure... not that much fun as people have that use NextJS (13, and maybe 14, but not 15) or AstroJS (2,3, and parts of 4, but not 5)... but hey... that's still only JavaScript (maybe Typescript) those AI/IDE/Agents are good at - the concepts still need either docs or a solid foundation. In the JS-world everything is a pattern, everything is JS or TS, the concepts are the same. But framework-specific... is another story. Laravel works great. Ok, maybe not the latest version, and maybe not all the extensions, like Forge and Filament. But yeah, it works. Even migrations. Depending on the database. And don't try Supabase or Neon. That's super wild. But... older versions with just *.blade.php - works! Flux, InertiaJS, VUE, React? meh I am still not a coder/developer/programmer BUT... I know how to write a technical concepts and know how to outline modules, hooks, whatever in ProcessWire. The moment I realised that those tools are great at PHP, and s*ck at ProcessWire - I understood what to do. A new project I work on, a NextJS/AstroJS/ProcessWire-combo, has already 50+ documents to outline which tool does what and how to do it. And I didn't even really start to outline anything in terms of modules or hooks. The ProcessWire part, or at least a big part, is already outlined here: https://github.com/webmanufaktur/pwai/tree/windsurf Which is the latest commit with most of the stuff needed - for my projects. But yes... those AI/IDE/Agents only see patterns and try to match up - in frameworks. To give a bit more helpful details here: AutoTemplateStubs is a great addition to help your tools to understand what's happening. In case you hate to do everything yourself: RockMigrations has some nice .vscode snippets that help and most AI/IDE/Agents understand it and can create templates and fields right from migrate.php. Noice!

Are those textarea fields direct children of templates or are they nested in repeaters or RepeaterMatrix types?

Not a crutch but the offical way to work with x-cloak. https://alpinejs.dev/directives/cloak

YES! I hoped/was whishing for a collab like this one with @diogo and @jploch. That's such a perfect match. Already love it without even having seen a screen yet. I can only imagine what's coming next. 👏

For TailwindCSS v 4.x I asked Grok (or maybe even Cascade itself - not sure) to read the migration/upgrade guide and compress it down to the bare minimum. I put that file into my `docs` folder, added it to the context and let Cascade do its work. Besides those changes, TailwindCSS didn't change that much so most of it worked as before. I also added a new base tailwindcss.css file with the new config syntax and changes and when necessary I mention that there is no need to setup TailwindCSS again. Works pretty well. /*file: `/site/templates/src/tailwind.css` */ @import 'tailwindcss'; /* PLUGINS */ /* @plugin "@tailwindcss/typography"; */ /* @plugin "@tailwindcss/forms"; */ /* CUSTOM */ @theme { /* 480px */ --breakpoint-xs: 30rem; } /* SOURCE */ @source "../../templates/**/*.html"; @source "../../templates/**/*.html.twig"; @source "../../templates/**/*.js"; @source "../../templates/**/*.latte"; @source "../../templates/**/*.php"; @source "../../templates/**/*.twig"; /* SOURCE NOT */ @source not "../../../node_modules/**/*"; /* ALPINE JS */ [x-cloak] { display: none !important; }

It's shocking to ask just the basics. Try:

Correct. You have to test everything with your setup, workflow, and everything. Even between projects I have to tweak lots of things. I guess in total about 5 different variations of setup are in that repo. Test it. Tweak it. Even feel free to raise a PR.

Have you tried Windsurf for PhpStorm? Or was that the "AI they integrated"? https://plugins.jetbrains.com/plugin/20540-windsurf-plugin-formerly-codeium-for-python-js-java-go-- Working? It's more a fight, especially with ProcessWire but most of the time and patience everything works out great. Recently pushed my last/latest iteration of my PWAI setup. Very opinionated especially in terms of settings, tools, and extensions, but hey... https://github.com/webmanufaktur/pwai

I totally support what @bernhardsaid and I just want to add: VS Code Insiders with Github Copilot - for free. Not sure why and how but the results feel a bit more nuanced at times. Combined with Cline/Roo you even could add a free Gemini 2.0/2.5 key which outperforms in conceptual tasks (PRDs/SOPs) quite often. All you need to do is installing VS Code Insiders, add Copilot through the interfaces provided (you can't miss them!). I enjoy writing mass content, like docs with it, as it doesn't ruin my credits in Windsurf/Cursor.

Family vacation/time > *

I haven't tried anything above 8.2 so far, but I am on the latest DEV version constantly without any issues in any of my project - from newest to oldest - with all kinds of modules/pro-modules. Not sure if this helps, but I could try install your version in my setup and try here as well. But with DDEV you have all options. You use apache-fpm and not nginx-fpm or some other weird setting in .ddev/config.yaml?

We see the most recent DEV version here so that's one thing AND PHP 8.3 which I never even considered trying. I have a feeling that PW and 8.3 aren't friends yet, but that's on me. Not sure about your overall setup but could you switch to PHP 8.2 and/or to the latest stable just to check out what's happening then? If this was my project, I'd switch to PHP 8.2 first, then change the PW version, but in a new install/copy-paste version.

I don't want to be that guy, but what versions and modules are installed? Do use use the PageListCustomChildren module or similar ones, like VirtualParents, that put's pages in other views?