21 |
22 | ## Built for Developers
23 | Redux was built by developers for developers. We save you months if not years in your development time. Everything we
24 | do is to help innovation in the industry. To help you get started, we have a number of docs you should read.
25 |
26 | [See: Guides](./guides/)
27 |
28 |
29 |
30 |
31 | ## Built for Users
32 | We built this framework to help users and fix a problem in the industry. We care deeply about every Redux user.
33 | We will always ensure your site is the most secure. If you find an issue, please report it to us.
34 |
35 | [See: Getting Help/Support](guides/basics/support-defined.md)
36 |
37 |
38 |
39 |
40 | ## Built for Professionals
41 | Redux 4.x is here! We've done all we can to keep it as close to perfect as possible. We've made sure this
42 | new version is backward compatable with the previous, although changes to some method names to be fully ready.
43 |
44 | [See: Migration Guide](guides/other/migration-guide.md)
45 |
46 |
47 |
--------------------------------------------------------------------------------
/docs/configuration/README.md:
--------------------------------------------------------------------------------
1 | # Configuration
2 |
3 | Redux can be overwhelming. There are a multitude of features that reach all areas of WordPress. This section will help you
4 | understand more complex configurations and how to use them.
5 |
6 | ::: tip Good Starting Points
7 | - [The Redux API](api.md)
8 | - [Object: Field](objects/field.md)
9 | - [Object: Section](objects/section.md)
10 | :::
--------------------------------------------------------------------------------
/docs/configuration/fields/arguments.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: "Global Field Arguments"
3 | sidebarDepth: 2
4 | ---
5 |
6 | # Global Field Arguments
7 | The following are universal arguments used by every field. The default field arguments can be used by any field. The
8 | extra functionality arguments may perform in different ways depending on the field type.
9 |
10 | ## Universal Arguments
11 | These arguments are available for every field.
12 |
13 | |Name|Type|Description|
14 | |--- |--- |--- |
15 | |id|string|Unique ID identifying the field. Must be different from all other field IDs or unexpected replacement will occur.|
16 | |type|string|Type of field to display. Each field must have a unique type.|
17 | |title|string|Display title of the field.|
18 | |subtitle|string|Subtitle display of the field, situated beneath the title.|
19 | |desc|string|Description of the option, appearing beneath the field control.|
20 | |default|string|Default value for the field.|
21 | |[permissions](../fields/permissions.md)|string|String specifying the capability required to view the section.|
22 | |[hint(s)](../fields/hints.md)|array|Array containing the `content` and optional `title` arguments for the hint tooltip.|
23 |
24 | ::: tip Also See
25 | - [Using the `hint(s)` Argument](../fields/hints.md)
26 | - [Using the `permissions` Argument](../fields/permissions.md)
27 | :::
28 |
29 | ## Extra Arguments
30 | These arguments may not be supported by all fields, and will be denoted on each field page of documentation.
31 |
32 | |Name|Type|Description|
33 | |--- |--- |--- |
34 | |[compiler](../fields/compiler.md)|bool/array|Flag to run the compiler hook or array of CSS selectors to pass dynamic CSS to the compiler hook.|
35 | |[data](../fields/data.md)|string/array||
36 | |[output](../fields/output.md)|array|Array of CSS selectors to dynamically generate CSS. Only works on supported fields types.|
37 | |[required](../fields/required.md)|array|Provide the parent, comparison operator, and value which will affects the field's visibility.|
38 | |[validate](../fields/validate.md)|string/array||
39 |
40 | ::: tip Also See
41 | - [Using the `compiler` Argument](../fields/compiler.md)
42 | - [Using the `data` Argument](../fields/data.md)
43 | - [Using the `output` Argument](../fields/output.md)
44 | - [Using the `required` Argument](../fields/required.md)
45 | - [Using the `validate` Argument](../fields/validate.md)
46 | :::
--------------------------------------------------------------------------------
/docs/configuration/fields/compiler.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: "Compiler"
3 | sidebarDepth: 2
4 | ---
5 |
6 | # Using the `compiler` Argument
7 |
8 | This article deals specifically with integrating a basic compiler hook for any field. For an in depth article on how to
9 | use the compiler hook to dynamically generate a CSS file, please view the
10 | [Updating a CSS File Dynamically](../advanced/advanced-updating-a-css-file-dynamically.md) article.
11 |
12 | ::: warning Table of Contents
13 | [[toc]]
14 | :::
15 |
16 | ## Using in a Field
17 | Every Redux field offers the `compiler` argument. By setting this argument to `true`, a specified hook will fire
18 | whenever the value of a field marked with `'compiler' => true` is changed.
19 |
20 | Creating this magic is really quite easy. Let’s begin with this basic field:
21 |
22 | ```php
23 | array(
24 | 'id' =>'text',
25 | 'type' => 'text',
26 | 'title' => esc_html__('Test Compiler', 'your-textdomain-here'),
27 | 'subtitle' => esc_html__('This is to test the compiler hook.', 'your-textdomain-here'),
28 | 'desc' => esc_html__('Each time this field is set, a flag is set. On save, that flag initiates a compiler hook!', 'your-textdomain-here'),
29 | 'compiler' => true,
30 | 'default' => 'Test Compiler'
31 | ),
32 | ```
33 |
34 | Note the `'compiler' => true` argument. This sets the compiler flag. Now we need to hook into the fired hook. Add this snippet to your code:
35 |
36 | ## Setting up the Compiler Function
37 | Next, the compiler function itself needs to be set up. It requires two parts. The add_filter statement, and the actual
38 | function. Ideally, these codes would be placed within your config PHP file; however, it can be used anywhere in your
39 | code provided the `opt_name` portion of the add_filter line is replaced with the value specified in your
40 | [opt_name](../global_arguments.md#opt_name) argument. For this example, we'll be using the example found in the
41 | [sample-config.php](https://github.com/ReduxFramework/redux-framework/blob/master/sample/sample-config.php).
42 |
43 | Make sure the following line is included and/or uncommented:
44 |
45 | ```php
46 | add_filter('redux/options/' . $this->args['opt_name'] . '/compiler', array( $this, 'compiler_action' ), 10, 3);
47 | ```
48 |
49 | Now, add (or uncomment) the following function to the [sample-config.php](https://github.com/reduxframework/redux-framework/blob/master/sample/sample-config.php) file. This is our test function
50 | that allows you to see when the compiler hook occurs. It will only fire if a field set with `'compiler' => true` is changed.
51 |
52 | Please note that for this example, `$css` will return empty as this is only a basic compiler hook.
53 |
54 | ```php
55 | function compiler_action($options, $css, $changed_values) {
56 | echo '
The compiler hook has run!
';
57 |
58 | print_r ($options);
59 | print_r ($css);
60 | print_r ($changed_values);
61 | }
62 | ```
63 |
64 | If all has been set up correctly, you will see the compiler hook message and the passed values on your options panel after the field with the active compiler hook's value has changed and settings saved.
65 |
66 |
67 | ::: tip
68 | If the [`output_tag`](../global_arguments.md#output_tag) argument is set to false, Redux will not auto-echo a tag into the page header.
69 | :::
70 |
--------------------------------------------------------------------------------
/docs/configuration/fields/permissions.md:
--------------------------------------------------------------------------------
1 | ---
2 |
3 | title: "Permissions"
4 |
5 | ---
6 |
7 | # Using the `permissions` Argument
8 |
9 | The `permissions` argument is useful for restricting access to certain [fields](../objects/field.md) or [sections](../objects/section.md)
10 | that require a specified user role. For example, if the options panel is set via [page_permissions](../global_arguments.md#page-permissions)
11 | to allow users with an editor role or higher to view and set options, but you'd prefer some options or sections be
12 | available only to administrators, the 'permissions' argument makes this possible.
13 |
14 | In the above scenario, the line `'permissions' => 'manage_options'` would be added to either the [sections array](../objects/section.md)
15 | to control an entire section, or the [fields array](../objects/field.md) to control a specific field. The 'permissions'
16 | argument accepts any [capability name](https://wordpress.org/support/article/roles-and-capabilities/).
17 |
18 | ::: warning
19 | The [WordPress documentation](https://core.trac.wordpress.org/ticket/22624) strongly recommends **not** using role names (administrator, editor, etc.) in place of capability names as
20 | they are not guaranteed to work correctly
21 | :::
22 |
23 | ::: danger
24 | The `permissions` argument cannot be used with the following core fields, as they do not accept or save data:
25 | [section](../../core-fields/section.md), [info](../../core-fields/info.md), [divide](../../core-fields/divide.md), and
26 | [raw](../../core-fields/raw.md).
27 | :::
28 |
--------------------------------------------------------------------------------
/docs/configuration/fields/required.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: "Required"
3 | ---
4 |
5 | # Using the `required` Argument
6 |
7 | Fields may be linked/required/folded according to a/multiple parent value(s). This is achieved by appending a
8 | `required` argument to the [field](../objects/field.md). Required can be very powerful, but due to the complexity requires
9 | some careful considerations.
10 |
11 | ::: warning Table of Contents
12 | [[toc]]
13 | :::
14 |
15 | ## Example Config
16 |
17 | To link a field's visibility to the value of another:
18 |
19 | ```php
20 | array(
21 | 'required' => array( 'LINKED_FIELD_ID', 'OPERATION', 'VALUE' )
22 | )
23 | ```
24 | |Key|Description|
25 | |--- |--- |
26 | |`LINKED_FIELD_ID`|Field ID that will affect the visibility of this field|
27 | |`OPERATION`|Comparison operation to perform|
28 | |`VALUE`|Value is the value to compare against for visibility|
29 |
30 | You can also link a field with multiple "parent" required values. If all of these conditions are not met, this
31 | [field](../objects/field.md) will not be visible and the [field](../objects/field.md#output) CSS will not be used.
32 | An example is as follows:
33 |
34 |
35 | ```php
36 | array(
37 | 'required' => array(
38 | array( 'LINKED_FIELD_ID_1', 'OPERATION_1', 'VALUE_1' ),
39 | array( 'LINKED_FIELD_ID_2', 'OPERATION_2', 'VALUE_2' )
40 | )
41 | )
42 | ```
43 | If you are checking the same key againt a different value then you have to do it as follows:
44 |
45 |
46 | ```php
47 | array(
48 | 'required' => array(
49 | array( 'LINKED_FIELD_ID_1', 'OPERATION_1', array( 'VALUE_1', 'VALUE_2' ) )
50 | )
51 | )
52 | ```
53 |
54 | ## Operations Available
55 |
56 | To attempt to support the various possibilities, a number of options have been coded. These operations have been found to
57 | support the majority of needs.
58 |
59 | |Operation|Test Equivalent|
60 | |--- |--- |
61 | |=|`$a = $b`|
62 | |equals|`$a = $b`|
63 | |!=|`$a != $b`|
64 | |not|`$a != $b`|
65 | |>|`$a > $b`|
66 | |greater|`$a > $b`|
67 | |is_larger|`$a > $b`|
68 | |>=|$`a >= $b`|
69 | |greater_equal|`$a >= $b`|
70 | |is_larger_equal|`$a >= $b`|
71 | |<|`$a < $b`|
72 | |less|`$a < $b`|
73 | |is_smaller|`$a < $b`|
74 | |<=|`$a <= $b`|
75 | |less_equal|`$a <= $b`|
76 | |is_smaller_equal|`$a <= $b`|
77 | |contains|`( strpos( $a, $b ) !== false )`|
78 | |doesnt_contain|`( strpos($a, $b) === false )`|
79 | |not_contain|`( strpos($a, $b) === false )`|
80 | |is_empty_or|`if ( empty( $value1 )`|
81 | |not_empty_and|`if ( !empty( $value1 ) && $value1 != $value2 )`|
82 |
83 |
84 |
85 | ## Nesting
86 | If any parent is hidden or doesn't match the value, all children are
87 | hidden and all CSS output from those children is hidden as well.
88 |
89 | ## CSS Output
90 | CSS output to both the head and compiler is removed from each field if the required value(s) is/are not met. You can,
91 | however, override this on a per-field basis by setting `'force_output' => true` for each field you want CSS to still be
92 | output with. This way you can nest a field under another, and still have it output to the dynamic CSS.
93 |
94 | ::: tip
95 | The CSS output will always be visible if items are within a `section` field unless that specific field has the required value set to the required parent as well.
96 | :::
97 |
--------------------------------------------------------------------------------
/docs/configuration/img/data-select-post.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/reduxframework/docs/c825c68c21b65839a11d3f6669937c07c00b5eb1/docs/configuration/img/data-select-post.png
--------------------------------------------------------------------------------
/docs/configuration/img/data-term-button-set.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/reduxframework/docs/c825c68c21b65839a11d3f6669937c07c00b5eb1/docs/configuration/img/data-term-button-set.png
--------------------------------------------------------------------------------
/docs/configuration/img/help_tab.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/reduxframework/docs/c825c68c21b65839a11d3f6669937c07c00b5eb1/docs/configuration/img/help_tab.png
--------------------------------------------------------------------------------
/docs/configuration/img/hints.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/reduxframework/docs/c825c68c21b65839a11d3f6669937c07c00b5eb1/docs/configuration/img/hints.png
--------------------------------------------------------------------------------
/docs/configuration/img/hints_alignment.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/reduxframework/docs/c825c68c21b65839a11d3f6669937c07c00b5eb1/docs/configuration/img/hints_alignment.jpg
--------------------------------------------------------------------------------
/docs/configuration/img/hints_colors.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/reduxframework/docs/c825c68c21b65839a11d3f6669937c07c00b5eb1/docs/configuration/img/hints_colors.png
--------------------------------------------------------------------------------
/docs/configuration/img/hints_style.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/reduxframework/docs/c825c68c21b65839a11d3f6669937c07c00b5eb1/docs/configuration/img/hints_style.png
--------------------------------------------------------------------------------
/docs/contributing.md:
--------------------------------------------------------------------------------
1 | # Contribution Guide
2 |
3 | Hello, and welcome to Redux!
4 |
5 | Please read them thoroughly before submitting an issue on our issue tracker.
6 |
7 | ## If You are NOT the Developer
8 |
9 | First, and most importantly, we need to know if you are a developer using Redux in their project, or if you are using a
10 | theme/plugin that uses Redux. **If you are not the primary developer**, please read out [Getting Support/Help](guides/basics/support-defined.md) guide.
11 |
12 | ## If You are the Primary Developer
13 |
14 | There are a number of things you can do to help us serve you better.
15 |
16 | ### 1. Update to the Latest Redux
17 |
18 | **Please** check to see if you are using the latest version of Redux. If you plan to reporting an issue with any version BUT
19 | the latest version, we are going to ask you to upgrade to the latest code base anyway to see if your issue persists.
20 | Please save yourself and us some time by taking this simple step first. Thanks!
21 |
22 | ### 2. Generate a Support Hash
23 |
24 | Before we will even look into your issue, we need a support hash. The reason is we have found around 80% of all our issues
25 | are a configuration issue. By looking at the data sent in the support request, we can quickly identify concerns and save
26 | you and us more time. Please read the [Generate a Support Hash](guides/basics/generating-a-support-hash.md) guide and
27 | have that URL handy.
28 |
29 | ### 3. Post to the Issue Tracker
30 |
31 | We designed our issue tracker to help identify and correct issues within Redux. If you believe you have
32 | discovered an issue, or something is not working as it should, then submitting an issue is appropriate. However, if you
33 | are looking for a custom solution involving Redux, or require assistance with original code unrelated to the Redux core
34 | itself, then this type of support falls under [Premium support](https://redux.io/extensions/premium-support/). We have
35 | far too many people using Redux to provide training on PHP/JavaScript or to debug your code without compensation.
36 |
37 | We handle all support for Redux Framework via our issue tracker. Email support is available only for those who have
38 | purchased Premium Support, or in instances where we have requested contact via e-mail.
39 |
40 | It would also be hugely helpful to us if you are able to indicate any steps taken up until the issue occurred. We may
41 | need to be able to recreate your issue on our end, and having this information would help with that. Simply stating
42 | something 'doesn't work' isn't helpful, and tells us nothing. PLEASE, be as specific as possible.
43 |
44 | Team Redux
--------------------------------------------------------------------------------
/docs/core-extensions/README.md:
--------------------------------------------------------------------------------
1 | # Extensions
2 |
3 | There are a number of extentions embedded within the Redux Core. These extensions all come pre-installed.
4 |
5 | ::: tip SEE ALSO
6 | - [Using & Creating Extensions](../guides/basics/using-extensions.md)
7 | :::
8 |
9 |
--------------------------------------------------------------------------------
/docs/core-extensions/custom-fonts.md:
--------------------------------------------------------------------------------
1 | # Custom Fonts
2 |
3 | The Custom Fonts extension is for users to upload a .ttf, .woff, .otf, or .zip containing any of the aforementioned
4 | fonts. It will then generate whatever fonts it may need, and make the font accessible via the typography field within
5 | Redux. A custom font CSS file will be enqueued to the panel as well as the frontend.
6 |
7 | ::: warning Table of Contents
8 | [[toc]]
9 | :::
10 |
11 | ## Arguments
12 | |Name|Type| Default |Description|
13 | |--- |--- |----------------|--- |
14 | |type|string| `custom_fonts` |Value identifying the field type.|
15 | |id|string| |Unique ID identifying the field. Must be different from all other field IDs.|
16 | |title|string| |Displays title of the field.|
17 | |subtitle|string| |Subtitle display of the field, situated beneath the title.|
18 | |desc|string| |Description of the field, appearing beneath the field control.|
19 | |class|string| |Appends any number of classes to the field's class attribute.|
20 |
21 | ## Example Config
22 | ```php
23 | Redux::set_section(
24 | $opt_name,
25 | array(
26 | 'title' => esc_html__( 'Custom Fonts', 'your-textdomain-here' ),
27 | 'desc' => esc_html__( 'For full documentation on this field, visit: ', 'your-textdomain-here' ) . 'https://devs.redux.io/core-extensions/custom-fonts.html',
28 | 'subsection' => true,
29 | 'fields' => array(
30 | array(
31 | 'id' => 'custom_fonts',
32 | 'type' => 'custom_fonts',
33 | ),
34 | array(
35 | 'id' => 'custom_fonts_typography',
36 | 'type' => 'typography',
37 | 'title' => esc_html__( 'Custom Fonts Typography', 'your-textdomain-here' ),
38 | 'font-size' => false,
39 | 'line-height' => false,
40 | 'text-align' => false,
41 | ),
42 | ),
43 | )
44 | );
45 | ```
46 |
47 | ## Example Usage
48 | This extension has no return value.
--------------------------------------------------------------------------------
/docs/core-extensions/img/accordion.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/reduxframework/docs/c825c68c21b65839a11d3f6669937c07c00b5eb1/docs/core-extensions/img/accordion.png
--------------------------------------------------------------------------------
/docs/core-extensions/img/color_schemes.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/reduxframework/docs/c825c68c21b65839a11d3f6669937c07c00b5eb1/docs/core-extensions/img/color_schemes.png
--------------------------------------------------------------------------------
/docs/core-extensions/img/color_schemes_picker.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/reduxframework/docs/c825c68c21b65839a11d3f6669937c07c00b5eb1/docs/core-extensions/img/color_schemes_picker.png
--------------------------------------------------------------------------------
/docs/core-extensions/img/color_schemes_picker_color.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/reduxframework/docs/c825c68c21b65839a11d3f6669937c07c00b5eb1/docs/core-extensions/img/color_schemes_picker_color.png
--------------------------------------------------------------------------------
/docs/core-extensions/img/color_schemes_replacer.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/reduxframework/docs/c825c68c21b65839a11d3f6669937c07c00b5eb1/docs/core-extensions/img/color_schemes_replacer.png
--------------------------------------------------------------------------------
/docs/core-extensions/img/color_schemes_replacer_color.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/reduxframework/docs/c825c68c21b65839a11d3f6669937c07c00b5eb1/docs/core-extensions/img/color_schemes_replacer_color.png
--------------------------------------------------------------------------------
/docs/core-extensions/img/dtp_nosplit.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/reduxframework/docs/c825c68c21b65839a11d3f6669937c07c00b5eb1/docs/core-extensions/img/dtp_nosplit.png
--------------------------------------------------------------------------------
/docs/core-extensions/img/dtp_split.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/reduxframework/docs/c825c68c21b65839a11d3f6669937c07c00b5eb1/docs/core-extensions/img/dtp_split.png
--------------------------------------------------------------------------------
/docs/core-extensions/img/google_maps.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/reduxframework/docs/c825c68c21b65839a11d3f6669937c07c00b5eb1/docs/core-extensions/img/google_maps.png
--------------------------------------------------------------------------------
/docs/core-extensions/img/icon-select.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/reduxframework/docs/c825c68c21b65839a11d3f6669937c07c00b5eb1/docs/core-extensions/img/icon-select.jpg
--------------------------------------------------------------------------------
/docs/core-extensions/img/io.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/reduxframework/docs/c825c68c21b65839a11d3f6669937c07c00b5eb1/docs/core-extensions/img/io.png
--------------------------------------------------------------------------------
/docs/core-extensions/img/options_object.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/reduxframework/docs/c825c68c21b65839a11d3f6669937c07c00b5eb1/docs/core-extensions/img/options_object.png
--------------------------------------------------------------------------------
/docs/core-extensions/img/options_object_console.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/reduxframework/docs/c825c68c21b65839a11d3f6669937c07c00b5eb1/docs/core-extensions/img/options_object_console.png
--------------------------------------------------------------------------------
/docs/core-extensions/img/redux-tabbed.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/reduxframework/docs/c825c68c21b65839a11d3f6669937c07c00b5eb1/docs/core-extensions/img/redux-tabbed.jpg
--------------------------------------------------------------------------------
/docs/core-extensions/import-export.md:
--------------------------------------------------------------------------------
1 | # Import/Export
2 |
3 | The Import/Export extension offers users the ability to back up and restore their Redux options data two ways: raw data or file.
4 |
5 | 
6 |
7 | ## Arguments
8 | |Name|Type|Default|Description|
9 | |--- |--- |--- |--- |
10 | |type|string|`import_export`|Value identifying the field type.|
11 | |id|string|Unique ID identifying the field. Must be different from all other field IDs.|
12 | |title|string|Displays title of the option.|
13 | |subtitle|string|Subtitle display of the option, situated beneath the title.|
14 | |desc|string|Description of the option, appearing beneath the field control.|
15 | |class|string|Appends any number of classes to the field's class attribute.|
16 | |permissions|string|String specifying the capability required to view the section. More info.|
17 | |full_width|bool|Sets whether or not the field is set full width or as a section, similar to the other fields.|
18 |
19 |
20 |
21 | ## Example Config
22 | ```php
23 | array(
24 | 'id' => 'opt-import-export',
25 | 'type' => 'import_export',
26 | 'title' => 'Import Export',
27 | 'subtitle' => 'Save and restore your Redux options',
28 | 'full_width' => false,
29 | )
30 | ```
31 |
--------------------------------------------------------------------------------
/docs/core-extensions/options-object.md:
--------------------------------------------------------------------------------
1 | # Options Object
2 |
3 | The Options Object field is designed to give developers who use Redux a quick glance at
4 | their option values in a readable JSON string. Ideally, the field/enhancement is for
5 | develop purposes and doesn't need to be shipped in your final product.
6 |
7 | 
8 |
9 | ::: warning Table of Contents
10 | [[toc]]
11 | :::
12 |
13 | ##Usage
14 | This field is not set in the traditional Redux way by adding an option array to your config.
15 | Instead, it is an argument set in the [global arguments](../configuration/global_arguments.md) array.
16 |
17 | The `options_object` is enabled by default and the field will automatically appear on your options screen.
18 | To disable it, simply add the following line inside the global arguments array:
19 |
20 | ```php
21 | 'options_object' => false,
22 | ```
23 | ## Console Log
24 | For added conveinence, one may also display the current options object via the developer's
25 | console log (CTRL+SHIFT+I) by clicking the "Show OPbject in JavaScript Console Object" button.
26 |
27 | 
28 |
--------------------------------------------------------------------------------
/docs/core-fields/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | sidebarDepth: -1
3 | ---
4 |
5 | # Core Fields
6 |
7 | Redux has a large variety of fields to choose from, over **35**, in fact. This section outlines all the fields that
8 | exist in the Core as well as how to configure these fields.
9 |
10 | ::: tip SEE ALSO
11 | - [Using & Creating Extensions](../guides/basics/using-extensions.md)
12 | :::
13 |
14 |
--------------------------------------------------------------------------------
/docs/core-fields/ace-editor.json:
--------------------------------------------------------------------------------
1 | {
2 | "type": "ace_editor",
3 | "name": "Ace Editor",
4 | "description": null,
5 | "icon": null,
6 | "groups": {
7 | "Global": ["id", "type", "title", "desc", "subtitle", "class"],
8 | "Advanced": ["attributes", "data", "compiler", "output", "output_variables", "permissions", "required", "default", "validate"]
9 | },
10 | "fields": {
11 | "id": {
12 | "name": "id",
13 | "title": "ID",
14 | "type": "input",
15 | "inputType": "text",
16 | "description": "",
17 | "order": 0
18 | },
19 | "title": {
20 | "name": "title",
21 | "title": "Title",
22 | "type": "input",
23 | "inputType": "text",
24 | "description": "",
25 | "order": 5
26 | },
27 | "subtitle": {
28 | "name": "subtitle",
29 | "title": "Subtitle",
30 | "type": "input",
31 | "inputType": "text",
32 | "description": "",
33 | "order": 10
34 | },
35 | "desc": {
36 | "name": "desc",
37 | "title": "Desc",
38 | "type": "input",
39 | "inputType": "text",
40 | "description": "",
41 | "order": 15
42 | },
43 | "class": {
44 | "name": "class",
45 | "title": "Class",
46 | "type": "input",
47 | "inputType": "text",
48 | "description": "",
49 | "order": 20
50 | },
51 | "compiler": {
52 | "name": "compiler",
53 | "title": "Compiler",
54 | "type": "bool",
55 | "default": false,
56 | "order": 25
57 | },
58 | "required": {
59 | "name": "required",
60 | "title": "Required",
61 | "fieldClasses": "full-width",
62 | "type": "array",
63 | "description": "Field visibility requirements.",
64 | "order": 35
65 | },
66 | "validate": {
67 | "name": "validate",
68 | "title": "Validate",
69 | "type": "custom-object",
70 | "order": 50
71 | },
72 | "mode": {
73 | "type": "select",
74 | "name": "mode",
75 | "title": "Mode",
76 | "values": ["css", "html", "javascript", "json", "less", "markdown", "mysql", "php", "plain_text", "sass", "scss", "text", "xml"],
77 | "required": true,
78 | "default": "javascript",
79 | "order": 80
80 | },
81 | "theme": {
82 | "type": "select",
83 | "name": "theme",
84 | "title": "Theme",
85 | "values": ["chrome", "monokai"],
86 | "required": true,
87 | "default": "monokai",
88 | "order": 80
89 | },
90 | "options": {
91 | "type": "custom-object",
92 | "formatter": "keyvalue",
93 | "title": "Options",
94 | "name": "options",
95 | "newElementButtonLabel": "+ Add Option",
96 | "selectValues": ["minLines", "maxLines"],
97 | "default": {
98 | "minLines": 12,
99 | "maxLines": 30
100 | },
101 | "order": 40
102 | }
103 | }
104 | }
--------------------------------------------------------------------------------
/docs/core-fields/ace-editor.md:
--------------------------------------------------------------------------------
1 | # ACE Editor
2 |
3 | The ACE Editor field offers the ability to edit back end code in an easy to use and easy to read embedded interface. In
4 | addition to matching the features of native code editors such as [Sublime Text](https://www.sublimetext.com/),
5 | [Vim](http://www.vim.org) and [TextMate](http://macromates.com), ACE offers real-time checking for code accuracy.
6 |
7 | 
8 |
9 | ::: warning Table of Contents
10 | [[toc]]
11 | :::
12 |
13 | ## Arguments
14 | Array containing the `content` and optional `title` arguments for the [hint](../configuration/fields/hints.md) tooltip.
15 |
16 | |Name|Type|Default|Description|
17 | |--- |--- |--- |--- |
18 | |type|string|`ace_editor`|Value identifying the field type.|
19 | |mode|string|`javascript`|Sets the language mode of the editor. Accepts: `css` `html` `javascript ` `json` `less` `markdown` `mysql` `php` `plain_text` `sass` `scss` `text` `xml`|
20 | |theme|string|`monokai`|Sets the theme of the editor. Accepts: `chrome` or `monokai`|
21 | |options|array|