||Capture a photo of the user by utilizing a camera in the users device. This could be a mobile phone, a tablet, a laptop or a standard computer with a USB webcamera.
||A simple editor allows the user to center and zoom the photo before accepting and storing it. The editor supports both mouse and touch, if available on current device. If both mouse and touch hardware options are identified the user can switch between them. The touch functions include pinch-zoom and double finger move for quick editing.
||The module comes with two standard skins - the DnnBro blue skin and a grey skin. If the module should adapt to your specific color scheme a custom skin can be chosen - and you can define the colors of the module (see guide for details).
||The module can be used in two different modes - capure photo of the user or display photo from session, database or userprofile.
|Multiple storage types
||You determine where to store the captured photo. It can be stored in the session e.g. for use elsewhere in the site during the same session – or perhaps by a different module.
Specify the name of the session variable to store the photo in. This can be relevant if the photo is to be used in another module that requires a specific variable name.
The captured photo can be saved to the current users DNN profile, which will require the user to be logged in.
The captured photo can be saved to a table in the database for later use – and there is an option to allow multiple photos to be stored for each user if desired. Only the latest will be shown by the view option though.
To enable this the Require UserId option must be checked. This can also be used to ensure that a UserId is present when storing the photo in the database, as a safeguard in case the module is added to a page that is open for everyone.
If only a single photo should be stored for each user in the database just untick the Allow multiple photos per user option.
||Define your own header which is shown when capturing the photo.
|Image format type
||You decide which image format type the photo should be stored in. It will be converted on the fly when the user saves the photo after editing. Supported options are:
||You decide which image format should be used. If the camera does not support the format the captured image will be cropped to support the chosen format before the captured photo is shown for editing by the user. Supported options are:
||Input the desired width of the stored photo - the height will be calculated automatically based on the chosen image format.
The photo is scaled to the desired size after editing, so the capture and edit window can be bigger than the resulting size.
||Enable this to allow the user to go in fullscreen mode when capturing and editing the photo.
|Switch camera option
||Enable this to allow the user to switch between all installed cameras if more than one is available. If only one camera is available the button will not be shown.
|Touch functions option
||Enable this to allow mobile devices to use touch functions for zoom and move when editing the photo (pinch-zoom and double finger move). When this is enabled the slider for zoom will not be visible.
|Touch override option
||Enable this to show a switch-to-mouse button when in touch mode, to allow devices with both touch and a mouse to switch between each mode. If Touch functions are disabled this will automatically be disabled as well.
|JS Console debug option
|Disable options in web.config
||If needed some of the available StorageTypes can be disabled. This could be a relevant scenario in a multisite environment where the database storage type is not desired – or if the individual site users are not allowed to use the built-in SQL connection.
To adjust which storage types are available the web.config file must be altered manually.
||The module integrates with the DnnBro BrainBreak module, allowing the user to solve a puzzle based on a captured photo from this module.