Thanks a lot, guys !
This will stop questions in our forums !
it's easiest way to know, from now, which bugs are or are not true.


marco (xoops france)

Any changes in language files???

Humm a lot of correction bugs, great! :D

Be careful in doing this upload and make sure you have a backup of your site first. I just tried uploading the files to a test site and my FTP client for some reason deleted files not found in the upload. Therefore the modules I had installed no longer exist. Lucky it was a test site.

I've seen this happen before and usually upload files a folder at a time, instructing the client to overwrite individual files.

again thanks a lot guys...

"upgraded" from 2.2 so far no additional problems created. Everything works as it did before. Of course there are little bugs there and there that I'm catching on. But in general it's workable. Thanks for the updates and development.

Please ensure if you find any bugs, you submit them here - as it'll help improve things further.

When upgrading from 2.0.13 to 2.2.1 I can't get the profile module to install...

Quote:

This table didn't exist in the 2.0.13 database but it appeared along with sps_profile_fieldcategory.

Deleteing both these tables seemed to fix the problem and the profile module installed.

Going to Extended Proflies-Users-Find Users I now see 0 users. I tried adding the pm module, redoing xoopsupdate, updating the system module again but nothing helped. I still have 0 users. :(

If anyone is interested in hanging out (no support questions) on irc then try irc.freenode.net #xoops.

I've previously tried upgradeing to 2.2 an only obtained blank pages. Now it seems to work, and only need spanish translation (I think it'll soon be available)

Good update - thanks for easy instructions in "News" item.

Question though: after the update, my xoops_footer still shows "XOOPS 2.2". Should it have advanced to 2.2.1? Probably not since there was no update script run. I'll simply alter the database _config record.

Thanks for such a fine program.

my footer still says 2.1 it never said 2.2 after upgrading to 2.2

but how would i go about editing the footer to say what i want it to say?

i followed the instructions for updating from 2.2 (which was running fine) to 2.2.1.
now i get the installation wizard when opening my site.... HELP
what do i have to do ?!

[Thus, to update from 2.2:
- Download the full install package
- Delete the mainfile.php file and the install folder from html/
- Copy the content of the html folder to your site, replacing the old files.]

Ouu, delete mainfile.php and the install folder from install package, no from website.

