Special order 0 of 0 ms alias not specified ID, name or alias ID, title, tag or category Native confirmed Native is not yet available SQL in public debugging SQL and diagnostics {{ native_verified ? 'The current plan matches Legacy' : (native_plan.eligible ? 'Run a preview for shadow comparison' : (native_plan.reasons|first)|default('Native is not available yet')) }} · category # · states: · number Alias: No changes Untitled Without rules, the order of materials can change if the values are the same. In Native There are no conditions for this group yet Return Legacy The top rule is applied first. Drag rows to change priority. Preview type Request preview type On Enable Confirmed External call Caching time, seconds All request conditions Select field Select comparison Choose a convenient view to check your request in the admin panel. The selected view is applied by the “Update” button in the preview. Conclusion Ready Ready to compare Ready value Condition groups The group sets the logic for all the elements inside. Nested groups become SQL parentheses and allow AND/OR combinations to be assembled without ambiguity. Tag groups Condition tree Add a nested group Add level Add condition All elements inside must be executed Any element inside is enough Pin by ID Reinforce order Request The request has been saved. Request: Requests requests in the list. No requests yet Run preview for shadow comparison Comparison value And Change priority Changed OR Parameter name Source: Ready Value. Source: "URL or Form Parameter"; an empty parameter is not used. For inquiries How to process a parameter How to show the result How to collect a condition What data does the API, preview and future renderers receive? Current public templates do not change. What value to substitute The catalog contains catalog Order key Compatibility code The Check All command first turns on Shadow, then sequentially compares the count, ID, and order. Native is enabled with a separate button only for exact matches. Result Contract Cache items Latin; used in the request insertion tag. listings templates and conditions for selecting documents Group logic Materials per page It only changes the display of the check below. On the main page = Yes AND (News OR Article) The site uses the current template Click "Update" to check your selection and contract. Group name found Find the material in this section and check each stage of the selection. Sort direction For example, 2026 For example, catalog For example: equals, contains, greater than, or is in a list. Query setup Not selected Not supported Don't show open document Not verified Nothing found for your request. new New request Need manual verification Needed for integrations and old templates General list template Explain Regular The same key maintains order between pages. Leave empty to mix again. Waiting for verification Basic parameters, conditions and presentation of the result. Where to get the value The order is different URL or form parameter The first documents are selected by the current public executor, and the display method is taken from the renderer registry. The item/main templates are not executed. Plan Ascending Descending Preparation Count all results Confirmed Search tags shown Show pagination Show statistics Field, comparison, value source and group logic with simple examples Category fields Order of materials No order specified The order is not fixed After saving, the real data of the selected category will appear. The constant value is set manually, the dynamic value is taken from the URL or form. Permanent filter Why did the document hit or miss? The preview has not started yet Preview the result Legacy reasons are stored next to the request and do not block other views. Check all Check request Native check Native Check Requests Document verification View Validation We are checking the request... Checked to field conditions. The public site remains on Legacy during verification Works Expand Advanced Edit site template Mode Editor mode Test results Results vary Rubrik Reconciliation Your request System name (alias) System data System limitations Parentheses and operators are shown in order of execution. Service presentation Service parameters Service tags and Legacy PHP are only needed for compatibility. For new conditions, select values ​​in the form: the engine itself will check the input data and safely assemble the filter. Random order First create a view. Save your request first First, save the request and the selected category. Gather groups Compatibility Compatible Matches Create a nested group and switch it to "OR". Create your first selection of documents. Create a new listing Sort by Save your request to add conditions Saved selections of documents and tags for inserting them. Saved list and material templates will continue to work without changes. Saved PHP code List of requests Comparison Comparing old and new selections without changing site templates Rows The current version of the plan is the same as Legacy Material type = News Only yours requires all the elements Requires Legacy The selected category has no fields. Remove level Delete group Removed template · # Please indicate your source Condition with brackets Terms Terms Query conditions and actual result of executor. Consider the language Filter Filter from address Single material template Pagination template Templates not created This is the document data that the request will check. - at least one. A nested group works like parentheses. (copy) . Prepared declarative conditions: . An empty parameter does not participate in filtering. <div class="request-explain-options-state is-error"><i class="ti ti-alert-circle"></i>Search unavailable</div> <div class="request-explain-options-state"><i class="ti ti-file-off"></i>Documents not found</div> <div class="request-explain-options-state"><i class="ti ti-loader-2"></i>Search...</div> <div class="request-explain-tree-empty">There are no active conditions in the group</div> <i class="ti ti-filter-off"></i><b>Documents not found</b><span>Check the conditions, publication status and selected category.</span> <i class="ti ti-loader-2"></i><span>Checking the request...</span> <span class="request-explain-condition-state"><i class="ti"></i></span><div class="request-explain-condition-copy"><div><b></b><code></code></div><dl><div><dt>Actually</dt><dd data-actual></dd></div><div><dt>Condition</dt><dd data-expected></dd></div></dl><p hidden></p></div> <td colspan="6" class="ax-empty">There are no conditions in this group yet</td> [structured data] Document ID Legacy SQL (compatibility) Native is enabled only for confirmed requests no changes: · extra IDs: · no ID: · checked states: · withdrawn from publication · deleted » in the format |value| » filled ", when the parameter " active conditions No explicit sorting Safe final order not found More more Greater than or equal to greater than or equal to Take a decimal number Take decimal range Take range from/to Get a list of text values Get a list of numbers Take the text as is Take an integer All available fields have already been added All requests returned to Legacy All requests are transferred to Shadow safe mode Included in the list included in the list selected field In progress groups Group saved Yes decimal number from parameter " Range including boundaries Range not including borders range min/max from the parameter " For each request, the complete Legacy sequence will be checked against the ID in ascending and descending order. Native will only be enabled if there is an exact match; any discrepancy will automatically cancel the change. Document Document title.innerHTML = Document var icon = document.createElement( Document this.setText(drawer, Document }, previewEntries: function (item, systemOptions, fieldOptions) { var entries = []; Object.keys(item.system || {}).forEach(function (key) { if (key !== No documents found All elements must match One coincidence is enough Reinforce the order without changing the output? Close Request not found Request verified Request verified, PHP conditions replaced with declarative tags There are no queries with loose order Requests Queries: view Queries: management parameter value " meaning " parameter value " from Cache, integrations, compatibility, result contract and Native executor. Content Extra in Native: (comparison.reasons || []).forEach(function (reason) { details.push(reason); }); if (details.length) { var meta = document.createElement( Boolean value Material Less less Less than or equal to less than or equal to You can add up to eight levels Found: Find document Starts with starts with Start typing your name Not included in the list not included in the list Doesn't start with doesn't start with Not equal not equal does not contain Does not contain text Failed to secure order Validation failed Failed to upload documents Failed to save group Failed to delete group No Nothing found Wrap value: |value| Wrap list: |value| Explain the result one of the parameter values " Published, not deleted and within the publication deadline Remains Legacy Error Validation error Network error Network error when checking document parameter Substitute constant if filled Position Field if ($type !== Field } elseif ($rule[ Field item.querySelector( Field " The order is fixed without changing the Legacy result The order is fixed: The order changed during the control check. The setting has been cancelled. Order verified Order preserved Check and secure Checking requests Verification failed Scan stopped Post verification The order of the request is checked self.auditRequest(self.auditBase() + checked by free condition View the list of requests (listings). Equals equals the result of the saved PHP code. Random order is used without other levels Shuffle cannot be combined with other levels First save your request. Matches any matches one of the values contains Contains text Creating/modifying queries, templates and conditions. Saved is compared with the value Shadow comparison failed Delete Delete group? Delete condition? specify a constant Conditions and nested groups will be moved to a higher level. fixed value Final order by ID has already been added The final order is already set an integer from the parameter " The number is greater Number greater than or equal to The number is less Number is less than or equal to This field is already being sorted