New ProcessWire modules directory

There’s a new modules directory on the ProcessWire site now up and running. In this post we’ll cover a few details about what’s changed and what’s new.

While the data behind the directory is largely the same, the new modules directory is a major upgrade in appearance, consistency and functionality, especially when it comes to tools for module authors.

The new modules directory is also using ProcessWire’s multi-instance support to boot a copy of modules.processwire.com and to pull and manipulate data from it. There's more about that (and a lot more) in part 1 of this post, which was in the forum. This post is part 2, which focuses more on the newly added module author tools. If you are interested, I recommend reading part 1 first.

First off, as you might expect, module authors can login to edit their modules anytime (by clicking the Login/Register link in the top right corner). But they can do a lot more too…

Module authors can create their own accounts. If you are a module author, please register with the email address that your existing modules were submitted with. That way it’ll migrate your modules automatically. Though let me know if any don’t come through into your account and I can update them.

Module authors can click a button on their module page to automatically refresh the README, version, and other module information, live from GitHub.

Once a module has been approved, module authors can un-publish and publish their own modules as they see fit. They also have the ability to delete their own modules.

Trusted module authors that have been around a long time have the ability to approve their own newly submitted modules.

Users can manage their own profile, including biography, photo, two-factor authentication settings, and more. Once you’ve added a bio and a photo, it’ll show these on your author page.

Users can maintain their own “favorites” list of modules that includes any modules in the directory. The plan is to show these in the public profile, but currently it only shows it to the user that created the list.

For newly submitted modules, we now require that they have a GitHub repository. The overwhelming majority of modules already do, so it seemed like a safe bet to standardize on that.

Beyond the appearance of the directory, these accounts are the biggest difference from the old modules directory, as the old directory had nothing like this. Though it also means it’s the one part of the site that has had the least testing so far. I’ve been working on it the last couple of weeks and only pushed it live to the server today. If you are a module author and have a chance to create an account, login and test it out, I’d appreciate your feedback. Also, if all of your modules don’t automatically show up in your account, please let me know so I can migrate them manually.

In addition to ProcessWire, the tools used to create the modules directory, accounts and editing ability are LoginRegisterPro, FormBuilder and FieldtypeLikes. The modules directory data still comes from its own separate ProcessWire installation at modules.processwire.com, but is booted by the main ProcessWire site using ProcessWire’s multi-instance support. The majority of the code behind the modules directory is now in the main ProcessWire site installation, even if all the data is still in a separate install. I found this setup to be a good learning experience and have taken a lot of notes about working with multi-instance that I hope to formulate into a good blog/post in the next few weeks.

There's still more work to do here and likely some bugs to iron out. But after spending most of the week on it, I think most of the work is now out of the way and I'm hoping to get back to focusing on the core next week. Thanks for reading, enjoy the ProcessWire Weekly and have a great weekend!