few, i fixed it (http://www.xoops.org/modules/newbb/vi ... opic_id=39810&forum=1) !
maybe it's interesting to add that last comment to the docs ! me was a little stupid.
loool

I know this might come somewhat out of the context , but... where can I find the values that are loaded to the MySql tables upon the installation of xoops?
Is there any *.sql text file, or the installation loads the values from the *.php files under each language folder?

Thanks

The footer in the admin area confused me for a while too.

You can edit it in Preferences Main »» Meta Tags and Footer

Nobody else having problems with _profile_category ???

I have it running (just one problem so far recorded in another thread and bug report).

I searched everywhere for a note or answer on the following.. where are the official modules for the 2.2.x release? These were bundled with 2.0.13 and I know the FAQ talks about unbundling these in a future release.. but I can't find them as a separate download...

thanks

Mark

Oh God...
Just kill me now...
I had the new 2.2 version all working fine on my site, then saw the new update.
I performed what looked like simple instructions.
Deleted mainfile.php and install folder, overwrote existing files on server.
Now I have nothing showing up.
Zero.
Nada.
Bupkiss.
Simply white.
I think I shall go jab a fork into my eye repeatedly now.

Oh God...

I guess you have "Deleted mainfile.php and install folder on server" which is supposed to be "delete mainfile.php and install folder from the package and keep existing mainfile.php on server".

If so, find back your mainfile.php
If not so, run xoops/recovery.php to enable "php debug" and see what message you can get

I'm still on the 2.013 or whatever the last one was and didn't upgrade to 2.2 is there an upgrade patch that goes to 2.2.1? Based your message, it seems like there isn't, so how do you expect people to upgrade? Are we supposed to download the full package and overwrite everything?

For those who requests/einquires about X2.0* to X2.21, hope this explains something

Quote:

nope - I kept the mainfile.php on the server - I deleted it from the package. That's what I mean... it seemed very simple. I generally don't have any problems whatsoever with a XOOPS install or upgrade, mainly because I am such a moron when it comes to the code I am very careful to read the instructions carefully.
I tried to run recovery.php (by that I assume you mean type my address and add /recovery.php to the end of it) but it did nothing.
Here - see for yourself... http://www.mustangsallys.ca/recovery.php
I'm a blank.
I may have to do a complete re-install and re-write of my site.
<sniffle>

Quote:

I need know this too.

Big problem here... but probably solvable by somebody cleverer than me. I followed instructions exactly as described. Recover.php info below. Help me Obi-wan, you're our only hope:-

Notice [PHP]: Undefined index: enable_badips in file /home/content/m/a/r/mariners/html/xoops/html/class/xoopssecurity.php line 212
Notice [PHP]: Undefined index: language in file /home/content/m/a/r/mariners/html/xoops/html/include/common.php line 152
Notice [PHP]: Undefined index: language in file /home/content/m/a/r/mariners/html/xoops/html/include/common.php line 172
Notice [PHP]: Undefined index: use_ssl in file /home/content/m/a/r/mariners/html/xoops/html/include/common.php line 183
Notice [PHP]: Undefined index: use_mysession in file /home/content/m/a/r/mariners/html/xoops/html/include/common.php line 185
Notice [PHP]: Undefined index: use_mysession in file /home/content/m/a/r/mariners/html/xoops/html/include/common.php line 206
Notice [PHP]: Undefined index: language in file /home/content/m/a/r/mariners/html/xoops/html/kernel/module.php line 318
Notice [PHP]: Undefined index: banners in file /home/content/m/a/r/mariners/html/xoops/html/include/common.php line 235
Notice [PHP]: Undefined index: debug_mode in file /home/content/m/a/r/mariners/html/xoops/html/include/common.php line 235
Warning [PHP]: in_array(): Wrong datatype for second argument in file /home/content/m/a/r/mariners/html/xoops/html/include/common.php line 235
Notice [PHP]: Undefined index: theme_fromfile in file /home/content/m/a/r/mariners/html/xoops/html/class/template.php line 66
Notice [PHP]: Undefined index: gzip_compression in file /home/content/m/a/r/mariners/html/xoops/html/class/theme.php line 143
Notice [PHP]: Undefined index: sitename in file /home/content/m/a/r/mariners/html/xoops/html/class/theme.php line 401
Notice [PHP]: Undefined index: slogan in file /home/content/m/a/r/mariners/html/xoops/html/class/theme.php line 402
Notice [PHP]: Undefined index: slogan in file /home/content/m/a/r/mariners/html/xoops/html/class/theme.php line 420
Notice [PHP]: Undefined index: theme_set_allowed in file /home/content/m/a/r/mariners/html/xoops/html/class/theme.php line 448
Warning [PHP]: in_array(): Wrong datatype for second argument in file /home/content/m/a/r/mariners/html/xoops/html/class/theme.php line 448
Notice [PHP]: Undefined index: theme in file /home/content/m/a/r/mariners/html/xoops/html/kernel/object.php line 279
Notice [PHP]: Undefined index: theme in file /home/content/m/a/r/mariners/html/xoops/html/kernel/object.php line 280
Notice [PHP]: Undefined index: theme in file /home/content/m/a/r/mariners/html/xoops/html/kernel/object.php line 375
Notice [PHP]: Undefined index: closesite in file /home/content/m/a/r/mariners/html/xoops/html/include/common.php line 238
Notice [PHP]: Undefined index: language in file /home/content/m/a/r/mariners/html/xoops/html/recovery.php line 28
Warning [PHP]: main(//home/content/m/a/r/mariners/html/xoops/html/modules/system/language//admin/preferences.php): failed to open stream: No such file or directory in file /home/content/m/a/r/mariners/html/xoops/html/recovery.php line 28
Warning [PHP]: main(): Failed opening '//home/content/m/a/r/mariners/html/xoops/html/modules/system/language//admin/preferences.php' for inclusion (include_path='.:/usr/local/lib/php') in file /home/content/m/a/r/mariners/html/xoops/html/recovery.php line 28
Warning [PHP]: constant(): Couldn't find constant _MD_AM_DTHEME in file /home/content/m/a/r/mariners/html/xoops/html/recovery.php line 89
Warning [PHP]: constant(): Couldn't find constant _MD_AM_DTPLSET in file /home/content/m/a/r/mariners/html/xoops/html/recovery.php line 89
Warning [PHP]: constant(): Couldn't find constant _MD_AM_SESSEXPIRE in file /home/content/m/a/r/mariners/html/xoops/html/recovery.php line 89
Warning [PHP]: constant(): Couldn't find constant _MD_AM_DEBUGMODE in file /home/content/m/a/r/mariners/html/xoops/html/recovery.php line 89
Warning [PHP]: constant(): Couldn't find constant _MD_AM_DOBADIPS in file /home/content/m/a/r/mariners/html/xoops/html/recovery.php line 89
Warning [PHP]: constant(): Couldn't find constant _MI_DEBUG_MODE in file /home/content/m/a/r/mariners/html/xoops/html/recovery.php line 89

hahahaha - welcome to my world...

TO THOSE WHO DELETE mainfile.php

- I edited the news item, sorry guys
- The recovery procedure is easy:

1) Re-upload the XOOPS installer folder to your site, and launch it again.
2) Fill the config value again
3) Continue the install procedure until the page titled SAVING CONFIGURATION DATA (its has a lot of "writing constants" lines).
4) Do not go further, you've fixed it.

