wbmnfktr

Why don't you put all the posts directly under /campus/ instead? That would result in page/post urls you are looking for. Or do only appear some of those posts under /campus/ once in a while and only there? That would be possible with a URL hook as shown by Ryan in the example. Minor changes necessary of course. Just in case you really want to have some posts under /blog/ AND /campus/ this would result in duplicate content and you would have to fix this with canonical tags. Some more questions just to understand this better: Why do you want to mix different content types (posts, news, ...)? I can get that but why would it then be necessary to change the URLs?

At first it did sound like a namespace issue but the module has a namespace so I threw it in a demo instance: No issues so far. Installed without errors, output is minified. ProcessWire 3.0.210, PHP: 7.4, 8.0, 8.1 @ZAP Can you please check that there is no other copy of that module in place. Maybe with a different folder name or something.

I really enjoy your insights and view on this. Especially with the shown example. ? Exactly that. I really enjoyed that video. Even though I really didn't care about his background in first place. The video title was all I needed to watch it.

I don't know if this was discussed already before... so in case you need to check if PrivacyWire is enabled to show/hide things, like a custom cookie-settings button or link. This is how you check if PrivacyWire is enabled: // needs $config->useFunctionsAPI = true; $privacyWireModule = modules()->get('PrivacyWire'); // check if PrivacyWire is active $privacyWireIsActive = $privacyWireModule->is_Active; // down in your template if($privacyWireIsActive) { // do whatever you need }

It's actually about PHP/Laravel as a backend/middle-man solution instead of all these JS/node.js solutions around and the benefits it brings. The main focus, at least in 2 of the 3 videos, is still somewhat how it works with JS-frontends but still a nice change compared to most other topics in that sphere. You might want to watch or at least skip through some of the videos, the last one is fairly short, to get an impression. It's super interesting, not because of the JS stuff, but because of what Laravel offers and what some see as easy setup and solution compared to what they build as a final product (portfolios, blogs, and such more minimal projects).

Just something I stumbled across and noticed the last few days/weeks. More and more Devs (mostly from the JS-sphere) are talking about PHP, and not only about the latest JS framework trends. There is a downside as they are talking about Laravel most of the time, yet it's something I didn't expect.

@ryan That's correct. Those messages appeared right after I upgraded to 3.0.219, coming from 3.0.217. At least that was what I thought yesterday. I just gave it another try starting with a fresh database backup from production, and everything went perfectly fine without any issues going from 3.0.217 to 3.0.219. I really can't remember I ever tried the 3.0.218 in that setup and moved back/down to the 3.0.217 again. That wouldn't make any sense at all. I made a big downgrade to 3.0.165 a while back for testing purposes but that shouldn't result in issues here. This is how it looked this time: I will keep an eye on this as I want to upgrade some more local setups to the latest dev version. And those definitely never ever saw a 3.0.2xx version before.

Just dropped the latest/3.0.219 into a local dev instance and was greeted with this: Besides my gastro modules nothing makes sense here (for me) and I can't find the source of this issue. Unfortunatelly moving back to another version of ProcessWire didn't solve the issue. I had to import an older version of the database as well.

Ok... so I made the move and downgraded everything down to 3.0.165 Still no data loss. Which is fine for me, yet... nothing that help's you a bit. Is there something special in your setup?

I use this with/on all major or high profile projects that handle lots of data to create a backup each and every time soneone logs into the site. The space is available. And if not... log in every 4 week to delete a few backups.

Tested in a local 3.0.217 without any data loss with the same behaviour I remember before when renaming a field. If you want, I could downgrade to your version (whatever it is) and go from there. It's local and I could take a look.

So... since there was lot's of feedback to 90s music... maybe you all want (and probably should!!!) to look up: https://www.youtube.com/@dj_jambor/videos So much and many awesome mixes and remixes.... for 90s, 2000s, and many more. András Jámbor has so many awesome mixes I couldn't even list here. I just love it... there is no need for me to create my very personal playlist of any kind as this already exists. Please follow András Jámbor and his channel. It's such a good and pleasant place to listen to awesome music. Follow him! No shout out needed.

As @MarkEsaid... set the default date to today in the settings. Don't be too flexible with clients, otherwise they enter things like "every third sunday after easter but only in leap years that end with 9" or something. Think about sane defaults a client can choose from. Similar to the ones provided by LazyCron.

Somehow this error sounds like a "We updated your host to PHP 8.1 from 7.x without asking you"-problem. Can you please check which PHP version is running on your instance.

What about the core module Page Path History? It takes care of page URLs in case they change and redirect from old to new URLs. ProcessWire is quite good at managing old URLs, at least for those created in your ProcessWire instance. In case of a migration it's something totally different. There is even a managing area under the settings tab in each page. There would be no real need to add redirects anymore. Unless you want to use something that never existed before.

