Uploading Files
To upload the files to your webserver, you can use any FTP client, as long as it allows you to chmod files. We suggest the free and open source FileZilla FTP client.
After you've logged on to your webserver, you should create a new folder where you want your weblog to be. Upload all the files in your local folder to this folder.
TIP
If your website is something like www.example.com, and you want your weblog to be at that location, you should not create a new folder, but instead upload all your files to your website's root folder. Usually this folder is called htdocs, www, or html.
After uploading the files, it should look something like the image below. In the example below you can see that the files were uploaded to a newly made folder called weblog, so this fictional weblog would be at www.pivotlog.net/weblog/.
File Permissions
After uploading we need to change the file permissions on some of the files. This is usually called 'chmodding the files' or 'chmod' for short. We have to do this, so Pivot will be able to write to these files and folders. (Not much use for weblog software if you're not going to make any webpages with it..)
You should chmod the following files and folders. Note that we have used weblog in this example, assuming that you've uploaded the files to a subfolder named weblog. If you've uploaded to html, www, htdocs or something entirely else, just substitute weblog for the name you picked.
| Files and/or Folders | CHMOD |
|---|---|
weblog | → 777 |
weblog/archives | → 777 |
weblog/images | → 777 |
weblog/pivot/db | → 777 |
weblog/pivot/templates | → 777 |
weblog/pivot/pv_cfg_settings.php | → 777 |
weblog/pivot/pv_cfg_weblogs.php | → 777 |
weblog/pivot/db/(all files and folders) | → 777 |
weblog/pivot/db/standard-00000/ (all files and folders) | → 777 |
weblog/pivot/templates/ (all files and folders) | → 777 |
You can do this in most FTP clients by selecting one or more files, right-clicking on them, and choosing the 'chmod' or 'properties' option in the context menu.
TIPS
- Usually you can just select all files, and change the rights for all of them at once.
- Not all webservers allow you to chmod files. In those cases - usually microsoft IIS servers - it's not necessary to chmod the files, so you can just skip this section. If you are not sure about what type of server you have, you can contact your hosting provider for details. He/She will also be able to tell you whether chmodding is necessary or not.
- On some servers, chmodding files and folders to 777 will result in an HTTP 500 - Internal server error message in your browser. If you encounter any of those, you could try chmodding above file to 755 instead.
- By default some systems may set newly created directories to 644 particularly if unzipping is done from the command line (depending on the value of umask). The includes, langs, modules, pics and theme directories (and any subdirectories they contain) may need to be set to 755. Or you can umask 022 before unzipping.
We're almost done now..
Next: Administrator Account.
Prev: Getting the Files
| Special thanks to our platinum sponsors: Gambling News |  |