FORUM PLAN UPDATE
Date revision: This forum will remain open to new posts and responses until December 1, 2018. (After that date, you will still be able to view and search the forum.) Also, we're taking a second look at the best place to host future conversation. For now, keep using this forum, and stay tuned for more news.


May 5, 2013, 2:35 PM
69 Posts

Issue from beta resurrected

  • Category: OpenSocial - Embedded Experiences
  • Platform: Windows
  • Release: 9.0
  • Role:
  • Tags:
  • Replies: 2

After couple of weeks with everything working I ended up having the Updates widget saying "Loading" forever in Notes. Neither Domino or Connections configuration has been changed in a way it should affect the Updates gadget.

In Notes trace I observe the error

CLPEE6503W: Javascript error from https://mail.televera.com/fiesta/gadgets/js/notes-container.js?c=1&container=default #202
notesdomino_container_preload is not defined

This issue has been already mentioned in beta forum http://www-10.lotus.com/ldd/ndsebetaforum.nsf/topicThread.xsp?action=openDocument&documentId=E4C1239F4961FF9A85257B180077FF7F

Ryan replied that this warning has been fixed but I am running the release version and have this warning in my trace every time I open the Updates gadget.

Embedded experience works fine.

May 5, 2013, 5:15 PM
38 Posts
RE: Issue from beta resurrected
You're using GA version of both the Notes client and the Domino server?

You can trying clearing your Notes browser cache by deleting the <Notes Data>/workspace/BrowserProfile/Cache directory.  Your Notes client may still have old code cached from the beta.
May 6, 2013, 3:24 AM
69 Posts
RE: Issue from beta resurrected

Stanton, yes, I use GA code for both client and the server. It cannot be old code cache since I have been struggling quite a lot to get it working after the upgrade from beta to release and it actually started to work with your help. After two weeks Updates stopped working.


FORUM PLAN UPDATE
Date revision: This forum will remain open to new posts and responses until December 1, 2018. (After that date, you will still be able to view and search the forum.) Also, we're taking a second look at the best place to host future conversation. For now, keep using this forum, and stay tuned for more news.