61
Stewdio
An alternative way to Upgrade XOOPSs from very old and aged versions.
  • 2006/2/15 5:20

  • Stewdio

  • Community Support Member

  • Posts: 1560

  • Since: 2003/5/7 1


Upgrading at this stage may be more difficult then it's worth, especcialy now that I know you that you also have forum posts that you would like to keep.

The forum module has changed so much over the past that it runs, functions and feels completely different.

However, all is not lost if you will follow this suggestion as apposed to another I made in another one of your posts.

Depending on the path you may take to uprading your site andother alternative is to upload a new version of XOOPS to a test area on your site with a new databse. Install, run and add modules as needed. Transfer your users and the user group permissions (and what ever I might be missing, someone here will fill the gap for me) from the current live site to your new test site. Ask a couple members of your site to help test a few things by getting them to log into the test site. This will confirm a proper user migration to the new system.

Get your test area running properly as you would to have, with a new theme, module, configuartions, etc. Of course, you will want a forum module, which is the topic of this post. I'm getting to a solution very soon.

Once you have your forum up and running with all the topics, user permissions for moderator if any, etc, it will be time to re-open your site to the new version.

Heres where it gets a little tricky, but it's very manageable. While your users are still using the old site, it's time to copy that version over to a new folder. It might be wise to inform them that your site will be undergoing an oerhaul. Don't worry about the database, this information will not change since you created a new one for your fresh installation. I would move it into a new folder call archives, or something suitable for reasons that will become clear in a moment.

Close your live site for new user registrations so that you do not have to migrate possible new members over to your database for a second time. Your site won't be closed for long, just long enough to move the files around.

Now that you have closed your site, it's time to copy the files of your live site over to the archive folder, or what ever name you chose. Now you MUST edit your mainfile.php so that the site will work in the new location.

Once this is done, you will need to change the look and feel of the archive site to your own tasts, but I would keep it very minimal. No blocks, no extra modules, closed all forums, and only keep modules that contain information that users need on a regular basis. Essentially what you want to achieve here is a place for all your users to go when they may be looking up information they need to refer to on the (now) old site.

Now, create an index.html for the root of your site. A simple graphic and text message telling users you are doing a system upgrade will do fine. Delete the root structue of your old xoops, you won't need this anymore since you have a cloned copy in your now named archive folder.

Now transfer your fresh installation over to your root directory and edit the mainfile.php to reflect the new location. Delete the index.html file you created in your root folder and users will now be presented with your new site.

Before opening up the site, you may want to add a news snippet, or sticky forum post telling your users of where to find the archived posts. They will like the look a fresh feel of the site and will appreciate your efforts of keeping vital information. You also get an added bonuse of retaining your user post counts because of the user/group migration we did in step one of this small tutorial.

Granted, this is merely only a suggestion, but it will provid much fewer headaches, because many of the module you use now will not be able to work and are simply un-upgradeable due to their declining age. You will have lost all of your information in the upgrade. Why loose that information, when you can point your users to whats relevent in the archive area of your site.

You too will also have given yourself a second lease on life because now you hae a new fresh website with great and exciting mosules to play with. You will be able to offer your users many new features at a fraction of the pain it would have taken to upgrade, test and trouble shoot a myriad of potential problems from a difficult upgrade.

Ok, this post turned more into a general how to upgrade XOOPS article, but it was fun to write!
XOOPS Community Support



62
Stewdio
Re: Block specific theme?
  • 2006/2/15 4:56

  • Stewdio

  • Community Support Member

  • Posts: 1560

  • Since: 2003/5/7 1


Try this litle bit of help over on www.xoops-tips.com.

http://xoops-tips.com/news-article.storyid-89.htm

Good Luck
XOOPS Community Support



63
Stewdio
Re: Upgraded to latest and now get an error on the main page.
  • 2006/2/15 4:50

  • Stewdio

  • Community Support Member

  • Posts: 1560

  • Since: 2003/5/7 1


require "header.php"; require "footer.php"; are in many files, so it could be anywhere.

It may be more simple to reupload your files to the server. This will not affect your instalation in any way. If the error persists, then it is likely that your download was currupted during transfer and you will need to redownload the upgrade files once more and then transfer those new files to your server.

This method may actually be a little quicker then find and replace methods. I tried that once and gave up after a while!

Let us know how it goes.
XOOPS Community Support



64
Stewdio
Re: Still unable to get 2.2.3 final to register new members!
  • 2006/2/15 4:33

  • Stewdio

  • Community Support Member

  • Posts: 1560

  • Since: 2003/5/7 1


Are you configuring your XOOPS instalation on your local computer or on your main domain site.

I was unable to see or otherwise locate XOOPS running at the link you provided, and the first link looks very strange to me. One would expect to see 127.0.0.0, or 192.168.x.x for a local instalation. If you are running your XOOPS on your local machine, as mentioned, your mainfile.php will have to be configured to reflect the IP of your computer, or set to "localhost". Please refer to your webserver documentation to find out more on how to configure your computer to view loacl web pages in general. Of course, feel free to ask your questions here, as we all will have something to contribute to help get XOOPS running localy on your machine, if that is in fact the case.

Can you please provide us with more information about your server environment (either local or remote) and your XOOPS configuration.

