All Activity

Hi ausblick, I'm happy to answer your questions. Basically, these are topics that for the most part don't specifically concern PAGEGRID, but rather ProcessWire in general. In ProcessWire, site profiles are essentially preconfigured starting points for a new site. They define the structure, templates, fields, and sometimes demo content that get installed when you first set up ProcessWire. Unlike themes in WordPress, which can be changed later, site profiles are installed together with ProcessWire when you first setup the site and can't be changed later. PAGEGRID supports the creation of site profiles, and there are currently two smaller PAGEGRID profiles that can be installed (click the thumbnail to see the frontend). However, these are currently only available in PAGEGRID Cloud. If you want to try them quickly, you can create a free cloud account. Cloud sites can then also be exported as a site profile (with a self-hosting license). But I can also upload them here as ZIP archives if you prefere. For my projects I usually don't use site profiles. Since PAGEGRID allows you to install pre-built blocks (which create all the templates and fields for you), it's already a good starting point for a new website. All you have to do is add the blocks you want to your page and design them using the style panel (visually) or with CSS code. Since my websites usually look very different from each other, I prefer blocks that are largely unstyled by default. Yes. Procache works with PAGEGRID. But it is not really needed since PAGEGRID is already using markup cache for all it's output. If you build a site that is mostly rendered through PAGEGRID it will be very fast out of the box, without any additional customisation. E.g. page-grid.com which is build with PAGEGRID has a performance score of 100 (best score) in Google lighthouse speed test and is not using any additional caching. First you have to add a PAGEGRID field to your home template inside the admin. Then open the file home.php inside your site/templates folder and add the following lines: <div id="content"> <?= $pagegrid->styles($page); ?> <?= $pagegrid->renderGrid($page); ?> <?= $pagegrid->scripts($page); ?> </div> Note in this example I am using the blank site profile and markup regions are enabled. The #content div in this file will replace the #content div in _main.php See the Markup Regions documentation for more information.

@ryan, You'd mentioned at some point that existing installs could retain the old theme and perhaps users prompted to update to the new one. At the moment if I upgrade an existing site to the dev branch, the new theme is enabled by default. This breaks any custom TinyMCE styling as the new theme overrides it. Are you planning to implement this prior to the next master version? Ideally for us, given we have several hundred sites which we update to the latest master when it is available, nothing would change for the users. We could then turn on recommending a theme upgrade on a per site basis, or if we choose to, force the upgrade on the users. Cheers, Chris

