wbmnfktr

Either I'm missing an important detail or ... // define yesterday $theDayBeforeYesterday = strtotime("-2 day"); // get our pages $reallyOldEvents = $pages->find("template=template, date<=$theDayBeforeYesterday"); foreach($reallyOldEvents as $oldEvent){ // let's do something with it // maybe we put them into an archive // and delete all of them in 2 years // rather than now. } Does this find your events prior to yesterday?

Your frontend doesn't have any styles in regards to present code snippets therefore it's a bit pale. Neither ProcessWire, nor TinyMCE take care of your frontend styling. You could use hightlight.js or other helpers like that. Another option could be looking into the backend code and figure out from where the styles come and use that in the frontend as well.

This should do the trick to get all events from yesterday and the next 6 days. // define yesterday $yesterday = strtotime("-1 day"); // make $yesterday match the saved date format // in this case: dd.mm.yyyy $yesterdayForSelector = date('d.m.Y', $yesterday); // get our pages $events = $pages->find("template=template, limit=7, date>=$yesterdayForSelector");

Your grid area solution looks nice and clean! While for the moment I use the plugin Grid Areas for TailwindCSS I might switch to your solution. There seems way less overhead with it.

Just a guess right now but you might be using an old version that's only working with ProcessWire 2.x. Here is another one Skyscraper profile for ProcessWire 3.x.

I'm not sure at all but maybe... at least it's way better than the usual "Deutschlands schönste Bahnstrecken" night program I can remember. ?

This reminds me of something... but I don't know what.

For YouTube videos... just use: https://orestbida.com/demo-projects/iframemanager/demo1/ or any other minimal YouTube solution with a placeholder as cover. If you hit a performance issue just with video thumbnails... mobile detection isn't your solution. In this case you probably have way bigger problems. Let's start with the basics: How many videos are on that (single) site/page? How large (in kb) is the poster/cover in average for a video? Where does that poster/cover come from? Are images lazy loaded if possible? How do you know there is a performance issue? Do you pay more than $0,99/month/year for hosting? Tell us more. I ran quite busy sites on cheap shared hostings solutions (H*stgator, Dr*amh*st, H*stnun,... and similar) without almost any issues.

