Geeklog Forums

This is my same issue... I restored my old database and reuploaded everything. Please help - my site has been down a couple days.

Okay, I have no idea how this could happen ... Could all of you having this problem 1. Please (one more time) restore your 1.3.7 database backup and check if table gl_topics has a field \"is_default\"? It shouldn\'t. 2. Tell me exactly what you do when you run the upgrade script? bye, Dirk

Okay - the field \"is_default\" was listed in gl_topics and I dropped it. I restored my database again and tried to re-install, but now I\'m getting this message: 1060: Duplicate column name \'pwrequestid\' (I went back in to my gl_topics and the is_default is there again.) I am upgrading from 1.3.7 to 1.3.8.

\"pwrequestid\" is also a new field in 1.3.8. It looks like you are mixing 1.3.7 and 1.3.8 tables. Please drop all tables from your database, restore your 1.3.7 backup and then try again. bye, Dirk

rofl I dropped the tables on Geeklog and I tried to restore. It shows the last restore time was about 20 minutes ago, but the tables are no longer there when I go in through my database. I downloaded the backup, thinking it was an .sql file, but it\'s not, so I don\'t know how to restore it manually. When I unzipped the backup, all the files within have .frm, .MYD and .MYI extensions. I\'m totally clueless now. Going to contact my host, but I\'ll probably have to wait a couple days to hear back from them

Well, wanna hear what my webservice provider offered me?! The backup does not contain your data in sql format. These are the actual data files. You will need to load the archived database backup using the database restore tool. 1) Click the MySQL link in your web hosting account. 2) Click \"Restore Database\" 3) Select a database backup to restore and click \"Restore Database\". I\'m very frustrated... I\'m afraid I\'ve lost over 300 stories... That may not sound like a lot to some, but these were actual short stories, poetry, etc. I suppose my restore isn\'t working as intended... Can anyone please offer me some options to try?

Yeah, that was obvious from your previous post. Did you ever user Geeklog\'s built-in backup option? I have no idea how portable those .MYD files are. You may try finding (or setting up) a machine with a similar setup than the one your website is running on and copying the files to the appropriate directory there. The MySQL manual seems to imply that this is possible. Hope that helps and good luck ... bye, Dirk

Thanks for the link; I checked it out. How detrimental would it be to install geeklog as a new install (since the tables no longer exist)? I think I can copy the table files into the new tables? I found this: tbl_name.frm -- Table definition (form) file tbl_name.MYD -- Datafile tbl_name.MYI -- Index file I didn\'t use the geeklog backup because I couldn\'t figure out the correct path ,p I know nothing about this stuff Thanks for the time.

Alright, I think I found a solution to this but requires some work. Unfortunately, I couldn\'t get the geeklog backup to work, and silly me didnt think of doing it manually, so I crossed my fingers and upgraded, running into this \'is_default\' problem. Note: I am upgrading from 1.3.7 to 1.3.8. Warning! Before you do any of this, be sure that you are confident working with mysql, and that you don\'t have a backup that you could use to re-install. Also, read through all the details and all the steps first, because some may not apply, depending on how much of the your upgrade processed the first time around before the error. AND, do this as a last resort, only after doing what Dirk said, and if you don\'t have a database backup to restore. So here goes... In the geeklog database you will need to make the following changes, under the assumption that your prefix is set to \"gl_\". 1) Drop the field \'is_default\' from the table \'gl_topics\'. 2) Drop the field \'pwrequestid\' from the table \'gl_users\'. 3) Drop the field \'lastlogin\' from the table \'gl_userinfo\'. 4) Drop the field \'emailfromuser\' from the table \'gl_userprefs\'. 5) Drop the field \'showonline\' from the table \'gl_userprefs\'. 6) Drop the table \'gl_speedlimit\'. 7) Create the table \'gl_commentspeedlimit\'. 7.1) You will need a field, so just create an empty test field. 8) Create the table \'gl_submitspeedlimit\'. 8.1) Again, you will need a field, create an empty one. 9) Now, if you are using one of Geeklog\'s theme\'s, such as XSilver, then you should be able to re-install the upgrade to 1.3.8, and get the success page. If you are using a custom theme, then copy the file adminoption_off.thtml from the folder /layout/XSilver/ to your theme folder (/layout/theme_name/). Quick Note here: If you are using a custom theme, you may not need to go through the first 8 steps listed above. In order to test this, in the config file, set the default theme to XSilver, and turn off the option for users to change themes. These settings are for $_CONF[\'theme\'] and $_CONF[\'allow_user_themes\']. Once you do that, open up the browser and check the site. You may still get some template errors with a \"Halted\" message, which I will address (step 11) and is okay. So if you see your site with the errors, this is good, just copy the file as described in step 9 and skip the next step (10). If not, then you probably need to do steps 1-8 first. 10) If you did steps 1-9, then go ahead and try to install the upgrade. You should hopefully get the success page, as I did. If not, then there is no hope. Just kidding... I didn\'t encounter any errors in this step, but if you do, then you might have to find another solution. 11) Again, if you are using a custom theme, there are some files that have been added to Geeklog\'s theme\'s and may not be in yours. When designing my theme I used gameserver for my template architecture as a starting point, because it had different templates for the left and right blocks. I am pretty sure though that you can copy the following files/folders from any of the Geeklog theme. The files are located in /layout/theme_name/ and are: adminoption_off.thtml (Same file from step 9). loginform.thtml topicoption.thtml topicoption_off.thtml useroption_off.thtml admin/database/* (The entire folder). admin/user/plainlist.thtml comment/startcomment.thtml comment/commentbar.thtml pollbooth/pollanswer.thtml pollbooth/pollblock.thtml pollbooth/pollcomments.thml pollbooth/pollresults.html pollbooth/pollvotes_bar.thtml pollbooth/pollvotes_num.thtml preferenes/* (The entire folder). search/resultauthdatehits.thtml search/resultrowenhanced.thtml search/resultsummary.thtml search/resulttitle.thtml users/newpassword.thtml Note: I\'m not sure if you need all the files (someone else might know, Dirk?), but I know that I needed some of them and just copied them all rather than QA\'ing my site after copying one file at a time (way to time consuming). Also, if you already have these files in your theme, don\'t copy them, or overwrite them. That should be it. I ran through my entire site real quick, and from what I could tell, all the updates were there, and nothing was broken, with no loss of content in the database. Again, make sure some of the steps apply to you before doing them. Hope this helps and good luck. Tym.

That\'s the hard way of doing things if you don\'t have a backup, yes. As for the themes: All the changed files are documented. To make things easier when you have a customized theme, you could also rename your layout folder, and upload a new one with, say, only one of the stock themes in it and set that as the default theme. Geeklog will fall back to the default theme if it can\'t find the one you\'ve set in your preferences. That way, you can concentrate on the upgrade first. Once your site is upgraded, you can start making the changes to your custom theme. bye, Dirk

Thanks, I was trying to find this before. And this will work if I need to for the next upgrade?

It's me. I'm back! Okay - I switched webhost providers (they are great) and they were able to restore my geeklog database for me. I'm still at 1.3.7 and tried to upgrade to 1.3.9 this time. I get the error: Duplicate column name 'is_default'.

My question is this:
Can I do a fresh install and create a new database and move over the data from the existing database? Or should I just drop the old database and use my backup? The only thing is: I know I only hit the upgrade button once, so I am assuming the same thing will happen as last time.

Thanks!