TikiWiki installation for CERT (OK Drill)

20110724 – Update: TikiWiki is a fun concept, but I’m just going to use phpBB for inter-comm for OK Drill.

I’m in the middle of the file upload for installing TikiWiki for upcoming Ojai OK Drill (www.okdrill.org) this September 21st at 7PM.

TikiWiki is one of these combo CMS systems that manage blogs, RSS, Forums, images, etc. While I’m focusing on developing WordPress skills, I thought it’d be fun to try out one of these all-in-one comprehensive suites — just for a specific exercise.

Reason for going down this path is that I’d like to see some forum interaction between Neighborhood Area Coordinators, NERT Coordinators and CERT Team Members. This will also aid other CERT Groups for their drill improve cross-communication.

After uploading and trying an install, I get the error — PHP 5.2 is required. Now I have to monkey with the .htaccess file, I think

The .htaccess file mentioned un-remming a couple lines:

AddType x-mapp-php5 .php (Advised by 1and 1 to add)
AddType application/x-httpd-php5 .php (Already in file and I unremmed)
AddHandler application/x-httpd-php5 .php (Already in file and I unremmed)

This appears to be some specific info for installing TikiWiki on 1and1 hosts:

http://doc.tiki.org/tiki-index.php?page=1and1+install

So typical!!! I need to start learning PHP. The htaccess file on server was named _htaccess and needs to be renamed to .htaccess

1.4. Rename _htaccess for clean URLs (optional)
You can rename _htaccess to .htaccess

Getting somewhat closer now, but now it wants to open the tiki-install.php file instead of running it…

Subdomain issue maybe?

I thought I was being swift by creating a subdomain — oktiki.ojaivalleycert.org vs ojaivalleycert.org/tiki

I think I need to modify .htaccess so that it knows it’s technically not within a folder off of root – ie /tiki

# If your Tiki is not at the root of the server (e.g. at http://example.com/tiki)
# You will need to uncomment and fix the RewriteBase value below to suit your installation.
# RewriteBase “/tiki”
# And if you get errors like “The requested URL /absolutepath/tiki-index.php was not found on this server”,
# You may need to uncomment the following line.
# RewriteBase /

I’m good at joining Forums now, so we’ll see what happens. I asked if OK to install within a subdomain.

Found this:

To run PHP5 on 1and1.com add the following lines to your _htaccess file (Tiki 3):
AddType x-mapp-php5 .php
AddHandler x-mapp-php5 .php
uncomment line 29 and 30 then rename in .htaccess

After a bunch of surfing, I found the magic bullet line to add to .htaccess within http://doc.tiki.org/Requirements

AddHandler x-mapp-php5 .php

TikiWiki Installation Notes
Tiki has detected your PHP memory_limit at: 90 MB.

Sent a test email from installer and received this email seconds later:

Congratulations!

Your server can send emails.

Tiki version: 7.0
PHP version: 5.2.17
Server: oktiki.ojaivalleycert.org
Sent: Tue, 21 Jun 11 02:40:29 -0400

Under Image Processing:

Tiki detected: GD bundled (2.0.34 compatible).

Success Tiki can create images.

Tiki uses the GD library to process images for the Image Gallery and CAPTCHA support.

Database Info:

-Entered MySql Classic vs MySqli (i for improved)
-HostName = LocalHost (entered by default)
-Database Name
-Database username and password
-Left default check on Always force connection to use UTF-8 — I remember cross-checking when I was doing phpAdmin during database creation

Database is not localhost
This is not uncommon. When you are in tiki-install.php, make sure to replace localhost with the value provided by 1and1.
I found this in my phpAdmin notes under: Host Name

Wahoo!!! A new install will populate the database….

Your database has been configured and Tiki is ready to run!

This was well worth sticking with — I definitely need to understand more HTML and PHP.

Posted in Blog Development, CMS (Content Mgmt System) | Leave a comment

Resolved – PHPList Upgrade to 2.10.14

Resolution was to:
-Backup the entire /lists folder from web to local HDD
-Fully delete the entire /lists folder contents — all files
-Upload from local HDD the new /lists folder only to the web (ojaivalleycert.org/lists)
-Go to the Admin Directory on web — which gave 500 error
-Update the .htaccess file (I copied from previous working install from backup) to address the 500 error.
REVISED 20110806 – Update the config.php file (I copied from previous working install from backup) – lists/config/config.php
-Go to the Admin Directory on web again
-Log-in to PHPList and click Upgrade Database (followed instructions)

Note: One of my concerns were the files within the root of /lists on the web — I saw things like “Upgrade”, but the instructions were to click upgrade within the PHPlist system. Needed to really follow instructions closely. The way the documentation reads it’s a bit confusing regarding the public_html folder, because all I needed was to go in and just focus on the /lists folder contents. All good now.

=====================================

I use PHPList for my mailing lists for both Ojai Valley CERT/Ham Radio and for Senga Classic Stage Company.

