jobberbase - Project Hosting on Google Code

Last 7 days Dec 14, 2009 r389 (changed: if the sidebar shows cities, allow to set the minim...) committed by putypuruty - changed: if the sidebar shows cities, allow to set the minimum number of jobs that a city must have in order to appear in the list - inspired by http://www.jobberbase.com/forum/topic2081-help- with-a-function.html changed: if the sidebar shows cities, allow to set the minimum number of jobs that a city must have in order to appear in the list - inspired by http://www.jobberbase.com/forum/topic2081-help- with-a-function.html Dec 14, 2009 r388 (fixed: the number of applicants was no longer shown (a line ...) committed by putypuruty - fixed: the number of applicants was no longer shown (a line of code was deleted with the last refactoring) fixed: the number of applicants was no longer shown (a line of code was deleted with the last refactoring) Last 30 days Dec 06, 2009 r387 (Removed unused, combined some css and sorted properties alph...) committed by evertsemeijn - Removed unused, combined some css and sorted properties alphabetically Removed unused, combined some css and sorted properties alphabetically Nov 28, 2009 r386 (moved 'Report fake ad' related configs to the end of the set...) committed by putypuruty - moved 'Report fake ad' related configs to the end of the settings list to allow for easier DB upgrade moved 'Report fake ad' related configs to the end of the settings list to allow for easier DB upgrade Nov 24, 2009 issue 21 (Textile Replacement) commented on by navjotjs...@gmail.com - Integrated CKEditor at all places where TinyMCE/Textile resided. IE 7 Bug still resides. Will need to test it more. May not be possible in v1.9. Separate branch containing CKEditor version of jobberBase will be committed in next 24 hours. Please test it. Integrated CKEditor at all places where TinyMCE/Textile resided. IE 7 Bug still resides. Will need to test it more. May not be possible in v1.9. Separate branch containing CKEditor version of jobberBase will be committed in next 24 hours. Please test it. Nov 24, 2009 issue 10 (Installer ) commented on by navjotjs...@gmail.com - Upgrading shouldn't be tough if we create a separate upgrade routine to be run after install if db does not match the new version. We need to introduce a new DB version variable. This way, it can perform upgrades easily. Updgrade file will check the current version of the install, match it whether upgrade is possible and then only update db settings. It should notify users that template changes need to be done manually. DB Change info can be stored somewhere so it knows what changes to perform when upgrading from let's say v1.9 to v2.0. Or use diff set of files for each type of upgrade just like vbulletin does. Upgrading shouldn't be tough if we create a separate upgrade routine to be run after install if db does not match the new version. We need to introduce a new DB version variable. This way, it can perform upgrades easily. Updgrade file will check the current version of the install, match it whether upgrade is possible and then only update db settings. It should notify users that template changes need to be done manually. DB Change info can be stored somewhere so it knows what changes to perform when upgrading from let's say v1.9 to v2.0. Or use diff set of files for each type of upgrade just like vbulletin does. Earlier this year Nov 12, 2009 r385 (Deleting unused images from Admin Image directory.) committed by navjotjs...@gmail.com - Deleting unused images from Admin Image directory. Deleting unused images from Admin Image directory. Nov 12, 2009 r384 (Completing last commit...oops.) committed by navjotjs...@gmail.com - Completing last commit...oops. Completing last commit...oops. Nov 12, 2009 r383 (Moving hardcoded text to translations file.) committed by navjotjs...@gmail.com - Moving hardcoded text to translations file. Moving hardcoded text to translations file. Nov 12, 2009 r382 (TinyMCE Upgraded to 3.2.7.) committed by navjotjs...@gmail.com - TinyMCE Upgraded to 3.2.7. TinyMCE Upgraded to 3.2.7. Nov 12, 2009 r381 (Preparing TinyMCE for Upgrade.) committed by navjotjs...@gmail.com - Preparing TinyMCE for Upgrade. Preparing TinyMCE for Upgrade. Nov 12, 2009 r380 (Fix API Jobs problem - 0 to show all jobs here.) committed by navjotjs...@gmail.com - Fix API Jobs problem - 0 to show all jobs here. Fix API Jobs problem - 0 to show all jobs here. Nov 12, 2009 r379 (Remove unused Images from frontend.) committed by navjotjs...@gmail.com - Remove unused Images from frontend. Remove unused Images from frontend. Nov 11, 2009 r378 (Making Admin directory completely independent of template di...) committed by navjotjs...@gmail.com - Making Admin directory completely independent of template directory regarding image paths. Making Admin directory completely independent of template directory regarding image paths. Nov 11, 2009 r377 (Fixed the Error when using 0 will display all jobs instead o...) committed by navjotjs...@gmail.com - Fixed the Error when using 0 will display all jobs instead of none. pointed to correct path of config.php in api.php Fixed the Error when using 0 will display all jobs instead of none. pointed to correct path of config.php in api.php Nov 10, 2009 Themes (List of Themes Available Publicly for Jobberbase.) Wiki page edited by myredjumpsuit - Revision r376 Edited wiki page through web user interface. Revision r376 Edited wiki page through web user interface. Nov 08, 2009 Themes (List of Themes Available Publicly for Jobberbase.) Wiki page commented on by susanu.liviu - Name: Jobswhite Version Jobberbase: 1.8 Link: http://code.google.com/p/jobswhite/ License: Free, under Creative Commons BY SA Thank you:) Name: Jobswhite Version Jobberbase: 1.8 Link: http://code.google.com/p/jobswhite/ License: Free, under Creative Commons BY SA Thank you:) Nov 04, 2009 r375 ([BUG FIX] Most Applied Jobs on Homepage being set to 0 does ...) committed by navjotjs...@gmail.com - [BUG FIX] Most Applied Jobs on Homepage being set to 0 does not work. http://bit.ly/agHia [BUG FIX] Most Applied Jobs on Homepage being set to 0 does not work. http://bit.ly/agHia Nov 04, 2009 r374 (Modifying Captcha Settings Page to become a Common Spam Sett...) committed by navjotjs...@gmail.com - Modifying Captcha Settings Page to become a Common Spam Settings Page with 2 new additions. Modifying Captcha Settings Page to become a Common Spam Settings Page with 2 new additions. Nov 02, 2009 r373 (changed: use the new translator utility class for the seo_ti...) committed by putypuruty - changed: use the new translator utility class for the seo_title changed: use the new translator utility class for the seo_title Nov 02, 2009 r372 (refactored: outsourced the translation logic into its own cl...) committed by putypuruty - refactored: outsourced the translation logic into its own class new: the messages in the translations file now support placeholders which are replaced at translation time refactored: outsourced the translation logic into its own class new: the messages in the translations file now support placeholders which are replaced at translation time Nov 02, 2009 r371 (seo improvement: the details page for any job inside a categ...) committed by putypuruty - seo improvement: the details page for any job inside a category had the same text for meta description and keywords seo improvement: the details page for any job inside a category had the same text for meta description and keywords Nov 02, 2009 r370 (cleanup: removed unused CSS code) committed by putypuruty - cleanup: removed unused CSS code cleanup: removed unused CSS code Oct 30, 2009 r369 (Fixing Image Url errors in Admin Area.) committed by navjotjs...@gmail.com - Fixing Image Url errors in Admin Area. Fixing Image Url errors in Admin Area. Oct 30, 2009 issue 22 ( r361 view all jobs) changed by navjotjs...@gmail.com - This has been completed by putypuruty even before you reported. Now all Jobs will be listed at yourjobboard.com/jobs/. Status: Fixed Owner: putypuruty This has been completed by putypuruty even before you reported. Now all Jobs will be listed at yourjobboard.com/jobs/. Status: Fixed Owner: putypuruty Oct 30, 2009 r368 (Category Names in Feed Description instead of urls.) committed by navjotjs...@gmail.com - Category Names in Feed Description instead of urls. Category Names in Feed Description instead of urls. Oct 24, 2009 r367 (cleanup: removed unused CSS code in the backend) committed by putypuruty - cleanup: removed unused CSS code in the backend cleanup: removed unused CSS code in the backend Oct 24, 2009 r366 (code cleanup, made it more readable) committed by putypuruty - code cleanup, made it more readable code cleanup, made it more readable Oct 24, 2009 r365 (enh: the apply online text is now inside a label; don't show...) committed by putypuruty - enh: the apply online text is now inside a label; don't show a border for the apply online checkbox enh: the apply online text is now inside a label; don't show a border for the apply online checkbox Oct 21, 2009 issue 4 (404 pages should use 404 code and not use a redirect) commented on by adefoor - Thanks for your response and discussion. I think the better solution for SEO, which is what snkeatr suggested, is to do a 301 redirect on jobs that no longer exist to the category page and on the that page displaying a message that says "The job you are trying to find no longer exists here are jobs that are similar" and then displaying jobs in that category. Anthony www.fullmedia.com Thanks for your response and discussion. I think the better solution for SEO, which is what snkeatr suggested, is to do a 301 redirect on jobs that no longer exist to the category page and on the that page displaying a message that says "The job you are trying to find no longer exists here are jobs that are similar" and then displaying jobs in that category. Anthony www.fullmedia.com Oct 21, 2009 issue 4 (404 pages should use 404 code and not use a redirect) commented on by navjotjs...@gmail.com - Well the 404 page only sends correct header - its not that we are directing a user to a dead link. So still he gets the link juice. If you customise the 404 page, you can take the user to anywhere you want from that 404 page. Its just that user should know that he landed up on a error page. Well the 404 page only sends correct header - its not that we are directing a user to a dead link. So still he gets the link juice. If you customise the 404 page, you can take the user to anywhere you want from that 404 page. Its just that user should know that he landed up on a error page. Oct 21, 2009 issue 4 (404 pages should use 404 code and not use a redirect) commented on by adefoor - I think what snkeatr is saying is an important feature that I would like to see in jobberbase to make it more usable. As an seo firm, we would like to utilize the job board to help get links for our client as well as it's other uses. Anthony www.fullmedia.com I think what snkeatr is saying is an important feature that I would like to see in jobberbase to make it more usable. As an seo firm, we would like to utilize the job board to help get links for our client as well as it's other uses. Anthony www.fullmedia.com Oct 21, 2009 r364 (fixed: use the correct i18n label for the RSS image readabil...) committed by putypuruty - fixed: use the correct i18n label for the RSS image readability: fixed code indentation fixed: use the correct i18n label for the RSS image readability: fixed code indentation Oct 21, 2009 issue 22 ( r361 view all jobs) reported by AlenStimec - What steps will reproduce the problem? 1. 2. 3. What is the expected output? What do you see instead? What version of the product are you using? On what operating system? Please provide any additional information below. is it now easyer to add a link to "jobberbase/jobs/all" What steps will reproduce the problem? 1. 2. 3. What is the expected output? What do you see instead? What version of the product are you using? On what operating system? Please provide any additional information below. is it now easyer to add a link to "jobberbase/jobs/all" Oct 21, 2009 r363 (cleanup: the bottom part of the "post a job" image still had...) committed by putypuruty - cleanup: the bottom part of the "post a job" image still had a few pixels from the old jobber background (more obvious on hover) cleanup: the bottom part of the "post a job" image still had a few pixels from the old jobber background (more obvious on hover) Oct 21, 2009 r362 (cleanup: removed unused CSS code in the frontend) committed by putypuruty - cleanup: removed unused CSS code in the frontend cleanup: removed unused CSS code in the frontend Oct 08, 2009 issue 4 (404 pages should use 404 code and not use a redirect) Status changed by navjotjs...@gmail.com - I am opening this issue...want to hear other people opinion on this. Status: Accepted I am opening this issue...want to hear other people opinion on this. Status: Accepted Oct 08, 2009 issue 4 (404 pages should use 404 code and not use a redirect) commented on by navjotjs...@gmail.com - If you want you can edit error page template and add suggested links to browse the site. Redirecting to category home without any message may confuse the visitor as he may not even know that url is dead and he may form an opinion that job board is acting weird. If you want you can edit error page template and add suggested links to browse the site. Redirecting to category home without any message may confuse the visitor as he may not even know that url is dead and he may form an opinion that job board is acting weird. Oct 08, 2009 issue 4 (404 pages should use 404 code and not use a redirect) Labels changed by snkeatr - Hi guys, I saw this and had to comment, 404 is correct for letting the search engines know that a job has been deleted or expired. However for SEO reasons there is a better way to do this. By using a 404 you lose all link juice that job may have picked up. If you are like me, your jobs are fed into twitter, friendfeed, identi.ca, and such picking up back links immediately. Instead of a 404, we should 301 permanent redirect to the job's category home page. This will require a simple query to determine it's origin. This should be implemented with a flag set to let the user know the job has expired when they surf in, a simple if statement on the category landing page. This allows the category pages to accumulate link juice from expired jobs. instead of just throwing them in the trash with a 302(current method) or 404 like is suggested Labels: Type-Enhancement Priority-High −Type-Defect −Priority-Medium Hi guys, I saw this and had to comment, 404 is correct for letting the search engines know that a job has been deleted or expired. However for SEO reasons there is a better way to do this. By using a 404 you lose all link juice that job may have picked up. If you are like me, your jobs are fed into twitter, friendfeed, identi.ca, and such picking up back links immediately. Instead of a 404, we should 301 permanent redirect to the job's category home page. This will require a simple query to determine it's origin. This should be implemented with a flag set to let the user know the job has expired when they surf in, a simple if statement on the category landing page. This allows the category pages to accumulate link juice from expired jobs. instead of just throwing them in the trash with a 302(current method) or 404 like is suggested Labels: Type-Enhancement Priority-High −Type-Defect −Priority-Medium Oct 07, 2009 r361 (+ enh: added "View all" link on home page which allows to br...) committed by putypuruty - + enh: added "View all" link on home page which allows to browse all jobs (available at /jobs/) + refactored: jobs-list.tpl now contains the markup for the list of jobs (before this, the markup was duplicated in multiple files) + enh: added "View all" link on home page which allows to browse all jobs (available at /jobs/) + refactored: jobs-list.tpl now contains the markup for the list of jobs (before this, the markup was duplicated in multiple files) Oct 05, 2009 issue 4 (404 pages should use 404 code and not use a redirect) Status changed by navjotjs...@gmail.com - Fixed in r360 Status: Fixed Fixed in r360 Status: Fixed Oct 05, 2009 r360 (Error Page now returns 404 header correctly fixes issue 4) committed by navjotjs...@gmail.com - Error Page now returns 404 header correctly fixes issue 4 Error Page now returns 404 header correctly fixes issue 4 Sep 27, 2009 r359 (minor cleanup, category related optimizations) committed by putypuruty - minor cleanup, category related optimizations minor cleanup, category related optimizations Sep 27, 2009 r358 (enh: call the new GetPaginatedJobsForCity method for paginat...) committed by putypuruty - enh: call the new GetPaginatedJobsForCity method for pagination enh: call the new GetPaginatedJobsForCity method for pagination Sep 27, 2009 r357 (+ refactored the code that is called when clicking on a job ...) committed by putypuruty - + refactored the code that is called when clicking on a job category => easier to read and understand + refactored the code that is called when clicking on a job category => easier to read and understand Sep 27, 2009 r356 (added the THEME variable to Smarty's context (this makes it ...) committed by putypuruty - added the THEME variable to Smarty's context (this makes it available in the template files) added the THEME variable to Smarty's context (this makes it available in the template files) Sep 27, 2009 r355 (enh: allow admin to filter jobs by type) committed by putypuruty - enh: allow admin to filter jobs by type enh: allow admin to filter jobs by type Sep 27, 2009 r354 (removed RSS feed related code for admin because it's never u...) committed by putypuruty - removed RSS feed related code for admin because it's never used removed RSS feed related code for admin because it's never used Sep 27, 2009 r353 (removed the get_seo_XXX methods, added methods for getting a...) committed by putypuruty - removed the get_seo_XXX methods, added methods for getting a category by id or var_name removed the get_seo_XXX methods, added methods for getting a category by id or var_name Sep 27, 2009 r352 (+ have split the GetJobsPaginate method into 2 methods: GetP...) committed by putypuruty - + have split the GetJobsPaginate method into 2 methods: GetPaginatedJobsForCategory and GetPaginatedJobsForCity + removed IsValidCategory, GetCategVarname methods + have split the GetJobsPaginate method into 2 methods: GetPaginatedJobsForCategory and GetPaginatedJobsForCity + removed IsValidCategory, GetCategVarname methods

