Nick Connors 17.Aug.12 01:49 PM a Web browser Application development 8.5.1 (Lotus Domino) All Platforms
We ran into an issue recently when we enabled the folder navigation feature that was returned to the 8.5.1 QD product. According to the instructions, the following applied to us as we do have several entries extending the widget registry:
2b. If this file is not empty, you will have to merge the contents of the file widgetRegistryConfig_ext.js_FOLDERNAV into widgetRegistryConfig_ext.js. widgetRegistryConfig_ext.js_FOLDERNAV is located in the same directory as the widgetRegistryConfig_ext.js file.
So all we should have to do is add these 2 objects to our registry:
However, we have a custom view that shows image thumbnails instead of the default simple list format. We enable this view widget to users of any place by just checking the foldername to see if it contains "Photos" in the name. If it does, then the thumnails view is used. If not, the standard view style is used. I know, high tech, right? So our widget extension registry had this entry already:
When we merged the folder navigation into our file, regardless of the order, our custom view would no longer work. Apparently the 'globalreplace' must take precedence over anything else. We were able to fix the issue, so I figured we share it in case any of you run into the same issue.
Peeking into the widgetRegistryConfig.js files (not the _ext version), we could see all of the entries that set the quickr.widgets.view.library and quickr.widgets.view.index view widgets to start. These were subsequently being overridden by the foldernav global replace. So our solution was to just set all of these view types directly to foldernav, therefore bypassing the need to global replace anything. So the portion of our widgetRegistryConfig_ext.js that deals with views now looks like this: