I have used PMC in the past with no problems.

On a new system using Acquia Drupal, I installed PMC and Elysia Cron.

I enabled Elysia Cron, decided I was too lazy to setup cron on my server, disabled it, and enabled PMC, at the same time.

PMC does not show up in the Site Config menu. I disabled PMC and re enabled it. No joy. Upgraded to V2.1 and still no workee.

Very strange...

Comments

dave reid’s picture

Status: Active » Fixed

You forgot to read the README.txt:

Once the module is enabled, you can configure the module at:
Administer > Site configuration > Site information

druplicate’s picture

Hmmm,

This isn't the way previous versions of PMC worked. I watched this video (http://gotdrupal.com/videos/setting-up-drupal-cron) and was also remembering how I set up PMC the last time I installed Drupal.

If it were up to me README files would be banned! It would be better to have a link or a notice somewhere prominent that something important has changed, like on the module enabling page, so that when someone goes to enable a module it's obvious. At least put a link on the project page to some kind of doc even if it's just the README. Some module maintainers do this, but consistency is poor. Drupal ought to have more rigid requirements for docs and other stuff like this.

What happened to the other controls like retry interval and logging? Are they no longer necessary?

If I enable other CRON modules like Elysia Cron, I presume they will work with PMC, yes?

Sorry for the minor rant - not condemning, just frustrated. It's just not that hard to do proper docs. I don't understand why Drupal doesn't use a wiki for docs. I had a major rant-counter rant with Earl Miles once about this and it touched a nerve apparently. He likes users to write docs, but where do we submit them for peer review? There's no proper place for it and it just begs for a wiki.

The Advanced Help module sounds like a good idea for example, but in fact it's lacking. Documentation changes all the time and should be up to date and editable by users. Developers want the users to write docs anyway, so give us the convenient tools to do so. The little "?" marks that trigger AH should bring you to a wiki not some canned and out of date help section that users cannot contribute to or edit conveniently. Some docs in fact can be quite lengthy with follow on discussion that simply would not fit or work well with the current concept of AH. AH is useful for short, concrete instructions, at best, but that's just basic "help". "Advanced" should connote an extensive wiki implementation, IMHO.

Just my 2 cents, and thank you for pointing me to the README...

Great module - saves a bit of annoying server config!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.