Jump to content

Modules Manager


Recommended Posts

@Neeks 500 errors are most often caused by .htaccess problems. Have a look at your .htaccess - does it need updating for 2.4? Also try commenting out any non-PW entries and see if you see an improvement.

Link to comment
Share on other sites

Hi there! Just updated to PW 2.4 - without updating the ModuleManager to 2.x, which worked fine. After that I added JQueryDataTables and then updated to the latest ModuleManager that gives me "400 Bad Request - Request Header Or Cookie Too Large" now.

I'm using a Nginx webproxy/server via HTTPS. The logs do not tell me much (access.log, error.log is empty): - - [06/Mar/2014:11:48:56 +0100] "GET /processwire-admin/setup/modulesmanager/ HTTP/1.1" 400 242 "https://bs.somedomain.com/processwire-admin/module/edit?name=ModulesManager" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0"

So nothing to see here. Thank you.

Link to comment
Share on other sites

module manager worked great until I upgraded to the latest version after upgrading from pw2.3-2.4 and upgrading to the latest module manager at the same time I kept getting:

"500 Internal Server Error"

Note: old module manager worked under 2.4.

I searched though my logs but an not finding anything in the porcessiwre error log or my apache error log.

every once in a while the page does load with the words "processings..." and "loading..." by the module table

when look at my js console it says "502 bad gateway"

90% of the time I just get the error 500 and don't even see the module manager table. 

I have tried setting max redirects from 0-25

and limit from 0-200


Please let me know if there is anything I can do to provide better debug information. 

This module is amazing and just want to give so much thanks for all the hard work that went into it. 

I don't see what could be the problem. Did you install JqueryDataTables module too?

Link to comment
Share on other sites

Hi there! Just updated to PW 2.4 - without updating the ModuleManager to 2.x, which worked fine. After that I added JQueryDataTables and then updated to the latest ModuleManager that gives me "400 Bad Request - Request Header Or Cookie Too Large" now.

I'm using a Nginx webproxy/server via HTTPS. The logs do not tell me much (access.log, error.log is empty): - - [06/Mar/2014:11:48:56 +0100] "GET /processwire-admin/setup/modulesmanager/ HTTP/1.1" 400 242 "https://bs.somedomain.com/processwire-admin/module/edit?name=ModulesManager" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0"

So nothing to see here. Thank you.

I don't understand. Does this happen when updating, after updating...

I don't see any problems and working/worked fine here. I did some changes on 2.1.2 but don't think that's doing anything you see here.

I have problem understanding where and what happened, let alone understanding that error as I don't know exactly when it did happen.

Link to comment
Share on other sites

Just tested with a ModulesManager 1.1.1 installed and updated (using ModulesManager) ModulesManager to 2.1.2, no problems.

Still wondering what is different, or when this errors occurs and if it has to do with your server, https nginx or whatever. There's hasn't really changed anything of the core stuff just minor tweaks and JqueryDataTables added.

Link to comment
Share on other sites

Hi there! Just updated to PW 2.4 - without updating the ModuleManager to 2.x, which worked fine. After that I added JQueryDataTables and then updated to the latest ModuleManager that gives me "400 Bad Request - Request Header Or Cookie Too Large" now.

I'm using a Nginx webproxy/server via HTTPS. The logs do not tell me much (access.log, error.log is empty): - - [06/Mar/2014:11:48:56 +0100] "GET /processwire-admin/setup/modulesmanager/ HTTP/1.1" 400 242 "https://bs.somedomain.com/processwire-admin/module/edit?name=ModulesManager" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0"

So nothing to see here. Thank you.

If the error is "request header or cookie too large", it'd be helpful if you could take a look at headers and cookies sent for that request and see if there are any anomalies there. From there it would be easier to debug why that's happening :)

Link to comment
Share on other sites

Hello and thanks for the nice ModulesManager module.

I'm running into a problem after deploying the site on the live server. When I open ModulesManager I get this error:

