I just found this link on digg: osjobber.com.
It seems they have taken jobberBase, replaced most (not even all!) of the references to jobber/jobberBase/myself and launched it as osjobber.

How pathetic is that!?

Later update, half a year later:
It seems that osjobber now has an entirely different app, so thank you to them for not assuming rights on jobberBase, anymore, and good luck!

Hey, guys,
If you’ve tested jobberBase, you’ve probably found out by now that there are some issues with the search functionality.

If anyone has fixed some of the problems and wishes to contribute to the project, you are most welcome and will receive eternal gratitude and recognition .

Enjoy!

Wow, it’s great to see that there’ve been 2.000 downloads of jobberBase!

If you have any feedback, please don’t hesitate to bring it on .

Hey all, I’ve just released a new version which includes pagination support for job categories. I had this planned for a while, now, but thanks to Adrian Rusu-Scurtu’s help, I was able to finally implement it .

Go out and download jobberBase 1.2 now.

I want to thank everybody that reported bugs, suggested features and provided fixes on the community forum!

There are still a lot of stuff to be improved, but I decided to release version 1.1, a bug-fix/clean-up version, mostly.

Here’s the changelog:

• Modified the directory structure and moved the entire application into /app subdirectory.
• Added an alternate .htaccess that seems to work better on some big hosting companies.
• Cleaned up config.php of unnecessarry defines.
• Fixed a number of bugs reported on www.jobberbase.com/community/ (thanks to everyone!)

Hope you enjoy jobberBase and hope you put it to good use!

Download latest version

As of today, I’ve added a PayPal Donate button on this blog’s sidebar.

I’m very happy that jobberBase has started to help people with their projects. If you’re successfully using jobberBase, would you consider making a small donation?

In the root directory of jobberBase, there’s a cron_maintenance.php script that you should run with cron (or Task Scheduler, on Windows). On jobber.ro, I have that script running every night.

Default maintenance

For now, what the maintenance script does is delete temporary and inactive job ads.

What else can you do

The standard job-board behavior is to allow an ad to be active for a number of days (30, for most of them). If you wish to implement this in your jobberBase-based site, you could use the cron_maintenance.php to deactivate older ads and/or notify publishers with 2-3 days before this deactivation…

I’m guessing that an OPTIMIZE TABLE jobs; would also be useful, from time to time .

I invite everyone to visit the community forum. It’s still pretty empty, but we’ll start adding content.

The forum has 3 main purposes:

1. Bug tracking.
2. Allow feature requests from users.
3. List projects that use jobberBase.

Have a great day, everyone!

It’s been a great first week and I’m really happy to announce that jobberBase was already downloaded over 500 times. I would have been happy even with 30 downloads, so 500 is simply amazing!

I’m also very grateful to all the people who talked on their blogs about jobberBase. Some of my friends, especially, have been very supportive of this project and I’m thankful for that!

Next steps

During the next few days, I have the following priorities:

• Get jobberBase on a Subversion repository and grant some people (who have already contributed to the project) write access.
• Install Vanilla as a means of communication and bug-tracking. I chose Vanilla for its simplicity… in the current stage of the project, the simplest solution is the best .

P.S. I promise to keep adding stuff to the Knowledge Base!

Would you like to contribute to jobberBase and have your improvements included with the original distribution? Here are a few items that could be improved (list under-construction):

1. Create an admin panel to manage all job posts.
2. Rewrite the classes that generate RSS feeds. Current implementation is an old legacy and it looks terrible (start from class.Feed.php).
3. Fix IE bugs (JavaScript, mostly).
4. Implement a multi-language system, with all the strings in language files.
5. Other?