wbmnfktr

I hope we all together can keep this project stay alive, and make it a super-awesome-meta-collection-of-goodness for ProcessWire. There are so many awesome solutions and answers to common questions and challenges for whatever task buried deep into the forums. From basic questions to full-blown Pro module solutions. Maybe we all should be more sensitive to answers and solutions we get and at least should think about submitting those answers to the repository. In my opinion this repo/project should have the goal to be the starting point for all ProcessWire Newcomers. From easy tutorials to advanced setups. BUT... that's just my thought for the moment. To make this whole project NOT my personal project, I will add more and more people from our community as maintainers/owners to this whole repo and will think about a solution to find a way to finance the domain without me. But those are future tasks. Just wanted to let you know. It's not about me, but the thought behind all this!

Thank you, @gebeer for the awesome feedback. I love that idea! I wish we could create some sort of snippet collection (right now) from all of these recipes in some kind or another. While it would be quite easy for me to export each recipe to another format of almost any kind, almost each and every recipe has to follow some or all rules of formatting. Right now... the formatting is super basic but we can work on it and even could create snippets for only those recipes that support the wanted formatting. I could export those snippets, each and every time into another repository, when a recipe get's flagged as "isSnippet=true". If we can find a workable solution and formatting for real snippets... I'm here to support it! But first we should define a default/standard format for recipes and go from there. I wish we could go through all of the recipes to make them some kind of uniform, working with ProcessWire 2+, and mark those which only work with ProcessWire 3, or whatever version of ProcessWire, just to find a solid foundation. From there we could work out a snippet format and necessary fields, export them and even publish them to whereever we want. Something I forgot... there are snippets, ready.php snippets, common hook snippets... and probably more... so we have to classify snippets and recipes right from the start in some kind. But sure... that's possible. This will be fun! I really love this idea.

Another short update: In the last few days @marcus and I talked and he made a member and owner of the "old" organization repo on Github so we can still use the old/former official repository - that's awesome! Yet... the old domain is long gone. I tried to contact the new owner but no chance so far. Even through buyback-services and domainer/s. Outlook: I will update all recipes to the new markdown format, while keeping a copy of the legacy version in a separate branch/version. I will update all guides on how to submit and update recipes in the next few days. AND: I bought the processwire.recipes domain - so I hope it was worth it. ? MORE (ideas and changes and whatsoever): Details will follow soon on processwire.recipes! In other news: Thanks @teppo for updating the link, I'll have to contact you again when the new domain and repo are online for the public. ?

Yes, but I haven't received it for quite some time now. ?

Are all these details you talk about here (and in some other threads) documented somewhere? I looked up, read and tried everything from Github (README, Wiki), YouTube (which gave me the final "Try it now!"), the Forums, all threads... but somehow I feel various parts are missing - at least for me. I really try to use RockMigrations in one or another real project... but for now only SUPER simplified. Then... in some other threads (like this) people are super happy, like @Stefanowitsch and @dotnetic. Did I miss something? Is there a doc/guide/howto about all those classes/functions/hooks/methods/options/younameit... OR did you all read through the module to find out what's probably possible in some way? (Please don't ask what I am missing in the docs. The answer would be: "Almost everything! B'cause I'm stupid. ?")

Have a look here: https://processwire.com/docs/start/install/new/#installation-with-composer-and-packagist

As the project processwire-recipes.com went offline quite some time ago now, I took the repository and deployed a browsable version of it over on: https://processwire-recipes.pages.dev/ There is also a new repo: https://github.com/webmanufaktur/processwire-recipes/ ... on which this deployed version is based on. Changes, fixes, updates can be submitted there. Feel free to update links, fork the repo, submit changes for recipes layout or whatever. It uses 11ty for rendering .md to .html and all the other magic. I will add further details in regards to formatting recipes and submitting new content in the future. Further notice: @teppo: you link to the old domain on weekly.pw Changes/Updates: incoming - right now this is WIP (work in progress) Maintainers: feel free to let me know, I'll add you to that repo Details: the repo is on github: see above hosting/deployment: on Cloudflare Pages via 11ty updates: all updates against the master-branch will be deployed within 60 seconds after commit changes: right now only via pull-request maintainers: wanted - see above

