I think this won't work ... you are trying to allow the as yet unregistered user to exercise permissions they do not yet have.

First get the user registered and with a correct role, and when they log on with that role granted, then use a photo module that has workflow permissions. I believe Ventrian's Simple Gallery would have that kind of permissions/work flow.

You can create a security role which is public and let the user know how to use "Manage Services" to subscribe to that role.

This scenario requires four steps: 1) register 2) Manage Services to select role 3) log off and log back on to initialize new privileges 4) navigate to the photo module to upload images.

I beleve that you can combine the first three steps into one if you use a custom registration module such as that offered by UCanUse, though I have not use it myself.

Personally, I find step 3 above rather distasteful ... I think that whenever any user navigates away from "Manage Services"  that their permissions should be refreshed, rather than only at login. Those should be the two times that a user's permissions are renewed.

---

pmgerholdt

You might want look at:

http://php.resourceindex.com/Complete_Scripts/Images_and_Graphs/Image_Voting/

Do some web searches for things such as "Picture Voting Script", "Image Voting Script"

I know of no such module for DNN but that does not mean you cant do it. Most hosting companies have PHP on IIs servers so you can run PHP.

MANY however may NOT have mySQL hosting (some do, some do at additional expense) and many PHP scripts require mySQL.

There is a whole world of software out there in PERL and PHP that it seems DNN'rs often forget. MANY of these scripts will happily exist in the IFrame module. So, you take your PHP script, slap it into a generic HTML page, take the URL of said page and use that along with the iFrame Module.

You can control permissions at the page or module level within DNN so say an annonymous user cant get at the page due to DNN role being set to registered users only.

There are some positives and negatives in doing things this way.

Positives are in many cases you can offload work off DNN and do things that DNN modules (and or incompatibilities of modules vs DNN release) wont do or wont coexist with your current DNN install version.

Downside is that many a PHP module wants a login/password. For example, a picture gallery with user ratings will need to assign a userID and password more than likely so your users would need "sign up" into it. This is something I have been looking into. Joomla/Mambo CMS (which I have a good degree of comfort with) for some items such as PHPBB (probably the most popular forum software in existence) simply has a bridge between the two app's. I've been playing a little bit with bridging and DNN.

the mySQL requirement for many scripts can suck or be of benefit depending on really the application. For example, a high traffic site that lets say allows uploads/downloads of whatall, mp3's or a script archive is often best distributing the computing. You could for example slap that portion of the site out on a completely different unix host, interface to it in a DNN iFrame and its essentially transparent to the end user.

In a site we are creating we purchased a forms module that was a disaster yet it stated it would work with DNN 4.4.1. I started working on a forms module which I am still working at. But, the site needed something NOW. Since we already had Coffee Cup's Flash Forms we decided to use it. The forms are created as seperate HTML pages and put in iFrames and access to them controlled at the page/module level via DNN roles.

We then decided to even go a step further... We wanted the ability to show flash video's etc. Again, we already had Coffee Cup's Video Player. Its nice as it does not rquire a flash server etc and it streams. We gave it a go, works perfectly. Again, same thing. We put it in a seperate HTML page, encapsulate the page in a DNN iFrame and can control access to the page/iFrame via DNN roles.

DNN is an extrordinarily versitile framework. From alot of reading in the forums many folks seem to think they are limited to modules and they are not. There exists a whole universe of Perl and PHP code that works just fine and it can be an excellent way to offload work. You can buy say some linux hosting for dirt and offload work to it. This is exactly what we "plan" on doing with the video the site we are working on. A cheapo $5 a month linux server that will send the video files to CoffeeCup's Video Player which just sits again in an iFrame. Effectively it takes 99% of the work of feeding the video to the end user off DNN and the DNN server. If need be as the site grows its membership we can just get another cheapo linux host account and offload some more.