Long introduction (I'm verbose), with what I think is a simple question at the end. Over the weekend, I went through installing the Buzztouch control panel on an Amazon EC2 instance. I basically followed a combination of "how to" instructions I got from the Buzztouch web site, but a few things had changed at Amazon Web Services since the relevant "how to" had been written, and I chose to do some things differently from the ways the authors of the "how to" guides had done them. I searched the Buzztouch forums and the web for solutions to problems I encountered and in the end managed to get the Control Panel set up. I am now going through the process much more carefully, writing things down and producing a new "how to" that I think could be useful for other new self-hosters. It's all been OK so far, through configuring and launching an EC2 instance, installing a complete LAMP stack on it and getting everything running, getting the Buzztouch 3.0.0 files from the Buzztouch web site and putting those in the right place on the EC2 instance, setting permissions in the /files directory, and opening /install in a web browser. So here's my question: was I supposed to point the browser somewhere else, or did somebody forget to change the version number on the Buzztouch installation page (or did I do something else wrong)? I ask because I just downloaded the v3.0.0 files (and I never had any earlier versions), and it was those I put on the EC2 instance, but the installation page says "Buzztouch v2.1.9 Installation."

Nope. Some additional text you'll need to add into your tutorial is: "By the way, your config.php file for BTv3 still has '2.1.9' in the version line (even though it's v3), and needs to be changed. On or around line 73 look for this: define("APP_CURRENT_VERSION", "2.1.9"); and change it to 3.0.0". Cheers! -- Smug (Someone forgot to change the version number. I blame Wayne Newton, but no one listens to me anyway, so....)

Thanks! It's just after 1 in the morning here and I'm at a relatively good stopping point, so I'm going to sleep, but I'll continue working on this tomorrow.

I think changing that line (and, in the name of consistency, the version number that appears in an extended comment at the top of the file) in config.php is important, so I've added that. In the new text I mention that SmugWimp told me about this in the forum. However, making that change to config.php does not change which version appears just under the Buzztouch logo on the Buzztouch installation page and on the browser's title bar when the installation page is open. At the end of the instructions on how to fix config.php in my "how to," I added an item that says those who are uncomfortable seeing "2.1.9" on the installation page (and in the title bar when that page is open) can adapt the instructions for modifying config.php to modify another file that has "2.1.9" in two places where it ought to have "3.0.0". The file is [wherever_you_put_the_BT-server_folder]/BT-server/install/index.php In my case, it was /var/www/BT-server/install/index.php As I mentioned, "2.1.9" appears twice in that file. I believe it's on lines 212 and 232. One of them specifies the title that appears in the browser's title bar. The other is the text that appears on the install page just under the Buzztouch logo. EDITED to add: I make it clear that changing what the installation page and title bar say is the version number makes no difference, so it's not necessary to change the two occurrences of "2.1.9" to "3.0.0" in [wherever_you_put_the_BT-server_folder]/BT-server/install/index.php

I'm only a little bit embarrassed about how long it took me to realize that just because I had put the files on the EC2 instance before discovering there was a mistake, that didn't mean the people using my "how to" would have to put the unmodified files on the server and then modify them remotely. And I only figured it out when I did because I've been saving images at different points in the installation process, and I got confused about some passwords, so I decided to revert to an earlier image (relaunch it and terminate the one that was further along in the process) and redo some of what I'd already done. I was thinking I could use my own guide to get from the earlier image to the end of what I've written so far, and as I was thinking about what steps I would need to repeat, I realized I could modify the Buzztouch files locally and then never have to modify them remotely on the EC2 instance. I'll take out the step-by-step instructions for modifying config.php on the EC2 server and put in the easier instructions for modifying it (and, because it's so easy, /install/index.php too) locally. Those shorter instructions will appear right after the user has unzipped the zip file from Buzztouch.