Delete your "install" folder again once its done

Just wanna make sure: There is no need to run xoopsupdate.php or update the System module? It's not mentioned in the News article, but is mentioned in the Docs folder. Or is that for the full install?

Quote:

The notice in the post is for users of 2.2. You only need to update the sytem module if upgrading from older 2.0.x versions.

skalpa.>

Thanks Skalpa and PHPPP!!


Update on test site went smooth. All modules seem to function (except known modules that need an update). I notice that PM and notifications have been added to the user menu!
Nice! Now I can make these items invisible in main menu and keep content and user items apart.

Greetz,
Ronaldus

Only thing:

"2 user(s) are online (2 user(s) are browsing System)" is visible in Who's online.
I prefer not to be shown that some one is browsing in system. Rather call them online with no further specification if they are on main page...

Greetz,

Ronaldus

Anyone to confirm this that the XOOPS_URL is not determined correctly during installation of 2.2.1?

Normally the complete URL is displayed on the page where you have to fill in database-information.

As is was before: http://localhost/twotwoone

As it is now: /twotwoone

When I look at mainfile.php XOOPS_URL is indeed defined as /twotwoone instead of http://localhost/twotwoone

Tested on WAMPP, WIN2000, PHP4.3.3, register_globals on, safe_mode off

EDIT: No bug! Thanks to Mithrandir for explaining me the difference!

Hi all

Just installed 2.2 and had meddled with module.php from kernel to change all system messages to other languages (installing modules uses english language only).

Can anyone tell me if kernel/module.php was changed in this version ? or moduleadmin.php from languages ?

Is core interested in getting module.php altered with different language capabilities ?

Thanks
Fab

For those have a punch of "error" messages:
they are there solely because your site need update.
So, do not hesitate, just go ahead.

Perhaps we should hide those messages since they just confuse people.

Quote:

Hi Core Developper,

Big sorry! Was my fault (I know now - wrong version)!

Thanks und best wishes. You make a great job. Please delete my comments if possilbe.