With dedicated sub-domains this isn't really an issue but it brings other challenges as Google expects a super highly optimized version then. So... choose your challenge. ? It's also not that big of a problem on trusted high-traffic sites as reducing HTML/source load is a very good reason in those cases. Google respects that. Here comes the big BUT... most sites can't offer a super optimized sub-domain version, neither are high-traffic, nor are they that trusted by Google. So if you aren't maintaining a 20-25+ year old financial, automotive, insurance, Fortune 500, or media/news outlet site... I highly support the following statement: (all of the above excludes member areas and sites Google/Bing/... can't officially crawl or see.)

I personally prefer to show a page/redirect to a page after a successful form submission. The reason for that is quite easy... a few examples: Contact form: I can inform people about how fast they can expect an answer and/or already offer a selection of FAQs - especially when the contact form was used from an info page. Forms on lead pages (newsletters or downloads): I can offer more "options" such as products, services or explain how to make sure they will receive e-mail updates (like "add our e-mail address to your contacts and check for spam"). The last part can be used for newsletter sign-ups as well. In case you offer a newsletter archive, tell and show your visitors about it. Forms on pre-sale pages: In real estate after someone submits a request for a house, flat, office or whatever you can offer already details and downloads they will need in order to rent or buy something and even answer questions. Or even tell them who their contact person will be. You car dealer for example: contact form submission with topic "parts" or "inspection" you could tell them "Mr/Mrs Doe, our expert for parts/inspection will contact you and answer your question. In case you might need it, here are the contact details..." You can even personalize those pages based on the form details, like name, topic, and whatever else. This way a form submission is not a dead end and I can keep the visitor/user a bit longer on the page(s). I really enjoy it (UX) when a contact form isn't a show-stopper but keeps it somehow going. Sure this might not work with every form or super simple contact forms. You might need more data to decide wether to show a page or just a short confirmation. Are there good reasons against it? Probably. Are there good reason for it? Absolutely.

The only similarity I can see so far is... modules. In my case a fresh install says there are modules missing which never existed - as it was fresh install.

Mutagen isn't enabled. I didn't re-use the projects. I created new ones instead and even tried it on my regular hosting server. Still... 2 modules are "missing".

Detecting mobile for what reason? JS can always detect mobile browser, or touch devices or based on display resolution. CSS can change due to media and/or container queries. PHP has quite some helpers to do the same. The module you mentioned might not be updated and compatible anymore but you could look into it to check out how it detected mobile devices. Btw.: Latte doesn't detect anything. It just helps making templating easier.

It is. Based on the recommendations in regards to RockFront Livereload. While enabling apache-fpm the only thing different is the "missing" yellow alert. The modules are still missing as before. Just tried it with another instance.

Hey... just grabbed a fresh copy of 3.0.208dev and installed it into an new and clean setup. Right after logging in I found this in the modules section (not the yellow banner ?). I'm quite sure that there shouldn't be any missing modules right from the start. More details about the setup: DDEV, PHP 8.0, MariaDB 10.4 @ Ubuntu 22.10 ProcessWire 3.0.208 (dev), blank profile Am I missing something here? As I can refresh and clear compiled files a few times and at some point those modules aren't missing anymore. A bit weird.

I'd support that statement. That was one reason I didn't spend that much time with Laravel even though it's interesting. But the community is quite nice as well. Not as good as PW but... yeah.

Sure... redoing the whole video isn't short by any means, but key concepts of Laravel... Routing, Components, Templates, Auth... maybe. That wouldn't take "that" long I image. Or maybe something different that might give Laravel users a WOW-effect. What was it in your case what made you think "In PW that's way easier!"? I'm not that deep into Laravel but from what I saw and know... there is way more in Laravel you have to take care of which is already backed into ProcessWire.

A nice, clean and short comparison with Laravel might attract even more people right from the start. At least as an opener to attract keen Laravel user. I like that idea.

I once added a field to my repeater-fields to switch files. It was called something like "theme" or "style" and when something was selected in it, I just took the value, pointed it to the "new" layout/render file and went from there. So... in some kind an alternate render file, yet controllable.

A few months back I had the urge to try a lot of new things and one thing was a SSG (static site generator) called 11ty.dev and there was one channel and one website that made it super easy to start. https://www.youtube.com/@11tyRocks/videos https://11ty.rocks/ I liked it because it showed everything from start to "sure you can build an app with that". What I want to say is that even guides on how to install ProcessWire, make it more secure, or about hooks or how to "write your own module" would make perfect sense. There is more than enough courses could cover. As already mentioned... there are few bits and pieces out there, most of them are quite outdated or at least the ProcessWire backend already looks totally different which makes it awkward in some kind to watch those videos. A new fresh approach sounds really good. There are tons of topics your course or maybe even courses could offer and talk about. See @bernhard's videos. They are really great and in full detail while only talking about a specific module. Haven't thought it through but I personally would provide some basics at least (installation, file and folder structure, some best practices), then maybe something like building a blog or magazine (as mentioned already) and go from there. A blog could have a RestAPI, a custom RSS Feed, and, so, on... oh and there is always: SEO, Online Marketing and Affiliate Marketing. There could be courses about "Why ProcessWire is perfect for (or) How to do SEO, OM, AM with ProcessWire". Just outlined a few ideas out of my head. ProcessWire Basics Installation Security Migration Updates and Maintenance How to structure your project Dos and Dont's Import a HTML Template/Theme ProcessWire: Your First Real Project Blog/Journal/Magazine Member Area ProcessWire Advanced User, User roles, Access rights How to Hook How to Customize How to Whitelabel How to RestAPI/GraphQL ProcessWire as Headless CMS Use VUE, Angular, Svelte, AlpineJS with ProcessWire Your very first ProcessWire module How to structure your backend, fields and templates ProcessWire SEO PageSpeed Caching SEO-related Modules ProcessWire Setups Multi-User Setup Multi-Instance Setup Multi-Domain Setup ProcessWire Master Class ... ... ... My 2 cents for now.

Super clean!

Really can't tell what's happening here but I can say that my old projects still work perfectly fine even with more recent versions of FormBuilder. Yet not that old as FormBuilder 30. Version 34 is probably my starting point... so you might have to upgrade for now as version 30 is quite far behind. Maybe it's an issue with PHP 8 or something. You could try that. Otherwise as mentioned above get a new license and go from there. What version of ProcessWire and PHP are you running with your v30 of FormBuilder?

I don't want to be a grinch here or anything like that... but: Did you talk to your tax accountant about receiving donations through PayPal, Buy me a coffee, Github, whatever? You might want to. At least to be safe. Just asking for a tax audit I had a few weeks back. ?

As you can use almost ANY available HTML in ProcessWire... the part of buying templates/themes is self-explanatory. While selling themes... there are some (3 or 4 I know of) but that's it. As ProcessWire is so individual in a lot of areas, creating themes only works out for basic setups like blogs or something. That's the reason I dropped most of my starter profiles a while back. Those worked for what they were but supporting tons of "I need this, that, and whatever ... BUT without paying anything" made me drop them completely. Yet selling full-projects based on ProcessWire is thing that works out pretty well if you know your audience/niche.

Interesting... for me it's always $config->dbHost = 'ddev-projectname-db'; You can use it on both actually quite easily. The benefit is (as @bernhard already mentioned) it's Docker-based and you could move on to almost any other machine just with your local config. BUT on Linux it depends a bit on your distro as Arch doesn't has the needed packages - even in the AUR they are missing. Ubuntu, Debian and Fedora/CentOS work totally fine. One thing I learned the hard way... talk to your real host to know what they are using so you can create a matching DDEV host with PHP, MySQL/MariaDB versions matching that exact provider. That makes things way easier sometimes. I can't as Laragon is one of most wonderful dev-setups you can use in my opinion. Install and go from there. It was always a real pleasure to use it and I never ever had any issues with it by itself. Yet... sometimes (as mentioned above) the real hosting company didn't match up with the Laragon setup which caused minor issues at some point - it's years back so I don't remember the details anymore.