Also, there is a known issue with XOOPS version 2.2.3/4 not allowing new registrations under certain conditions. This has not affected all users, just certain people running under certain environments.

Your website, www.moorishnationalrepublic.com, is running on Apache/1.3.34 which may or may not be part of this known issue. We have not be able to confirm if running under a different version of Apache will or will not solve the issue, so kplease stay tuned to the forums for any information in the future that may relate to this.
XOOPS Community Support



65
Stewdio
Re: Oops! Updating from RC3/1.3 to 2.0?
  • 2006/2/15 4:30

  • Stewdio

  • Community Support Member

  • Posts: 1560

  • Since: 2003/5/7 1


Quote:

halfdead wrote:
how about upgrading from 1.10 to the new xoops2? i cannot find any files for 1.10 to XOOPS 2...


You will need to upgrade from 1.10 to 1.3.10.

After that, you will need to apply each upgrade patch as it was released until you get to the 2.x series.

In order to make a smoothe transition, I would create a new database and copy your cuurent DB into that. Then copy your site files to a new directory and edit the mainfile.php to reflect the new database changes and file locations. This would be for testing reasons.

Once completed, then start applying all the patches to your test version (the newly copied information). Once all your patches are completed, you can then begin to move your test files back into the live section of your site.

Those are just my reccomendations. It may take longer, but at least your site will still be intact if anything goes wrong with the testing grounds.

Please remember, that your old modules may not work any longer. In many cases, the only salvageable data from this sort of upgrade path after such a long time, would be your user groups and users. You would essentially be building a new website in the background for your users to use at a later date, if you follow my meaning.

Good Luck!
XOOPS Community Support



66
Stewdio
Re: Install problem: could not connect to the database server
  • 2006/2/13 6:14

  • Stewdio

  • Community Support Member

  • Posts: 1560

  • Since: 2003/5/7 1


The error reported at that point of the installation is rather cryptic and somewhat misleading. Even a mistyped password will produce the same error. It connects, but doesn't report the correct error.

Be that as it may, create a specific user account in MySQL for your XOOPS install and use that account to be absolutly sure. Also create a separate XOOPS DB and assign that user account to that db, of course with all the proper privledges.

I'm sure you aware of all this, but I have found that when I get right down to specifics with all my XOOPS instalations, I can be sure that I eliminate any potential slip-ups with a misconfiguration or what have you.

On a side note, I spent three days trying fix one XOOPS instalation because I used my DB prefix in the password field! Yes, it can happen to the best of us
XOOPS Community Support



67
Stewdio
Re: New User Can Not Register
  • 2006/2/12 18:33

  • Stewdio

  • Community Support Member

  • Posts: 1560

  • Since: 2003/5/7 1


Quote:

jlm69 wrote:
Stewdio,

Welcome to Linux, I think you will love it.


Thanks! I've rediscovered computers after a decade of mainstream computing, I'm loving it!
Quote:

On your hosted site.

1. If you remove the PM module can you add a new user?

Removed the module and I get module doesn't exist for registrations.

Quote:

On your new Linux site.

1. Can you copy your old site to your new box and see if the problem goes away.


No problems on my local machine.
XOOPS Community Support



68
Stewdio
Re: 2.0.12 --> 2.2 upgrade snafu
  • 2006/2/12 5:41

  • Stewdio

  • Community Support Member

  • Posts: 1560

  • Since: 2003/5/7 1


Since you can not save your changes, turning on the debug tools would be a bit of a pain via MySQL admin.

Try going to the root of your site /recovery.php and setting php debug and/or MySQL debug to on and see what error output, if you you get in your admin section when you try to save the changes.

Let us know how it goes.
XOOPS Community Support



69
Stewdio
Your Top 5 Firefox Extentions
  • 2006/2/12 5:29

  • Stewdio

  • Community Support Member

  • Posts: 1560

  • Since: 2003/5/7 1


Please list your Top 5 extentions to install once you have Firefox running,with a brief description for each

Mine Are (In no certain Order)

Tab Mix Plus - Killer tab options with session restoration.
Ad Block - Handy for blocking Advertisements.
Adblock Filterset.G Updater - An enhancement for Ad Block with predefined, auto-updating lists. A good time saver for not having to manualy block commonly used ads. Includes a whitelist for allowable sites.
FireFTP - Handy FTP with some nice features, like File Diff.
Xinha Here! - Excellent WYSIWYG HTML editor for any editable region or form on the page you are viewing. A must have for news editors, bloggers.
BBCode - A simpler version of Xinha Here! from a different developer. Adds BBCode/HTML/XHTML formating to the context menu for forums.
XOOPS Community Support



70
Stewdio
Re: 2.0.12 --> 2.2 upgrade snafu
  • 2006/2/12 4:57

  • Stewdio

  • Community Support Member

  • Posts: 1560

  • Since: 2003/5/7 1


Log into your site via FTP and delete the admin file int he cache. It will be recreated once you log back into your system. Also delete the template_c files and update the system module from with your module administration pages.
XOOPS Community Support




TopTop
« 1 ... 4 5 6 (7) 8 9 10 ... 131 »



Login

Who's Online

168 user(s) are online (63 user(s) are browsing Support Forums)


Members: 0


Guests: 168


more...

Donat-O-Meter

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

Latest GitHub Commits