# Actions

***

### License Actions

#### `sce_core_license_{$action}`

Fires when a license action is performed. This is a dynamic action where `{$action}` can be: `check_license`, `activate_license`, or `deactivate_license`.

**Parameters:**

* `array $response` - Response of the license action.

**Since:** 1.0.0

**Example:**

```php
// For check_license action
add_action( 'sce_core_license_check_license', function( $response ) {
    // Log the license check response
    error_log( 'License check: ' . print_r( $response, true ) );
} );

// For activate_license action
add_action( 'sce_core_license_activate_license', function( $response ) {
    // Perform custom action when license is activated
    if ( isset( $response['success'] ) && $response['success'] ) {
        // License activated successfully
    }
} );
```

***

### Mentions Subscribe Actions

#### `sce_mentions_subscribe_after_scripts`

Fires after scripts are printed in the header on the subscribe page.

**Parameters:**

* `string $sce_mentions_theme_name` - The theme name.

**Since:** 1.0.0

**Example:**

```php
add_action( 'sce_mentions_subscribe_after_scripts', function( $theme_name ) {
    // Add custom inline script after header scripts
    echo '<script>console.log("Subscribe page loaded");</script>';
} );
```

#### `sce_mentions_subscribe_after_styles`

Fires after styles are printed in the header on the subscribe page.

**Parameters:**

* `string $sce_mentions_theme_name` - The theme name.

**Since:** 1.0.0

**Example:**

```php
add_action( 'sce_mentions_subscribe_after_styles', function( $theme_name ) {
    // Add custom inline styles after header styles
    echo '<style>.custom-class { color: red; }</style>';
} );
```

#### `sce_mentions_subscribe_body_open`

Fires when the body tag opens on the subscribe page.

**Example:**

```php
add_action( 'sce_mentions_subscribe_body_open', function() {
    // Add custom content at the start of the body
    echo '<div class="custom-wrapper">';
} );
```

#### `sce_mentions_subscribe_body`

Fires inside the main content area of the subscribe page.

**Example:**

```php
add_action( 'sce_mentions_subscribe_body', function() {
    // Add custom content to the subscribe page body
    echo '<p>Thank you for subscribing!</p>';
} );
```

***

### Mentions Unsubscribe Actions

#### `sce_mentions_unsubscribe_after_scripts`

Fires after scripts are printed in the header on the unsubscribe page.

**Parameters:**

* `string $sce_mentions_theme_name` - The theme name.

**Since:** 1.0.0

**Example:**

```php
add_action( 'sce_mentions_unsubscribe_after_scripts', function( $theme_name ) {
    // Add custom inline script after header scripts
    echo '<script>console.log("Unsubscribe page loaded");</script>';
} );
```

#### `sce_mentions_unsubscribe_after_styles`

Fires after styles are printed in the header on the unsubscribe page.

**Parameters:**

* `string $sce_mentions_theme_name` - The theme name.

**Since:** 1.0.0

**Example:**

```php
add_action( 'sce_mentions_unsubscribe_after_styles', function( $theme_name ) {
    // Add custom inline styles after header styles
    echo '<style>.custom-class { color: blue; }</style>';
} );
```

#### `sce_mentions_unsubscribe_body_open`

Fires when the body tag opens on the unsubscribe page.

**Example:**

```php
add_action( 'sce_mentions_unsubscribe_body_open', function() {
    // Add custom content at the start of the body
    echo '<div class="custom-wrapper">';
} );
```

#### `sce_mentions_unsubscribe_body`

Fires inside the main content area of the unsubscribe page.

**Example:**

```php
add_action( 'sce_mentions_unsubscribe_body', function() {
    // Add custom content to the unsubscribe page body
    echo '<p>You have been unsubscribed successfully.</p>';
} );
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.dlxplugins.com/comment-edit-pro/developers/actions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.