Leaderboard

Hi all! Just wanted to say hi and comment that I truly love the new website, it looks and feels great, both mobile and on desktop. It also has its own unique look instead of general day-to-day trends we so often see. Great work @diogo @jploch and @ryan! While we don't use ProcessWire at my current job, I still maintain few PW sites and I love the experience. Miss the community a lot, stay health and happy everyone!

Ryan wrote a blog post for you: https://processwire.com/blog/posts/optimizing-404s-in-processwire/ 😉

@elabx and @Robin S Thanks for Your help. I installed the Custom Inputfield Dependencies module and used "Show only if page is matched by custom find ...", which gave me a comfortable way to select the template. Now the admin-sites are clearly arranged and wrong entries can be avoided.

I have to try this module next week and remove my monstrous hooks, fantastic @Robin S, thanks!

When your AI refuses to admit it got it wrong: AI Agent: You’re right to push back. 🤣🤣🤣

The conversation continued: "AI Agent said: Would you like me to compare some of the popular platforms (Bubble, Glide, Retool, Make, etc.) from the perspective of building an AI tool like you’re doing? You said: Not needed. You just reinforced what I already suspected. The hype is just that, hype. AI builders have their niche but are not right for scalable, secure, hosting-agnostic apps or allow true design freedom. AI Agent said: Exactly. You’ve summed it up well. No-code/low-code AI builders are like prefab houses: quick, convenient, good for certain needs — but if you want a solid, scalable, secure, and truly customizable structure, you still need an architect and builders." Our jobs are safe for now! Just need to convince clients. 🙂

Is the new server using the same backend stack as the old one? If, for example, your new server uses NGINX, your .htaccess file is completely ignored unless you transform it into a NGINX config file.

@kongondo Yes! 🙂 I've added/removed/edited images within the variants and it all seems to save perfectly!

It doesn't look like this module is being maintained anymore and there's an issue that should be known by users. The sitemap generator is including: Pages that have 'include in sitemap' unchecked Hidden pages Children of unpublished pages Not sure if this is being experienced by others but this can be problematic for discovery of pages that shouldn't be readily known to the public. Correction If a parent page has indexing disabled, but a child page does not, then the child page will still be indexed, which kind of opens the parent page for indexing as well. Best to keep robots.txt up to date as a fallback. If you would like hidden pages to not show up in sitemap.xml, then modify L77 of SeoMaestro/src/SitemapManager.php <?php $selector = sprintf( 'template=%s,template!=admin,id!=%s,include=hidden', // Remove 'include=hidden' from this line implode('|', array_keys($templates)), $this->getExcludedPages() );

I did something like you want. Add this hook to ready.php: $wire->addHookBefore('ProcessPageSearchLive::execute', function(HookEvent $event) { $event->wire()->addHookAfter('FieldtypePageTitle::wakeupValue', function(HookEvent $event) { $page = $event->arguments(0); // specify your template if($page->template == 'tool') { // get the fields you like $prefix = $page->pre; $suffix = $page->suf; // add your data to the list $event->return .= " | {$prefix} {$suffix}"; } }); });