Product SiteDocumentation Site

2.3.2.2. Interface Settings

Also included in settings.php are a few settings that determine what options are presented to the user.
Some of these settings may seem redundant, since they are configured in the backend as well. Retrieving these settings automatically, however, would require extra traffic between the frontend and backend, possibly on every view of the job submission form. While it is a small inconvenience, manually providing these settings increases efficiency and reduces complexity.
The option $wmrAllowTestJobs is a boolean that determines whether an option should be provided to submit a job as a test job. If you enabled test jobs on the backend as described in Section 2.2.5, “Enable Test Jobs (Optional)”, set this to true: 
$wmrAllowTestJobs = true;
Next, we will configure which languages are presented as options for mappers and reducers. The list of languages is stored in the variable $wmrLanguages as an associative array, like this: 
$wmrLanguages = array(
  'Java'     => 'java',
  'Python 2' => 'python2',
  'Python 3' => 'python3',
  'C++'      => 'cpp',
  'Scheme'   => 'scheme'
);
Each key-value pair is a language, where the key is the name of the language as the user sees it, and the value is the name of the language as it is known to the WMRServer backend—the name in languages.conf, as described in Section 2.2.3.2, “Language Configuration”.
The default set of languages should already be listed in the file. Simply remove any that you removed from the backend configuration.
Also, set the language that should be selected by default: 
$wmrDefaultLanguage = 'language';
where language is one of the values in the $wmrLanguages array (i.e., "python3", not "Python 3").