Ivan Gretsky

Good morning everyone! Congratulations with the new look! This redesign effort is something we've been waiting for a long time! I am reading the new site from mobile and I rediscover a lot of great content I forgot existed. I think the navigation logic is improved greatly. Surely, there are visible bugs and glitches here and there. And I didn't see the new site from the desktop yet. But new look is modern and cool. I remember getting used to the last redesign. It was a pain. We as people have hard times seeing something we love change. But the world has to move on) And I am pretty sure here it is for the good! Another amazing thing is that an international community-driven team of volunteers has been working on a redesign. This is so cool and I hope to see more of such for PW in every aspect of its development (like in fixing those bugs and glitches)). Great thanks to the volunteers!

Great! I was waiting for this moment since the times stars were not yet rounded in k's)) Congrats, everyone! But I still want to encourage everyone reading this go and check it their ⭐ is there and properly counted. And add it if not. We are heading for 2k))

And now... someone is going to be the one to change that 3-digit count to a beautiful 1000. Who is that going to be? I am a little jelous I can't be the one.

And here goes another friend of mine! Only 2 more to go! Seems like we won't need the whole weekend😎

@kaz, pages in PW are just a storage mechanism. They are called pages historically, but are often used as nodes, data items etc. Using pages as values for selects is a recommended way to go in PW. So @virtualgadjo's advice is a great one and a best practice. So do not hesitate and use it. See the 1st sentence of the official docs here : "While we usually recommend using the Page Fieldtype for selectable options..." P.S. Please star ProcessWire on github!

@harmvandeven, @thomas, join us! Got the game! I hope we're not getting banned for spam)

+2 !!! +3 !!!!! Hey, I know those 3 by names... Community! Start to show your power!!!

Nice challenge! Pinging my friends and colleagues. Already +1 )))

Good day, everybody! Sorry for not answering in this thread. Going through some not so easy times here. And working on this module is out of my reach for now. More to that the leaflet site is not even accessible from Russia (this is where I am at) as the lib author is in Ukraine. You can guess why. But maybe I have got a way around. Just maybe you noticed that the module repo is under the FriendsOfProcessWire organization. I was hoping to gather a team of PW loving devs under this org and support some important but abandoned modules there. This plan didn't work out (yet?) but we can try to make it work. If someone here in this topic feels willing and capable to take care of FieldtypeLeafletMapMarker (at least for a while), please write to me a PM and we will decide how to go on. I was always wishing a more productive community cooperation around PW and just maybe it is time))) P.S. I am now out of town so might not answer quickly. But I will)

I am using Bookstack too for some docs. But I really do not think it should be used for community maintained docs for an open source project. Those should be open for commits from everyone. I think that VitePress or Docusaurus or Mkdocs or even some php static site generator. The docs are markdown in the repo and contributing is just a PR.

Not so fluent with composer. So consulted the docs. Seems like composer update --with-all-dependencies will do it.

What a twist!!!

I have not tested the module with PR merged. Just seen it in the last moment before creating an issue in github repo about compatibility. I am waiting for @robert to share his thoughts on this. Maybe he is already in the process of working with your PR. Will ping him on github too.

Good day, @robert! We have been using your module for a long time. Thank you for making it! We have even extended you classes for our own modules: a form on edit page to configure how the page has to be translated on save; a Lister action for mass transtlation. Now I have updated Fluency to a newer version (211). @FireWire has made a major rework. And you module no longer works. I have not examined the new Fluency's features. Maybe they already do all the things you wonderful module does... I see that the incompatibility has already been reported and @FireWire even created a PR (which seems to have issues and needs some work to be merged). Could you please look into this and update the module? If you find some time... 🙏

Could you please explain why is this important and how do you use it?