TemplateFile: cannot read cache file /is/htdocs/.../site/assets/cache/ModuleManager.cache

The file is there and its permissions are set to 640 so it should be readable by PW.

Any idea what might be the cause?

Thank you


Running into exactly the same problem. Deleting the ModuleManager.cache file did not help neither did removing and re-installing.

Developing locally on XAMPP on Windows 7.

Link to comment
Share on other sites

Hi, just wanted to say that my error: 500's magically fixed themselves. No sure if the  module manager was just having a hard time connecting to the server to get a listing or what. But my modules manager seems to be working flawlessly with no changes on my end. I increased the listing limit, all seems to be working great without a problem. Thanks.

  • Like 1
Link to comment
Share on other sites

  • 2 weeks later...

Hi, I just unzipped and placed the module in the modules folder on localhost.

To install this module the 'install' button is dimmed, does not seem to work.

If I click the module-name itself then in a window it ask me if I want to install this module. But also nothing happens.

Any suggestions? I use PW2.4 and am on localhost.




I had to download and install Jquery Data Tables module first. In my opinion:

when I see a text "requires..." I do not assume that I do not have it and WHAT it is.

How is one to know what it is - a file or something - and if it is not installed in the core already?

It would however be nice if this text - when not installed yet - could be: please download and install Jquery Data Tables module first!

Any way it's working now. Thanks

  • Like 2
Link to comment
Share on other sites

Any module that has a requires line is saying it requires those other modules first in order to work.

Perhaps it should display a toolkit on hover of the greyed out button or something to make it clear.

  • Like 1
Link to comment
Share on other sites

This is wrong thread for this to be discussed. 

For me I assume you know what a module is and how to search for it, and finally install it. But as said this has nothing to do with Modules Manager.

  • Like 1
Link to comment
Share on other sites

Well, not to be rude or anything, but now you are implying people need to know that the phrase "JqueryDataTables" is a module?

I guess I just have to learn all existing modules by memory and hope no-one creates a new one - I might flunk the test. lol

This phrase is put in the module part upon installing.

And when I was in the Modules/plugins section of this site at ModuleManager it did had a button saying "support board"???

But never mind, maybe the link over there is simply redirecting to the wrong topic....

Link to comment
Share on other sites


I agree with Soma here. The work of developing websites and installing modules is not for the client. It is the work of the developer. In that sense, It is assumed (nay, required even) that a developer working on PW (or any product for that matter) has some basic knowledge about how to develop in that system. In my opinion, before you install a module, you need to know what it is, what it does and what you need to get it up and running (how to install and uninstall it, what it requires - including PHP and PW versions). You also need to know and understand the notices and description text in the PW Admin and the modules you install. Logically, it follows then that when you see something labelled as "required", it means you have to check and confirm whether you have it or not..."

I don't mean to be rude (or presumptuous) but the indication (as you state in another thread) that you by going through a certain tutorial in the Wiki you understood the difference between $pages and $pages tells me you probably haven't read the PW docs, especially the must-read PW API about $page and $pages. Or maybe I am wrong and that's where your PW journey started. Further, going by the conversation above, I can only assume that you haven't read about Modules either (http://processwire.com/api/modules/) in the docs. If you did, you would have noticed that the issue of "require" is addressed...

I normally don't wade in like this, especially when it comes to new forum members. I am not attempting to put you off but gently suggesting that it is in your best interest to read the necessary docs. Then, we can sort of be on the same page (no pun intended) when discussing the ins and outs of ProcessWire...


Edited by kongondo
Link to comment
Share on other sites

Well, not to be rude or anything, but now you are implying people need to know that the phrase "JqueryDataTables" is a module?

I guess I just have to learn all existing modules by memory and hope no-one creates a new one - I might flunk the test. lol

This phrase is put in the module part upon installing.

And when I was in the Modules/plugins section of this site at ModuleManager it did had a button saying "support board"???

But never mind, maybe the link over there is simply redirecting to the wrong topic....

No problem. I'm glad you actually brought this up. 

By saying "it's probably wrong thread", I meant that the problem you had there isn't directly related to Modules Manager but installing modules in PW core module manager in general.

For me and others it seems to be clear that if it shows "Requires: SomeName" means that it's a module that is required to be installed (since you can't install it) This is always a module, and never something else. The requires dependency is something handled by ProcessWire and not Modules Manager. So Modules Manager isn't responsible for it, I just tell ProcessWire what Modules Manager requires as a "JqueryDataTables". I don't have influence on how this particular feature shows and works within admin core module page, since Modules Manager it isn't even installed yet at this point.

