Nisus Icons Invade Safari bookmarks

[xenon134]

Ever since I installed NWP 2.0, Nisus icons have appeared in places where they do not belong, such as Safari (5.05). In the Bookmarks Menu, which lists bookmarks folders, the Apple folder icons are replaced by NWP file icons. Though masquerading as files, they still display the folder contents.
The bookmarks icon at the far left of the Bookmarks Bar does the same thing. It opens a sidebar and a main window, as usual. The first 4 icons under "COLLECTIONS" display normally, but when "Bookmarks Menu" is clicked, the main window shows all folders in the disguise of Nisus files. The next group in the sidebar, BOOKMARKS, again displays Apple folders as Nisus files.
The freeware program, X-Menu, also is affected. (It places several menus in the menubar, which can display a "User-Defined" menu that one can fill with aliases of any files or folders, as well as the Applications menu. As in the old Apple menu, that's an easy way to get instant access to any item, no matter how deeply buried.) In the User-Defined Menu, the following file aliases now appear as Nisus file icons: NowContact, Reunion, Moneydance, and PasswordWallet.
Common remedies such as rebuilding the Launch Services database or trashing Safari Preferences have not helped. I have used Nisus software for 8 years but have never seen this problem before. A Level 2 TechSupport technician at Apple said that the problem is caused by Nisus, not Apple.

[Hamid]

It appears to be the same problem encountered here:
Please view this thread:
http://www.nisus.com/forum/viewtopic.php?f=18&t=4271
The solution is to download a fresh copy of NWP 2.0 and replace your copy of the NWP 2.0 app with the fresh one.

Now there is also a public beta of NWP version 2.0.1 available which resolves certain other issues:

http://nisus.com/files/pro/NWP-v201-p1.zip

[martin]

Hamid is correct. This issue was triggered by the first release of NWP version 2, but was quickly corrected thereafter. Replacing your copy of NWP with a fresh one should solve the problem (though you might have to rebuild your Launch Services database afterwards).