issue 4 (404 pages should use 404 code and not use a redirect) Labels changed by snkeatr - Hi guys, I saw this and had to comment, 404 is correct for letting the search engines know that a job has been deleted or expired. However for SEO reasons there is a better way to do this. By using a 404 you lose all link juice that job may have picked up. If you are like me, your jobs are fed into twitter, friendfeed, identi.ca, and such picking up back links immediately. Instead of a 404, we should 301 permanent redirect to the job's category home page. This will require a simple query to determine it's origin. This should be implemented with a flag set to let the user know the job has expired when they surf in, a simple if statement on the category landing page. This allows the category pages to accumulate link juice from expired jobs. instead of just throwing them in the trash with a 302(current method) or 404 like is suggested

Labels: Type-Enhancement Priority-High −Type-Defect −Priority-Medium

Hi guys, I saw this and had to comment, 404 is correct for letting the search engines know that a job has been deleted or expired. However for SEO reasons there is a better way to do this. By using a 404 you lose all link juice that job may have picked up. If you are like me, your jobs are fed into twitter, friendfeed, identi.ca, and such picking up back links immediately. Instead of a 404, we should 301 permanent redirect to the job's category home page. This will require a simple query to determine it's origin. This should be implemented with a flag set to let the user know the job has expired when they surf in, a simple if statement on the category landing page. This allows the category pages to accumulate link juice from expired jobs. instead of just throwing them in the trash with a 302(current method) or 404 like is suggested

Labels: Type-Enhancement Priority-High −Type-Defect −Priority-Medium

Last 7 days

Last 30 days

Earlier this year