I hope I'm posting this (probable) bug report to the correct place. If not, please relocate it.

I have been trying to upgrade my site from 2.2.4 to 2.3.3. I am testing the upgrade on a duplicate of my live site, fortunately, because I've run into a serious problem, which I now believe must be a bug.

What I did was this: I've actually tried this four times now with the same very reproducible problem. The last time I was very careful, as follows. I made a separate folder into which I copied all my 2.2.4 files and folders. I made a new database and copied all the tables from the live site to it. I edited mainfile.php on the duplicate site to reflect the appropriate database, user name, password, and paths to xoops. I then tested the duplicate site. It functioned normally. In particular I could search for members via profile/search.php and find all the correct hits. (The significance of saying this will become apparent). I then uploaded the ugrade files to the duplicate site, followed by running checksum. All files were fine. I then moved xoops_data and xoops_lib out of the server root. I ran the upgrade scripts, including copying over the replacement folder for Protector. There were no problems reported with the upgrade. I updated the system module, PM and Profile modules. In the most recent upgrade attempt I did not update all modules and I didn't activate various blocks. However, on previous attempts at this I have.

Now, the problem: When I search for users using profile/search.php I don't get all the appropriate hits. For example, if I search for my own entry, using any of various fields (e.g. user name, member number or last name, the last two being custom fields, I do not find my admin entry. I do find a couple of other entries with the same last name. If I search for = cole, I should find 5 users, 3 named Cole and two names Coleman. In the 2.3.3 site I find only two Coles, no Colemans. There are many other such examples.

I can log on using my admin user name and I can find the correct number of hits if I search via the admin find users function. The problem lies specifically with the Profile module's search function (search.php).

It is crucial for our site to be able to find all of the members correctly. We use the profile module to keep track of our member roster and for generating member lists, etc. I simply cannot upgrade until the Profile module is working correctly. I find it peculiar that searching via profile/search.php finds some matching entries but not others.

I would appreciate advice on how this might be fixed. I believe it is a bug in the Profile module. As the upgraded site(s) at this point are duplicated test sites I can provide access to them for any of the XOOPS programmers to evaluate the problem.

Looking for help,

Barry Cooper

Quote:

Why did not you said that before, give me access please.

Trabis,

I did indicate that I could give access in my second message, replying to the first response in the other thread. I started this one as new thinking this might be a bug. Anyway, I have PMed you to let you know a user name and password that will give you admin access to one of the two 2.3.3 installations I mentioned. This is the most recent, carefully done, update. It is bare bones but illustrates the problem. Please also see my post at this link in which I describe the tests I did on the database. If you need other information from my database we can talk about how to do that.

Thanks,

Barry