Navigator Dojo Error Causing Plugin to not function nor do the actions display
I have a plugin that has been coded and tested and works in a number of different version of Content Navigator. We have a client that cannot get the actions, the viewer or any other functionality for the plugin to even display or be invoked. Our plugin class uses a static {} reference in the code to output that the plugin has been loaded by the JVM which we see in the System out log, but for whatever reason, nothing (menus, context menus or actions) show any sign of functioning even though the plugin loads in the Plugins Screen. We see an error in the Chrome Dev Tools console window (see attached) and we're wondering if there is something wrong with the ICN install where the actions or any other plugin feature are not getting initialized or invoked in the page. The console and error logs show no output from our plugin yet under normal circumstances, we have some debug logic that will display to indicate the plugin has been invoked correctly. Please also note that typically I have default navigator actions that show up on the search page (i.e. the standard ICN refresh button) but even they do not display. We have confirmed that the the menus, desktops etc are configured correctly in the admin panels.
Update: Please note even when disabling the plugin from Navigator the errors below appear.
Does anyone have any ideas what might be wrong?
Hi -
Can you please confirm the full build level of ICN on the affected environment?
Thanks,
-Mark
Hi Mark,
Thanks for your response. They are using 2.03 fix pack 8
Just a quick update too Mark, looks like the xhrFailed error does appear to be related to the plugin but we can't figure out why. When we deleted the plugin and set the default search result, the default actions do show up. Is there a chance the plugin version is not compatible with the ICN we are using since we know this works in our test ICN.
Thanks, Gary
Hi Mark,
We decided to delete the plugin and reinstall it. After restarting the JVM It would appear Navigator indicates it can't access once of the JS files inside of the JAR.
[2/27/17 10:28:43:334 CST] 000000b5 filter E com.ibm.ws.webcontainer.filter.FilterInstanceWrapper doFilter SRVE8109W: Uncaught exception thrown by filter GZipFilter: java.io.FileNotFoundException: SRVE0190E: File not found: /crawfordtechPlugin/AddToCartAction.js at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor._processEDR(DefaultExtensionProcessor.java:976) at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.processEDR(DefaultExtensionProcessor.java:957) at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:485) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:136) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:97) at com.ibm.ecm.filters.GZipFilter.doFilter(GZipFilter.java:179)
Does Navigator expand the JAR plugin contents into it's own web context in order for the files to be accessed? Could it be a permissions related issue where the JAR is not being unzipped/extracted?
Let me know if I can provide any other information. Appreciate your help.
Thanks, Gary
We managed to find the problem and I thought it would be important to document this here for anyone that was interested. There were a number of things we had to do that may have contributed to solving the problem, so I'll explain our steps. First we had to make sure that when navigator is running via https and it was communicating with another EAR file to load the JAR, we did enable https in the site hosting the plugin JAR. I don't know if this was required, but it may contribute to issues. Make sure the certs are installed in both EAR locations. The main issue we found was we identified a Plugin section in the Desktops of the Navigator Administration. It appears you can configure Plugins to be enabled within each desktop, a new feature in Navigator but it's not very intuitive to find or to use. Ends up our plugin was not enabled for the desktop we were testing with, but we still received errors in Navigator indicating it could not load the contents of the JAR. This was very confusing. I believe a change should be made to Navigator to make sure no plugin features can be used in Menus, Viewers etc when that plugin is not enabled. In addition, Navigator should report something in the UI or in the logs that inform the user that when a plugin is not enabled if they allow you to choose features from the plugin even though it was disabled. This little checkbox cost us many days of labour trying to understand what was wrong. Just keep this in mind the next time you are trying to use the plugin but can't understand why features won't work.
Sorry, I meant to open a PMR.
Can you please open a collaboration for this problem? And can you please upload the customer's plugin?
Hi Jon,
Can you tell me what this means, "open a collaboration"?