spacer

spacer
Home About Demo Download Hosting Extend Docs Forums

b2evo Manual

  • Main / TOC
  • Install/Upgrade
  • Getting Started
  • The Backoffice
  • Customize/Extend
  • Advanced uses
  • Administration
  • Contributing

Special pages

  • Categories
  • Recent changes
  • Help

Toolbox

  • What links here
  • Related changes
  • Special pages
  • Printable version
spacer
Personal tools
  • Log in
Views
  • Page
  • Discussion
  • Edit
  • History

Install b2evolution

From b2evolution manual

Jump to: navigation, search

This manual page is outdated. NEW PAGE: Install b2evolution in b2evolution v5+.

Please note that the install instructions are included with every release ZIP file. This page is here for reference. Please refer to the index.html file included in the ZIP file you downloaded.


Contents

  • 1 Pre-Installation
  • 2 Installing b2evolution
  • 3 After Installation
    • 3.1 Activate .htaccess files
    • 3.2 File Permissions
    • 3.3 Be Careful about Blank Lines

[edit] Pre-Installation

Before you begin installation, make sure you have the following:

  • A web host that can properly support a b2evolution installation System requirements. In a nutshell, you need the following:
    • PHP version 4.3 or above
    • mySQL version 4.1 or above
  • The ability to create and use a MySQL database on your web hosting server. If needed, you can install b2evolution in an already existing database and put several b2evolution installations into a single database.

[edit] Installing b2evolution

  1. On your web server/host, create an empty database for b2evolution. You can name this database as you choose. Creating the database is not done through b2evolution, but through your web host or through a program like phpMyAdmin or cPanel. It will be required later in the installation, that you type in the name of your database, as well as the user name and password you choose so that b2evolution can actually use your database to store data.
  2. Next, upload the b2evolution files to your server using an FTP program. You need to make sure that all the files in the /blogs directory and all the /blogs sub-directories are copied to the server. The /blogs and /blogs sub-directory files are the only essential files at this time, however, you may upload the entire package if you wish. (Note: Some hosts can install the b2evolution files for you.)
    • Keep in mind that the location of the /blogs directory files will become the base URL of your blog. For example, if you install the /blogs directory files to the /weblog directory of your site, then your URL will be www.yoursite.com/weblog. If you install the /blogs directory files in your root directory, your web log will be at www.yoursite.com/.
  3. Once you've uploaded all the files, you can set the permissions of certain key files using your ftp software. Assuming your b2evo is installed under /blogs, here's what you would need to change:
    • chmod 666 /blogs/conf/_basic_config.php (_config.php before version 1.8) - if you want the installer to be able to automatically update your config based on your input.
    • chmod 777 /blogs - to allow creation of blog stub files from the admin interface or to generate static pages for your blogs.
    • chmod 777 /blogs/media - in order to upload images and other media from b2evo's backoffice.
    • mkdir /blogs/media/blogs and then chmod 777 /blogs/media/blogs - to allow uploading files.
    • chmod 666 /blogs/skins/custom/*.* - if you want to use the template editor for the custom skin (you want to make sure the 'img' directory retains permissions of 755).
      For more information on directory and file permissions and a list of which reported FTP clients work or struggle to work, you can go here.
  4. The next step is to run the built-in installer, which will finalize your settings. You can run the installer by typing in your blogs address and adding /install to the end of it. For example, www.yoursite.com/blogs/install. If a list of directory files appear, add "/install/index.php" instead and try again. For example, www.yoursite.com/blogs/install/index.php.
  5. Fill in your database username and password (from step 1) as well as your database name. Check that the other fields look right and then click to update the configuration file.
  6. Choose "New Installation" from the next screen and click "Go!"
  7. b2evo will write your config files and populate your database with some sample blogs and posts. At the bottom of this page you will see your "login" and "password", which you will use to access your new blog. Don't lose these. They can be changed later, but they are required to access your new blog.
  8. Click the "log in" link at the bottom of the page and you will be brought to the login screen. After inputting your login and password from step 7, you will be taken to the back office of your new blog. In the upper right hand corner of the back office, you can "Exit to blogs" to take a look around.
 Congratulations - you did it! You've just completed your installation of b2evolution!

[edit] After Installation

[edit] Activate .htaccess files

In the /blogs folder, there is a file called "sample.htaccess". You should try renaming it to ".htaccess" (with a leading dot). This will optimize the way b2evolution is handled by the web server (if you are using Apache).

This file is not active by default because a few hosts would display an error right away when you try to use it. If this happens to you when you rename the file, just remove it again and you'll be fine.

[edit] File Permissions

See directory and file permissions.

[edit] Be Careful about Blank Lines

When you edit any of the config files, be careful not to add any extra blank lines at the start or end of the file. For some very tricky reasons, this will cause your cookies to fail where needed in the application, and you won't know why. We have spent a very looooong time figuring this out! :-/

Retrieved from "manual.b2evolution.net/Install_b2evolution"
gipoco.com is neither affiliated with the authors of this page nor responsible for its contents. This is a safe-cache copy of the original web site.