Ciao! Y.

Thanks to the developers for fixing the PM link issue.

Problem
Bad URL for comments icon: /images/subject/subject/icon1.gif

Solution
Edit modules/system/block/system_blocks.php and find (line 388):



Replace with:

I would just add the following hint. Whenever you have uploaded files and get errors, try reuploading the files at least a second time. Very often my problems have gone away. Upload corruption is very often the culprit.

Cheers

THANK YOU!
Great work, my site go very well
Congratulations

@Yeoman,
I posted that comment not to point to you specificly, but because I saw other users also had ever such confusion.

If it is offensive, I would say sorry to you.

No offence taken here, phppp. All I ask is that you clarify what you mean. I did it (see my earlier post for output), and now I get a mostly blank screen (see www.marinersrugby.com). Any advice appreciated, as I'm new to all this.

Glad to see this...and hope it helps with the security issues too.

I have experienced an issue after running the upgrade and was wondering if anyone else had the same problem or can give me a hand getting setting things straight.

My problem is that after running the xoopsupgrade.php is that the gui and the database have become detached where users are concerned. Meaning that I can not browse, edit, modify or delete users via the xoops gui...because it doesnt see any users. However the mysql dbase still shows and accepts users. Any ideas?

How does one edit the existing users? If you select 'profile' module, go to 'users' tab, there are no users. Under 'edit user' section, the (drop-down) list is blank even though there are many users.

Urgent help,
I update my site to XOOPS 2.2.1 .
First , everything is ok.
Then, when i turn my site from off to on ( at preference ). Then they show nothing both on Admin and front page.

Please help me solve asap.
I dont see any errors showed.

Please urgentlyhelp me....

Kurt

when i login with my id and pass the address change to xoops/error.php?c=1. and do not show any thing on screen...

What does it mean?

Please urgently help me..

Glad to see the work moving forward, well done.

Though I will stick with 2.0.13a for awhile until this 'shake down cruise' is done with 2.2 :)

Thank you very much. Updated from 2.0.13 without problems.
But when I try to "List all blocks" in Admin-Section I get the following PHP-Error:

"Fatal error: Call to a member function on a non-object in /htdocs/mydomain.de/www/modules/system/admin/blocksadmin/blocksadmin.php on line 58"

I did a fresh installation of 2.2.1, I got the punch of error messages mentioned in this thread. Then I ran xoopsupdate.php, I got rid of those errors. Now i am getting the error

