OK, it gets stranger.

We have a dev server running the exact same version of DNN and mostly the same modules.  We upgraded events about 2 weeks ago and it works fine.  The production has the will not allow viewing detail or editing problem.

We bit the bullet and uninstalled the module and reinstalled.  The first re-install gave us a bunch of SQL errors for invalid columns.  We installed again and there were no errors.  But to no avail.  The exact same problem.

BUT.... During this, we discovered something else!  We had originally setup the module to be edited by a certain role, viewed by all. We also allowed that role to have edit rights to the module so they could get to the editing dropdown.

As soon as we turned on the moderatin role, it overrode the module's view permissions.  It unchecked the 'inherit view from page' and check only the role that we made moderators!  So... No one could see the module at all, unless they were in the moderator role and logged in.  We reset everything and went through the steps 2-3 times and it did it everytime.

This scenario happens both on the development server where viewing detail and editing is working fine AND on the production server. Seems to be a rights issue?  Maybe related to the view/edit problem?

I would be happen to provide an admin level access to our production portal so you can see it happen.

HELP!!!!!

Me again!

One more thing we noticed.  The development server is running DNN without a qualifier, while we use 'dnn_' as a qualifier on production.

As someone else stated, we can usually work through these issues but no success this time! We give up!

Help!!!

Bob

We can't do that. It runs fine on our dev machine. It's only production. We are running the same DNN, same skins, same events, same everything.

We've deleted it, reinstalled it, we've turned off the skins and used DNN defaults.

What really irritating is that it doesn't generate any errors.

As far as the fact that quite a few folks are running it without a problem, I see three in this thread that have the EXACT same problem.

The only other thing that I can think of is that we are hosted at WEBHOST4LIFE.  How about the other?  You mentioned a rights issue?  But I assume you are using standard DNN calls so everything should work the same as all of our other modules.

If one of the other guys have it broken on their DEV system, maybe they can debug it?

We are currently testing 4.5 and are planning a rollout in about 4-6 weeks.  Of course it is working fine on our dev systems with 4.5

Anymore insights would be helpful.