Leaderboard

Fluency has been added to the ProcessWire modules directory! https://processwire.com/modules/fluency/ The readme and module documentation has been expanded significantly to document all of the features available to you when using Fluency, including markup rendering. Enjoy!

? PW Weekly 501 ❤️ Thank you, @teppo!

If you haven't yet noticed it, @teppo has hit the 500th issue of PW Weekly! That is a ridiculously massive milestone and an amazing achievement, and after some quick maths, also tells me that he's held strong for almost 10 years now! I'm not sure what's more surprising, that he's managed to keep it going continuously for this long, or that I remember when he started it... That's a long darn time. I may not be a hugely active member of the community, but I'm darn proud to be a part of it regardless. Thank you so much for your devotion to the PW Weekly project, @teppo!!!!

There's pretty much always a sensible reason when it comes from Ryan ?

Hah. I do the same for the processwire-dev branch using Zapier. Near instant notifications when commits are made. Living on the cutting edge.

@Robin S ProcessWire Weekly (weekly.pw) is a great website and I don't want the email to take any of the limelight from Teppo's website. The content is 100% authored by and owned by @teppo, and he's very generous to let us re-publish it in the email. It seems appropriate to me to send the email a week later, ensuring the website remains the primary, most up-to-date source, and the email doesn't take any traffic from it. My hope is that the email increases traffic to the weekly.pw website. The other thing is that the introduction part sometimes refers to the weekend (since that's when it is published), and if I were to send it earlier, the earliest would be on a Monday. So it often reads better to send it on a Friday when any references to the weekend still make sense.

I wrote this search module: https://github.com/dtjngl/simpleSearch It works OK so far, however I don't know why I cannot uninstall it. When I uninstall it, it keeps reinstalling. Is that issue to be found in the module? Cause I do have locations in my website template files where I initiate this module but that shouldn't matter because it reinstalls (or doesn't uninstall) while still on the modules overview page in admin. Also no mentions of it on ready.php etc. Thanks for help!

Yeah i see your Point, i think this Will get hands on the Google apps scripting language!?

I tried that, didn't help. However, once I upgraded my /wire/ folder, no conflicts anymore and I was able to uninstall. So ProcessPageViewStat was never the problem apparently. I could reinstall it actually. Thanks!

This is not related to the module it's self. Therefore no support here.

Oh wow, you are amazing, LOL! That worked great. The only downside I can see if that I can't see a way of having a dynamic number of rows in the Google Doc. So I have to paste more than I need for the update to work. E.g. If I paste 10 rows in the Doc that limits it to 10. That should be okay but am I missing something that would allow me to have any numbers of rows pull through?

Something like this? Create as many sheets as the number of different options in your cell Recall the filtered datas by using a query function like =QUERY(all_data!A:C; "select * where C = 'alpha'";1) Now to make it in Gdocs: Open the Google Sheets spreadsheet that you want to embed into your Google Docs document. Highlight the data you want to copy, and select Edit > Copy or use the appropriate keyboard shortcut. Switch to your Google Docs document, click where you want to insert the table, and select Edit > Paste. A window will appear, allowing you to choose between "Link to spreadsheet" or "Paste unlinked." Selecting "Link to spreadsheet" will create a linked table that can be refreshed and updated if the original spreadsheet data changes (not automatically) From now on, You can also setup the interval range but the downside is that you'll get a lot of empty lines if these cell contains no data. I think this would be the cheapest option ?

$t->flags = Template::flagSystemOverride; $t->flags = 0; // etc... save here or delete $t->save();