wbmnfktr

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.

It's in the core.

Yet again curious but how does this differ to the Markdown/Parsedown Extra textformatter?

As much as I support @BrendonKozanswer... I really don't understand what you want to accomplish. Do you want to hide images from backend or frontend users? And if so... what should be the result to which? There is always the option to secure PageFiles. But.... does this fit to your task/question?

Ok... I didn't notice your usage of n in your query/selector but what @taotoo said is true. n is a placeholder for n=number/integer for the amount of entries/pages/items (however you wanna call it). It's the number of entries you want to see.

I really can't tell if this is a bug or feature, to be honest. I talked about this with @ryan and he wasn't sure either back when I found this issue. And yes, that was about at least 2 years back. So... right now... this seems only to affect PW-sites that were single-language and then were migrated to multi-language support. Which is probably the case here too. I almost never stumble over this, due to my profiles I use for new projects, but YES... it could and will be... kind of a show-stopper in a setup once in a while - as we see here. But here is the "easy fix"... never use title somewhere else outside of default templates. I know it sounds weird as re-using fields is such a common task nowadays (for good), but... I learned about the years that title is more or less not a field, rather a tool to define name-based default IDs (besides the regular page ID). I see the title field as something like fkTitle (foreignKeyTitle) which I used to use in Oracle DBs back in my agency times. Way less strict and only applicable with additional selector-queries, but... it's close enough in my use-cases. In my setups I ALWAYS use headline, subline, topline and similar fields instead of title. Especially in RepeaterMatrix to create unique jumplinks. tl;dr (my definition for the title-field) Use title in your templates but never in an ongoing or extended way like using it in RepeaterMatrix Blocks or similar. It's a system field for a reason. Almost like a human-readable ID. That how I handle it.

That's why this module is already on my TODO list to give it a try. Your website, the module, and docs look awesome so far and I can guarantee you I'll give it an in-depth look.