Yup. Did all of that. Even went and downloaded another core package for 2.3.2b and took out the profile module and replaced the old one with the new one, just in case the old one managed to get corrupted on the download or the install.

Unforunately, same result. However, I did discover that if I elevate the registered user to "webmaster" status, then that user sees his profile when he hits the "view account" link and also sees his profile when he hits the "User Profile" link.

So, the problem definitely has something to do with how my installation views the status of registered users and anonymous users versus the status of webmasters.

Yet, I've turned on all the switches to give everyone an opportunity to view everyone else, but to no avail. In addition, on the "Permissions" tab of the Profile module, I've given permission to everyone to view ("visibility") to search ("searchable by these groups")and to access the profiles of ("Profile accessible by these groups") everyone (i.e., webmasters, registered users, anonymous users), but all to no avail, simply so that I could see that the "view account" and "User Profile" functions for at least registered users would work. But again, nada!!!

Is there anything else you can think of that I might try??? It's become a very frustrating experience and the shame of it is that it is only these two simple functions that are problematic. Everything else works like a charm.

I'd hate to have to give up XOOPS as the CMS simply because of these two wiggles...but if I can't solve this problem, that's exactly what'll have to do.

Even a substitute module or even being able to eliminate profile viewing (except when editing) entirely, would be acceptable as a solution (I'm desperate at this point).

Anyway, hope you can help.

Thanks.

Peter

Sorry, tried all the suggestions that everyone so generously provided, you included, but none of them seem to work.

Is there some other place (besides the Profile module's "Permissions" tab) that I should be looking to try to correct the problem?

If you have any additional ideas, I'd sure like to hear them...

Thanks.

Peter

Can anyone help with the very few remaining hiccups I'm having with my XOOPS 2.3.2b installation?

There are a couple of remaining issues which I just don't seem able to be able to solve. They're relatively small, should be easy to fix, but I just can't seem to do it. Here they are:

1. When any of the normal registered users tries to "view account" or view "user profile", all that comes up is a blank page. (right now we only have two registered users since the site is still in the testing stage). Yet when they go to "edit account" all of their info comes up and is viewable. However, no such problem exists with the webmaster (me). I can "view account", view "user profile" and "edit account" and everything works just fine... What gives here?

2. Second, inside the "administration" panel, when I hit the menu "news" at the top of the panel, I get the following error message: "XmlParse error: not well-formed (invalid token) at line 43".

Here's some additional info:

1. I was previously asked by a XOOPS techie if anonymous users have access to the profile module. I've checked, and as far as I can tell, anonymous users do not have access to the profile module. When they click on the "user profile" link it brings up a login/registration page that they need to deal with before they can move forward onto the site or to view any of that info...

2. At the additional suggestion of XOOPS tech person, I tried using another admin theme (in fact I tried all three, i.e., default, exm, legacy) with the same result.

While I'd like to get a fix for the "news" control panel problem as well, the real issue here is that a registered user is not able to view his/her account or his/her profile unless he/she is trying to edit it. As you can imagine, this is a very BIG PROBLEM for a site open to the computer illiterate general public. In fact, it's such a large problem that it could kill my ability to convince the client to use XOOPS for the CMS.

If I could just get some help on these last two items, the site would be working perfectly and, with that out of the way, I think I could convince my client to choose XOOPS among all other CMS programs to use for her new site, a very large public site used to service inventors worldwide...

If you have any suggestions, I'd sure appreciate hearing them as I've grown rather fond of XOOPS in the meantime.

Thanks very much for any help you or anyone else can provide.

Peter

ghia:

I've installed all the modules that I can find that will work with 2.3.2b so that the client can see the type of functionality associated with each and determine which ones she wants incorporated into her site.

In answer to your suggestions/questions:

1. As far as I can tell, anonymous users do not have access to the profile module. When they click on the "user profile" link it brings up a login/registration page that they need to deal with before they can move forward onto the site or to view any of that info...

2. I'm not sure I understand your second question/comment. The admin (me) has full permissions and except for the "news" menu at the top in the middle of the Administration Panel (the third error I mentioned above), everything works fine as long as I'm in the admin mode.

3. I tried to use another admin theme (in fact I tried all three) with the same result.

By the way, I decided to uninstall the "Downloads" module. Given the tremendous number of modules that do work fine, I'm hoping that the missing module will be relatively unimportant in the grand scheme of things. Even the error message using the "news" menu is no big deal, since only I will see that (it won't be viewed by anyone else).

However, a registered user not being able to see their account or the profile unless their trying to edit it is a BIG PROBLEM and could kill my ability to convince the client to use XOOPS for the CMS.

If you have any other suggestions, I'd sure appreciate hearing them as I've grown rather fond of XOOPS in the meantime.

Thanks very much for any help you or anyone else can provide.

Peter

Can anyone help with the very few remaining hiccups I'm having with my XOOPS 2.3.2b installation?

First of all, XOOPS rocks big time!!!! Here's a list of all the modules I'm currently running, virtually trouble-free:

Home
User Profile
Content
Documentation center
Articles
Small ads
eXtGallery
BmSurvey
inthetube
Google Talk
eXtCal
Event Guide
Edito
DokuWiki
Guestbook
EvenNews
Kshop
Liaise
multiMenu
MyAlbum
Web Links
CBB
News
piCal
Private Messaging
PopnupBLOG
Instant Messenger
My comments
MatchDart
OpenID Auth
Job Listings
Netquery
Contact
iSearch
Marquee
Downloads
iFrames
ForumEx
Logtick

This type of performance is, in my opinion, unheard of in the CMS arena where modules are used and even completely unschooled users are encouraged. Bravo!!! Congratulations to a magnificient piece of work...

However, there are a couple of remaining issues which I just don't seem able to be able to solve. They're relatively small, should be easy to fix, but I just can't seem to do it. Here they are:

1. When any of the normal registered users tries to "view account" or view "user profile", all that comes up is a blank page. (right now we only have two registered users since the site is still in the testing stage). Yet when then go to "edit account" all of their info comes up and is viewable. However, no such problem exists with the webmaster (me). I can "view account", view "user profile" and "edit account" and everything works just fine... What gives here?

2. No matter what I try, I can't change the permissions on the "downloads" module to enable anyone to use it, not even me, the webmaster. I've toggled the permissions several times, but to no avail. The toggle never seems to stick. What's going on here?

3. Last, but not least, inside the "administration" panel, when I hit the menu "news" at the top of the panel, I get the following error message:

"XmlParse error: not well-formed(invalid token) at line 43".

If I could just get some help on these last three items, the site would be working perfectly and, with that out of the way, I think I could convince my client to choose XOOPS among all other CMS programs to use for her new site, a very large public site used to service inventors worldwide...

Hope you can help! And thanks for producing what appears to be such a great program....

Thanks again.

Peter Bell

Hi:

I'm having a tremendous problem identifying those modules which are suppose to work with version 2.3.2b of the core program and those modules which aren't suppose to work with this new version.

Rather than trying each one, one-by-one, is there a comprehensive list somewhere for people who just want to drap and drop the module into the "modules" folder on the server and then have it show up for installation on the core program's "Module Administration" page?

If someone could just provide such a list, I could then concentrate on those modules which aren't showing up but which should show up, rather than trying one-by-one to see whether or not the module shows up in the "Modules Administration" page after I've dragged it into the "modules" folder on the server.

Any help would be greatly appreciated.

Thanks.

Peter

BTW: Here are the modules I've already installed which are working just fine...:

Home
User Profile
Content
Documentation center
Articles
Small ads
eXtGallery
BmSurvey
inthetube
Google Talk
eXtCal
Event Guide
Edito
DokuWiki
Guestbook
EvenNews
Kshop
Liaise
multiMenu
MyAlbum
Web Links
CBB
News
piCal
Private Messaging
PopnupBLOG
Instant Messenger
My comments
MatchDart
OpenID Auth
Job Listings
Netquery

sourceforge site, the recommendation on sourceforge that one use the 2.3.2b version of XOOPS and the implicit recommendation that all of the modules in the module packs can be safely used with version 2.3.2b, it may hurt the reputation of this new version unless the offending modules are removed or someone finds a way to fix them to operate easily with version 2.3.2b.

I'd do it myself if I had the skill sets necessary to accomplish the task, but, unfortunately, I'm still in the middle of the learning curve on php and MySQL and wouldn't be able to produce anything useable at this point.

In any event, thanks very much for your trying to help. I really do appreciate it and I'm really astonished at how quickly I was able to receive a response to my request for help.

Thanks again.

Peter Bell

Thanks to both of you for trying to help me. However, after repeatedly doing what both of you have suggested, I still find that with the following six modules, I still have the same problem. While they are modules that sounded cool and ones that, if they had worked properly on 2.3.2b, I would have enjoyed incorporating into the cite, given the tremendous number of modules available, and also the considerable capabillity of the site without these modules included, I've decided to not try to incorporate them at this point.

The only thing that I think may be a problem for the program is to have these be part of the module packages offered up on sourceforge.

For the newbie, the quickest way to get up and going without having to do a lot of exploration, is to download one or more of the module packs and install them.

Given their presence on the sourceforge site and

Thanks, I'll try that.

Peter

Hi!

Anyone know if there is a limitation on the number of modules you can upload and then install on a single installation of Xoops?

I'm running XOOPS 2.3.2b and I've uploaded (and successfully installed) over twenty modules. However, there are a few modules which, despite my attempt to re-upload and re-install, never end up showing up in the "Modules Administration" page on my website. These modules are the following:

* smartfaq
* smartobject
* smartpartner
* smartsection
* wfdownloads
* xoopspoll

I've tried both default and zetagenesis themes, with the same result in both. Also, I tried to use the "debugging" approach before posting this post, but all that ends up doing is obliterating the site so that I have to go back and restore my files and MySQL database from the backups that the hosting company maintains for me for both.

Any assistance you can provide would be greatly appreciated.

Thanks.

Peter Bell

pbell [at] seomarketsolutions.com