Unpack the file eg #unzip FR-3.0-0.rc6 will unpack to /var/www/FR-3.0-0.rc6/
This allows you to play until you 'get it right' as a previous version would be in /var/www/FR-2.8.6, etc.
Set up the database. This involves creating the database and setting up a user/password combination.
FreeRealty only uses MySQL.
Decide whether you want your images in the database or in folders on the
server
There are arguments and preferences for each method.
If you are going to use the folders method I highly suggest you put them either in a "public" folder with proper
permissions or in a non public folder.
By proper permissions I mean, on my server they are in a folder owned by me, in the web server group and
NOT WRITABLE BY ANY OTHER PARTY. Do not set permissions to 666 or 777! I cannot stress this enough. If you
must use the folder method, make sure that it is owned by you and the web server process group ie mine is pat:apache.
Permissions are 665 (user can read write and "execute"or open the folder, the group has the same permissions. Everyone else
can read and "execute" or open the folder but not write to it.) Setting the permissions any looser is asking for trouble.
Sorry if this seems obvious, but there are at least two other scripts (one happens to be a real estate listing script) that
suggest setting permissions to 666 or 777. I am suggesting you lock your scripts down.
Image folders should be set to 664, 665, 774 or 775 to allow uploads.
The current configuration will use the images/listings and images/agents sub directories.
The images folder is relative to your install path to make it easier. The scripts will look for your images in
$install_path/$imageloc/listings and $install_path/$imageloc/agents.
Listing images will be named as image number _ (underscore) filename, so an image named mybighouse.jpg that is the
10th image to be uploaded (the autoincremented image id) will show up as 10_mybighouse.jpg the thumbnail will be
10_thumb_mybighouse.jpg. The database will save the filename as mybighouse.jpg.
Copy common30.sample.php to common.php
Edit common.php, change $user to the name of your database user
Change $password to password of the database user
Change $table_prefix to match any table prefix that is necessary. This is an optional setting and most users will not need to do this
Access install30.php
Enter the database user name from above
Enter the database user password from above
Edit the server name or installation path if necessary
Click Log In, you should see the database commands appear in your browser
Once the installation is done, click the link at the bottom of the page to login to your administration panel
Use the upgrade scripts in /upgrades
Several different scripts are available depending upon which version you are currently running. If you are upgrading from
V 2.6 make sure to run the conversion scripts below for your thumbnail images.
To use the new thumbnail features for previewing the homes you will need to convert the
existing images in the db by running
/upgrades/convert.php
This file modifies the database by pulling images for each listing, creating a thumbnail view
and inserting that back into the database.
/upgrades/convert_agent.php should be run to convert the agent images and add the thumbnails.
Files changed: Nearly every file has had changes, please consult the patch files to
determine whether the changes are trivial for your installation.
To have images saved to folders instead of the database, insert the following configuration items in common.php:
$images_use = "folders";
$imageloc = "images";
Access and run /upgrades/exportimages.php Delete exportimages.php
Unpack the file eg #unzip FR-2.9-pre3.zip will unpack to /var/www/FR-2.9-pre3/
This allows you to play until you 'get it right' as a previous version would be in
/var/www/FR-2.8.6, etc.
Set up the database. This involves creating the database and setting up a user/password
combination.
FreeRealty only uses MySQL.
Decide whether you want to have your images in the web folders or in the database. There are two options: db or folders.
Failing to set either "db" or "folders" in the common.php file will result in the database being used for images.
There are arguments and preferences for each method.
If you are going to use the folders method I highly suggest you put them either in a "public" folder with proper
permissions or in a non public folder.
By proper permissions I mean, on my server they are in a folder owned by me, in the web server group and
NOT WRITABLE BY ANY OTHER PARTY. Do not set permissions to 666 or 777! I cannot stress this enough. If you
must use the folder method, make sure that it is owned by you and the web server process group ie mine is pat:apache.
Permissions are 665 (user can read write and "execute"or open the folder, the group has the same permissions. Everyone else
can read and "execute" or open the folder but not write to it.) Setting the permissions any looser is asking for trouble.
Sorry if this seems obvious, but there are at least two other scripts (one happens to be a real estate listing script) that
suggest setting permissions to 666 or 777. I am suggesting you lock your scripts down.
Image folders should be set to 664, 665, 774 or 775 to allow uploads.
The current configuration will use the images/listings and images/agents sub directories.
The images folder is relative to your install path to make it easier. The scripts will look for your images in
$install_path/$imageloc/listings and $install_path/$imageloc/agents.
Listing images will be named as image number _ (underscore) filename, so an image named mybighouse.jpg that is the
10th image to be uploaded (the autoincremented image id) will show up as 10_mybighouse.jpg the thumbnail will be
10_thumb_mybighouse.jpg. The database will save the filename as mybighouse.jpg.
Copy common.sample.php to common.php or run /install.php
The install script will run and create your common.php if your installation directory is writable.
If you need to set the directory as writable (temporarily) under *nix simply run chmod o+w /<installation directory>
Access install.php
Afterwards remove the world writable setting: chmod o-w /<installation directory>
If you can't run install.php for some reason copy common.sample.php to common.php and edit common.php
Delete upgrades/exportimages.php
Set the user name and password for the database
If you are using a 'sub' database ie your host will only allow you a single MySQL
database, set the $table_prefix variable. This allows you to do multiple installs on the
same database. For instance assume you have a database named web_data, setting the
table_prefix to 'realty' creates the following tables in web_data: realtyhomes,
realtytbl_Files, realtyagents, etc.
Unless you want people to just add agents without your control set $require_admin = 'y'
Edit index.php and content/main.php to give the desired content.
Edit includes/thumbnail.php for the image library you have installed on the server.
By default the GD libraries are set. If you have either the NetPBM or ImageMagick libraries
set the image_style variable to use the other library. (ImageMagick and NetPBM create awesome
looking thumbnails compared to GD1)
(optional)Rename the folder to freerealty or whatever you want(just make sure the
install_path variable is set right in common.php)
You should now be able to upload properties, add agents, etc. by logging into
/admin/admin.php
email me at freerealty (at) rwcinc.net to let me know if you found this script useful
Unfortunately, creating the database is beyond the scope of this
script.
File Name: FR-2.8.5.php
FreeRealty documentation
Welcome to FreeRealty 2.8.5
Beginning with version 2.8.4 additional documentation is being added in an attempt to
make use of this project easier. Several different types of installations will be covered in
this document. Since this is a fork of Jon Roig's version 2.6 OpenRealty
(here) we will first cover installing over the top of
OpenRealty 2.6. If you are starting from scratch you can skip to the
new install instructionsUpgrade from OpenRealty 2.6- assuming a clean 2.6 install
Use the upgradasaurus2.7.php file.
This file upgrades your database from the 2.6 version setting up new tables to make use of
Tom Anderson's feature code. It does this by first inserting the new tables into the current
database, modifying each listing to use the new features, then dropping the old tables.
The features are editable using /admin/adminfeatures.php. It also sets up the tbl_Files for thumbnails as well as agent_tbl_Files.
To use the new thumbnail features for previewing the homes you will need to convert the
existing images in the db by running
/upgrades/convert.php
This file modifies the database by pulling images for each listing, creating a thumbnail view
and inserting that back into the database.
/upgrades/convert_agent.php should be run to convert the agent images and add the thumbnails.
Files changed: Nearly every file has had changes, please consult the patch files to
determine whether the changes are trivial for your installation.
(optional)Rename the folder to freerealty or whatever you want(just make sure the
install_path variable is set right in common.php)
You should now be able to upload properties, add agents, etc. by logging into
/admin/admin.php
email me at freerealty (at) rwcinc.net to let me know if you found this script useful
Unfortunately, creating the database is beyond the scope of this
script.
File Name: FR-2.8.4.php
FreeRealty documentation
Welcome to FreeRealty 2.8.4
Beginning with this version (2.8.4) additional documentation is being added in an attempt to
make use of this project easier. Several different types of installations will be covered in
this document. Since this is a fork of Jon Roig's version 2.6 OpenRealty
(here) we will first cover installing over the top of
OpenRealty 2.6. If you are starting from scratch you can skip to the
new install instructionsUpgrade from OpenRealty 2.6- assuming a clean 2.6 install
Use the upgradasaurus2.7.php file.
This file upgrades your database from the 2.6 version setting up new tables to make use of
Tom Anderson's feature code. It does this by first inserting the new tables into the current
database, modifying each listing to use the new features, then dropping the old tables.
The features are editable using /admin/adminfeatures.php. It also sets up the tbl_Files for thumbnails as well as agent_tbl_Files.
To use the new thumbnail features for previewing the homes you will need to convert the
existing images in the db by running
/admin/convert.php
This file modifies the database by pulling images for each listing, creating a thumbnail view
and inserting that back into the database.
/admin/convert_agent.php should be run to convert the agent images and add the thumbnails.
Note that the thumbnail creation should work 'out of the box'
Files changed: Nearly every file has had changes, please consult the patch files and CHANGELOG to
determine whether the changes are trivial for your installation.