Yeah, as to the entry point, was struggling with that, too. I set it up to /madmin, but … it doesn’t work at [site.com]/madmin that’s for certain. That entry point only works as a handler path once in the admin. So I had to setup an interceptor to even build links. As in [site.com]/cbadmin/module/madmin/home
The interceptor, I’m doing this:
prc.madmin.rootLink = '/cbadmin/module/madmin'; // for links
prc.madmin.rootSource = '/modules/contentbox/modules_user/madmin'; // for other stuffs
Then I can build links off them. This doesn’t work:
href="/cbadmin:madmin/home" (or madmin.home)
The errors, though, are those ASP.net’ish error looks (via IIS), so the colon might be throwing it off. But I couldn’t find any functions that would give me what I needed.
Anyway, I see your point, @lmajano , about “all of cbadmin” requiring a login, that makes sense. Truth is, with the “Contentbox take over everything mode” (that I quit trying to fight), I ended up deleting all my root views and handlers. I simply didn’t need them, nor would they even work.
The truth is, for what I need, if I completely eliminated my services, etc. I can just throw into a straight CFM file. What I did, though, today instead of trying to fight the security, I tied into the Contentbox interception points to fire the reindexing of my Lucene collection:
Hopefully this will reduce the need for the scheduled task. And I threaded it to reduce the delay in saving pages in the CB UI.
Still, even with the “flaws” I’m coming across, Contentbox is awesome. And you KNOW I love Coldbox. (Except for “interfaces”, bwah ha ha. Inside joke for future readers.) You and your team have done awesome stuff, man.