cb2004

@ryan was there ever any movement on this, they are now up to version 8.1.2. I don't keep up with the WYSIWYG landscape, does it matter that PW is so far behind?

Very very nice. Good work to all involved.

With the talk of a new master in this post its worth mentioning mobile admin needs some work still. Great progress all around though.

Using ::render would probably be too late? Try ::renderReady

Unrelated but how can something not work on shared hosting? Especially something open source in 2025. Is there some over thinking here when something like Google Docs would be just fine?

Very well said. Although if you start inviting module developers into a conversation where does/should it stop. I agree with the way this was approached, and the dev branch has always been available for this sort of thing. Some of the criticism has come across as negative but I don't think it was meant to, it seems everybody wants the best from this especially KONKAT.

Couldn't have said it better. This is on the dev branch and is amazing so far. Massive thanks to all involved. And all the people giving feedback is amazing as well. By the tine this is ready for prime time it will be awesome.

Been testing this and loving it so far. A website is never finished, neither is an admin theme. Keep up the great work, I will do some thorough testing closer to a master release, but everything that needs looking at seems minor at present.

I was also wondering about an update yesterday as Tiny are already up to version 7.5.1

https://github.com/wanze/FieldtypeSecureFile Could get some inspiration from there. I think this is a well needed core feature personally.

@wbmnfktr I have also noticed the same over the years, but I thought nevermind, I have this module.

@ryan enjoy the extended break from work, although it is something you love it needs to be done

@BitPoet any further plans for this as it looks like Tiny is here to stay with version 7?

Nicely said @Pete. I have struggled with mental health in the last 10 years and I actually find the ProcessWire forums with its community to be a relaxation tool for me. I love seeing people help each other every day and that makes me feel positive about the world. Sounds corny I know.

@ryan reading your reply makes me realise you are such a master of your craft, but you can't take all this on by yourself to grow the project. Rather than the community telling you what they want, tell us how we can help you.

Might also be worth mentioning, it looks like you are trying to set the crop point of an image. Do you know about focus points on images with newer versions of ProcessWire? There would be no need for a dropdown then.

@BitPoet I see great potential with this module, have you had a chance to take a look at the issue reports and can I help with anything?

@BitPoet it certainly did, thank you for the quick response.

Unfortunately this doesn't seem to work with the current version of ProcessWire 3.0.237. As soon as I add 1 page with a template that is restricted, it then cant be added anywhere else, even way out of the way of the other parent.

@ryan great to see this module updated. Would you consider adding this feature to the next version: https://github.com/ryancramerdesign/ProcessExportProfile/issues/15

I was thinking maybe it could be a bit simpler, for me all I need to do is check the modified date every 5 seconds and if it is different to what the page currently says then it just refreshes.

Hi all. My JS/jQuery really struggles towards the end of the week, but I was just wondering if anybody has had the need to check the modified date of a page and if there is new to refresh. If not I will take a stab at it again next week. Have a good weekend all.

@Stefanowitsch in the 'Input' tab of the field settings, there is a 'Custom settings JSON' area. You can put it in the 'JSON text' field, or if you need to reuse it, create a file on your server add the above to the file and point to it using the 'JSON file' option.

@Tintifax I recently had the same requirement: { "color_map": [ "595885", "Purple", "6a905e", "Green" ], "custom_colors": false }

@ryan summed it up really nicely. I mentioned earlier about Swiper, and Splide etc, completly forgetting they have moved to ES6 some time ago. Front end modules would be advantageous to remove jQuery I agree (if we are thinking very long term) but why remove it in the backend. I also hate vanilla JS, always have always will (not as much as I hated Flash), so I will continue to champion jQuery. It has such little overhead (especially the slim build) that it makes it strange to me that Lighthouse complains about Google Fonts, YouTube embeds, Analytics and lots of other things but not jQuery. They are already talking about what will be in jQuery 5 so it's here to stay I think.