I can post one later. One biggie is the emulated cron job doesn't always run automatically.

Can you describe, briefly, how is the emulated cron meant to work ?

Similar to the built-in system, it shows a 1x1 image (or an error icon if the cron fails) that checks the mail in the background. A global plugin checks to see when the last checkmail was, and if it was a certain time ago, it'll show the image.

Actually, is the only reason you do you own cron because you can't set more than four options in the minutes (or six in vb 3.6) ? - because the cron system itself can do as many as you want (you could run every two minutes if you want) - that 4/6 is only a limitation of the ACP inteface screen.

I'm sort of leaning on an option with vBulletin to have cron-based, cron jobs. It would make things so much easier, as most servers support cron jobs.

Wow I would love to see someone make this stable...

That, and it was dying for seeminly no reason when run as a scheduled task. It would run just fine manually in the admin CP container for it, but it would just never run on its own for some reason.

But if you (all) want to convert it back to the scheduled task system, go right ahead; you're probably more experienced with the behavior in question.

Not all do, though, including IIS and crappy hosts who don't expose the functionality to their users. As a bit of nostalgia, the 2.3.x version of vBMS actually did require Unix cron jobs, mainly because there was no standardized alternative at the time.

Here's also what's new in this version over the one featured on the product home page. This page was intended to go live alongside a stable version, so it's not an official page. All the features listed on the page are in this version, and I believe all of the ones in the screenshot work.

http://www.intertubes.org/vbms-vb3-21/index.php

...which brings up a huge feature: the permissions system. It looks daunting in the code, but it's actually very simple, and even better, easily extensible. We can get to that when the time comes...and the permission system doesn't have any bugs that I recall for now.

Obviously, ignore all the ordering information on that page.

Rock on Filburt :)

The usual reason for that is that people forget that cron jobs are run by any random user (or guest) - so they won't have the same permissions as you running the code manually.