After all it's fine, at least you posted something (a concern) that maybe helps us improving it. We are all for improving things, but this hasn't really come up for anybody, but that doesn't mean it couldn't be improved.

It shows...

... it may not clear for some what "requires: SomeName" really means. Along with that you can still click on the module name and opens an alert, that doesn't say much. I think this is a "bug" that needs to be addressed by Ryan. So please file an issue (or someone else) on ProcessWire github, explain it or link to your post.

...Modules Manager readme needs an update with a note about requirements.

I think some more, clearer "newbie-friendly" instructions could be implemented by Ryan for the module installing process. So will I need to for Modules Manager (kinda same story)

I also just updated the readme and this threads first post. Thx.

Link to comment
Share on other sites

As for installing modules. 

In PW 2.4 you don't necessary need Modules Manager to download and install modules.

Instead of donwloading and put folder in modules folder, you could've done it via PW module page. Go to the modules page in admin and go to tab "New", enter name  "ModulesManager" (class names are always unique and in this kind of format "SomeName", you'll see that name on module details screen on modules.processwire.com) and submit. It will look for the module and if found allow you to download and install it directly from within admin. This you could've done with the "JqueryDataTables" module too. Just copy and enter the name and go to "New" tab.

If a module has all required modules installed it won't show the "requires" note. To make sure that you don't have the module already downloaded you could search the module screen and look under "Jquery" section. 

Link to comment
Share on other sites

  • 2 weeks later...

Hi tobaco, Soma is the King of this so I can't be sure of the following but my guess is that for some reason the initial attempts to list all Modules failed (e.g. a glitch in the Matrix) and so you initially saw 10. My experience of this Module has been that it is 100% reliable across multiple sites. I think when it connects and lists all 224 (and counting) it stores this list locally and so until you next manually refresh that list will remain.

So I would expect for these reasons you will find this Module very robust going forward; unless there is something else happening here with the particular install/environment.

Edit: PS: DOH! Misread your reply, though you said "so this seems to be only a temporary problem fix" - sorry, sounds like you're all good and don't need any comforter comments like mine :) Enjoy PW it's been a revelation each time I've needed it.

Edited by alanfluff
  • Like 2
Link to comment
Share on other sites

@Soma, Thanks for your great module! I am using this on every site I developed and it works great!

I just updated to latest Module Manager and was looking for updates on my installed modules and I have noticed two things: 

1) My module is older than the one is installed as per the module modified date but the version is same and module manager show it's up-to-date which should not be.

2) I have Video Embed for Youtube/Vimeo module which doesn't show up in module manager.

Thank you!

Link to comment
Share on other sites


The info at the top of the modules page should say something like:

Modules found on modules.processwire.com (224)

Maybe the file limit in the module's prefs is to low to check for all availabe modules?

I had to increase the limit at my installations recently.

  • Like 1
Link to comment
Share on other sites

So for the modified, just ignore it for now. Depends much on how Ryan will handle the modified date on module directory.

