monollonom

->find() checks the access control/page status (contrary to ->get()) and repeater templates are hidden to guest users. Just add "include=all" to your selector and it should work.

Is the issue still happening for localhost as well? Also, have you tried to create an empty MAMP project with just an index.html (or even a simple index.php) to rule out a MAMP issue? I did the update to 7.2 and didn’t have any issue.

Reading the blog post again, I wonder if Ryan didn’t use an InputfieldPage to get the radios input

It’s even blacklisted. I think this has to do with FieldtypeMulti being harder to manage..? Otherwise you can use a FieldtypeCombo as an alternative by toggling it on in the FieldtypeFile’s module configuration page.

Hi @psy, Thanks for raising this issue and providing a fix. This was an oversight from me, sorry about this. I just pushed the fix! Let me know if you have any other issue.

If you have a feature in mind you would need or some help you’d like to get on a project, there’s also the option to purchase a “Custom Development” block from Ryan. I always wondered if someone used this in the past 🙂

Could you share an example (a screenshot?) and what you are expecting so I can better understand your issue?

Hi @Angelino, Does name, status sort correctly by name, regardless of status? Since pagenames are unique it doesn’t surprise me if status doesn’t have an influence in your sort setting. If you have pages with the same title but different status, then I would advise using title, status instead.

I love it that you called it “RockCare”, to rockfinity and beyond... 🙃 In all seriousness, IMHO I don’t think this is something worth developing for others to buy (nor as a free module). Everyone has their own set of requirements (and their own way of doing) and this would make it a very hard time on you to figure out a “one-size-fits-all” solution. I would advise to save yourself this burden, knowing you’re already going on big endeavours with other modules (e.g. RockCommerce). However this is just me and you could definitely beta-test it with select users to see if they could adapt to your way of doing and in this case foresee a potential public release. In my particular case though, this is something I wanted to tackle for a while now, also with ProcessWire. But I know for sure that I would want to do it all by myself, as a way to experiment (and have fun like you said) but also to make sure it’s perfectly tailored for my usage. What would be nice though is having a thread (this one?) so people can share what they put in place (PW-based that is) to help them managing this aspect of their work. Not going as far as sharing a whole site-invoice profile, but something along the lines of the associated blog post 🙂

It depends on what you want to achieve but basically with lazycron you specify a time interval target and whenever someone loads a page the lazycron checks if the interval has passed and then triggers its function. This means that depending on where you put the hook, it may check more often or not: if you put the code in a template, then the lazycron is checked only when a guest is visiting a page with this template. However if you put the hook in init.php (or ready.php) then the lazycron will be checked for every pageview, even the admin ones.

Do you remember which ones you read about? I don’t know how well it scales, but this is something that makes it interesting to have a PW module (same way there is a WP one): it would allow users to have a simple and manageable instance with one (or potentially more) users, on a shared hosting. But I did read some issues about how Mastodon is agressively sending requests to websites when they are referenced in a toot, especially if said toot is shared on a big instance (read https://www.jwz.org/blog/2022/11/mastodon-stampede/), I don’t know though if this changed in the meantime. I read that as well. Apparently ActivityPub is quite “loosely” spec’d so there’s a lot of parts that can be interpreted differently. And since Mastodon is (one of) the biggest player, their way of doing became a de-facto standard (others had to implement the Mastodon-way to be able to interact with the bigger network).

This is something I have had on my “things I’d like to do” list for a while now... I left Twitter some years ago and wanted to switch to Mastodon, but after learning how this is based on a (supposedly) web standard I wanted to have a look and try to implement my own thing, based on PW of course. I do feel as well that there is a gap and I would love it if it could be as simple as installing a module. From what I’m seeing the wordpress plugin does it really well and would definitely be an inspiration of mine. I also feel this could be a great addition to artists/designers/photographers’ website as a way to share their work, an alternative to Instagram potentially (but not as literally as Pixelfed does though). The closest I’ve seen here regarding this is the webmention module (thread) by @gRegor.

Hi @Robin S, Would you consider the idea of allowing something similar to In my use-case (the same one still), I would like add an edit button to allow to edit the page in a modal. In the meantime I’ll try to add this using javascript.

As this topic helped me to get on track, here’s a new module I created for this:

PageListCustomSort Github: https://github.com/eprcstudio/PageListCustomSort Modules directory: https://processwire.com/modules/page-list-custom-sort/ This module enables the use of a custom sort setting for children, using multiple properties. About This module is similar to ProcessPageListMultipleSorting by David Karich but is closer to what could (should?) be in the core as it adds the custom sort setting in both the template’s “Family” tab and in the page’s “Children” tab (when applicable). Usage Once a custom sort is set, it is applied in the page list but also when calling $page->children() or $page->siblings(). You can also apply the custom sort when calling $page->find("sort=_custom") or $pages->find("parent_id|has_parent=$id,sort=_custom"). Unfortunately this won’t work the same way sort=sort does if you only specify the template in your selector.