I receive the markup but couldn't access any data somehow. Using $rockfrontend every time wouldn't save me that much time so I tried using it the .latte way. This did the trick. Thanks for this hint!

Can someone please give me a hint on how to use RockFrontend with Latte and combination with RepeaterMatrix? I just can't find a way to show the content of my blocks (RepeaterMatrix types). {* home.latte *} <ul n:if="$page->blocks"> {foreach $page->blocks as $block} <li> {include '../blocks/' . $block->type . '.latte'} </li> {/foreach} </ul> {* oneOfTheBlocks.latte *} <div> {* NOPE *} {$block->headline} </div> <div> {* NOPE *} {$page->headline} </div>

What exactly does this mean? In case this means "5 people updating pages and the host goes down"... yeah you really should look for a more reliable host. In case this means "we have 50-100 users visiting the site to look up the news"... you might want to look into optimizing the page or invest in ProCache. Can you give us a number (ballpark ranges are fine) of visitors and page impression we talk about here? Low traffic can mean everything between 100/month to 50k/month.

Just stumbled over this... https://www.slant.co/topics/5409/~php-cms

@bernhard you might want to check this one out as it works perfectly well with the free ChatGPT 3.5 (GPT 4 is acting weird with this prompt). https://flowgpt.com/prompt/qGQmSnF-MDsfhDhpfzZEM Copy the whole prompt Send it and wait a moment Explain what you want to accomplish Answer questions or add details if needed Ask GPT to write the code You have to get used to it as it's quite verbose sometimes.

I was just looking for the Page Autosave and Live Preview module to re-install it in a project, yet I couldn't find it anymore. I probably missed something somewhere. Right?

Please check your installed and used extensions - from password managers to vpn and privacy-related ones. Most of them are off/disabled in incognito mode so they don't interfere there.

90s and early 2000s House/Dance/Techno Remixes #oldschool

Do you have more details on that setup? I have an old machine running that kind of dev setup but never noticed that issue at all. Which ProcessWire version are you running?

Based on my recent post and your answers in Module: ProcessWire Core Upgrade I decided to no longer hijack that thread and therefore open this one. @bernhard asked some very good questions there and here are some of my answers. First and foremost, I keep all of my "Automation Hooks" at /site/ready.php, and they are not present in all of my projects. I mostly utilize them in larger long-term projects and projects in which I have devoted a significant amount of effort - see samples below. I considered building a module for each project so that I could keep it around, fork it, alter it... that kind of dev approach. But that didn't work out as expected, so everything was moved back to ready.php - which actually works best for me. One file in plain sight, right next to everything else. For these activities, I have my own collection of snippets. I simply grab the appropriate snippet, tweak it, position it, test it, and proceed from there. No overly complicated workflow at all. But why should I care if there are any module changes (see thread above) if I'm not going to update them right away? I'm curious about what's going on in each project. I can see which modules were installed, which are in use, and which may be upgraded the next time there is a release. I rarely update modules or anything else outside of my development environment. I learned my lessons here. This isn't something I'd use in a project in which 99% of the code consists of echo/foreach like in some smaller sites I built. I honestly don't care because their code base and modules will almost certainly never be touched again. Projects like these are a totally different thing - some of those "Automation Hooks" are in place there: What things I "automate" and have in place across my projects - to give you an idea why this makes my life easier. Checking for news updates (weekly) No updates in the last 2 weeks? Remind the client to say something on their website and suggest doing so on social media, Google Business, and everywhere else too. Checking event count (weekly) Only 3 events left? Tell the client to check this and update the event pages or at least post something in the news to tell visitors what's going on. Checking newsletters (weekly) No newsletter in the last 2 weeks? You get the deal: the client will be notified to either send a newsletter or hand out content so someone else can do this Checking lunch deals (daily) Same as above. A restaurant runs out of lunch deals and will be notified via email right away. Archive old stuff (weekly) Short term content, like lunch deals, don't have to stay in there until the end of days. Archive them under another branch of pages, delete/trash them. Out of sight, out of mind. Checking for TODOs (weekly) This is a special one as I sometimes like to add a notes field to content pages in which I can write down things I need to do on that specific page in a project. I look for all pages having content in this field, put everything in a mail and go from there. It's something like a TODO app but direct in the project. No Jira, Asana, Todoist needed for this. There are plenty other options available. In my situation, it varies depending on the specialty, the project's budget for maintenance, or the overall scope of my tasks. I typically utilize these "Automation Hooks" to learn more about a project and remain informed. Sometimes it's for the client, but it's all automated. There have been projects performing comparable automated tasks for over a year now or more, and the customer is thrilled to receive an email every now and then with a list of things he should do. WINNER WINNER! I get paid to remind him, and he gets things done. You could put anything you wanted in those. File counts, database size, login errors, PHP version, PW version, and so on. Ping at @flydev @monollonom @horst