TastyIgniter 3.x does not let you edit order emails

This procedure applies only to TastyIgniter 3.x. The 4.x branch does not use this configuration path.

If the visual email editor does not respond, first open Console and Network in the browser tools. Keep the first JavaScript error or failing resource and check the TastyIgniter log for the same time. The symptom alone does not prove a combiner conflict.

If the combined assets fail, make a copy of config/system.php, find enableAssetCombiner and temporarily change TRUE to FALSE:

'enableAssetCombiner' => false,

Clear the application and browser cache, reload the editor and repeat the same action. If it works, keep the original error and update TastyIgniter 3.x and its extensions before deciding whether to keep the combiner disabled. If nothing changes, set it back to TRUE: the test did not confirm that hypothesis.

For TastyIgniter 4.x, follow the documentation and configuration of the current branch; do not add enableAssetCombiner to a file that no longer contains it.

The snippet is an entry in the existing configuration array, not a complete PHP file. Keep the commas and structure of config/system.php and check its syntax before testing.

If the editor works again, save a test template and check the generated email without sending messages to customers. A visual change in the editor does not prove that delivery works. This 3.x mitigation should go together with a plan to migrate to a maintained branch and a review of its extensions.