_install.php

  • Step 0
    • Check if Plogger already installed by checking for plog-config.php information and if database has Gallery URL or Gallery Name already in place (Wordpress uses Blog Name)
      • Utilize same check code for Plogger function connect_db() and prompt for _install if needed
    • Check read / write requirements
    • Check for session.save_path and session variables
  • Step 1
    • Gather gallery information (Gallery Name and Admin Email)
      • Verify email syntax
    • Gather database information if plog-config.php information does not already exist
    • Gather FTP information if safe_mode is enabled and ftp_connect() function exists
      • Run this even if database information already entered into plog-config.php, unless FTP information already entered into plog-config.php manually
  • Step 1a
    • Prompt for download of plog-config.php if not already present and cannot write information to the Plogger folder
      • May be combined with Step 2 if we can figure out how to make people download and upload the information before proceeding
  • Step 2
    • Install database information
    • Send email
    • Present generated username and password
  • Step 2a
    • May be part of Step 2
    • Redirect to login information (current code) or provide link to admin login (similar to Wordpress)

_upgrade.php

  • Step 0
    • Check if Plogger already installed
      • Prompt for _install.php if not previously installed
    • Check if Plogger needs to be upgraded
      • Utilize same check code for Plogger function connect_db() and prompt for _install if needed
      • Add and use plogger_version and/or plogger_revision fields in the plogger_options database table
        • May need to wait until we convert over to 2-dimensional options table as described in ticket #131
    • Check read / write requirements
      • Keep current code for rewriting plog-connect.php to plog-config.php if upgrading from Beta 1? If so, keep check for writing to the root Plogger folder. Remember to prompt the user at the end of upgrade to change permissions back.
      • Check for session.save_path and session variables
  • Step 1
    • Move database connection info from plog-connect.php to plog-config.php if upgrading from Beta 1
    • Prompt for FTP information if safe_mode enabled and user has been manually CHMODding new albums / collections and add information to plog-config.php
  • Step 2
    • Check that plog-config.php exists and has the necessary information
    • Update the database
      • Tie into plog-admin/includes/install-functions.php instead of duplicating functions for upgrade (same functions for upgrade and install now exist in two locations)
  • Step 3
    • Check to see if user has moved images, thumbs, themes, translations, and uploads to plog-content
      • If not prompt the user to move them manually or
      • Ask if they want Plogger to attempt to move automatically
        • Show user time and size limitations and let them decide if they would like to attempt automatic moving of folders/files
        • May need to limit to only a couple of albums or images at a time in case server times out or reaches maximum memory or size limits?
        • If fail, prompt user to manually move folders
  • Step 3a
    • Update comment form action URLs in themes from 'plog-comments.php' to '$_SERVERREQUEST_URI?'
  • Step 4
    • unlink() all unused files if user just uploaded new Plogger code on top of old Plogger code
      • Prompt user which files to delete if unlink() fails
  • Step 5
    • update version / revision if no errors
    • change SQL table charset to utf-8