I finally managed to get the self hosted 2.18 working. At first, it did not show any plugins, but I have found a button called Refresh, which has read all the available plugins. Plugins are now working. This leaves me with the next problem: the /files directory has 11 or more apps, but the 2.1.8 cannot see them. I wish there were a 'refresh' button for apps, but there doesn't seem to be any. So, how can I make the software for self hosted BuzzTouch read my apps?

Did you use the same database?

I did an update from 2.1.7 to 2.1.8 and was able to see my old apps just fine. I even downloaded new source just to make sure. I had to replace an app icon, but other than that, no issues!

No, it is a new database. The manual says it should be new, preferably. If it says we have to use the old database, then I have missed that part and that might have been the error. I went to phpMyAdmin, and compared the tables. The old database has table bt_applications, which contains the data, and the table of the same name in the new database has no entries at all. (If you create a new app, there will be an entry there, so the software works on its own.) The new bt_applications table has lots of new columns, so when I added the fields from the old table to the new one, the new columns were blank. I still have a problem. Is there a special part of BuzzTouch dedicated to support?

You're going to want to use the same database. It sounds like you might want to back it up first. Unless you're familiar with all that, you might not want to add or delete fields from the database tables, either. Good Luck! Cheers! -- Smug

I have backed up my old database already. That is not a problem. > Unless you're familiar with all that, I am very familiar with all that, phpMyAdmin, database and all. ----------------- Here is what it says in the manual for installation, under No. 4. You can create a new empty database or you can use an existing database. It's usually best to create a new empty database. That is exactly what I did and now I have a problem. I would like someone from Buzztouch to tell me what to do next -- either install it inside the old database, or provide some kind of fix to transfer the data from the old table to the new one.

Understanding the Update Process It's logical that you'll be updating this software in the future. Use the Admin > Settings > Check for Updates function to check for new releases. When you update the software you'll be running the same installation process you just did. However, because the software will already exist, it's important to understand what will happen. Here's how it works... 1) You download a newly updated package..BT-server-vXXXXX 2) You upload the package to the same website you did when you originally installed it. This effectively overwrites the existing install. THIS WILL NOT OVERWRITE the /files directory. It's important that the /files directory remain unchanged during updates. 3) You visit the same /BT-server/install screen you used to install the original package and use the same database login information. The database exists so it is not populated with any new data. It's structure may be altered, depending on the nature of the updates. 4) You complete the update process then remove the /install directory again. 5) The /files directory and all of it's contents (plugins, application data, other data) is in the same state it was before the update.

Effectively that says to use the old and existing database. So why does it then say (under No. 4) that we are free to use the old database or create a totally new one?

Effectively that says to use the old and existing database. So why does it then say (under No. 4) that we are free to use the old database or create a totally new one?

Thats the last thing listed in your install guide, before that is for new installs. It just walks you through the process.

Effectively that says to use the old and existing database. So why does it then say (under No. 4) that we are free to use the old database or create a totally new one?

For new installs, top of installation pdf, install, bottom update process.

I see your point, but why did they not say so in the first place? This document should have had two chapters, or there should have been two different documents. There are two audiences, really, newcomers and those who already have the self hosted version installed.

Finally, I got to install version 2.1.8 over the old database and now everything seems to be working. Sigh.