HI,

thanks for your answer. I saw the same message on the RadEditor project : http://radeditor.codeplex.com/

Hope it will be solve quickly.

JB

---

Jean-Baptiste Bouillet Developer - Aricie

Jim, Leslie and Jean-Baptiste,

I'm in this boat with you too. From my research we've all become victims of what appears to be a "shifting of ideas" around the present and future of DotNetNuke's document management solutions and/or core or 3rd-party.

My understanding of the DMX (Bring2Mind) and DNN Corp. relationship is muddy.

Here you can see the CodePlex project that made popular the use of the RadEditor in an RTE as well as document linking from your document management solution.

This project still shows both Bring2Mind and DNN Corp. players listed in the "People" section: http://radeditor.codeplex.com/

Unfortunately, on the home page of that project you see Peter Donker (Bring2Mind) posting the following:

"Important Note: DNN Corp has taken out the DMX Integration as of version 06.02.01 of DNN! It looks like what is here has all become obsolete now. We're looking into this and will try to get a response from DNN Corp how users can get integration again."

Charles Nurse has updated the home page as recently as January 2012, but otherwise I have heard/seen NO activity, support or even comments on the status or relationship of the DMX product, at least, as how it pertains to having an "integrate me" checkbox, or any documentation, specific to enabling support for DMX links in an RTE for DotNetNuke.

Perhaps I'm ignorant (due to being left in the dark, intentionally or not) but I can't help but feel that Bring2Mind may need to produce an alternative RTE (i.e. continue to upgrade the CodePlex managed product, or introduce a version that supports DNN 6.2.3+) OR DotNetNuke needs to make it OFFICIAL that they are going to:

a) Allow ANY document manager to integrate links into the RTE via some plug-in, provider, or other "integration" hook.
b) Allow ONLY DMX document manager integration by re-adding the, what appears to be "legacy" code to do so.
c) Make it official that they are removing document management integration from DNN, except perhaps to their own offering. In which case, vendors like Bring2Mind can at least know for sure that they must maintain their OWN RTE (very wasteful for vendors as they must reinvent the WHOLE RTE on account of wanting a few link buttons).

Whatever the case, this has left a great many DotNetNuke customers very upset. Obviously they too are DMX customers, but I stress *DNN* customers as a reminder that we are one and the same and being left in a bad bind.

In this case, I feel Bring2Mind should have just assumed their integration wasn't safe unless they have some kind of contract that has them expecting otherwise. That way I wouldn't be without an option (assuming they updated the RTE).

OR, DotNetNuke could have made their intentions clearer and/or coordinated with Peter (Bring2Mind) so that one or both parties could have protected their mutual clients. Instead, it feels as though protecting interests around the future of DNN document management may have cause the rest of our fates to hang in the balance.

In my case, a client NEEDS and LOVES DMX. Unfortunately DNN7 is a *requirement* since a bug in 6.x is only addressed in 7. And therein lies the rub.

Good luck everyone else, I'm hoping my "call it how I see it" summary here gets us some action on this. Even if only in the form of expectation setting.

Thanks, Dylan

---

Dylan Lopez - Solution Developer, INNO Software Inc. E: http://www.innosoftware.net/contact.aspx P: 1-888-INNO-001 / 604-628-4467 W: http://www.innosoftware.net

Thanks for the help here, Dylan. As you notice I'm not very active in these forums as the noise tends to drown out the interesting bits.

A little more background for those that wish to know. A long time ago I was contacted by Philipp Becker who was working on the mentioned Codeplex project. He needed the DMX integration for a client and together we made this work and released it to the public. Then (and I can't remember the year/Month), Philipp was asked by DNN Corp if it was OK to use his project in the core. He agreed. Subsequently I got a call from the Corp when they discovered the DMX integration. It was clear that this could not survive in the long run. But the Folder Provider that was just released was not adequate to replace what Philipp and I had made.

This is where readings of what happened diverge a little. I clearly recall that at that point in time I got a commitment from the Corp that they'd improve the Folder provider so I could properly hook in DMX. In the meantime the hook would remain. So I sat back and waited for news while the DMX hook remained in place. And frankly, after a year or so it wondered off my radar. So I was somewhat taken aback that in 6.2.1 the hook was erased without as much as an email in my direction to alert me to this fact. Since then we've been back in touch but now memories have faded and those involved at the time deny ever having made a commitment to improve the folder provider. It didn't make me a happy man, but what can you do? It's gone and we have to live with the limited provider there is.

What is and is wrong with the folder provider? It's a way for the framework to pump folder/files to a component that will handle storage. So far, so good. But it does not pass on any information about security on these items. Nor does it request any security of these items. Security is taken to be handled by DNN, not the component. This, of course, can't work for DMX. When I get a file I need to know who can access it, or it will begin to show everywhere else.

The consequences: the folder provider I've added to DMX 6.1 now has this limitation: all content managed through the folder provider is considered public. That is: if you wish to create a hook to DNN, then DMX only allows you to select public folders. If you change this after the fact, you risk breaking the hook. So keep this in mind. This only works for public documents.

This caveat is, IMO, something we can live with. Most applications are for hooking in DMX to the editor so you can add documents/images to HTML/Text modules. And in 99% of cases, this would be public data anyway. But if we ever want something more advanced, then we have to put pressure on DNN to improve the provider.

Peter

---

Peter Donker

http://www.bring2mind.net Home of the Document Exchange, the professional document management solution for DNN