Hi, being french, you can imagine than most my websites are multinlingual 🙂 and i alwys use this kind of language switcher foreach($languages as $language) { if( ! $page->viewable($language) ) continue; $url = $page->localUrl($language); $iso = $language->name == 'default' ? 'fr' : $language->name; // use your own default language instead of fr... if($language->id != $user->language->id) { echo '<a hreflang="' . $iso . '" href="' . $url . '" title="' . $language->title . '">' . $iso . '</a>' . "\n"; // echo '<a hreflang="' . $iso . '" href="' . $url . '" title="' . $language->title . '"><img src="/site/assets/img/' . $iso . '.svg" alt="' . $language->title . '" /></a>' . "\n"; // echo '<a hreflang="' . $iso . '" href="' . $url . '" title="' . $language->title . '">' . $language->title . '</a>' . "\n"; } else { echo '<span>' . $iso . '</span>' . "\n"; // echo '<span><img src="/site/assets/img/' . $iso . '.svg" alt="' . $language->title . '" /></span>' . "\n"; // echo '<span>' . $language->title . '</span>' . "\n"; } } and never ran into the issue you describe whether the urls are ...com/toto and ...com/en/toto or ...com/fr/toto and ...com/en/toto (in this case you have to give a name -the name you gave you default language- to the homepage, not the preferred way tu use pw but it works if necessary) the two important things are the use of $url = $page->localUrl($language); like @monollonom says and the line where $language->name is defined for the default language in case it may help 🙂 have a nice day

Awe-inspiring website! I loved that you demod the backend as well. Kudos to the team!

Hi As a beginner in PW I just want to ask a. how Pagegrid interferes/interacts with siteprofiles? b. Does Pagegrid supports ProCache? c. How to cahgne to main Home pw page to pagegrid? Merci.

impressive

You guys rock!

You can have a Look a the findRaw function: https://processwire.com/api/ref/pages/find-raw/

Hello, I have a site which have comparisons of products. There's an ajax select form from this tutorial. I have ~8000 pages The problem is high cpu load when multiple users are searching (server two 5GHz cores, 1 GB ram). I get db connection errors or very slow response time Is there a way to optimize searching? I want to minimize db queries and make ajax responses as fast as possible

Great news, I've a couple of old sites where I'm still using this module. Thank you @matjazpfor taking care!

Hello @perplexed Are you sure that you have added this method to the WireMail object and not to the form object? I have tested it without problems. Please take a look here at the example of a simple contact form and let me know if this solves your problem. Jürgen

if you are still using this module, one way to get around the aforementioned error is to copy the class into a new file (from the Fieldtype module) and then put this at the top of the inputfield module: if(!class_exists('ProcessWire\RuntimeMarkupUtilities')) { include_once __DIR__ . '/RuntimeMarkupUtilities.php'; } i haven't extensively tested it yet but so far it seems to work. I couldn't import any fields as the admin would crash and this has now allowed importing fields without this module showing the "class "RuntimeMarkupUtilities" does not exist error."

AIOM is alive 🙃 I am pleased to announce that the AIOM module will be further developed and supported by @matjazp. My original repository is now archived, and matjazp's fork is now the official one. The forked version is now also listed in the Processwire module directory. This should make it possible for everyone to update the old version to the new one, either manually or via the ProcessWire upgrade module.

Hi Juergen I have the new title property set - ->title('<h1>From LPN website contact form</h1>') // this is a new property from this module but it does not show up in the email. I've read your docs where you say "This will be added automatically to the email, independent if you are using a HTML email template or not - no need to add it manually." so I'm puzzled. Thanks for a great module

Thanks, @matjazp. I need to get myself looking at the github issues more regularly.

Thanks @Robin S for taking a look - much appreciated. It seems like a random issue here even with my simplest modules. I have played around with removing those FileCompiler files and DB entries and sometimes it helps and other times not. Sometimes I literally need to remove the namespace so I can uninstall, then add it back and then I can reinstall. I am just worried about breaking the admin for users upgrading my modules. I also wonder if sometimes it matters how the module is upgraded - replacing files directly vs updating via the PW Upgrades module - perhaps it triggers a modules refresh before the module gets to load and potentially break things 🤷

https://github.com/processwire/processwire-issues/issues/2150

Hi, since i updated my local PHP to 8.4.13 (from 8.2), all PW installations are quirky. Regardless what 3.0.x.x.x PW versions. On load (Backend/Frontend): Deprecated: session_set_save_handler(): Providing individual callbacks instead of an object implementing SessionHandlerInterface is deprecated in [...]/wire/core/WireSessionHandler.php on line 51 Followed then by: PHP Warning: session_set_save_handler(): Session save handler cannot be changed after headers have already been sent in [...]/app/wire/core/WireSessionHandler.php on line 51 Although it is a deprecation/warning, it has effect on the behavior within the Backend (page tree doesn't load etc.) when debug is on. I also tried to upgrade a local PW installation (v. 3.0.242) to the latest master/dev, the folders and files are created (wire, index.php etc.). But loading the backend or frontend both gives completely blank page immediately. Fortunately the rollback works. I did a search, but found not much on this topic, i am afraid. Emptied all caches, compiled files multiple times. Does anyone have a clue what to do or where to look at? Thx in advance Olaf

Hey everyone, we just released a small companion module for StripePaymentLinks: 👉 GitHub: https://github.com/frameless-at/StripePlCustomerPortal PW Repo: https://processwire.com/modules/stripe-pl-customer-portal [pending approval] What it does The module auto-creates a ready-to-use page at /account/ where logged-in customers can: view all their purchases (table or grid view) access their purchased products / membership pages update profile data (name + password) open Stripe’s Customer Portal to download invoices or manage subscriptions No custom template coding required — the module installs a template + page, and you can still override the markup if you want. ⸻ Why we built it StripePaymentLinks already handles the checkout & user/purchase creation. This module completes the loop and gives customers a proper account area. 💡 Bonus benefit (Marketing): The grid view not only shows purchased products — it also shows available-but-not-yet-purchased products in greyscale. This turns the account page into a soft upsell area without being salesy. ⸻ Requirements ProcessWire 3.0.210+ StripePaymentLinks module installed & working Stripe Billing Portal must be enabled (Stripe → Settings → Billing → Customer Portal) ⸻ Status 🚧 BETA — already used on live sites, but we’d love developer feedback. If you try it out, please tell us what works and what’s still missing. Issues / PRs welcome. ⸻ Cheers & happy coding, frameless Media

How are you switching languages? Using javascript? I tried on a test setup and I can indeed reproduce your issue by changing the URL in the browser the way you described but maybe you should instead rely on something like $page->localUrl to create your language switcher? You can also raise your issue on Github, ideally by mentioning from which PW version you updated.

Stefan, thanks for such a great module. 😀

@ryan Hi Ryan, is there no solution for this? This seems to be a serious bug. I can't be the only one experiencing this … Cheers, Stefan

Yeah, I thought so. I'm using my own by the spam emails are still getting 0.9 (same as me!). I don't get these spam emails since there's nothing promotional in them whatsoever and yet they're making it passed everything.

Ok, so it seems that you have 10 000 free requests per month, so maybe you can still use it. 😉 Are you using your own reCAPTCHA script or with FormBuilder? If it is your own script I think you could set your a treeshold score, for example 0.6 or so. Regards, Andreas

Hi @Noboru. Glad you got it working. I'll look into the DefaultPage issue and maybe add a help note about it the class is really needed.