Phpgooglestorelocator Changes
Needed: script changes (extension of functionality)
Script: phpGoogleStoreLocator (standalone version 2)
Demo: http://crystaldawn.net/modules/phpGoogleStoreLocator/
Info & download: http://crystaldawn.net/
For this project i need modifications to be made to the script so it fit’s my needs.
Programmer must be very experienced with good references..
The script already provides option to pass search vars as get variables in urls string instead of post vars with the form (with the “use_url=on” switch).
(by calling it like: index.php?use_url=on&zipcode=4811ks&street=&city=&state=&country=nl&radius=25)
The actual changes i need (project is divided in 3 steps):
————————————————————————————
1 – Implement a paging class for the search results..
2 – Add extra database field called searchtext (longtext), then add this field to the front end search form and admin forms.
3 – Add extra switch to script search function: “fulltext=on” (triggered by search form or url input)
This switch should trigger a modified search function that is basically the same as default search function as seen on:
http://crystaldawn.net/modules/phpGoogleStoreLocator/
But extended with a fulltext search on the ‘company name’, ‘categories’ and ‘searchtext’ database fields..
Without using the “fulltext=on” switch the script should work as it does out of the box.
So make sure that the script keeps functioning as it does, and that extra functionality of fulltext search is available but optional to be used by the “fulltext=on” trigger.
While working with you on this project some more requirements from our side may occur.
For new changes we will discuss and arrange a price. But first we need to finish project as described above..
Guidelines and documentation of coding / changes
————————————————————————————
Changes must be separated from original code as much as possible by using a custom include file that holds the new classes and functions.
The project must be documented as good as possible. I require the following documentation:
-Separate text document that describes what is changed in what file and line number. Similar as how most oscommerce contributions are formulated and explained.
-In the changed original files i want comments saying: change date / change purpose / programmer name
-Also, when code is changed in original files, i want the original code not to be removed, but kept for reference while being put between comment tags.
I will send you an example of documented and changed code the way i like it.
Payment terms:
Project is split into 3 steps as seen above.
I will pay upfront for each step.
On start I pay for step 1 upfront.
-If you’re ready, I test and if necessary you debug.
If step is 100% finished I pay for step 2, then you start working on step 2.
and so on…..