Warning [PHP]: main(/home/discover/public_html/language//notification.php): failed to open stream: No such file or directory in file modules/system/xoops_version.php line 215
Warning [PHP]: main(): Failed opening '/home/discover/public_html/language//notification.php' for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in file modules/system/xoops_version.php line 215
Notice [PHP]: Use of undefined constant _NOT_NOTIFYMETHOD - assumed '_NOT_NOTIFYMETHOD' in file modules/system/xoops_version.php line 223
Notice [PHP]: Use of undefined constant _NOT_NOTIFYMETHOD_DESC - assumed '_NOT_NOTIFYMETHOD_DESC' in file modules/system/xoops_version.php line 225
Notice [PHP]: Use of undefined constant _NOT_METHOD_DISABLE - assumed '_NOT_METHOD_DISABLE' in file modules/system/xoops_version.php line 228
Notice [PHP]: Use of undefined constant _NOT_METHOD_PM - assumed '_NOT_METHOD_PM' in file modules/system/xoops_version.php line 228
Notice [PHP]: Use of undefined constant _NOT_METHOD_EMAIL - assumed '_NOT_METHOD_EMAIL' in file modules/system/xoops_version.php line 228
Notice [PHP]: Use of undefined constant _NOT_NOTIFYMODE - assumed '_NOT_NOTIFYMODE' in file modules/system/xoops_version.php line 236
Notice [PHP]: Use of undefined constant _NOT_MODE_SENDALWAYS - assumed '_NOT_MODE_SENDALWAYS' in file modules/system/xoops_version.php line 241
Notice [PHP]: Use of undefined constant _NOT_MODE_SENDONCE - assumed '_NOT_MODE_SENDONCE' in file modules/system/xoops_version.php line 241
Notice [PHP]: Use of undefined constant _NOT_MODE_SENDONCEPERLOGIN - assumed '_NOT_MODE_SENDONCEPERLOGIN' in file modules/system/xoops_version.php line 241


I am wondering is 2.2.1 package a complete one, or is xoops 2.2 supposed to be installed on top of 2.0.13 and then 2.2.1

Can someone help here

I did upgrade but if I select Blocks->List all blocks (../modules/system/admin.php?fct=blocksadmin&selmod=-1&selgrp=2&selvis=2), I see only three blocks (Login, User Menu and Main Menu). Earlier I had all the blocks listed there (such as New Members, Recent Comments, Most Viewed Topics etc.)

Therefore, I am unable to assign the rest of the blocks to left, right or center. Any help will be much appreciated.

Regards

Did you update the system module in the modules administration page?

Yes but no change. Thanks for the quick response. Not sure what else could be broken.

Could you "add" the blocks from the top-left select box?

Before installing that package, plz open modules/system/xoops_version.php and modify
line #653

Change to


If you have installed when seeing the message, change it from you system admin area => meta and footer.

Sorry for the inconvenience.

Hi phppp,
When I click on "add" , I can get to "Blocks Administration »» Add a new block" screen but the name field is non-editable. There is no text box for me to enter the block name.

In other words, no I cannot add a new block. Sounds like you are pointing me to the right direction :) What is next should I do?

--update--
Actually, I checked my test site which has 2.2. that also did not have the name as the text box.

So, I can ADD blocks both in 2.2.1 and 2.2 by entering the name in the title field.

Regards

It is very weird but have you enabled php debug?

Yes. I know. It is weird. Do I need to run xoopsupdate.php. When I do that I get the following:

Notice [PHP]: Undefined variable: ids in file xoopsupdate.php line 11

I know it is too much to ask but if wish I can email you my admin user/pass to you. Sorry for any trouble.

I put my 2.0.13 site in maintenance mode and then attempted to perform the upgrade to 2.2.1. Needless to say, I can no longer log into my site at all as an administrator or otherwise.

Help!

Hi Core Developer,

no offence taken - I ment it seriously. It was really my fault alone in this case. I should have known better, so to say. Thanks for doing that great job!

Ciao! Y.

I am upgrading forom 2.2.0, I have the same error that was stated before, I followed your steps:
1) Re-upload the XOOPS installer folder to your site, and launch it again.
2) Fill the config value again
3) Continue the install procedure until the page titled SAVING CONFIGURATION DATA (its has a lot of "writing constants" lines).
4) Do not go further, you've fixed it.

I had no result, I am still having the long list of errors, so any suggestins?

Wahoo, the update seems to have worked with no problems. Well done to all you XOOPS core people.

Can a couple of rooks get a little assistance here?

Basicly after doing the upgrade per the instructions, it turns out that the administrative interface looses a connection with the users table. Meaning that there are no users listed in the interface, however, if you check the table, the users are there and can still log in or what not.

Thanks in advance.

I was having problems upgrading from 2.0.13 --> 2.2.1 but I have now achieved it on 2 of my sites.

One proceeded without major problems (only blocks not selected for display on the front pages).

The other site was causing problems with the profile module not installing. It turned out that my database had a table called 'profile' which was causing problems. This may have come from an old module but I can't find it. When this table was deleted I had no problems upgrading.

I've recently found that IRC can be a very good way to communicate. If we can get more people using this channel we can add to the xoops community created by this site Mambo, drupal and other CMSs have active IRC channels - why can't xoops!

http://www.hyperpod.net/modules/ircmod
or
irc://irc.freenode.net/xoops

