Documentation Code Camp Events General
<< Back to Code Camp Events Documentation
The Code Camp Events module is built to be a "single page application" or SPA-style module. This allows you and your visitors to get instant feedback when interacting with any of the features available to you.
When installing this module, please note that there's nothing additional you need to do. It simply installs and performs all necessary configuration on your behalf, with the exception of things that require your input.
When you add this module to a page, there's nothing special that will need to be done. The module will prompt you for what it needs.
Some of the cornerstones of a typical open source community/project include transparency, communication, and honesty. This module attempts to apply that philosophy to how it operates for you and any visitor to your event's landing pages.
As an example, this means that any speaker that submits sessions is automatically shown on the site, including all of their sessions. Once you choose your sessions and save your event's agenda, any unassigned speakers/sessions will no longer be shown on the site. Another example is the ability for visitors to "vote" or express interest for sessions that they intend to attend. However, this also helps you during your planning, and especially during the speaker/session selection process.
When adding this module to a page, please note that this module is currently built using Bootstrap version 3.3.5. Your theme (skin) MUST be compatible with this version of bootstrap, but you should remove all references to including Bootstrap from your theme page. This is often done by creating a copy of an existing theme page, and deleting the lines of code that include the Bootstrap CSS and JavaScript files. This will only be necessary until DNN Platform includes the ability for you or I do do this in a more user-friendly way.
This module will then include the Bootstrap files on your behalf. This is necessary due to the large number of Angular and Bootstrap dependencies it requires for the user experience you'll enjoy, as these dependencies all need to be added in a specific way. Allowing you to do this in the skin/theme will only make using the module a bit more difficult and time consuming.
It's highly suggested that you add the module to a page that's not accessible by the general public. Then, perform as much configuration as possible prior to making the page available to your general audience.
There are a number of views in this module that require an additional level of security. These features are protected in the site itself, as well as in the API that communicates with the respective views. If someone attempts to access a view without appropriate permissions, they'll see a message similar to that seen below. The API will give a different message/error, but you won't see that reported like this.
If you feel you're supposed to have access to that view, ensure the following:
- You're logged in; and
- Your user account is an admin; or
- Your user account is given "edit" permissions to the module.
While every effort will always be attempted to be made to prevent errors from occurring, they will happen. When they do, you should always be able to find the errors in two places:
- Event Viewer: This is important for all non-technical site admins to be able to articulate issues that may be occurring.
- Web Service: The web services will always return error messages that should almost mirror what you see in the event viewer. However, the event viewer will always have more detailed information.