Comments

  • Adrian Jones

    Adrian Jones

    • 2 weeks ago
    • 10
    Ryan - looks really great so far. The only thing I noticed is that the QR code for 2FA was generated, but manually copying/pasting still worked.
    • ryan

      ryan

      • 2 weeks ago
      • 00
      Thanks for the feedback, glad you like it so far. For the 2FA, the QR code is there as an alternative to copying/pasting the "secret". That's because many people use a mobile device for TOTP, so it's easier to scan the QR code in that instance. But they are the same thing, so whether you copy/paste or scan the QR code doesn't matter, it's whatever is more convenient for your configuration.
      • Adrian Jones

        Adrian Jones

        • 2 weeks ago
        • 00
        Sorry Ryan - I mistyped above - the QR code was NOT generated - I just got a missing image icon.
  • Adrian Jones

    Adrian Jones

    • 2 weeks ago
    • 00
    Although I just tested again and it is working now.
  • HMCB

    HMCB

    • 2 weeks ago
    • 20
    Awesome work Ryan. This is a great way to see the year off.
  • Teppo

    Teppo

    • 2 weeks ago
    • 10
    Hey Ryan!

    Great job on the directory. Registration and module management worked flawlessly too :)

    There's a glitch on some module pages at the moment — see https://processwire.com/modules/seo-maestro/. Looks like page content is rendered before , so perhaps it's a Markup Regions issue?

    • ryan

      ryan

      • 2 weeks ago
      • 10
      Thanks Teppo. For that messed up page I hit the GitHub Refresh button and that seems to have cleared it up. Must have been a broken markup tag in the readme markdown to HTML conversion, but seems to work now. Let me know if you spot any others like it and I'll refresh them too.
  • Adrian Jones

    Adrian Jones

    • 2 weeks ago
    • 00
    Ryan - did you intentionally delete the other comments, including one from teppo, or is there a big that deleted them?
    • ryan

      ryan

      • 2 weeks ago
      • 00
      I haven't deleted anything. It sounds like maybe you were seeing a cached version. Sometimes cache sticks longer than it should since we're load balanced among multiple servers. I'll clear the caches just in case.
  • Adrian Jones

    Adrian Jones

    • 2 weeks ago
    • 00
    Ok, now all the comments are back after I posted that last one. I had checked on multiple devices / browsers and there was only my original comment do something weird is going on.
  • Tomas

    Tomas

    • 2 weeks ago
    • 00
    I think there's a bug in the search page.

    When Searching for TextFormatters in the Modules Directory (https://processwire.com/search/?q=textformatter&t=Modules) 2 result pages show up.
    When the second page is clicked, 3 pages are now displayed - page 3 being marked as currently active (the url is https://processwire.com/search/page2?q=textformatter&t=Modules - so Page 2). When I click on "Page 2" I get redirected back to the first page.

  • Adrian

    Adrian

    • 2 weeks ago
    • 00
    Right now I see one of your replies, but not the second one, nor the one from Thomas - both of which I was notified of by email, but I think that once I post this, they will both show up.
  • Adrian

    Adrian

    • 2 weeks ago
    • 00
    Yep, now I can Thomas' comment and your reply to teppo. Definitely something related to replying and therefore being "logged in" - by that I mean that my name and email is now populated - presumably via cookie / local storage.
  • Adrian

    Adrian

    • 2 weeks ago
    • 00
    Ryan - clearly the caching is causing problems. My last post from yesterday is still showing that it was 46 minutes ago. Something definitely needs fixing.
  • Pi3r

    Pi3r

    • 1 week ago
    • 00
    Hi! It looks great. But I can not find the Module Classes anymore :-/
    • adrianbjones_gmail.com

      adrianbjones_gmail.com

      • 1 week ago
      • 00
      The class name is what you see in pink on any of the list pages. And on each of the single module pages, it's in the blue banner at the top, eg:

      RestrictMultiLanguageBranch by Adrian Jones

      https://processwire.com/modules/restrict-multi-language-branch/

  • Alchime

    Alchime

    • 1 week ago
    • 00
    Hi,

    On this page there is a typo i believe : " you’re modules"
    ;-)

 

Twitter updates

  • In this week’s blog post we’ll take a brief look at a powerful new ProFields module for ProcessWire that’s just around the corner—the Combo field: More
    4 December 2020
  • There’s a new modules directory on the ProcessWire site now up and running. In this post we’ll cover a few details about what’s changed and what’s new—More
    20 November 2020
  • ProcessWire 3.0.168 core updates — More
    26 October 2020

Latest news

  • ProcessWire Weekly #342
    In the 342nd issue of ProcessWire Weekly we're going to check out brand new admin theme called Admin Theme Canvas, a new module called MatomoWire, latest ProcessWire core updates, and more. Read on!
    Weekly.pw / 28 November 2020
  • About the new ProcessWire ProFields Combo Field
    This week we'll take a brief look at a powerful new ProFields module for ProcessWire that's just around the corner—the Combo field.
    Blog / 4 December 2020
  • Subscribe to weekly ProcessWire news

“The end client and designer love the ease at which they can update the website. Training beyond how to log in wasn’t even necessary since ProcessWire’s default interface is straightforward.” —Jonathan Lahijani