Looks like I found a minor bug:

If the private messaging module is not installed then /modules/profile/admin/field.php brings up an error referring to :

$fields[$i]['module'] = $modules[$fields[$i]['field_moduleid']]->getVar('name');

If Private Messaging is installed this problem goes away.

It is a shame that the profile module does not allow the permission to be set for displaying the user's email address.

I want to set this per group - ie. not display any email addresses to anonymous.

I had a similar error to this:
Notice [PHP]: Undefined index: enable_badips in file /home/content/m/a/r/mariners/html/xoops/html/class/xoopssecurity.php line 212
Notice [PHP]: Undefined index: language in file /home/content/m/a/r/mariners/html/xoops/html/include/common.php line 152
Notice [PHP]: Undefined index: language in file /home/content/m/a/r/mariners/html/xoops/html/include/common.php line 172
Notice [PHP]: Undefined index: use_ssl in file /home/content/m/a/r/mariners/html/xoops/html/include/common.php line 183
Notice [PHP]: Undefined index: use_mysession in file /home/content/m/a/r/mariners/html/xoops/html/include/common.php line 185
Notice [PHP]: Undefined index: use_mysession in file /home/content/m/a/r/mariners/html/xoops/html/include/common.php line 206
Notice [PHP]: Undefined index: language in file /home/content/m/a/r/mariners/html/xoops/html/kernel/module.php line 318
Notice [PHP]: Undefined index: banners in file /home/content/m/a/r/mariners/html/xoops/html/include/common.php line 235
Notice [PHP]: Undefined index: debug_mode in file /home/content/m/a/r/mariners/html/xoops/html/include/common.php line 235
Warning [PHP]: in_array(): Wrong datatype for second argument in file /home/content/m/a/r/mariners/html/xoops/html/include/common.php line 235
Notice [PHP]: Undefined index: theme_fromfile in file /home/content/m/a/r/mariners/html/xoops/html/class/template.php line 66
Notice [PHP]: Undefined index: gzip_compression in file /home/content/m/a/r/mariners/html/xoops/html/class/theme.php line 143
Notice [PHP]: Undefined index: sitename in file /home/content/m/a/r/mariners/html/xoops/html/class/theme.php line 401
Notice [PHP]: Undefined index: slogan in file /home/content/m/a/r/mariners/html/xoops/html/class/theme.php line 402
Notice [PHP]: Undefined index: slogan in file /home/content/m/a/r/mariners/html/xoops/html/class/theme.php line 420
Notice [PHP]: Undefined index: theme_set_allowed in file /home/content/m/a/r/mariners/html/xoops/html/class/theme.php line 448
Warning [PHP]: in_array(): Wrong datatype for second argument in file /home/content/m/a/r/mariners/html/xoops/html/class/theme.php line 448
Notice [PHP]: Undefined index: theme in file /home/content/m/a/r/mariners/html/xoops/html/kernel/object.php line 279
Notice [PHP]: Undefined index: theme in file /home/content/m/a/r/mariners/html/xoops/html/kernel/object.php line 280
Notice [PHP]: Undefined index: theme in file /home/content/m/a/r/mariners/html/xoops/html/kernel/object.php line 375
Notice [PHP]: Undefined index: closesite in file /home/content/m/a/r/mariners/html/xoops/html/include/common.php line 238
Notice [PHP]: Undefined index: language in file /home/content/m/a/r/mariners/html/xoops/html/recovery.php line 28
Warning [PHP]: main(//home/content/m/a/r/mariners/html/xoops/html/modules/system/language//admin/preferences.php): failed to open stream: No such file or directory in file /home/content/m/a/r/mariners/html/xoops/html/recovery.php line 28
Warning [PHP]: main(): Failed opening '//home/content/m/a/r/mariners/html/xoops/html/modules/system/language//admin/preferences.php' for inclusion (include_path='.:/usr/local/lib/php') in file /home/content/m/a/r/mariners/html/xoops/html/recovery.php line 28
Warning [PHP]: constant(): Couldn't find constant _MD_AM_DTHEME in file /home/content/m/a/r/mariners/html/xoops/html/recovery.php line 89
Warning [PHP]: constant(): Couldn't find constant _MD_AM_DTPLSET in file /home/content/m/a/r/mariners/html/xoops/html/recovery.php line 89
Warning [PHP]: constant(): Couldn't find constant _MD_AM_SESSEXPIRE in file /home/content/m/a/r/mariners/html/xoops/html/recovery.php line 89
Warning [PHP]: constant(): Couldn't find constant _MD_AM_DEBUGMODE in file /home/content/m/a/r/mariners/html/xoops/html/recovery.php line 89
Warning [PHP]: constant(): Couldn't find constant _MD_AM_DOBADIPS in file /home/content/m/a/r/mariners/html/xoops/html/recovery.php line 89
Warning [PHP]: constant(): Couldn't find constant _MI_DEBUG_MODE in file /home/content/m/a/r/mariners/html/xoops/html/recovery.php line 89

Can you please advise?

As always great work!

One thing that would be nice for the profile module is picture upload as another kind of field, so users can upload pictures for their profiles for example.

Oh, and the PM module should look more like the phpBB PM site, with the "Inbox XX% full" etc. But I assume it's being worked on ;)

Hi has anyone else had this after 2.2.1 install,
this text appears in the centre block area, I dont have any centre blocks yet

return $form; } ?>

