Leaderboard

This week I’ve continued work on the new modules directory and today have launched an updated version of it on the site. This is just an initial version of it, as there’s still plenty to do. But the basics are up and running if you’d like to take a look at https://processwire.com/modules/ The new modules site is using ProcessWire’s multi-instance support to boot a copy of modules.processwire.com and to pull and manipulate data from it. In order to prevent content duplication, I’ve setup most of the pages at modules.processwire.com to redirect to their equivalent versions in processwire.com/modules/. There’s not much new here in terms of data that is being displayed, though it is also different in several ways. For starters, it finally has the look-and-feel of the main site. The modules homepage takes a different approach and lists 3 modules each in these different sections: Recently added modules Recent updated modules Popular modules Modules recently liked by users Modules in the “recently updated modules” section are those that have had recent commits at GitHub. The “popular modules” section randomly selects 3 modules that have a certain threshold of “likes” quantity and date of user activity, combined with being updated within the last 6 months. Or you can view them all (no random selection) at the dedicated popular modules page ... this section will grow as users interact with it. The “modules recently liked by users” section looks for modules that have had the “like” button clicked on recently, and puts them into this bucket. Like the “popular modules” section, this one will grow and increase in relevance once there is more user interaction with the new modules directory. There’s also a new feature on this modules site where you can maintain a “cart” (of sorts) that keeps track of which modules you have liked. In addition, the new modules site estimates how much usage each module has by analyzing request data from the ProcessWire modules web service. This is something the old modules site does not do. It uses this data solely for providing a unique sortable view of modules. Because this data hasn’t been tracked for long, it’ll increase in relevance over time. One area that I want to build out quite a bit more is the module “authors” section. Since the new modules site will be using authenticated login sessions with LoginRegisterPro, we’ll be able to maintain a lot more “profile” info for module authors (full name, bio, photo, website, anything else?) There are a few things still in development, so you won’t see them just yet: Edit module ability (it directs you to the old modules site for that) Add module ability (also directs you to the old modules site) Informational pages (how to install modules, etc.) More to come here, but that’s where it is now. Nothing all that exciting I know, but still an improvement hopefully. If you find anything that isn’t working, or have other feedback or suggestions, please let me know. Thanks for reading and have a great weekend!

Hi Ryan, Looks like a great start. First thing I noticed is that pagination doesn't work. I'll let you know if I come across anything else. I also think it's probably time to remove modules that don't support PW 3 from the sorted lists - highly liked modules that don't work with v3 will be confusing to new users.

Hi guys, I thought, this collection of alternative google services would be interesting for someone of you: https://nomoregoogle.com

Tip: Giving Folders Custom Display Names I created a workspace where I wanted to add the "site" folder from various ProcessWire sites that I'm working on to do some updates across all the projects, as opposed to opening each workspace independently, one after another. VSCode can handle this, however because the folder name is always "site", it's impossible to differentiate which "site" folder belongs to which project in the sidebar. But, there's a way to set up a custom name override which I thought was very useful. Simply edit the .code-workspace file and add a "name" property to each root folder, so it looks like this: { "folders": [ { "path": "." }, { "name": "website 1 /site/", "path": "../website-1.com/site/" }, { "name": "website 2 /site/", "path": "../website-2.com/site/" }, ... While I could have added "website-1.com" and "website-2.com" which would have resulted in unique folder names anyway, my specific use case was a bit more involved than what I demonstrated above, so hopefully you find this tip helpful! Link: https://github.com/Microsoft/vscode/issues/45227#issuecomment-371380617

Let's not forget a mobile phone without Google https://e.foundation/ https://itsfoss.com/open-source-alternatives-android/ https://fsfe.org/activities/android/liberate.en.html

@adrian Thanks, pagination fixed. I meant to mention about non PW3 modules above, that I'm going to be removing them from the directory, or at least from the generated lists that it outputs. I don't think there's any need for the directory to maintain PW2 modules anymore, but I wanted to go through them one-by-one just in case there are any that are mislabeled as PW2, or maybe some are still actively developed and work with PW3. But the reason the new modules directory doesn't say anything about PW version is because it was going to be exclusive to PW3 compatible modules going forward.

Oh awesome - thanks for pointing that out. I have updated the module to use this and it seems to be working fine.

No need to change the module with the Google API keys. You can retrieve the title with oEmbed by using a url like this: http://www.youtube.com/oembed?url=http%3A//youtube.com/watch%3Fv%3DM3r2XDceM6A&format=json For more info check here.

Hi Ryan, Looks like a great start. First thing I noticed is that pagination doesn't work. I'll let you know if I come across anything else.

Hi @adrian great module, thank you!

FieldtypeGridSpace A grid selector for space design An input field for placing DOM elements in horizontal grids based on Bootstrap grid system. Module URL: https://processwire.com/modules/fieldtype-grid-space/ Here is the github https://github.com/carlitoselmago/FieldtypeGridSpace With updated images of backend and frontend example

I found it here: https://github.com/carlitoselmago/FieldtypeGridSpace just for anyone interested.

Hey, I'm new and I created a simple module for tagging pages because I didn't found a module for it (sadly this is not a core feature). This module is licensed under the GPL3 and cames with absolutly no warranty at all. You should test the module before using it in production environments. Currently it's an alpha release. if you like the module or have ideas for improvements feel free to post a comment. Currently this fieldtype is only compatible with the Inputfield I've created to because I haven't found an Inputfield yet, that returns arrays from a single html input. Greetings Sebi2020 FieldtypeTags.zip.asc InputfieldTagify.zip InputfieldTagify.zip.asc FieldtypeTags.zip

Just add: protected static $fM; at line #19 You'll also need to change line 94 from: self::$fM['type']($f, $fM['label'], $data[$f], $fM['desc']) to: self::{$fM['type']}($f, $fM['label'], $data[$f], $fM['desc'])

Another option that might work (though not yet tested to compare): $result = $pages->find("template!=admin, has_parent!=2, include=all");