Currently, I’m running version 2.10.10 and the Latest version is: 2.10.14

Here is the link to the upgrade procedure: http://docs.phplist.com/PhplistUpgrade

-Followed procedure to use phpAdmin to make backup of database to local HDD
— Find the correct PHPList SQL database — I have several
–So far so good — just followed backup procedures from within phpMyadmin
–Just to be sure, because the upgrade documentation isn’t really clear, I also copied the lists folder to my local HDD (Note: In hindsight, this may have saved me).

Big Note: Making a backup copy of the server directory /lists saved me big time, because I had to restore to get back online again. Need to ask forum why upgrade didn’t work.

Downloaded latest PHPList to local HDD
-Downloaded and Unzipped

Upload the unzipped folder to the /lists directory on server
–What’s throwing me off is the folder structure for the new download doesn’t match any folders within current /lists
—Didn’t delete any files on server, but uploaded anyway to the /lists folder

Not sure why I need to adapt the config.php file as I didn’t see any overwrites of the admin folder — this documentation I’m following seems to missing something.

Great… now I’m seeing that there is a /public_html parent directory of /lists that was uploaded. Somehow, the current parent directory I had on server was /lists. That explains why I wasn’t overwriting any existing files during the upload.

I’m seeing this within config.php, so I must have edited out the /public_html for some reason:

# if you change the path to the PHPlist system, make the change here as well
# path should be relative to the root directory of your webserver (document root)
# you cannot actually change the “admin”, but you can change the “lists”
$pageroot = ‘/lists’;
$adminpages = ‘/lists/admin’;

I think my answer, if I’m going to keep things relatively the same, is to transfer the files out of /public_html directly into /lists on the server.

What I don’t get is the documentation alludes that I did the above correctly – http://docs.phplist.com/PhpListConfigDatabase This is now really weird that the installation had /lists within /public_html

Now I’m getting this error when I deleted the files within /lists on server and uploaded fresh from the /public_html directory on HDD:

Error 500 – Internal server error
An internal server error has occured!
Please try again later.

Note on 500 Server error:

-I now vaguely remember getting this error initially when I first installed PHPList. Now I’m wondering if my upgrade actually had worked OK and I just had to do the following:

Why do I get a 500 Server Error?

If you get a ‘500 Server Error’ when installing, your server probably runs PHP as a cgi, not as an apache module (also known as phpsuexec). You need to edit the file ‘/lists/.htaccess’ delete or comment out (with a #) the line about ‘php_flag magic_quotes_gpc’. e.g. # php_flag magic_quotes_gpc on

Deleted the entire /lists directory on server and re-loaded the backup of /lists I had made to the HDD. Somehow, I’m missing some files.

What’s weird is that the documentation says “ie, your /lists folder” but doesn’t specifically say to just copy the files up from within public_html. Not sure what files it’s looking at to discern needing an upgrade — the upgrade button should be an automatic pick, I think.

Hopefully the backup restores me back so I can access the data. If that works, then I’m going to post to the PHPList forum and go from there. Also going to go through www.lynda.com course on Intro to XTML and HTML — needing a basics course on managing HTML.

I just installed phpList, but sending my first messages fails. Why can’t I send any message?
Please check if phpList is still running in Test mode. In config.php check your value for this constant (0 is off, 1 is on): define (“TEST”,0); . See also Preflight Checklist.

My list has grown a little and now all my subscribers disappeared
When you reach a certain limit, phpList will stop listing your subscribers when you load the page. You will need to add some text in the search box to find the subscribers you are looking for. If you still want to see all you can search for % (just the percentage sign).

Posted in Management | Leave a comment

WordPress Upgrades

Recurring Procedure for doing manual upgrade for WordPress sites:

-Go to the online doc — http://codex.wordpress.org/Upgrading_WordPress for instructions
-Note: 1and1.com always has the minimum requirements for PHP and MySQL
-Take a backup. Note: Use the “SnapShot Backup” Plug-in and download the .TAR file to local HDD
-Disable all plug-ins. Select all plug-ins and choose “Deactivate all”
-Download the latest WordPress zip to local HDD and unpack the zip file that you downloaded
-Using FileZilla, Delete the old wp-includes and wp-admin directories on your web host (through your FTP or shell access).
-Using FileZilla, upload the new wp-includes and wp-admin directories to your web host, overwriting old files.
-Upload the individual files from the new wp-content folder to your existing wp-content folder, overwriting existing files. Do NOT delete your existing wp-content folder.
-Do NOT delete any files or folders in your existing wp-content directory (except for the one being overwritten by new files).
-Upload all new loose files from the root directory of the new version to your existing wordpress root directory.
-Actual command within browser to finalize the upgrade — http://paulgarth.com/wp-admin/upgrade.php (Note: I don’t have a /wordpress directory)
-Activate plug-ins
-Update any plug-ins
-Update Techozoic Theme, if applicable

Posted in Checklists | Leave a comment