Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 400580

Summary:	The content buttons on the main navigator page all result in clone URL action
Product:	[ECD] Orion	Reporter:	Ken Walker <ken_walker>
Component:	Client	Assignee:	Susan McCourt <susan>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	libingw, simon_kaegi
Version:	1.0
Target Milestone:	2.0 RC2
Hardware:	All
OS:	All
Whiteboard:

Description Ken Walker

2013-02-12 09:36:57 EST

For me (varies per person) if you clear cache, local storage and go to navigator page on orion.eclipse.org and press any of the three create content buttons, the only result is the clone URL button.

Comment 1 libing wang

2013-02-12 09:58:15 EST

I also tried self hosting.
1.Clear localStorage(forgot to clear browser cache)
2.Refresh page.
3.Click on Orion sample plugin. Worked.
4.Refresh the page again. I brought me to clone page.
5.Refresh again same thing.

Then I realized I have to clear the browser cache.
I cleared browser cache and did step 1-5 again. Same result.
I am sure that after clearing browser cache, for the first several times I could not reproduce 4 and 5. But when I tried to confirm that again, every time I could reproduce 4 and 5.

Comment 2 Susan McCourt

2013-02-12 16:40:54 EST

I don't observe the problem.  When I fixed bug 400227 (NLS'ing the task strings) I had to change the code flow to account for all the NLS deferreds.  And while I was there, I changed some 
  for (var i=0; i<foo.length...
stuff to
  foo.forEach(

So I believe the bug could have been there, but I think it was fixed when Gosia reviewed and committed the fix for bug 400227.  I believe you could see it easily on orion.eclipse.org, but not in master/self hosting.  For it to work from master, you need to reload all your plugins.

Libing and ken, can you try reloading your plugins self hosted and see if you run into the problem?

Comment 3 Susan McCourt

2013-02-19 14:34:24 EST

marking this as fixed during RC2, no one has reproduced this since the fix for bug 400227 was in.