DDE does disruption (2)

For some reason I was unable to open JavaScript libraries in the JS editor in DDE. It concerned both client- and server-side libraries. LotusScript and Java libraries I could open just fine.

The only thing I could see was this:

The problem was not concerned all databases, but at least the problem was consistent in multiple NSF’s. Building and refreshing the project no effect. Also removing the applications from the workspaces, restarting DDE and re-opening the NSF’s did not change the editor’s behavior.

At this point I was getting a bit annoyed. Colleagues reported similar problems in the past but none had a suggestion other than re-installing the client.

So I let my stubbornness win and installed Feature Pack 9 instead. After 10 minutes (!) the installation was complete so I started DDE and opened the unwilling script library. Hurraaaah! The problem was solved, I could see the code in the editor.

However I noticed some missing in DDE: the nice Swiper 2.0.1 toolbar buttons where gone! So I removed the files from the notes/data/workspace/applications folder, downloaded Swiper from OpenNTF again and installed them. Back to normal. Well not quiet yet.

When working on an XPage I noticed that all the plugins I was using where not recognized anymore. For example the Debug Toolbar plugin. Again, I could not see the plugin disabled under Application Management. So I removed the files, downloaded the plugin from OpenNTF and re-installed it. Now the plugin was visible again in DDE.

So the feeling I am left with is that this Superhuman Software is not so Superhuman anymore.


One thought on “DDE does disruption (2)

  1. Hans-Peter Kuessner (@q_esel) 2017-August-30 / 2:50 pm

    To help against the first problem – no SSJS editor in DDE – there actually is a interim fix for feature pack 8 (or is that an interim feature to fix pack 8? 🙂 – i love those naming conventions :-/ ). We had the same problems, and also have seen that at customer sites: it is a bug introduced with FP8, and obviously fixed in FP9.

    Installing the fix – 901FP8SHF216_W32_standard.exe – should solve that without the need to install FP9, if that is not possible to use for some reason.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s