wbmnfktr

Kerim Pamuk https://www.kerimpamuk.de/ Client details Kerim Pamuk a turkish/german author and cabaret artist with such a kind of detailed humor for details you have to listen very closely and think twice to really appreciate his Wortspiele (en: puns) and anecdotes. Some more details about Kerim Pamuk (one of our first clients with a personal Wikipedia page): https://de.wikipedia.org/wiki/Kerim_Pamuk Design details As you can see... Bright colors, big typo, and subtle animations to emphasize the already bold visual statement. No miss but a lot of hits wherever you watch, like the stage program performed by Kerim Pamuk himself. The original design and the entire frontend were built in Webflow by the designer but was migrated over to ProcessWire later on. Some tweaks were made during the migration process to keep things a bit more flexible and easier to maintain on the long run. Technical details There is not that much in the backend to show or tell. Only a few tweaks and hooks in order to maintain all events automatically. Adding additional press statements, books or any other kind of content is simple and straightforward as always in ProcessWire. Modules used: Cookie Management Banner: for the obvious reason FieldtypeColor: for custom colors on sub-pages if needed PageHitCounter: as alternative to Google Analytics and Matomo ImportPagesfromCSV: importing new events to the site with ease (maintained by the client) Markup Sitemap XML: you know why Jumplinks: in case things change or someone needs a nice pretty link ProCache (Pro): ProcessWire is fast - with ProCache even faster VerifiedURL (Pro): to keep track of all linked event locations The team behind this: Muskaat for the technical part (yes, I'm part of Muskaat) https://www.muskaat.de/ Polimorf for the design part https://www.polimorf.de/ I hope you'll enjoy this site as much as I do!

The $page->created is empty at that very moment you query it because it hasn't been set yet. <?php namespace ProcessWire; $timestamp = time(); $page->setOutputFormatting(false); $page->created = $timestamp; // that quiet=true part is important in this case $page->save(array('quiet' => true)); You could add the date on your own if the date is necessary for whatever reason in that moment.

In case you are using tools like Xenu, Screamingfrog and some others you might want to remove those from the lists.

Awesome! My sunday is saved with some new fun I never really got into.

<?php foreach($page->heroimage as $image): ?> <li> <img src="<?php echo $image->url; ?>" alt="<?php echo $image->description; ?>"> </li> <?php endforeach; ?> You might want to try this instead. In your foreach() the $image has to be adressed and not the $page->image. And also the <li> should probably be in there too.

Just played around with UTF8 page names here in a local setup and it throws 404s here as well. Can't really say why as I rarely use that feature. I might have to dig a little deeper into this.

In order to have UTF8 support in URLs you have to define a whitelist as well. See here: https://processwire.com/blog/posts/page-name-charset-utf8/ With "social chars" you mean Umlaute? I guess... so you can have those either with the UTF8 page name support or you transform the classics like ä,ö,ü, and ß to ae, oe, ue, ans ss within the page name settings. You will find it here: domain.tld/processwire/module/edit?name=InputfieldPageName

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.