Hello John, have you tried pulling the current version of 2.6 from GitHub?

There are a lot of changes between the Alpha 2 release last year and the current code on GitHub that is heading toward Alpha 3.

Richard is working on some new items that should make module development much different. You should be aware that as more of the items get finished you should be able to take advantage of them. There is a great effort to maintain legacy support but since you are actively developing you should be aware that things are changing and in some cases dramatically.

Rodney

Is that the site that supports the Java Applet?

I know the last time we had issues with it we went to the site and downloaded the latest and that worked.

There was supposed to be someone working on an Ajax option but I do not know what heppened with that.

When I looked at what they were in the past they didn't seem to be worth using. It IS currently a selection you can make with 2.5.7 as far as I know in the installation program but is removed in 2.6.0. You can always go back and toggle it on in your secure.php file as mentioned by Mamba.

When I converted Doctrine to work with Xoops for 2.6 the persistent connection stuff did not work and when I looked through the support forums for Doctrine it appeared that the PDO library has a much more efficient way of doing things so a persistent connection is not necessary and will actually prevent some functions of Doctrine to work if you try to use it so support for it is non existent for 2.6 but again it is not needed.

In short my understanding is that is creates a connection to the database that never gets closed. The intent is that the performance is boosted with this because you do not need to keep opening and closing the connection. My understanding is that in reality it creates little if any actual performance boost and because you are opening connections you never close it can create a bunch of open threads to the database server. Most hosts limit the number of open threads to the database so you could potentially cause problems on the server so most hosting companies discourage or openly ban use of persistent connections. This is as I understand it when I researched this a few months back so if my memory is accurate this information should be accurate.

Why do you need a persistent connection?

I ask because the library 2.6 is using does not support persistent connections without losing much of the functionality so unless there is a good reason to use it I wouldn't suggest it. Otherwise I would like to hear of why you would need it.

Thanks!

Rodney

My understanding is that the normal convention is to use www to show that it is a web page. Some sites may use ftp. to show it is an ftp site or m. to show it is a mobile site. If you register as xoops.org though you should be able to use www.xoops.org on your site and it should recognize it.

On the same server you could then have an ftp.xoops.org, m.xoops.org, doc.xoops.org dev.xoops.org and many other setups and it would still be based off the xoops.org domain name.

So you SHOULD use the www to prefix your site but you don't HAVE to.

Rodney

I too am a programmer of many languages and the internet has many different issues. The biggest problem is that Microsoft doesn't abide by the standards built by the W3C so their browsers tend to break things that work perfectly in Firefox, Safari, Opera or just about any other browser out there.

And as Michael said, Xoops is a lot better at compatibility between versions than most are. If a module written for 2.0.x series was written properly it can me run with very little modification even in the 2.5.x series and MAY run under 2.6 without issue. And in some cases won't require major rewriting even if it doesn't quite work.

Rodney

You will want to do this on a local host first to insure you can upgrade your main site.

Also before upgrading you will want to remove any unnecessary modules and make sure you can find replacements for your current modules.

You will want to disable all of your modules except system before you upgrade so you don't have any incompatible modules active when you do the upgrade.

Once you upgrade check your theme for compatibility and once your theme is running smoothly then try upgrading your modules one by one and getting them to work on your site.

You may find some of your modules have totally new replacements for them and others not. 2.0.13 is pretty old so you may find you can not replace some of your modules with upgrades and have to go to different modules or not be able to use that module.

All depends on what modules you have installed. Feel free to post what modules and versions you have so we can better help you with your migration.

Rodney

Right now extgallery is the best module available.

You do NOT have to use the Java applet to use this program. Only when uploading multiple files.

There should be a setting that allows for single file uploads that does NOT use that Java Applet.

If you don't get anyone to do this for you I will be available to help you with this after the current semester finishes. I am in Grand Rapids, MI so I am about 2-3 hours drive from you if that matters.

I am more of a programmer than designer and attending school at Grand Valley for a Programming Degree. But I know enough to redesign an existing theme to work if need be.

My semester finishes the last week in April so I would not be available until May to take on a project like this.

Rodney

That sounds like a good plan.

Just make sure you remember to delete the cache files and clear the session data when you move it back and forth.

If you are using windows and install something like WAMP you can try using different versions of PHP which can be helpful when moving from an old system to a new one especially if the old modules have an export option.

The only files you should have to adjust when moving things around are the mainfiles.php and the xoops_data/data/secure.php files.

It is suggested to upgrade to 2.5.6 and when 2.5.7 final is available to upgrade to it. Going from 2.5.6 to 2.5.7 should be painless and require very little if any modifications to anything.

Rodney