New 7.x Problem?
Category Lotus Domino
I have a 7.0.2 Domino driven web site that pretty much runs on its own without much interaction from my limited admin skills.
Today I got an email from a user that the <<Previous>> and <<Next>> navigation commands were working on two of the discussion forums main indices.
So I started to investigate. I found that the two forms only had one thing in common that did not correspond to the other forms...their views were embedded in a computed subform and the 'navigation' links were held in a different computed subform. This design has not changed in over two years...and I don't know how long this problem has existed, but I am betting that it is a regression bug that has appeared in 7.x somewhere.
It was an easy fix however, I simply deleted the computed subforms and placed the two subforms on the form directly and the problem disappeared.
Anyone seen this or know of a technote before I phone it in?
Update - BTW, the error message that the user received when clicking the nav links said '@Function not allowed in this context' and only occured when the user was anonymous...once they logged in the problem went away.
I have a 7.0.2 Domino driven web site that pretty much runs on its own without much interaction from my limited admin skills.
Today I got an email from a user that the <<Previous>> and <<Next>> navigation commands were working on two of the discussion forums main indices.
So I started to investigate. I found that the two forms only had one thing in common that did not correspond to the other forms...their views were embedded in a computed subform and the 'navigation' links were held in a different computed subform. This design has not changed in over two years...and I don't know how long this problem has existed, but I am betting that it is a regression bug that has appeared in 7.x somewhere.
It was an easy fix however, I simply deleted the computed subforms and placed the two subforms on the form directly and the problem disappeared.
Anyone seen this or know of a technote before I phone it in?
Update - BTW, the error message that the user received when clicking the nav links said '@Function not allowed in this context' and only occured when the user was anonymous...once they logged in the problem went away.
|
Permalink
| Comments (1)
| TrackBacks (0)
Bookmark :
Comments
Basically the subforms weren't marked for Public Access and even though they were displaying to Anonymous users, the code wouldn't run (for reference the underlying form was a Public Access form.)
Rebuilt the form to its original structure, marked the subforms to allow Public Access and everything is fine.
It is still interesting that the Non Public Access subforms were displaying to Anonymous Users though.
Posted by Andy Broyles at 06:16:09 PM on 01/31/2007 | - Website - |