From /Admin/ModuleDefinitions/EditModuleDefinition.ascx.vb (this is from my memory):

If ... AndAlso Request.IsLocal Then

is part of the logic as to whether or not to show the hyperlink to create a PA module.  But this screen is only available to users with the host level of access. Isn't there already enough of a trust level imparted by giving a login host rights that we should allow them to create a PA module from a given module definition. I bring this up because we are frequently developing modules on a staging environment where there are >20 distinct DNN sites with their own IIS web site.  It would be infeasible for us to add the portal alias, make the IIS modifications, and then login via remote Desktop every time we want to create PA a module from our staging environment that we plan to push to production.

I've already removed this portion of the "if" logic from the staging site that I'm working on, but I'm wondering about the reasoning behind the business logic and whether or not it might make sense to push the change back upstream.

Thoughts?

Thanks,
-Eric