Print  
Gray star Gray star Gray star Gray star Gray star --Not rated--
499 Visits 6 Comments
Created
Dick Turnquist Dick Turnquist
Modified by
Peter Hurley (Novell) Peter Hurley (Novell)
Dec 13, 2007 11:19 PM
Kablink Component
  • -- select one --

I'm having an issue where the 'My Teams' dropdown box on the ICEcore Navigator doesn't always work right.  I have some users where all there teams show up, but others where none of their teams show up, and others where some of their teams show up. 

 In my own user profile, I had myself on three teams, of which one showed up.  Then I created another team of which I was a part, and then the list changed to show that team, but not the one before that was showing up.

 Is there some trick to making them show up, or what's going on?

Workflow
Process State Action
Discussion workflow Active
This entry is currently active
Attachments(0)
Entry History
Tags
 
Replies
Thumbnail Image
Peter Hurley (Novell) Peter Hurley (Novell)

The "My teams" list is created using the built-in search engine. I am guessing that this may be an access control problem or an indexing problem. Here is what to do to help figure out what is happening:

First, try re-indexing the whole site. This is done by going to the ICEcore administration portlet logged in as "admin". Click on the menu item to manage the search index. Then on the resulting page select the top workspace and click ok. This will reindex everything. (This should not normally be necessary. It does take awhile to do this if there are lots of entries in the system. However, to help with the diagnosis, we can do this). Once this finishes, see if the teams came back.

If that doesn't fix it, go to each team and make sure you really have access to the team in question.

Another possibility is that your browser is not supportted. We officially support IE 7 and the latest Firefox. Most everything works on IE6. Various verasions of Safari on Mac have bugs that prevent some things from working. If you are on the MAC, try using Firefox to see if it works. The latest beta release of Safari seems to work fine.

Please tell us what browser version you are using. We can try that version here.

Also, could you log in as admin and get the error log files. To do this, go to the ICEcore administration portlet and click on reports. Under this, there is a way to download the system error log files as a zip file. Please do this and post that zip file here. (If you have problems getting this to work, read the help pop-up. Your browser may block this operation.)

 

Thumbnail Image
Dick Turnquist Dick Turnquist

I had tried with several browsers (IE7, Firefox 2.0.0.11, Opera 9.0 - all on Windows; Firefox 2.0.0.11 on Linux; Safari 3 beta for Windows - wouldn't even load the initial page), but they were all the same.

However, when I reindexed the site, that fixed the problem.

Like you say, that should be happening automatically, so if you can find anything in the attached log files, that would be great.

Thanks. 

Attachments
  File Name Version Status Date Size Modified by Actions Edit
logfiles.zip V1.0
Dec 10, 2007  4:37 PM 13KB Dick Turnquist  
Thumbnail Image
Peter Hurley (Novell) Peter Hurley (Novell)

In the ICEcore v1.0 kit there was an access control problem that occurred when changing the team membership of a team. We fixed this in V1.0.1 (a service pack). Can you check your build number and version. It should be Build 850, Nov 6, 2007. You can see this info on the ICEcore administration portlet.

If you are running V1.0, then the problem you are seeing is most likely fixed in V1.0.1. You should be able to get that version from SourceForge.

Let me know what build number of ICEcore that you are running.

Thumbnail Image
Dick Turnquist Dick Turnquist
I show as running 1.0.1 (build 850 / November 6, 2007)
Thumbnail Image
Roy Klein Roy Klein
Modified by
Peter Hurley (Novell) Peter Hurley (Novell)
Dec 13, 2007 11:19 PM

Hi,

 

Did you install 1.0 and then upgrade to 1.0.1?  (Or, was 1.0.1 your first installation?)

We want to know if you started with V1.0 and then upgraded to v1.0.1.  If so, did you perform a re-index operation after going to v1.0.1? If not, there would probably have been some bad information left in the index that would have caused the problem.


Thanks,

Roy (and Peter)

Thumbnail Image
Dick Turnquist Dick Turnquist
5. 1.0.1
Although I had originally installed 1.0,  when 1.0.1 came out, I had put in a new disk drive and reinstalled everything from the OS up.  The only thing I kept from the original install was the installer.xml file.  (And in case you're wondering - yes, the database was running on the same server, and so it was rebuilt from scratch, too.)
Skip Footer Toolbar