Leaderboard

Hi @Paul Greinke - as @teppo said, it still works as intended on the most recent PW versions and I use it in production so I should be aware of any issues that might arise in the future.

Hey all ! I've worked with Processwire to create websites for a while now, so I sort of know my way around, but this time I'm stuck. I've started a migration the other day, following these steps : install PW Empty site folder and DB upload site folder upload root .htaccess Upload DB in OVH empty cache and sessions ( /site/assets/cache/*/*.* & /site/assets/sessions/*/*.*) update site/config.php (DB + httpHosts) This worked at first, only admin url would return a fatal error with a list of missing modules. It appeared that the DB was the problem. Then I tried again but with reuploading the BD from new pw installation, with BDbackup module. This created reverse situation, admin working, but website returning same error, which is : Erreur fatale: Uncaught TypeError: LanguageTranslator::textdomainTemplate(): Argument #3 ($translations) must be of type array, null given, called in wire/modules/LanguageSupport/LanguageTranslator.php on line 514 and defined in wire/modules/LanguageSupport/LanguageTranslator.php:138 #0 wire/modules/LanguageSupport/LanguageTranslator.php (514): LanguageTranslator->textdomainTemplate(NULL, NULL, NULL) #1 wire/modules/LanguageSupport/LanguageTranslator.php (338): LanguageTranslator->loadTextdomain('wire--modules--...') #2 wire/modules/LanguageSupport/LanguageTranslator.php (312): LanguageTranslator->___getTranslation('wire--modules--...', 'Name', '') #3 wire/core/LanguageFunctions.php (210): LanguageTranslator->getTranslation('/home/macbwberw...', 'Name', '') #4 wire/modules/Inputfield/InputfieldName.module (16): __('Name', '/home/macbwberw...') #5 [internal function]: InputfieldName::getModuleInfo() #6 wire/core/Modules.php (2752): call_user_func(Array) #7 wire/core/Modules.php (3026): Modules->getModuleInfoInternal('InputfieldName', '\') #8 wire/core/Modules.php (5157): Modules->getModuleInfo('InputfieldName', Array) #9 wire/core/Modules.php (572): Modules->saveModuleInfoCache() #10 wire/core/ProcessWire.php (755): Modules->triggerInit() #11 wire/core/Wire.php (413): ProcessWire->___init() #12 wire/core/WireHooks.php (952): Wire->_callMethod('___init', Array) #13 wire/core/Wire.php (484): WireHooks->runHooks(Object(ProcessWire), 'init', Array) #14 wire/core/ProcessWire.php (889): Wire->__call('init', Array) #15 wire/core/ProcessWire.php (645): ProcessWire->__call('init', Array) #16 wire/core/ProcessWire.php (593): ProcessWire->setStatus(2) #17 wire/core/ProcessWire.php (315): ProcessWire->load(Object(Config)) #18 index.php (52): ProcessWire->__construct(Object(Config)) #19 {main} thrown (ligne 138 de wire/modules/LanguageSupport/LanguageTranslator.php) Ce message d'erreur apparaît car : vous êtes connecté en tant que Superuser. L'erreur a été enregistré dans l'historique. The wierd part is, when a page returns that error, it triggers all the pages (that used to work a second before) to do te same, and nothing works at all. Did I miss something in migration of the modules ? Does that feel familiar to anybody ? Any magic solutions I haven't thought of ?

Here's an article that talks about hot-reloading in Craft CMS using Alpine.js: https://aaronmbushnell.com/hot-reloading-content-in-craft-cms-live-preview/ It also references an article about Statamic's live preview as well: https://jacksleight.dev/posts/hot-reloading-statamic-s-live-preview-in-a-traditonal-mpa Just thought I would share in case it is relevant?

Thanks a lot! I do have a construction, like this, for the emailSubject: <?php $processor = $event->object; $processor->emailSubject = "Page title is: $page->title"; echo $form; ?> Is it possible to make it very simple like $processor->emailReceipient = Only a quick thought!

I should also say : my dev version of Pw was 3.0.210. I've also just tried simply dumping my whole dev folder (site and wire and all) into the wanted migration location, and the whole website (pages requiring module included) work fine. Now it's only the pages requiring modules in the admin that crash, and attempting to refresh the admin module page crashes the whole situation again (website and admin).

Sorry, that was too short ? Nope --> That was the answer to your question if your shortcuts make a difference. Just tried to paste it into the html field of jsfiddle.net and it pastes just the text without any markup --> that was something that I tried on my own after your suggestion to see what is actually stored in my clipboard. But that was nonsense, I think. I thought that jsfiddle might also show all the markup with all the tags when pasting, but it just shows text only. I'm not sure why this happens and what's going on and what is actually stored in the clipboard when copying text from websites, but I think a plain text field should be frontend editable without having to worry about encoded markup ending up in the field ?

Hi @cwsoft Thanks for the quick fix - I tested on my small site and it works fine: in the promailer prefilled form the email address is displayed correctly all email addresses on other pages are encrypted Have a good day- BR Thomas

Last week we had a big update of Pro modules and this week we have another batch of Pro module updates. These are now posted and available for download in the relevant boards: ProDevTools Profiler Pro (v3) ProDevTools Sitemap XML (v4) ProDevTools ProcessWire API Explorer (v5) ProDevTools User Activity (v7) LoginRegisterPro Frontend File Inputfield (v3) FormBuilder Stripe Processor (v3) FormBuilder Stripe Inputfield (v9) If you use the ProcessWireUpgrade module, it can also tell you when Pro module updates are available. In addition to the Pro module updates, we also have a new dev branch core version available: 3.0.228. ProcessWire 3.0.228 primarily focuses on fixing newly reported issues. We'll likely merge this version to the master/main branch sometime early next week because it contains a couple of fixes that belong on the master/main branch. For instance, there was a bug with ProcessWire's pages_parents table (present for the last year) that could affect the result on has_parent selectors in some situations. There was also a bug found by @Robin S where ProcessWire's image fields weren't using the stored/cached value for width/height on images, and instead was pulling it from the image file, which takes more time. So for image-heavy pages, 3.0.228 theoretically could offer a nice performance benefit (especially in the page editor), and is a worthwhile upgrade. Thanks for reading and have a great weekend!

Hi Ryan, Would it be possible to create a more streamlined way for your 1st party commercial modules to be downloaded? I have licenses for most of them and grabbing them all one-by-one through the respective forum threads is less than ideal. Too much friction. Ideally, if they could be upgraded via ProcessWireUpgrades module (although I think I understand your hesitation doing it that way), or if there were some sort central control panel on processwire.com/talk/ (or just processwire.com), that would be a nice upgrade.

Hi Murray I now have a few sites running on MariaBD 10.6 and have no issues so far.

That's the one...

"If it works, don't touch it" ? Seriously speaking though, this module works well and does what it needs to do. So yes, if you want to restrict access by branch then it is a good option, regardless of which core version you are using.

I remember using Textpattern way back in 2005 or 2006. I'm old (by web developer standards).