There's no notation on your post of the XOOPS version. It is my recollection that some XOOPS versions/modules have some issues with php5.

Thanks, JMorris...

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

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.

Yeah, that file, admin.php, is in the language/english file (which is my default language) is there. I'll be glad to entertain any other suggestions. Again, though, no big deal.

I just checked my sitemap at google and noticed the same thing. This is an issue and I would be very glad if someone had a solution that they are using. I don't want to be downgraded by google because XOOPS is reporting 200 when it should be 404.

Go to admin|modules|the "Your profile" module (it must be installed).

Under the "user" tab, you will see near the uppsermost part of the page a section titled, "Edit User." Click the "Search Link". A pop-up window will come up. Search for the user you are looking for. Hit enter. It will reload the pop-up with links for the users it found.

Now, select the user you want, and click add me. You are taken back to the prior page you were at before the pop-up. Now, in the drop-down box, you'll see the name of the user you are trying to delete. Also, it has to form labls to either edit the user or delete the user.

Again, you have to have the User Profile module installed to do this. It is a separate module from the system module...

It is my undertanding that the user profile thing was to be fixed in the next versions. I think it was hoped that it would be fixed pretty soon. But when 2.2 didn't go as planned, those who were using 2.2 were stuck with this extraordinarily convoluted method (other words may come to mind) of managing users. Having said that, the recognition is there that everyone is doing what they can. And, I can certainly live with that. Anyway, I hope that this helps. Someone else may have a less abstruse method of doing it but this is the only one I've heard about or found.

I'm getting this, too. I have for some time. I've reuploaded language files a bazillion times. It probably doesn't matter that much except that it sits there, screwed up. I did a search and found this post. Truly, this page (System Configuration) isn't used much in 2.2. But, still, I'd like to see it fixed if anyone has another guess as to why it's not working.

Thx

None of the following constitutes a recommendation, nor is that any promise of support if it screws up. But, for my money, I would do the following course of action:

1) If you made a backup of your site before the autologin hack was applied (you did do that, right?) I personally, on my site, would reupload that backup. Now, clear the cache, clear the templates_c directory, go to admin|modules|system and update that. See if it works right now.

2) If it still does not work right, I would reupload the core (except the theme directory) and module files that you are using (assuming that you have not made any other hack changes). Now, clear the cache, clear the templates_c directory, go to admin|modules|system and update that.

3) If you made a backup of your database before you implemented the autologin hack, and you are tired of messing around with all this, you could delete your current database and put your old database (the backup) back up on your site. Of course, you'd lose the stuff from however long it has been that you've been working on this issue. This is not something to be taken lightly. But I have done it a few times. It's roughly akin to reinstalling windows from the ground up... I'm not recommending this, especially if you are, uhh, new to phpmyadmin. But, if you statements about ditching the whole site are accurate, perhaps it's time to take the chance. Due to extended time off, I can't add any further help to this reply. Others may be able to help. It may be best for you not to take this last step. As I said, I have done it with success, but it does take a degree of familiarity with mysql.

An additional "not worth a dime" suggestion: Get a book on php and MySQL and perhaps webmastering. You'll save yourself a bunch of time and agony.

Thanks, comflash!

After several attempts at installing this mod and getting blank pages each time, this solved the problem.

Personally, Mandlea, I like the feature. I would like the option to disallow users to change their displayname for the reasons mentioned above. But, frankly, the value of the approach XOOPS has taken to securiy is one that has been hard earned, as anyone who has been around here for a few years can attest. The new approach makes common sense to me, your mathematics and quotes from someone you chatted with on IRC notwithstanding.

Nonetheless, I'm glad you brought up the change for examination and hopefully the feature will be adjusted somewhat as noted above.

At the same time, is this one feature really so odious that it brings about all this angst and anger? You have suggested a change. It has been heard. If you really care about your point, you might choose to make friends, not enemies. Or, perhaps, you could move on to another CMS (since you are familiar with their features). In any case, your approach to this discussion has won you, and, perhaps your argument, few friends. In this sense, perhaps you could learn something from this discussion: Having made your point, you devalued it. Learn to back off a bit. You said you are young. This is a good time to learn.