I should start at the beginning and mention that when I installed PM and enabled it, I got the error "Could not create directory /var/www/[domain name of host]/[subdomain that I use]/http//sites/all/themes". I did not yet have the folder "themes" in "sites/all" (my installation uses the "sites/default" folder), but I have seen references to it before and figured that maybe I should just make it myself. So I did. I disabled and enabled PM, and got no error messages. Whether this means anything good, I don't know.
Next, I tried to search for modules to install (this is how you update existing modules, too?). The Modules page presents categories, but clicking any of them, "Import/Export" for example, brings me to the Site Building section of Administration, even though the address is "admin/build/plugin_manager/modules/Import_export". Does this mean PM never installed properly from the start?
Searching does not work at all. The first time I searched, I got these three messages in this order (this is from memory, not verbatim):
Repository is old or out of date.
Repository is old or out of date.
Repository has been updated.
I didn't know what else to do, so I hit Queue for Installation and one message went away (or, put another way, I got the other two messages again). I hit it again and the other one or two messages went away. But nothing else happened, which makes sense since I was probably supposed to be seeing modules that could be selected before hitting that button.
The server my friendly acquaintance is letting me use runs PHP 5, that's all I know about it.
Comments
Comment #1
Anonymous (not verified) commentedI believe the most recent development snapshot should fix that. (At least I certainly hope that it does. :P)
Comment #2
jabapyth commenteddang. sorry about that. -- ill try and fix this right away
Comment #3
Iritscen commentedI installed the dev build and it gives me a much improved search page for finding modules... but it doesn't do anything. It does say it's a prototype; is it not supposed to be functional yet?
Comment #4
jabapyth commentedsorry -- it was a small bug that has been fixed. the search page now works
Comment #5
Anonymous (not verified) commentedActually, I've removed and reinstalled the cvs version. It still isn't working here.
Comment #6
Anonymous (not verified) commentedAnother typo was keeping it from working. The CVS copy now should be working.
Comment #7
Anonymous (not verified) commentedThe dev build now works.
Comment #8
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.