Skip to main content

Custom Order plugin settings

Fixed source separates the generic Plugin settings list from the Pro Custom Orders component at /all-settings?category=custom_order. Project-returned plugin categories, IDs, roots, fields, and values are not portable.

Plugin settings navigation showing Custom Order without its toggle value

Plugin-category boundary​

AllSettings supplies returned key_plugin categories to SettingsMenuOptions; a numeric category opens generic SettingsList. Returned config edits stage locally and Save persists items sequentially; type-5 images save immediately. Historical Custom Order Enabled belongs to this returned category evidence. The separate Developers → Plugins manager owns install/root/iframe actions.

Pro Custom Orders source trace​

The Dashboard checks fixed key custom_order before adding the Pro item. If returned, it uses the plugin root and project code to request an external settings schema. The fixed component treats these keys as administrator-only global settings:

  • max_weight
  • delivery_fee_multiplier
  • max_distance

Names, descriptions, values, types, validation, and all other keys belong to the returned external schema. Historical label Custom Order Enabled is not a fixed Dashboard schema guarantee.

The Pro form displays numeric inputs and on Save converts every displayed value with parseFloat(value) || 0 into one combined POST to the external plugin-root settings URL. No lookup, schema read, navigation, edit, or combined write ran.

Order and data separation​

The plugin settings and Pro configuration components do not mount Orders → Create custom order. Historical customer/address/store/product/total/payment fields and order effects are outside this page and remain excluded.

Source-only boundary​

  • /all-settings is level-0 routed; Plugin settings requires returned categories and the Pro item requires the plugin-key response.
  • API-core declares config category/item plus plugin collection/key/item/install/uninstall routes; verbs and presence do not prove authorization, installation, persistence, or effects.
  • The retained screenshot is sanitized historical navigation evidence, not current installation/configuration proof.
  • No runtime/GET/HEAD, config/image write, plugin-manager action, schema request, order, delivery, payment, PII, job, or outbound call ran.

Re-entry requires immutable Dashboard/API and Custom Order plugin serving receipts plus a synthetic project with lookup, navigation, schema read, combined write, order data, and all external egress intercepted.

Related guides: Plugin settings · Custom orders settings · Create custom order