I have realized since iniating my production site (2.2.3) a few months ago that indeed a number of of the modules do not owrk correctly or are difficult to install under 2.2.3.

It seems that I would be better off with the more stable 2.0.13.2.

I understand the concept of applying patches to upgrade to the most recent version. I have not been able to find a descrition of a way to roll back a site to an earlier more stable line. (2.2.3 --> 2.0.13.2)

I don't mind copying and pasting the existing pages. I am more concerned about maintaining the registered users already accumulated.

I had in mind installing 2.0.13.2 as a new website

webroot~/xoops-2.0.13.2/

copying the involved pages from the original site

webroot~/xoops-2.2.3/

to the new site.

Then transfering the users from the first installation to the second installation using a PHP script and a couple of SQL statements:

Select user1 from xoops_users-2.2.3;
Insert user1 into xoops_users-2.0.13.2;

I would appreciate information on a recommended rollback procedure or other addittional thoughts on this matter.

You may want to check out the comments in this article. From what I understand, using the hack that is referred to in that article, 2.2.3 will roll back. From my experience, though, 2.2.4 will not roll back using that hack (unless I made an error, which I will allow as a possbility may be the case, though I don't imagine how). I would love to roll mine back at this point. I wish the hack was updated or someone else had figured out what the errors were that I noted on the rollback hack. Anybody have any ideas about rolling back 2.2.4 and the error that was noted about block functions?

Anyway, I hope that this helps.

Chappy,

You may want to contact jdseymour. If I'm not mistaken, he has performed a few downgrades and may have some useful advice.

Best Regards,

James

Thanks, JMorris...

BTW, you'all are doing a heck of a job trying to get things back on track.

Thanks! We just want to keep a good thing goin'. Well, that and we're addicted to XOOPS.

Best Regards,

James

Quote:

I'm with you on that. Been here since 2003. Though I can't spend as much time here nowadays, I get by usually several times a day. One of the first three places I go when I get the chance. It's a lot happier place to stop by when folks get along.

I appreciate the feedback. I especially appreciate the link to the earlier discussion of 2.2.* and 2.0.*. It still represents a tough decision: “To rollback or not to rollback, that is the question. Whether tis safer to hold tight and wait on 2.4 or to rollback to the stable branch 2.0.13.2.

I t explains a lot. I was having a lot of trouble getting many of the features on the modules to work and this explains why.

I installed wiwimod, tiny content, cjay content, and newBB. Many of the features were broken and while I got newBB installed none of the users could access the bulletin board. I have not yet been able to figure out how to grant the registered users access.

I have installed both 2.2.3 and 2.0.13.2. Having the most commonly used modules already pre-installed is very useful. From the viewpoint of a new/inexperienced XOOPS administrator I wish I had seen the instructions about 2.0.13.2 being the stable production version before preceding with my first installation.

Any wild guesses about when the two forks will merge back together into 2.4?

You can follow the progress of XOOPS 2.3/4 at the following site.

http://devteam.xoops.org/

You may want to take a look of Skalpa's roadmap there.

Hope that helps.

James