Regarding the versions, the "modified date" wouldn't always mean the module has updated its version. It could as well be an readme update or just the maintainer updated the modules info page. ModulesManager only looks for the version of the module to mark an newer available version. 

  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By LuisM
      Symprowire is a PHP MVC Framework based and built on Symfony using ProcessWire 3.x as DBAL and Service-Provider
      It acts as a Drop-In Replacement Module to handle the Request/Response outside the ProcessWire Admin. Even tough Symfony or any other mature MVC Framework could be intimidating at first, Symprowire tries to abstract Configuration and Symfony Internals away as much as possible to give you a quick start and lift the heavy work for you.
      The main Goal is to give an easy path to follow an MVC Approach during development with ProcessWire and open up the available eco-system.
      You can find the GitHub Repo and more Information here: https://github.com/Luis85/symprowire
      The Symprowire Wiki https://github.com/Luis85/symprowire/wiki How to create a simple Blog with Symprowire https://github.com/Luis85/symprowire/wiki/Symprowire-Blog-Tutorial Last Update
      16.07.2021 // RC 1 v0.6.0 centralized ProcessWire access trough out the Application by wrapping to a Service https://github.com/Luis85/symprowire/releases/tag/v0.6.0-rc-1 Requirements
      PHP ^7.4 Fresh ProcessWire ^3.0.181 with a Blank Profile Composer 2 (v1 should work, not recommended) The usual Symfony Requirements Features
      Twig Dependency Injection Monolog for Symprowire Support for .env YAML Configuration Symfony Console and Console Commands Symfony Webprofiler Full ProcessWire access inside your Controller and Services Webpack Encore support Caveats
      Symfony is no small Framework and will come with a price in terms of Memory Usage and added Overhead. To give you a taste I installed Tracy Debugger alongside to compare ProcessWire profiling with the included Symfony Webprofiler

      So in a fresh install Symprowire would atleast add another 2MB of Memory usage and around 40ms in response time, should be less in production due to the added overhead of the Webprofiler in dev env
    • By FireWire
      Hello community!

      I want to share a new module I've been working on that I think could be a big boost for multi-language ProcessWire sites.

      Some background, I was looking for a way for our company website to be efficiently translated as working with human translators was pretty laborious and a lack of updating content created a divergence between languages. I, and several other devs here, have talked about translation integrations and have recognized the power that DeepL has. DeepL is an AI deep learning powered service that delivers translation quality beyond any automated service available. After access to the API was opened up to the US, I built Fluency, a DeepL translation integration for ProcessWire.
      Fluency brings automated translation to every multi-language field in the admin, and also provides a translation tool allowing the user to translate their text to any language without it being inside a template's field. With Fluency you can:
      Translate any plain textarea or text input Translate any CKEditor content (yes, with markup) Translate page names for fully localized URLs on every page Translate your in-template translation function wrapped strings Translate modules Fluency is free, and now so is DeepL
      Since this module was first built DeepL has introduced free Developer accounts that allow anyone to start using Fluency at zero cost and beginning with the version 0.3.0 release Fluency now supports free DeepL accounts. As of June 2021 DeepL supports translation to 26 languages and continues to offer more!
      Installation and usage is completely plug and play. Whether you're building a new multi-language site, need to update a site to multi-language, or simply want to stop manually translating a site and make any language a one-click deal, it could not be easier to do it. Fluency works by having you match the languages configured in ProcessWIre to DeepL's. You can have your site translating to any or all of the languages DeepL translates to in minutes (quite literally).
      Let's break out the screenshots...
      When the default language tab is shown, a message is displayed to let users know that translation is available. Clicking on each tab shows a link that says "Translate from English". Clicking it shows an animated overlay with the word "Translating..." cycling through each language and a light gradient shift. Have a CKEditor field? All good. Fluency will translated it and use DeepL's ability to translate text within HTML tags. CKEditor fields can be translated as easily and accurately as text/textarea fields.

      Repeaters and AJAX created fields also have translation enabled thanks to a JavaScript MutationObserver that searches for multi-language fields and adds translation as they're inserted into the DOM. If there's a multi-language field on the page, it will have translation added.

      Same goes for image description fields. Multi-language SEO friendly images are good to go.

      Creating a new page from one of your templates? Translate your title, and also translate your page name for native language URLs. (Not available for Russian, Chinese, or Japanese languages due to URL limitations). These can be changed in the "Settings" tab for any page as well so whether you're translating new pages or existing pages, you control the URLs everywhere.

      Language configuration pages are no different. Translate the names of your languages and search for both Site Translation Files (including all of your modules)

      Translate all of the static text in your templates as well. Notice that the placeholders are retained. DeepL is pretty good at recognizing and keeping non-translatable strings like that. If it is changed, it's easy to fix manually.

      Fluency adds a "Translate" item to the CMS header. When clicked this opens up a modal with a full translation tool that lets the user translate any language to any language. No need to leave the admin if you need to translate content from a secondary language back to the default ProcessWire language. There is also a button to get the current API usage statistics. DeepL account owners can set billing limitations via character count to control costs. This may help larger sites or sites being retrofitted keep an eye on their usage. Fluency can be used by users having roles given the fluency-translate permission.

      It couldn't be easier to add Fluency to your new or existing website. Simply add your API key and you're shown what languages are currently available for translation from/to as provided by DeepL. This list and all configuration options are taken live from the API so when DeepL releases new languages you can add them to your site without any work. No module updates, just an easy configuration. Just match the language you configured in ProcessWire to the DeepL language you want it to be associated with and you're done. Fluency also allows you to create a list of words/phrases that will not be translated which can prevent items such as brands and company names from being translated when they shouldn't

      No "translate page" - Translating multiple fields can be done by clicking multiple translation links on multiple fields at once but engineering a "one click page translate" is not feasible from a user experience standpoint. The time it takes to translate one field can be a second or two, but cumulatively that may take much longer (CKEditor fields are slower than plain text fields). There may be a workaround in the future but it isn't currently on the roadmap. No "translate site" - Same thing goes for translating an entire website at once. It would be great, but it would be a very intense process and take a very (very) long time. There may be a workaround in the future but it isn't on the roadmap. No current support for Inline CKEditor fields - Handling for CKEditor on-demand hasn't been implemented yet, this is planned for a future release though and can be done. I just forgot about it because I've never really used that feature personally.. Alpha release - This module is in alpha. Releases should be stable and usable, but there may be edge case issues. Test the module thoroughly and please report any bugs via a Github issue on the repository or respond here. Please note that the browser plugin for Grammarly conflicts with Fluency (as it does with many web applications). To address this issue it is recommended that you disable Grammarly when using Fluency, or open the admin to edit pages in a private window where Grammarly may not be loaded. This is an issue that may not have a resolution as creating a workaround may not be possible. If you have insight as to how this may be solved please visit the Github page and file a bugfix ticket.
      ProcessWire  3.0+ UIKit Admin Theme That's Fluency in a nutshell. A core effort in this module is to create it so that there is nothing DeepL related hard-coded in that would require updating it when DeepL offers new languages. I would like this to be a future-friendly module that doesn't require developer work to keep it up-to-date.
      The Module Is Free
      This is my first real module and I want to give it back to the community as thanks. This is the best CMS I've worked with (thank you Ryan & contributors) and a great community (thank you dear reader).
      DeepL Developer Accounts
      In addition to paid Pro Developer accounts, DeepL now offers no-cost free accounts. Now all ProcessWire developers and users can use Fluency at no cost.
      Learn more about free and paid accounts by visiting the DeepL website. Sign up for a Developer account, get an API key, and start using Fluency today.
      Download & Feedback
      Download the latest version here
      Github repository:
      File issues and feature requests here (your feedback and testing is greatly appreciated):
      Thank you! ¡Gracias! Ich danke Ihnen! Merci! Obrigado! Grazie! Dank u wel! Dziękuję! Спасибо! ありがとうございます! 谢谢你!

    • By tcnet
      PageViewStatistic for ProcessWire is a module to log page visits of the CMS. The records including some basic information like IP-address, browser, operating system, requested page and originate page. Please note that this module doesn't claim to be the best or most accurate.
      One of the biggest advantage is that this module doesn't require any external service like Google Analytics or similar. You don't have to modify your templates either. There is also no Javascript or image required.
      There is only one disadvantage. This module doesn't record visits if the browser loads the page from its browser cache. To prevent the browser from loading the page from its cache, add the following meta tags to the header of your page:
      <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate" /> <meta http-equiv="Pragma" content="no-cache" /> <meta http-equiv="Expires" content="0" /> How to use
      The records can be accessed via the Setup-menu of the CMS backend. The first dropdown control changes the view mode.

      Detailed records
      View mode "Detailed records" shows all visits of the selected day individually with IP-address, browser, operating system, requested page and originate page. Click the update button to see new added records.

      Cached visitor records
      View modes other than "Detailed records" are cached visitor counts which will be collected on a daily basis from the detailed records. This procedure ensures a faster display even with a large number of data records. Another advantage is that the detailed records can be deleted while the cache remains. The cache can be updated manually or automatically in a specified time period. Multiple visits from the same IP address on the same day are counted as a single visitor.

      Upgrade from older versions
      Cached visitor counts is new in version 1.0.8. If you just upgraded from an older version you might expire a delay or even an error 500 if you display cached visitor counts. The reason for this is that the cache has to be created from the records. This can take longer if your database contains many records. Sometimes it might hit the maximally execution time. Don't worry about that and keep reloading the page until the cache is completely created.
      Special Feature
      PageViewStatistic for ProcessWire can record the time a visitor viewed the page. This feature is deactivated by default. To activate open the module configuration page and activate "Record view time". If activated you will find a new column "S." in the records which means the time of view in seconds. With every page request, a Javascript code is inserted directly after the <body> tag. Every time the visitor switches to another tab or closes the tab, this script reports the number of seconds the tab was visible. The initial page request is recorded only as a hyphen (-).

      New in version 1.1.0
      A new feature comes with version 1.1.0 which offers to record user names of loggedin visitors. Just activate "Record user names" and "Record loggedin user" in the module settings.
      You can access the module settings by clicking the Configuration button at the bottom of the records page. The settings page is also available in the menu: Modules->Configure->ProcessPageViewStat.
      This module uses the IP2Location database from: http://www.ip2location.com. This database is required to obtain the country from the IP address. IP2Location updates this database at the begin of every month. The settings of ProcessPageViewStat offers the ability to automatically download the database monthly. Please note, that automatically download will not work if your webspace doesn't allow allow_url_fopen.
      This module uses DragScroll. A JavaScript available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability in view mode "Day" to drag the records horizontally with the mouse pointer.
      This module uses the PHP class parseUserAgentStringClass available from: http://www.toms-world.org/blog/parseuseragentstring/. This class is required to filter out the browser type and operating system from the server request.
    • By clsource
      Inertia Adapter ProcessWire Module
      Hello! Long time no see.
      I created this module so you can use Inertia.js (https://inertiajs.com/) with ProcessWire.
      Inertia allows you to create fully client-side rendered, single-page apps, without much of the complexity that comes with modern SPAs. It does this by leveraging existing server-side frameworks.
      Inertia isn’t a framework, nor is it a replacement to your existing server-side or client-side frameworks. Rather, it’s designed to work with them. Think of Inertia as glue that connects the two. Inertia comes with three official client-side adapters (React, Vue, and Svelte).
      This is an adapter for ProcessWire. Inertia replaces PHP views altogether by returning JavaScript components from controller actions. Those components can be built with your frontend framework of choice.
      - https://github.com/joyofpw/inertia
      - https://github.com/joyofpw/inertia-svelte-mix-pw
      - https://inertiajs.com/

    • By sms77io
      Hi all,
      we made a small module for sending SMS via Sms77.io. It supports sending to one and multiple users.
      You can download it from GitHub and follow the instructions on how to install it - it is quite easy. An API key is required for sending, get yours for free @ Sms77 and receive 0,50 €.
      Hope this helps somebody and we are open for improvement suggestions!
      Best regards
  • Create New...