PR: Ability to delete blogs in mutisite

.styleci.yml

@@ -34,14 +34,12 @@ enabled:
   - no_extra_block_blank_lines
   - no_extra_consecutive_blank_lines
   - no_leading_namespace_whitespace
-  - no_php4_constructor
   - no_short_echo_tag
   - no_spaces_after_function_name
   - no_trailing_comma_in_list_call
   - no_trailing_comma_in_singleline_array
   - no_trailing_whitespace
   - no_trailing_whitespace_in_comment
-  - no_unneeded_final_method
   - no_unused_imports
   - no_whitespace_before_comma_in_array
   - no_whitespace_in_blank_line

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [email protected]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

HISTORY.md

@@ -1,5 +1,11 @@
 ## Changelog ##
 
+### 2020 (In dev) - v6.1.0 ###
+
+Enhancements
+
+- Ability to schedule deletion of terms.
+
 ### 2019-04-11 - v6.0.2 ###
 
 Enhancements

assets/js/src/bulk-delete.js

@@ -31,10 +31,21 @@ jQuery(document).ready(function () {
 	jQuery( "input:radio.schedule-deletion" ).change( function () {
 		var submitButton = jQuery( this ).parents( 'fieldset' ).next().find( 'button[name="bd_action"]' );
 
+		var scheduledLable = 'Schedule Bulk Delete »';
+		var label = 'Bulk Delete »';
+
+		if ( submitButton.data( 'label' ) ) {
+			label = submitButton.data( 'label' );
+		}
+
+		if ( submitButton.data( 'schedule-label' ) ) {
+			scheduledLable = submitButton.data( 'schedule-label' );
+		}
+
 		if ( "true" === jQuery( this ).val() ) {
-			submitButton.html( 'Schedule Bulk Delete »' );
+			submitButton.html( scheduledLable );
 		} else {
-			submitButton.html( 'Bulk Delete »' );
+			submitButton.html( label );
 		}
 	} );
 

assets/js/src/delete-comment-meta.js

@@ -0,0 +1,20 @@
+/**
+ * JavaScript for handling Delete comment meta module.
+ *
+ * @author Sudar <https://bulkwp.com>
+ * @since 6.1.0
+ */
+
+/*global jQuery, document*/
+jQuery( document ).ready( function () {
+	jQuery( 'input.use-value' ).change( function () {
+		var useValue      = jQuery( this ).val(),
+			$valueFilters = jQuery( this ).parents( 'table' ).find( '.value-filters' );
+
+		if ( 'true' === useValue ) {
+			$valueFilters.removeClass( 'visually-hidden' );
+		} else {
+			$valueFilters.addClass( 'visually-hidden' );
+		}
+	} );
+} );