Leaderboard

Modules Manager for ProcessWire2.+ Module Manager enables you to browse the modules directory on modules.processwire.com, download, install or update them. Requires the JqueryDataTables module to be installed before you can install Modules Manager. "allow_url_fopen" to be enabled in your php.ini. "openssl" PHP extension needs to be installed on your server. PHP to have read/write access to the /site/modules/ directory For further informations contact the readme seen on modules directory or github. Modules Directory: http://modules.processwire.com/modules/modules-manager/ Github Project: https://github.com/s.../ModulesManager

I just commited an update with some things corrected and improved. Also changed install parent to "Setup". Not necessary now, but also added apikey and remoteurl config. Thanks Nik for the feedback. I changed the function to private and not static, so it should be ok. I haven't really tested it before, but should work now and throw some infos that if the dirs are not writeable. Thanks Ryan, very helpful infos. I removed the chmod 0777 as it was to test. And I use now wireMkdir. Good to know. Also corrected the deinstall typo! Point #5. Good point. I'll try to use the array keys for name => title. Will let it for now. As for the work on it and future. I'm pretty sure at some point I would love to get any help (any time), I would love someone with more experience in all those advanced stuff could help. Especially if it should be a core implementation once, I think you would be the person #1 to help and take it over. But I also think there's so much about it that can or should be done my head already explodes.

Hello to all, I keep testing ProcessWire on my 'amateur' side (compared to what you all do) and I'm really impressed by the work. And this blog profile sounds excellent to me. I can't wait to see the distribution version! I was trying to build a personal site from scratches, but I do have to admit that it is difficult for non-professional programmers to think of everything and profiles like this one is a great help for us (at least, for me...). So thanks in advance ! My post doesn't help for anything... but I just wanted to let you know that I am interested and... happy to use PW ;-)

Wonderful, I should say that every time! The quality of modules here are so high, never seen it elsewhere on CMS land. Think it has to to with the simplicity & the flexibility of the core. This is without doubt beautiful work Soma ! You're on a killing Spree!

Howdy! Just created a module for authenticating via LDAP. It works great for our implementation of LDAP, however I'm sure it may need additional work. Looking for some feedback if there are better ways to implement this or clean up my code a bit. File attached. -Jim

I updated my modules and modules page according to those rules. Hope it helps.

I agree with everything Pete said! Tested out here and worked beautifully. Such an easy way to install modules. Great work Soma! I was actually experimenting with something similar here this morning before work. But my version was limited to pasting in the ZIP file URL and having it install from that. Yours is so much farther along. So let me know what I can do to assist or collaborate here. I agree that it would make sense to have this buit in as a core functionality once stable. A few minor things to mention: 1. It installed under /processwire/modules/modulesmanager/ rather than /processwire/setup/modulesmanager/. So I moved it to Setup. Your instructions mentioned it would install on Setup, so just wanted to mention this in case anyone else tries it and can't find the Modules Manager. 2. Your uninstall function is named "deinstall" rather than "uninstall". As a result, it won't get executed when the module is uninstalled. 3. Rather than using mkdir() and $this->config->chmodDir, you can use the wireMkdir() function if you want to (which pulls from $config->chmodDir on it's own). 4. There are some chmod(0777)s in there. Should this use $config->chmodDir instead? 5. For lines like this (below), I'd suggest comparing the page name rather than the title, just because I can see tweaking headlines, but not changing page names. Though what we'll probably do is just setup the web service to have an option to exclude modules that aren't auto-installable, so that you don't have to perform the check at all. if(in_array('Language Packs',$categories)) continue; if(in_array('Admin Themes',$categories)) continue;

This one's just great, Soma! Had to give it a try straight away. Same goes for site/assets/ as well. Without write permissions downloading the module zip file fails. This actually revealed a bug too, giving this: Error Using $this when not in object context (line 278 of /Users/nik/Sites/test/site/modules/ModulesManager/ModulesManager.module) Looks like you're using $this inside a static method (downloadFile()). Changing $this->error(...) to wire()->error(...) does the trick (don't know if this is the best way, though). There seems to be a few of these actually in the same method. This left me a bit confused at first as there was no new page under "Setup" after installation. But then I found it under "Modules". So, either that's what you intended and just documented it wrong or maybe page with id 21 isn't always "Setup". Either way, something should be fixed here as well . Anyway, good work so far!

I don't like this... I LOVE IT I understand that this is a work in progress, but I think it would make sense if this were eventually merged with the actual modules page in the PW admin once it's tested.

Hi, I'm new here, I'll start by posting in an existing thread ;-) I'm trying to do something similar than the OP, but I can't get it to work : Basically, - I have pages with template "one-category", where each page represent one category - I have pages with template "one-article", which are used for the actual contents. - one of the fields of "one-article" is "article_categories", it is of type "Page", more specifically "Multiple pages (PageArray)". It is used to reference a list of pages of type "one-category" (which means it is used for assigning categories to each article). Now, I want to select, for each existing category pages, the list of the "one-article" pages which are referencing the category. For troubleshooting, I also try to "just" select all the "one-article" pages which are referencing one single category page. here is the code : $the_articles = $pages->find("template=one-article"); // select all existing real pages $the_cat = $pages->get("template=one-category, title='cat1'"); // select one category page $the_list = $the_articles->find("article_categories=$the_cat"); // select real pages referencing the desired category page as a result, - this is working if I have only 1 category referenced in the articles : $the_list->count() returns '1' for the relevant article, and I can use the returned objet - but it (seems to) fail as soon as I add a second category to this article : $the_list->count() now returns '0', while I would expect it to still return '1' any idea ?

I was wondering... Now that the man man from the grim north has extended the image field, can we cache the images?? I could come hande now with all those big image sliders.. Keep it up, Im soon gonna release a lot of stuff.. Bjørn aka ChrisB @ChrisB_dk

Anyhow, to the subject at hand - if you don't want to merge my changes, can you post here and let me know when similar changes have been implemented on your codebase? I'd like to pursue the namespace-conversion, but as mentioned I can't continue from my own branch since your changes would not be identical to mine...

ok, I'm so sorry for wasting your time... it is a really simple setting. my new pages made by inputfield were put under the parent 'tags'.. so in the admin tree, I just needed to click tags > edit > children... then there is a sort setting there. I never knew that setting existed, another win for PW usability. Thanks Ryan~!

Ryan, this, and the whole of PW just reeks of awesomeness! Unfortunately i'm not in a position where i can promote PW in way that would actually matter, so you better set something up so we can contribute in a monetary fashion. You deserve some Euro's coming your way for the pleasure i've had working with PW.

Alright, the first pass for "wire/core" was pretty easy - have a look. This doesn't seem to break anything - fortunately PW doesn't have a million admin-screens, so I clicked through all of them, and everything appears to be working normally. If you'd like, I can send a pull-request? I wonder if I should branch again before starting some of the more "dangerous" work...