chaim
d266380e6d
Two UI-breaking issues discovered after 2.10.0 hot-patch: * Hitting /#CaseMemory in the navbar returned a 404 because CaseMemory was missing a Controller class. The entity used to be accessed only through Case relation panels and SmartAssistant action endpoints, so the bare REST surface was never wired. Same one-liner fix pattern as the AssistantRule controller in 2.9.2. * Layouts were placed under Resources/metadata/layouts/... but EspoCRM expects them at Resources/layouts/... (without the metadata/ prefix). Result: every new entity rendered only one column / one row in list views because EspoCRM fell back to a generic default layout. Moved AssistantPrompt, AssistantRule, AssistantSkill, CaseMemory, UserProfile layouts to the canonical path. Verified all five list endpoints now serve the configured columns. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
15 lines
370 B
JSON
15 lines
370 B
JSON
{
|
|
"name": "SmartAssistant",
|
|
"module": "SmartAssistant",
|
|
"description": "Unified AI Assistant for Legal CRM — floating chat with case memory, office alerts, and AI Gateway integration",
|
|
"author": "klear",
|
|
"version": "2.10.1",
|
|
"acceptableVersions": [
|
|
">=8.0.0"
|
|
],
|
|
"releaseDate": "2026-05-27",
|
|
"php": [
|
|
">=8.1"
|
|
]
|
|
}
|