wbmnfktr

Never used it but for some reason I believe this could be the reason.

That would actually be the start in the page array. To get a specific page, based on a selector with start and limit, you might want to look at this: https://processwire.com/api/ref/wire-input/page-num/ This way you can actually go straight to the specific page, like 3 of 7.

Do you mind sharing your special use case and solution. Just in case as this is quite a common question - at least once in a while.

@Pete got this message a while back: Where would I find this? I can't see it in this thread or in edit view.

Yet again I stumbled across a great series of videos. This time from PlanetScale - mostly about MySQL and of course PlanetScale itself. Yet I think this could be interesting to some of you. https://www.youtube.com/@PlanetScale/videos NOT AFFILIATED WITH THEM OF COURSE! (Did I already post this somewhere else here? I have that feeling right now.)

When everything is up and running again, as it was before, you could initialize a Git repo on your server. Every change in every file would be totally transparent from that moment. At least in theory.

Give us a screenshot and list those files, please, so we can check AND please download the whole directory and archive it in case someone wants to look into it further.

You see this? That's fine! It's part of ProcessWire since version 3.0.152 - see here: https://processwire.com/blog/posts/pw-3.0.152/#new-ability-to-specify-custom-page-classes It tries to extend the Page class.

Had a similar issue a while back because I used this: 'Content-Type': 'application/json', Just switched the content type and it started working: 'Content-Type': 'application/x-www-form-urlencoded',

The developer map says so. https://directory.processwire.com/map/

I don't know if "Woah... impressive!" or "WOW!" is the right answer to this.

Does this help? https://processwire.com/blog/posts/processwire-3.0.107-core-updates/#trash-for-all Found here:

Maybe you could try to check what was changed. There are two modules I used in the past to do so. Install them in a test-environment to find out which works better in your case. For now I can't really recommend the one or the other. https://processwire.com/modules/version-control/ https://processwire.com/modules/process-changelog/ both by @teppo PageHitCounter had this issue in an early version... so page hits resolved in an update BUT... that was long ago.

Drag'n'Drop all files to an image field is my way to go.

Have a great weekend, @ryan!

Woah... yes! They do the trick for me. These settings are hidden pretty good. @cpx3maybe you try the above mentioned setting. It works for me in my current setup. On a side note: just noticed that this issue doesn't occure in Firefox (115.0.2) and only in Chrome-/Chromium-based browsers.

As the title pretty much says... my TinyMCE always adds an almost empty paragraph (containing only a nbsp) after saving the page. I have to manually remove it via Source Code view to have it fixed for that moment. The next time I edit the content the paragraph gets added again. In total I have to save a page twice. I tried to find a setting or plugin that does that and even disabled lazy loading. No chance. The only setting that fixes this issue is using the inline editor and not the normal editor. But that's not really an option. Has anyone encountered this issue as well or maybe even knows a nicer fix for it? ProcessWire: 3.0.221 PHP: 8.2 Profile: PW Multi-Language Field export below: [BEST SOLUTION FOR ME SO FAR]

I'd fake it and use a selector like this: $pages->find("id=1")->each('<li><a href={url}>{title}</a>');

Short follow-up: it's perfect now!

Absolutely! Even their Twitter account is having fun right now and ThePrimeAgen is on board of course. https://twitter.com/htmx_org https://www.youtube.com/results?search_query=primeagen+htmx

As there are already a few fans of HTMX here - just to let you know: htmx 1.9.3 has been released https://htmx.org/posts/2023-07-14-htmx-1-9-3-is-released/

This would be awesome! I was afraid you would say that, yet I almost knew it. On the other hand I wanted to mention such an addition for your fieldtype. Since my last post I tried a few things more and there is another thing I found... would it be somehow possible to wrap days and times in individual <span>s or define a dl instead of an ul? My goal is to make it look like a table, which is not possible right now - besides using the array version, which isn't that handy - but would work probably. On the other hand... your JSONLD output example is absolutely perfect for what I can tell right now.

I just started playing around with this module, and so far it's really nice. There is just one thing that is a bit weird for me, as I don't really need that holiday entry. Is there a way to hide it? Sure, I could use showClosed=false, yet I'd like to list all days of the week, as it makes it way easier to read and compare. Another minor thing in regards to that holiday option that came up while playing around... would it be possible to somehow add a label to it and add up to 5 or more entries? For example, if I wanted to add Christmas Eve, the 1st and 2nd Christmas Day, New Year's Eve, and New Year's Day, That would be 5 days for which I would either need a date or a label, so everyone knows exactly what days are meant.

Are those different to the ones in the standalone VS Code extension?

Future-Proof involves a bit of work on your side. Future proof just means, it could and will probably be a solid setup in the future, either with your knowledge or changes brought in, or by PW/Ryan/Module Devs. See below, please. If you are not THAT into PW or PHP... future proof or all-in/DEV setups might not work for you. You chose to use an experimental* setup of PW/PHP. * some kind of non-official setup right now (2023-07-05) The combo you chose is somewhat in-between everything right now. IMHO. I had quite a lot of issues with that combo and therefore moved to my Peace-of-Mind of setup in most cases. [Disclaimer] I AM NOT A PROGRAMMER, or even a DEV - since 2014 I just use and work with ProcessWire. And it works for me. I know almost nothing about PHP, besides echo/foreach/if/else and similar. And some details about PHP in general. I do concepts most of the time, sometimes frontends (nowadays), and in the majority SEO, Marketing, and such. So... yes... you still get those issues for whatever reason in some setups. That's why I mentioned my personal Peace-of-Mind setup above. (as it totally works for me without any issues - and I am not an example for anything in those regards) As @bernhardmentioned... contact that module dev and let them know there might be something wrong. A PR/issue report is probably the best way to communicate that, AFTER contacting that DEV directly in one way or another. PRs with a solution at hand... always a great way to contribute. SO... even though you got errors/warnings ... you helped to find issues to make PW more FUTURE PROOF and maybe even DEV setups. That's awesome. (as mentioned in some other thread, I can't find right now: PW and PHP are moving quite fast right now... issues are a thing, but the outcome will be worth it)