Right here: https://processwire.com/download/site-profiles/ But keep in mind:

Disable them in /site/config.php.

The easiest and fastest solution would probably be to disable/disallow indexing of PDFs: https://cloudpdf.io/blog/how-to-prevent-your-pdf-documents-from-being-indexed-by-search-engines (not the robots.txt way!) But... are those PDFs worth being indexed by Google or anyone else? If so you could look into URL hooks: https://processwire.com/blog/posts/pw-3.0.173/

Check for AdBlockers, VPNs (especially in Opera), internet security or firewall software (Norton, McAfee, ...). Some password managers sometimes interfere as well (Lastpass did that quite often in my setup) and maybe even DNS and CDN settings when using Cloudflare. Best would be a clean browser without any extensions and password managers. If Cloudflare is used as DNS and/or CDN disable caching for the ProcessWire backend/admin via page rules. Disable software from Norton and such.

I prefer simple plain-text signatures as well as plain-text emails. Less hassle and way less problems in case mails get forwarded or nested in a thread somewhere. Nothing fancy at all. Just the details someone might need or are required by law.

I really enjoy those hardcoded/static structures in projects. In this case (real estate) it's super workable and I love it. ?

You can edit your first/original post and change the title. Add [SOLVED] at the beginning and you are done. That's our "Mark as solution" button here.

Seems to be a known issue:

For me a click on Home (root) does the trick.

Aren't your prepend/append files listed within the template settings (Files tab)? That would be the easiest way.

Wow... Didn't know that the $sanitizer and the specification do allow this now for the local-part as well. ?

Just gut feeling here but... Whenever I see these kind of errors on pretty decent hosting it's most of the time maintenance-related and therefore high load on the servers due to missing ressources. Another thing I experienced where routing issues at the hosting company either after a broken upgrade to their systems or new DNS settings that didn't exist everywhere. One last thing, especially on shared hostings could be new settings for database connections. For example from localhost to db.hosterdb.tld I'd probably check with the hosting company. I once had this issue after my version of DDEV was updated. As you use docker... I'd check if something changed there for whatever reason.

If you only test with this exact e-mail address the value is NOT valid and shouldn't pass the $sanitizer. So if that's the case, the sanitizer works. This shouldn't work: hans.müller@müller.com This should work: hans.mueller@müller.com

So the number of items isn't fixed. Didn't think about that. Then your version with negative margins would be the best solution* here. You could play around with padding and positioning those items a bit to remove that extra space but to be honest I wouldn't care that much. If it's about aliging you always can reposition the parent container a bit. * in case it's a real table, I'd recommened to use a real table markup

The main reason is that outlines are used when tabbing through content and an item is in :focus . So when using outline instead of border the default highlighting in your browser won't work anymore. Another thing is that a border is within or part of the element while an outline is slightly outside of it. So there could be another challenge in more complex designs. Last but not least... using outline wouldn't fix the issue. At least not without further fixes and changes.

I'd probably do it this way. .cards { display: flex; width: 150px; flex-wrap: wrap; /* border */ border-left: 1px solid black; border-top: 1px solid black; /* taking care of the box model */ box-sizing: border-box; } .cards__item { flex: 0 1 33%; width: 50px; height: 50px; /* border */ border-bottom: 1px solid black; border-right: 1px solid black; /* taking care of the box model */ box-sizing: border-box; }

It's markdown... so: https://www.markdownguide.org/cheat-sheet/ You could by using: [title](https://www.example.com) Sometimes there was the need for a link... I didn't like it but the client paid for it. This would probably work out as expected. Still I didn't like it in the title field therefore took other fields and tried other approaches.

I know what Markdown/Parsedown do and how the core module works. I used it before in the exact same way as you describe it but as the title field is often a fallback for the page title and in other places the additional markup didn't play out that well - at least with the title field in my case. But in other simple fields it's nice to have this option. Adding links was nice. The markup was easier to add for non-tech people than the whole anchor tag. That's why I was asking. As I thought it would do things in a totally different or another way. I can see your point here.