monollonom

In the meantime this came out https://processwire.com/modules/page-edit-restore/ and it can definitely mitigate this issue of losing your edits.

@joe_g It’s a bit of a late reply, but I pushed an update for the module which allows to extract the footnotes across all fields where the textformatter is applied to then output them wherever. Please have a look at the first post in the thread for an example.

Fortunately you don’t have to use Mailjet to receive and use a MJML API key 🙂 You just have to give your email address to receive your API key and that’s it. For now it’s free and it’s been so for a while, let’s hope it stays that way.

You can try to use my module https://processwire.com/modules/page-mjml-to-html/ It allows you to write your newsletter’s template using the MJML syntax and get it converted into proper HTML when viewing a page (and also when sending via ProMailer). Please have a look and if you happen to have an issue, don’t hesitate to share it here

As I was exploring the modules page I came across this module which reminded me of this topic: https://processwire.com/modules/textformatter-markdown-in-markup/ Maybe this could help?

->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.