They are currently using a CA that is not installed on our servers. Since it
isn't a top-tier CA and we aren't submitting anything particularly sensitive
anyway, we don't have to feel too bad about this.

these are configured to be too long in the settings.

Updated safe_key() so that it: (a) avoids creating keys that
are too long for memcache, and (b) handles unicode in keys, prefixes,
and versions

Added __init__.py, which should have been in the last commit

Pep8/Pylint fixes

This functionality requires the Zendesk URL, user, and API key to be specified
in django.conf.settings. Also, add a flag to MITX_FEATURES (enabled by default)
to control the endpoint and the front-end feature (yet to be added).

This allows specification of profile parameters when creating a user. Because
the profile contents are always accessed from the database, the user must be
saved to the database before the profile is created. This means that the
profile cannot be created if the user is merely being built (and not saved)
rather than created.

LH: 381, 382, 383

* hide the login behind a setting that is turned off by default
* clean out some of the outdated settings and hardcoded test strings

Conflicts:

	lms/templates/staff_problem_info.html
	lms/xmodule_namespace.py

use a request-scoped cache to keep the metadata inheritence tree around for the whole request. This means we should only do one trip to Memcached/Mongo per course per request. This is expected to keep memory utilization down

An integrity error while creating an enrollment just means that our work has already been done. Fixes https://www.pivotaltracker.com/story/show/46915947

when loaded by rake test_cms

I moved the test into lms/courseware/tests so they run correctly.

strings.

Added unit tests that verify the fix.

* Missing docstring
* Redefining name from outer scope

manipulation

Added a wait time before checking the page HTML,
and changed it to check just in the HTML body

for common ui manipulations

terrain/steps.py