Well I've upgraded from 2.0.13 to 2.2 and ran the install and delete the install folder and now the inbox is gone. So now I'm unable to PM people on the site. Any Suggestions??? right now I'm in the progress of during the update to 2.2.1.

After updating from 2.2 to 2.2.1 now I have some code on the top of my page here's my site so you can see what I'm talking about

Nimrod1: Is the PM (Private Messaging) module installed?

@nimrod

Looks like a file is not uploaded correctly or corrupted, reupload all the files.

Dave_L & Lance_ :

Thank you.

Dave_L yes, :) I did not see the module at the bottom on the page. It was the last one on the list . LOL

Lance_ yes I had to upload the file and folders one by one... it sux but now it works...

Thank you again Guys..

Anybody tried edit groups in this version?!


$Id: groupform.php,v 1.9 2005/08/08 06:29:29 skalpa Exp $

and some comments
1. There isn't modules/system/admin/users/ directory in 2.2.1 distro at all - I have it from CVS-RCs-2.2
2. There isn't modules/system/admin/themes/ directory in 2.2.1 distro at all - I have it from CVS-RCs-2.2 (empty)

It's example of delirium code, packaging and documenting changes

Waiting 2.2.2 ?!

My 2.2.1 Frontier, main page. SiteInfo has "Show admin group" enabled in preferences - where are my admins?

Quote:
What is system/admin/themes? That hasn't been part of XOOPS since I joined in, 2 years ago.

modules/system/admin/users/ is removed in 2.2+ since its functionality is in the Profile module. I'm pretty sure I mentioned that somewhere, but probably not visibly enough. I'll remedy that.

1. See at it

It can be result of CVS-checkout from 2.1 branch from your repository, but it's not important at all, because

2. Properly coded groupform.php must not (sic!) interfere and even see any scrap, which can appear somehow.

Resume: Nobody debug it, nobody try it before releasing this (or probably 2.2.0) version

I think, everybody will get my result on attemot to execute modules/system/admin.php?fct=groups

I have a same kind of problem. Updated first from 2.0.13 to 2.0.13.1 and now to the latest 2.2. Everything went well, no errors, except the module SiteInfo, with mailfunctionality to recommend the site and send mail to the webmaster has gone. It can not be found somewhere. I looked for a separate module with this name on this site to install, but I can not find it. Somebody knows how to solve this????