Best bet is to try doing your upgrades on a test site locally on your local PC if at all possible. It will be much faster for you in the long run and you will be able to try different things.

For a variety of reasons you should not work on your production server to do such an upgrade.

If you MUST work on your production server you COULD make a sub directory on your production server, duplicate your database and do all of the work there if you so desired too if you are not sure... Not suggested but still better than actively working on the active production server. If you use a sub directory on your active server and get everything working it is simple to move it back.

Since it looks like you upgraded from a somewhat older version of xoops I would strongly suggest doing the following.

Inactive modules can potentially interfere if they are incompatible you should uninstall any modules you don't plan to use and remove them from the modules directory.

If you have a problem with a module you should disable all of the other modules (other than system) to insure it is really an issue with just THAT module and go from there.

It can be a somewhat tedious project when you have a bunch of modules but the only way to insure the problem you are having is really that module you need to go one at a time. Once you know the module works then you can keep adding the other modules back until you have other issues.

As mamba mentioned, you should update the modules to the latest versions but make sure you have good backups. In some or maybe all of the cases you upgrade or move to another module they may be able to import your old data but otherwise you should expect to lose all of the old data unless you understand how to manipulate the database to move your information over from one module to another.

One way to try exporting is to take your original 700 picture library and export the list of pictures from the database table for your module and then try putting a couple pictures into the new database and do the same. Compare the two and you can then manipulate the old database text file to add the new values you need and simply import it into the new database using phpadmin. Very important to make sure you have the data backed up if you are not sure what you are doing but it shouldn't take too much effort if you understand how it should work.

Rodney

I am currently working on updating the email system in 2.6 and my next project is cleaning up the authentication system and hopefully making it easy to add new systems so assuming I am successful it will be possible to add something like this.

Those errors would be simple to get rid of but I suspect since you updated from an older version something didn't transfer over correctly.

A couple things to try before continuing.

Did you clear your sessions and caches?

Sometimes old stuff gets stuck in those and you don't see updates until they are rebuilt.

I don't currently have a 2.5.6 test version installed but I believe there is an option in your admin to do this.

Also, you MAY end up having to try the upgrade again.

I suspect if cleaning the cache and sessions doesn't do it then your upgrade may not have updated the database.

If it is not something you can resolve easily quickly I can likely help you out next weekend. (I have too many projects due this week.)

How many pictures do you have? Would it be feasible to load your module from scratch and reload the pictures?

And hopefully you have a full backup of your system before you attempted upgrading?

Rodney

Since this thread is already here... Can you give a brief mention of what you mean by a two factor authentication? If added it would be a 2.6 version addition and there are many updates still to come with 2.6.

In my limited time (Spring Break!) I am working on small projects to help move 2.6 along until I complete my semester and can work on some bigger projects(Profile, Protector and others).

At the moment I am working towards pulling the conventional mailer from the core and moving it to a new system Richard has recently added. This will allow us to provide support for different mailers and I am working on implementing both PHPMailer and Swift into this new system.

While I plan to expose the whole mailer to the system I need to build a common set of functions as well that will be used by most any module or system. In the XoopsMultiMailer there is a function called SmtpSend that will send an email when given a header and body. Are there any other options we need?

Thanks!

Ps, the intent is to provide a system that doesn't care which mailer is being used and let the admin use the mailer they prefer to use.

With a slight modification of the code you should be able to accomplish what you want as long as you have a field for it to sort on.

If all you want to do is sort by the country and you have one field you want to sort it on you could modify the database query to do this very simply. I do not know the module myself to do it for you but if you are getting the list you want and you have the fields available at worst it should be a simple modification to get what you want.

Yes, there are some very cool things coming to Xoops...

This and the Service Manager are big upgrades. The addition of the Service manager has me rethinking some of my projects because they just became much simpler.

Rodney

Some pointers for you...

The actual code you want to install is included in the zip file under the directory "htdocs" you want to create a folder on your server that will be your base site and it is a good idea to use a simple name you can easily remember.

On my server I use for testing my 2.5.7 installation:
c:\wamp\www\x257

So with this I take the contents of the htdocs and copy this to the above mentioned folder.

This will allow me to go to the site by using the following URL:

http://localhost/x257

In your setup it looks like you copied the whole zip file over so you will have to access with the URL:
http://localhost/xoops-2.5.6/htdocs

Within this htdocs directory you have two folders as mentioned by Mamba. These are the folders refered by the settings you mentioned so in order to use them you would have to do the following on your system based on your settings:

move contents of C:/wamp/www/xoops-2.5.6/htdocs/xoops_lib to:
C:/wamp/richlib

and move the contents of C:/wamp/www/xoops-2.5.6/htdocs/xoops_data to:
C:/wamp/richdata

You won't need the xoops_lib or xoops_data folders any longer since your richlib and richdata are used in place of them.

This should all be spelled out in the documentation Mamba provided links for.

Rodney

Although this will hopefully change with 2.6 currently you do have to do the full install yourself if you are not using an automated system. You COULD do an upgrade from the version installed from your provider as well if you are not totally comfortable with that.

As far as modules go you need to make sure you inspect the contents of the zip files. Normally they contain an htdocs directory that contains all of the code you need to copy to your installation.

But of course this should all be spelled out in the installation and operational documentation for xoops.

Rodney