@cmswarrior- The search is throttled to a quarter second of no character entry. If you think it needs to be cranked up a bit, I can do that. I suppose not everyone types as fast as I do. :)
@robinnp - What you're looking to do with a MMDOM is simply not what it was built to do. If you look at the way a MMCTF works, you'll see the same thing. The idea is to give the user a global view of all available DataObjects and allow single-click association of those DataObjects to the page. The objects that are associated with the page should show an activated checkbox and a differently colored row. If the MMDOM were to filter out all the unassociated objects, how would one associate more existing objects at another time? It occurs to me that MMDOM and MMCTF are not the solutions you may be looking for?
yea I got a little confused by this at first, it's because if you extract the archive directly to your root the folder is called modules-dataobject_manager-rXXX/ which means the requirements don't work as they look for dataobject_manager/.
Is there a way to make the requirements more dynamic and pick up the name of the folder automatically? Not a huge issue but might get a some people confused as most modules don't mind what the root folder is called.
Interesting. I think what I need to do is put dataobject_manager in a parent folder so that the ZIP file name does not become the folder name.
Also, to all of you who are using the download, I highly recommend switching to SVN. Updates happen so rapidly to DOM, it's impossible for me to constantly be exporting and posting a new ZIP file to Silverstripe.