It's still hardcoded (fixed in 1.8), so it doesn't appear in translations.ini. To add it, do the following steps:

[b]1. In file "translations.ini"[/b]

[u]Find:[/u]
[code] recent_jobs = "Most recent job offers"[/code]
[u]Add above:[/u]
[code] spotlight_jobs = "Spotlight Jobs"[/code]

[b]2. In file "_templates/home.tpl"[/b]

[u]Find:[/u]
[code] <h2>Spotlight Jobs</h2>[/code]

[u]Replace with:[/u]
[code] <h2>{$translations.homepage.spotlight_jobs}</h2>[/code]

I've added Prefix support for JB, you can check the changelog for the SVN update to manually update your files. I'm afraid writing an automatic installer would be more work than writing the functionality itself, so you'll have to do the replacing yourself.

In upcoming releases an installer script should take care of creating the tables with their prefix, for now you can use PHPMyAdmin. Go to each table, go to 'Operations' and use the 'Rename table to' functionality.

Except for the config.php adjustment, all other replacements are mostly '.DB_PREFIX.'. Here's the log of changed files:

http://code.google.com/p/jobberbase/source/detail?r=167

Hmm. It would be fairly easy to do, if there was support for a database prefix (you would have 'site1_jobs', site2_jobs' etc. tables). Even though it's fairly simple to write, all the queries in functions.php, class.Job.php and perhaps some other files need to have some code added.

I'll add it to my tasks for 1.8, as well as make a guide for existing users (I'll include an automatic installer for the search/replace). Perhaps I'll get to it today, otherwise should't be long. Good suggestion :)

Thanks Evert, I've updated the post :)

Made a quick fix for it, I'll make sure it'll find it's way into the next release.

[u]1. In file "page_category.php" [/u]

[b]Find:[/b]
[code]$smarty->assign('current_category', $id);[/code]

[b]Add below:[/b]
[code]$smarty->assign('current_category_name', get_categ_name_by_varname($id));[/code]

[u]2. In file "_includes/functions.php" [/u]

[b]Find:[/b]
[code]function get_categ_id_by_varname($var_name)
{
global $db;
$sql = 'SELECT id FROM categories WHERE var_name = "' . $var_name . '"';
$result = $db->query($sql);
$row = $result->fetch_assoc();
return $row['id'];
}[/code]

[b]Add below:[/b]
[code]function get_categ_name_by_varname($var_name)
{
global $db;
$sql = 'SELECT name FROM categories WHERE var_name = "' . $var_name . '"';
$result = $db->query($sql);
$row = $result->fetch_assoc();
return $row['name'];
}[/code]

[u]3. In file "_templates/category.tpl"[/u]

[b]Find:[/b]
[code]{$translations.category.jobs_for} {$current_category}[/code]

[b]Replace with:[/b]
[code]{$tra …

Will do, but I'll wait for some people to have it running, to make sure it's bug-free :)

I've released the source at: http://chronoscripts.com/search-rewritten-for-pagination/. Please try it out and let me know if any bugs appear!

Fixed the bug. While it's possible to make it search within a category, I'm not sure if it's clear to the user.. an extra 'advanced search' option might be better?

It depends on how advanced you want it to be. PhpBB is probably the most popular and advanced free solution (plenty of mods etc.), but only really useful if you expect heavy forum usage.

FluxBB is a good light-weight solution, though some would probably prefer to have a BB code editor. Some alternatives are found here: [url=http://webtecker.com/2008/05/02/8-popular-open-source-forums/]http://webtecker.com/2008/05/02/8-popular-open-source-forums/[/url]

You're sure you replaced the image? Perhaps the old version is still loaded from the cache, try a ctrl-f5?

You'll have to edit (or replace) the file '/img/bg-box.png' in a photo-editing program. As no source files for JB images are available, the easiest way is to replace it with an image of the same size I guess.

Another option is to edit the "div#box" in the css file.

That's the translation.ini loaded in javascript. Without it you wouldn't be able to set translations for messages inside JavaScript functions (you'd have to edit the .js files instead).

It doesn't do much good for SEO I'm afraid, it would be better to only load the translations that are actually used in JS files.