XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk
  1. Board index / 
  2. XOOPS Community Support forums / 
  3. XOOPS general usage questions 
  4.  / Was upgrade successful? How to tell?
Register
1
dplittle
Was upgrade successful? How to tell?

  • 2006/6/29 18:40

  • dplittle

  • Just popping in

  • Posts: 49

  • Since: 2004/9/15


I am finally getting around to upgrading from version 2.0.7.

I started the process and uploaded the 2.0.7 to 2.0.9.2 files. I upudated all my modules and the system seems to still be working fine. However, before going on to 2.0.10 in preparation to going to 2.0.14 I wanted to make sure everything was okay.

I happened to notice at the bottom of my Admin page that it still lists the version as 2.0.7. I don't want to just keep moving on if things aren't really getting applied correctly.

I do use a custom template but there is no change if I go back to using the Default template. Is this a cache issue? How else can I find out what version I am actually running? The System module stills shows version 1.

Thanks

David
2
Quest
Re: Was upgrade successful? How to tell?

  • 2006/6/29 18:48

  • Quest

  • Friend of XOOPS

  • Posts: 1034

  • Since: 2005/11/19


Try updating the system module in admin/system/modules. This I think also clears the template_c too.

Quest
3
dplittle
Re: Was upgrade successful? How to tell?

  • 2006/6/29 19:15

  • dplittle

  • Just popping in

  • Posts: 49

  • Since: 2004/9/15


Quote:

Quest wrote:
Try updating the system module in admin/system/modules.


I have done and just did it again. Same results.
4
Bender
Re: Was upgrade successful? How to tell?

  • 2006/6/29 20:38

  • Bender

  • Home away from home

  • Posts: 1899

  • Since: 2003/3/10


For the system module it is normal to show 1.

However the admin section should display the correct version.

- did you try uploading and overwriting all files from the update package again?

- you can check the file \include\version.php
If it is 49 bytes large and dated 14.06.2004 then its still 2.07
If it is 113 bytes in size and dated 30.12.2004 then it is 2.09
You can also look into the file.
Sorry, this signature is experiencing technical difficulties. We will return you to the sheduled signature as soon as possible ...
5
snow77
Re: Was upgrade successful? How to tell?

  • 2006/6/29 21:21

  • snow77

  • Just can't stay away

  • Posts: 864

  • Since: 2003/7/23


@dplittle, as far as I know you don't need go through all those upgrades one by one unless there is database upgrade script along the way. I'm not sure if there is a db upgrade script between 2.0.5 and 2.07 or between 2.0.7 and 2.0.9. If you are already on 2.0.9, why not just go ahead into 2.0.14, downloading the full package and overwriting all the files (except mainfile.php and other custom images or themes you might have that could be mistakenly overwritten)and going along with the 2.0.14 upgrade instructions as written by the devteam:

Quote:

Upgrading from any XOOPS version between 2.0.10 and 2.0.13.2

1. Copy the content of the htdocs/ folder except mainfile.php over your existing installation.
2. Delete the following folders and files:
* class/smarty/core
* class/smarty/plugins/resource.db.php
3. Empty the templates_c folder (except index.html)
4. Upload the upgrade folder to your site
5. Ensure the server can write to mainfile.php
6. Login using an administrator account
7. Access /upgrade/ using your browser, and follow the instructions
8. Write-protect mainfile.php again
9. Remove the upgrade folder after use
[quote]


and

[quote]
XOOPS is now released with an experimental script able to check if all the system files were correctly uploaded to the server. To use it, follow these instructions:

1. Upload the xoops_md5.php and xoops.md5 files located in the XOOPS package root to your XOOPS server folder (putting them next to mainfile.php).
2. Execute xoops_md5.php with your browser
3. If necessary, re-upload the missing or corrupted system files
4. Remove xoops_md5.php and xoops.md5 from your server


everything should go well for you this way.
6
dplittle
Re: Was upgrade successful? How to tell?

  • 2006/6/29 21:25

  • dplittle

  • Just popping in

  • Posts: 49

  • Since: 2004/9/15


Quote:

Bender wrote:
- did you try uploading and overwriting all files from the update package again?


I did but I'm trying one more time just to make sure.

Quote:

Bender wrote:
- you can check the file \include\version.php
If it is 49 bytes large and dated 14.06.2004 then its still 2.07
If it is 113 bytes in size and dated 30.12.2004 then it is 2.09
You can also look into the file.

It did still say 2.0.7 so something isn't happening. I'll see what happens after I reupload.

According to the tutorial to which I was pointed, all I needed to do after uploading was update the System and other modules plus check my custom templates. Am I missing anything? There's no upgrade documentation in the patch zip file.

Thanks

David
7
dplittle
Re: Was upgrade successful? How to tell?

  • 2006/6/29 21:27

  • dplittle

  • Just popping in

  • Posts: 49

  • Since: 2004/9/15


Quote:

snow77 wrote:
@dplittle, as far as I know you don't need go through all those upgrades one by one


According to this FAQ I need to run the first two upgrades and then can do the big jump to 2.0.14.

David
8
dplittle
Re: Was upgrade successful? How to tell?

  • 2006/6/29 21:44

  • dplittle

  • Just popping in

  • Posts: 49

  • Since: 2004/9/15


That loud slapping sound your heard was me hitting my forehead. I had downloaded everything ok but when I sent it to my server, I just transfered the HTML directory as /html, not a level lower. Doh!! Redid it and now it looks okay.

Thanks everyone.
9
snow77
Re: Was upgrade successful? How to tell?

  • 2006/6/29 21:51

  • snow77

  • Just can't stay away

  • Posts: 864

  • Since: 2003/7/23


xoops-2.0.7_to_2.0.9.2 patch as for I can see this patch is just file overwriting so is Xoops-2.0.9.2-to-2.0.10 , you can see for yourself that they don't even have to execute an upgrade path; at least I'm not seeing it in my old archives (maybe I'm mistaken, yet I've been upgrading since 1.3). So I don't see where's the point to following those steps. Going from 2.0.6 to 2.0.7 does include an upgrade script as excpetion to other, so does 2.0.14

I can't remember very well but there was a lapsus XOOPS had where getting from 2.0.7 to 2.0.10 wasn't so easy and there were some mistakes done in between one patch and another.

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

308 user(s) are online (249 user(s) are browsing Support Forums)

Members: 2

Guests: 306

kalibri, margoritka,

more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Nov 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits