KumiSystems/moodle-mod_htmlcert
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
moodle-mod_htmlcert/classes/edit_element_form.php

85 lines
2.9 KiB
PHP
Raw Normal View History

Completely refactored the code for editing a custom certificate The elements for each page are listed in a table below the other page settings, meaning each page has a separate table for listing their elements. Each element is now edited in a pop-up, rather than having all the element settings displayed at once on the form causing it to look overcrowded. There is also no longer any need for the function add_element to add default values for the elements when they are added, as a a form is shown when you click to add an element where you can enter the values before it is created. Note: I did not create a db/upgrade.php script to add the new database columns as this module should not be currently used by anyone.
2013-06-06 10:59:08 +00:00
<?php
// This file is part of the customcert module for Moodle - http://moodle.org/
//
// Moodle is free software: you can redistribute it and/or modify
// it under the terms of the GNU General Public License as published by
// the Free Software Foundation, either version 3 of the License, or
// (at your option) any later version.
//
// Moodle is distributed in the hope that it will be useful,
// but WITHOUT ANY WARRANTY; without even the implied warranty of
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
// GNU General Public License for more details.
//
// You should have received a copy of the GNU General Public License
Changed PHPDocs and added date to the copyright to match Moodle coding guidelines
2013-07-22 05:06:18 +00:00
// along with Moodle. If not, see <http://www.gnu.org/licenses/>.
Completely refactored the code for editing a custom certificate The elements for each page are listed in a table below the other page settings, meaning each page has a separate table for listing their elements. Each element is now edited in a pop-up, rather than having all the element settings displayed at once on the form causing it to look overcrowded. There is also no longer any need for the function add_element to add default values for the elements when they are added, as a a form is shown when you click to add an element where you can enter the values before it is created. Note: I did not create a db/upgrade.php script to add the new database columns as this module should not be currently used by anyone.
2013-06-06 10:59:08 +00:00
Huge refactor 1) Every certificate is a template. Before a user would create a certificate then had the option to save it as a template. This could potentially be chaotic with numerous users creating templates, making the template system a mess. Now, rather than creating a certificate first, then saving it as a template, you are always creating a template. Each template is associated with a context, so depending on where you are creating it the context is different. This means users in the CONTEXT_MODULE context are creating a template specific to that module, where as a user creating a template in the CONTEXT_SYSTEM context would be creating a general template that can be used by others. This meant we can remove the 'customcert_template_*' db tables. Yay - no duplicated tables. 2) Created new helper classes and moved functionality there. 3) Moved files to classes/ for autoloading. 4) General tidy up.
2016-02-16 09:03:34 +00:00
namespace mod_customcert;
Completely refactored the code for editing a custom certificate The elements for each page are listed in a table below the other page settings, meaning each page has a separate table for listing their elements. Each element is now edited in a pop-up, rather than having all the element settings displayed at once on the form causing it to look overcrowded. There is also no longer any need for the function add_element to add default values for the elements when they are added, as a a form is shown when you click to add an element where you can enter the values before it is created. Note: I did not create a db/upgrade.php script to add the new database columns as this module should not be currently used by anyone.
2013-06-06 10:59:08 +00:00
defined('MOODLE_INTERNAL') || die('Direct access to this script is forbidden.');
require_once($CFG->dirroot . '/course/moodleform_mod.php');
require_once($CFG->dirroot . '/mod/customcert/includes/colourpicker.php');
Huge refactor 1) Every certificate is a template. Before a user would create a certificate then had the option to save it as a template. This could potentially be chaotic with numerous users creating templates, making the template system a mess. Now, rather than creating a certificate first, then saving it as a template, you are always creating a template. Each template is associated with a context, so depending on where you are creating it the context is different. This means users in the CONTEXT_MODULE context are creating a template specific to that module, where as a user creating a template in the CONTEXT_SYSTEM context would be creating a general template that can be used by others. This meant we can remove the 'customcert_template_*' db tables. Yay - no duplicated tables. 2) Created new helper classes and moved functionality there. 3) Moved files to classes/ for autoloading. 4) General tidy up.
2016-02-16 09:03:34 +00:00
\MoodleQuickForm::registerElementType('customcert_colourpicker',
Completely refactored the code for editing a custom certificate The elements for each page are listed in a table below the other page settings, meaning each page has a separate table for listing their elements. Each element is now edited in a pop-up, rather than having all the element settings displayed at once on the form causing it to look overcrowded. There is also no longer any need for the function add_element to add default values for the elements when they are added, as a a form is shown when you click to add an element where you can enter the values before it is created. Note: I did not create a db/upgrade.php script to add the new database columns as this module should not be currently used by anyone.
2013-06-06 10:59:08 +00:00
$CFG->dirroot . '/mod/customcert/includes/colourpicker.php', 'MoodleQuickForm_customcert_colourpicker');
/**
* The form for handling editing a customcert element.
*
* @package mod_customcert
Changed PHPDocs and added date to the copyright to match Moodle coding guidelines
2013-07-22 05:06:18 +00:00
* @copyright 2013 Mark Nelson <markn@moodle.com>
Completely refactored the code for editing a custom certificate The elements for each page are listed in a table below the other page settings, meaning each page has a separate table for listing their elements. Each element is now edited in a pop-up, rather than having all the element settings displayed at once on the form causing it to look overcrowded. There is also no longer any need for the function add_element to add default values for the elements when they are added, as a a form is shown when you click to add an element where you can enter the values before it is created. Note: I did not create a db/upgrade.php script to add the new database columns as this module should not be currently used by anyone.
2013-06-06 10:59:08 +00:00
* @license http://www.gnu.org/copyleft/gpl.html GNU GPL v3 or later
*/
Huge refactor 1) Every certificate is a template. Before a user would create a certificate then had the option to save it as a template. This could potentially be chaotic with numerous users creating templates, making the template system a mess. Now, rather than creating a certificate first, then saving it as a template, you are always creating a template. Each template is associated with a context, so depending on where you are creating it the context is different. This means users in the CONTEXT_MODULE context are creating a template specific to that module, where as a user creating a template in the CONTEXT_SYSTEM context would be creating a general template that can be used by others. This meant we can remove the 'customcert_template_*' db tables. Yay - no duplicated tables. 2) Created new helper classes and moved functionality there. 3) Moved files to classes/ for autoloading. 4) General tidy up.
2016-02-16 09:03:34 +00:00
class edit_element_form extends \moodleform {
Completely refactored the code for editing a custom certificate The elements for each page are listed in a table below the other page settings, meaning each page has a separate table for listing their elements. Each element is now edited in a pop-up, rather than having all the element settings displayed at once on the form causing it to look overcrowded. There is also no longer any need for the function add_element to add default values for the elements when they are added, as a a form is shown when you click to add an element where you can enter the values before it is created. Note: I did not create a db/upgrade.php script to add the new database columns as this module should not be currently used by anyone.
2013-06-06 10:59:08 +00:00
/**
Huge refactor 1) Every certificate is a template. Before a user would create a certificate then had the option to save it as a template. This could potentially be chaotic with numerous users creating templates, making the template system a mess. Now, rather than creating a certificate first, then saving it as a template, you are always creating a template. Each template is associated with a context, so depending on where you are creating it the context is different. This means users in the CONTEXT_MODULE context are creating a template specific to that module, where as a user creating a template in the CONTEXT_SYSTEM context would be creating a general template that can be used by others. This meant we can remove the 'customcert_template_*' db tables. Yay - no duplicated tables. 2) Created new helper classes and moved functionality there. 3) Moved files to classes/ for autoloading. 4) General tidy up.
2016-02-16 09:03:34 +00:00
* @var \mod_customcert\element The element object.
Completely refactored the code for editing a custom certificate The elements for each page are listed in a table below the other page settings, meaning each page has a separate table for listing their elements. Each element is now edited in a pop-up, rather than having all the element settings displayed at once on the form causing it to look overcrowded. There is also no longer any need for the function add_element to add default values for the elements when they are added, as a a form is shown when you click to add an element where you can enter the values before it is created. Note: I did not create a db/upgrade.php script to add the new database columns as this module should not be currently used by anyone.
2013-06-06 10:59:08 +00:00
*/
Huge refactor 1) Every certificate is a template. Before a user would create a certificate then had the option to save it as a template. This could potentially be chaotic with numerous users creating templates, making the template system a mess. Now, rather than creating a certificate first, then saving it as a template, you are always creating a template. Each template is associated with a context, so depending on where you are creating it the context is different. This means users in the CONTEXT_MODULE context are creating a template specific to that module, where as a user creating a template in the CONTEXT_SYSTEM context would be creating a general template that can be used by others. This meant we can remove the 'customcert_template_*' db tables. Yay - no duplicated tables. 2) Created new helper classes and moved functionality there. 3) Moved files to classes/ for autoloading. 4) General tidy up.
2016-02-16 09:03:34 +00:00
protected $element;
Completely refactored the code for editing a custom certificate The elements for each page are listed in a table below the other page settings, meaning each page has a separate table for listing their elements. Each element is now edited in a pop-up, rather than having all the element settings displayed at once on the form causing it to look overcrowded. There is also no longer any need for the function add_element to add default values for the elements when they are added, as a a form is shown when you click to add an element where you can enter the values before it is created. Note: I did not create a db/upgrade.php script to add the new database columns as this module should not be currently used by anyone.
2013-06-06 10:59:08 +00:00
/**
* Form definition.
*/
Added missing scope to functions
2013-07-23 06:44:11 +00:00
public function definition() {
Completely refactored the code for editing a custom certificate The elements for each page are listed in a table below the other page settings, meaning each page has a separate table for listing their elements. Each element is now edited in a pop-up, rather than having all the element settings displayed at once on the form causing it to look overcrowded. There is also no longer any need for the function add_element to add default values for the elements when they are added, as a a form is shown when you click to add an element where you can enter the values before it is created. Note: I did not create a db/upgrade.php script to add the new database columns as this module should not be currently used by anyone.
2013-06-06 10:59:08 +00:00
$mform =& $this->_form;
Added ability to edit an element on the rearrange page Increased the Moodle version required as this feature uses the AMD module 'core/fragment' which was introduced in 3.1.
2016-06-13 11:39:57 +00:00
$mform->updateAttributes(array('id' => 'editelementform'));
Completely refactored the code for editing a custom certificate The elements for each page are listed in a table below the other page settings, meaning each page has a separate table for listing their elements. Each element is now edited in a pop-up, rather than having all the element settings displayed at once on the form causing it to look overcrowded. There is also no longer any need for the function add_element to add default values for the elements when they are added, as a a form is shown when you click to add an element where you can enter the values before it is created. Note: I did not create a db/upgrade.php script to add the new database columns as this module should not be currently used by anyone.
2013-06-06 10:59:08 +00:00
$element = $this->_customdata['element'];
Added ability to edit an element on the rearrange page Increased the Moodle version required as this feature uses the AMD module 'core/fragment' which was introduced in 3.1.
2016-06-13 11:39:57 +00:00
// Do not display the name if we are on the rearrange page.
if (!isset($this->_customdata['rearrange'])) {
// Add the field for the name of the element, this is required for all elements.
$mform->addElement('text', 'name', get_string('elementname', 'customcert'));
$mform->setType('name', PARAM_TEXT);
$mform->setDefault('name', get_string('pluginname', 'customcertelement_' . $element->element));
$mform->addRule('name', get_string('required'), 'required', null, 'client');
$mform->addHelpButton('name', 'elementname', 'customcert');
}
Completely refactored the code for editing a custom certificate The elements for each page are listed in a table below the other page settings, meaning each page has a separate table for listing their elements. Each element is now edited in a pop-up, rather than having all the element settings displayed at once on the form causing it to look overcrowded. There is also no longer any need for the function add_element to add default values for the elements when they are added, as a a form is shown when you click to add an element where you can enter the values before it is created. Note: I did not create a db/upgrade.php script to add the new database columns as this module should not be currently used by anyone.
2013-06-06 10:59:08 +00:00
Huge refactor 1) Every certificate is a template. Before a user would create a certificate then had the option to save it as a template. This could potentially be chaotic with numerous users creating templates, making the template system a mess. Now, rather than creating a certificate first, then saving it as a template, you are always creating a template. Each template is associated with a context, so depending on where you are creating it the context is different. This means users in the CONTEXT_MODULE context are creating a template specific to that module, where as a user creating a template in the CONTEXT_SYSTEM context would be creating a general template that can be used by others. This meant we can remove the 'customcert_template_*' db tables. Yay - no duplicated tables. 2) Created new helper classes and moved functionality there. 3) Moved files to classes/ for autoloading. 4) General tidy up.
2016-02-16 09:03:34 +00:00
$this->element = \mod_customcert\element::instance($element);
Completely refactored the code for editing a custom certificate The elements for each page are listed in a table below the other page settings, meaning each page has a separate table for listing their elements. Each element is now edited in a pop-up, rather than having all the element settings displayed at once on the form causing it to look overcrowded. There is also no longer any need for the function add_element to add default values for the elements when they are added, as a a form is shown when you click to add an element where you can enter the values before it is created. Note: I did not create a db/upgrade.php script to add the new database columns as this module should not be currently used by anyone.
2013-06-06 10:59:08 +00:00
$this->element->render_form_elements($mform);
$this->add_action_buttons(true);
}
/**
* Fill in the current page data for this customcert.
*/
Added missing scope to functions
2013-07-23 06:44:11 +00:00
public function definition_after_data() {
Fixed issue when creating an image element The images were not loading in the filemanager. This meant that when the element was saved the images would be deleted for that course, affecting existing image elements as well.
2015-12-10 07:26:49 +00:00
$this->element->definition_after_data($this->_form);
Completely refactored the code for editing a custom certificate The elements for each page are listed in a table below the other page settings, meaning each page has a separate table for listing their elements. Each element is now edited in a pop-up, rather than having all the element settings displayed at once on the form causing it to look overcrowded. There is also no longer any need for the function add_element to add default values for the elements when they are added, as a a form is shown when you click to add an element where you can enter the values before it is created. Note: I did not create a db/upgrade.php script to add the new database columns as this module should not be currently used by anyone.
2013-06-06 10:59:08 +00:00
}
/**
* Validation.
*
Tidied up the PHPDocs and set the base element to an abstract class
2013-06-12 10:35:27 +00:00
* @param array $data
* @param array $files
Completely refactored the code for editing a custom certificate The elements for each page are listed in a table below the other page settings, meaning each page has a separate table for listing their elements. Each element is now edited in a pop-up, rather than having all the element settings displayed at once on the form causing it to look overcrowded. There is also no longer any need for the function add_element to add default values for the elements when they are added, as a a form is shown when you click to add an element where you can enter the values before it is created. Note: I did not create a db/upgrade.php script to add the new database columns as this module should not be currently used by anyone.
2013-06-06 10:59:08 +00:00
* @return array the errors that were found
*/
public function validation($data, $files) {
return $this->element->validate_form_elements($data, $files);
}
}
Reference in a new issue Copy permalink