wbmnfktr

What other changes did you make already? And another question... how did you change the default language to german? Just by removing/changing page name defaults from the homepage or are you using any hooks already?

There is something wrong with your setup. I upgraded my recent project to the latest PW DEV version and still... module install works as expected. Let me know if you are interested and we can go through a kind of "step by step debug" session. For details contact me via DM.

That's what I was talking about. I imagined a setup like that and it's nice to see I wasn't that wrong about it. Could and will be a good example for others that like to build something similar (which reminds me about a site profile I built a long time back). In regards of SEO are some options available here. From category to ingridient pages and even more. Which led me to this: https://www.dothiscookingthing.de/zutaten/ https://www.dothiscookingthing.de/kategorien/ Both sites look quite empty right now but that's an easy fix. That site looks like fun for all parties involved here.

?? I love these nice little details that make the site so much more interesting and better than a lot of recipe sites out there. Meanwhile it's a very good example on how ProcessWire can be used for almost anything - even as a blogging platform/tool. It even gets nice results in the Google Lighthouse Audit. Might be me but I'd find it interesting to see how the backend is structured. Mind sharing a look behind the scenes?

Something seems to be broken somewhere... as I know almost nothing about Tracy a look into the logs is one step and clicking that icon might help. A screenshot might help others who work with Tracy more often. What ProcessWire versions are those other sites running? Can you use the latest master 3.0.165 instead?

That's strange. I never ever had any issues like that but I'm only using PW up to version 3.0.165. Maybe the dev-tree needs more attention or something. But that shouldn't be the case if your local setup is the same version. Which PHP version are you using? Maybe that affects it for some reason. Have you tried the $config->moduleInstall('download', true); option? If that doesn't work out as well, you still can upload modules via FTP and yes I know that's not ideal at all.

Maybe you aren't allowed to write changes to site/config.php and need to change read/write settings first. Double check the changes were submitted to the server and not to your local file. Either log in via SSH or maybe even via WebFTP or something. Oh... and check if there is a second $config->debug in your site/config.php. If so... delete it.

I'm not totally sure about the HTML Options in the textarea settings if they might already do that or just look for changes. But ProCache is able to do that (never tested to be honest). Edit: I have to revoke this. ProCache does not change any <a href="">.

I'd like to buy a shed there... right next to the coast or at least a lake or something... this would be even more than awesome. Offers are welcome and can be made through my public profile. :)

Well... what module is affected and which versions of PW are you running. This kind of error is uncommon to me at least. It looks like the regular textarea field needs an update so this error is even more... weird. Are you running a special kind of setup... like IIS oder NGINX or... whatever?

Sure... yes... but... why? Most of us aren't whistleblowers, keep secret start-codes for whatever kind of m*ssles or r*ckets... so... ?

Just a little side note... Thank you @joshua! Don't know when or if I will visit Göttingen anytime soon but... dein nächster Bierdeckel geht auf mich! (for english readers... try DeepL Translate for the last part.)

Just tested... within 3.0.169 and the most recents version of those modules/Textformatters. Vimeo and Twitter work. YouTube doesn't work with any of the modules/Textformatters ... but it worked a few weeks back.

This gets an A for awesome! And big thanks for the modules. They look pretty neat as well.

I used some .xyz and .pw domains but for real projects. Not as dev/stage domains. I dropped the .xyz because users don't click them at all. You can have a #1 spot in the SERPs but still CTR is super low. At least in non-fancy or super small niches these domains didn't work out that well for me. Same content on a .com/.net and even .org workes way better. There are some areas users seem not to care at all. Like Linux or less usual topics as crypto, privacy and security. For client projects I use my regular domain - most of the time. Something like clientname.dev.domain.com .pw domains are... well... some kind of special as well. I kept most of them for the time being.

Just stumbled over this: https://javascript.info/

As it says... the trial is unlimited in terms of time. Sometimes a message pops up but that's it. For testing purposes absolutely fine.

Similar to @BillH I use Prepros to build my static versions (which I keep in each and every step of a project). YES... There is in 95% of all projects a static copy/version of all my projects. Just to be able to change and tweaks things even without any database and PW instance. It makes devlife so much easier - at least on my side. New projects will be build totally static before I even start using PW. Somewhere here in the forums I posted a detailed workflow I use for a couple of years now. Sadly I can't find it right now. So... in short: no livereload in PW projects, only in static versions.

Frohe Weihnachten!

Totally different and strange... yet absolute awesome! Love those tracks right now... while listening you might know why. Follow their channels. They are AWESOME!

If you are handling real Adult content this is not enough - at least in the EU region. You can use a lot of cookies and checks to serve rendered HTML (depending on your region with a small whitelist/blacklist of words or based on corporate decisions without any of those) without any images or videos and you are fine. See recent changes over at P*rnh*b. They had to delete a lot of content due to reasons. Maybe define your or your business's goals to make the need more clear. There are a lot of ways to skip certain things. As said before... if you have to deal with REAL ADULT content... there forums out there that describe ways to get around restrictons. Most basic solution is - as far as I know - log in those who confirm with YES, OVER 18 WHATEVER... and deliver content which is viewable for those. You might want to use Login Register Pro for that. Which works fine as I have heard from others. *cough*

Well... while this works (1): This doesn't (2): I use a slightly modified version of Ryan's Video embed for YouTube/Vimeo module which already saves the "no cookie" domain to the database. Users would paste the URL as usual, the module fetches the oEmbed data but in my case the domain will be replaced. Around line 104 in Ryan's module I changed that part: $embedCode = str_replace('youtube.com', 'youtube-nocookie.com', $data['html']);

TextformatterPrivacyWire.module works fine here as long as: 1) the iframe contains www.youtube.com/embed/ and not www.youtube-nocookie.com/embed/ and 2) as long as its the second textformatter (or at least the textformatter after VideoEmbed). Just played around with it here in my testing setup.

As we see huge progress in terms of privacy (GDPR/DSGVO) over at PrivacyWire with this module, wouldn't it be an awesome addition to embed YouTube videos with the "no cookie" domain in order to allow even more privacy? I worked my way through to this in a hacky way (see below) in the past but maybe this could be an option some day in the official module itself. $embedCode = str_replace('youtube.com', 'youtube-nocookie.com', $data['html']);

To be honest... I don't know as well. This kind of behaviour is totally new to me but on the other side... I almost never have to deal with almost any textformatter plugins/modules/extensions. I guess it was a huge hickup or some kind of this as it was the first time ever I had to deal with this kind of problem in any of my setups. Nontheless your module does a pretty good job - as soon as it runs in a setup.