anjaliprasannan → changed the visibility of the branch 3521839-console-errors-after to hidden.
@marcus_johansson this issue is replicated in 1.0.x
anjaliprasannan → made their first commit to this issue’s fork.
Keeping the mMR in draft as there is further work to be done.
anjaliprasannan → made their first commit to this issue’s fork.
Yes, This is correct. It would be better to use 2 different icons for ai ckeditor and ai baloon menu.
I tried installing the ai module 1.1.0 - beta version and did not get the above error in the status report.
Can you elaborate on the steps to reproduce?
@dudeweb The issue is not reproducible.
Steps I followed:
- Enable translation for content in admin/config/regional/content-language
- Enable Ai translation module and enable content translation in admin/config/ai/ai-translate
- Choose default provider for Translate Text in admin/config/ai/settings
- Try translating content using Translate ai option in content edit.
Content is translated.
Please provide more detailed steps to reproduce.
@ishani patel the issue exist in 1.0.x and the fix works well.
Moving to RTBC
anjaliprasannan → made their first commit to this issue’s fork.
@marcus_johansson I have modified the code now, can you review it?
Closing as druplicate of https://www.drupal.org/project/ai/issues/3523327 🐛 Select fields toogle not working for content suggestion sections Active
anjaliprasannan → created an issue.
anjaliprasannan → created an issue.
anjaliprasannan → created an issue.
The main changes are:
- For chat operations, now includes all GPT models including o3 models
- For JSON output capability, includes all GPT models without excluding mini versions
- For image vision capability, includes all GPT-4 models
- Removed unnecessary filtering of specific model versions
- Kept basic operation type filtering to ensure models are used for their intended purpose
anjaliprasannan → made their first commit to this issue’s fork.
anjaliprasannan → made their first commit to this issue’s fork.
anjaliprasannan → made their first commit to this issue’s fork.
Converted the patch to MR,
Reviewed the changes and it works well for me. adding before and after patch screenshots.
Moving to RTBC
Chose to provide a centralized list of all configured providers at /admin/config/ai/providers with checkboxes to enable or disable each.
Please review
Resolved MR conflicts
anjaliprasannan → made their first commit to this issue’s fork.
anjaliprasannan → created an issue.
Here are the steps to implement that I understand from the requirement.
1. Enhance ContentType Agent for Required Actions
Implement All Required Actions:
- Add getBundleTypes($entity_type_id) to retrieve bundle types for an entity type (currently supports node only, extensible for others).
- Modify getVerboseNodeTypesAsString($dataName = '') to support fetching detailed information for all or a specific node type.
- Retain and refine createNodeType() to create a new node type with structured inputs.
- Retain and refine editNodeType() to update an existing node type’s settings.
- Keep deleteNodeType() restrict, returning user instructions for manual deletion due to permission limitations.
Update agentsCapabilities():
- Define detailed schemas for all actions (get_bundle_type, get_verbose_node_type_information, create_node_type, edit_node_type, delete_node_type) with inputs, outputs, and descriptions to support GUI integration.
- Add support for both free-text prompts and structured action inputs (e.g., { "action": "create_node_type", "data": { ... } }).
- Update determineTypeOfTask() to handle structured action inputs alongside free-text prompts, mapping them to the appropriate task types (e.g., create_node_type, edit_node_type).
- Enhance validation for edit_node_type and delete_node_type to check node type existence, suggesting similar node types if not found.
Add Utility Methods:
- Introduce getPreviewModeLabel($mode) to provide human-readable labels for preview mode in verbose output.
- Ensure setOverrideValue() supports default field values (e.g., sticky, promote, status) for node types.
Added Action Discovery:
- Implement getAgentActions($agent_id) to return an agent’s action schemas (from agentsCapabilities()['actions']) for dynamic GUI form generation.
- Supported Structured Action Requests:
- Updated triggerAction($action_id, $parameters) to process structured parameters (e.g., { "action": "create_node_type", "data": { ... } }) by merging action and data into the agent’s data structure.
@marcus_johansson Please confirm if I can proceed with these steps or you have a different approach?
anjaliprasannan → made their first commit to this issue’s fork.
Please update the steps to reproduce once identified.
@jeetmail72 I have reviewed and tested your patch. it is working fine.
Before:
After:
I have also create MR for the patch. Moving to RTBC
anjaliprasannan → made their first commit to this issue’s fork.
anjaliprasannan → changed the visibility of the branch 3492413-automator-llm-audio to hidden.
anjaliprasannan → made their first commit to this issue’s fork.
anjaliprasannan → made their first commit to this issue’s fork.
anjaliprasannan → created an issue.
Fix the issue and no ajax error in console.
Please review
Ok lets wait for input from maintainers.
anjaliprasannan → made their first commit to this issue’s fork.
anjaliprasannan → made their first commit to this issue’s fork.
anjaliprasannan → made their first commit to this issue’s fork.
anjaliprasannan → made their first commit to this issue’s fork.
I see the same issue in summarize, translate, fix spelling, reformat html, tone prompts as well.
@sirclickalot Can you give more precise steps to reproduce the issue?
The issue is not reproducible. It should be some local installation issue.
Steps followed:
- Used ollama provider as ai assistant
- Enabled the ai deepchat bot block in content region
- In homepage tried using the ai deepchatbot
No error poped up.
The issue is not reproducible. It should be some local installation issue.
Steps followed:
- Used ollama provider as ai assistant
- Enabled the ai deepchat bot block in content region
- In homepage tried using the ai deepchatbot
No error poped up.
Moving to Needs review. Fixed the MR pipeline issues.
anjaliprasannan → made their first commit to this issue’s fork.
SS after fix
Work done:
- Correctly process the tools selected in the modal.
- Rebuild the detailed tool usage section when tools are selected.
Remaining work
- Update the save method in ai agent form to handle the data from the modal form on click apply.
To continue with the remaining work, I am a bit confused with the implementation of how to take the values in the modal form on apply click to the ai agent form and save them in the ai agent form?
This issue should go under ai_agents. Hence I have created one and linked the issue.
anjaliprasannan → created an issue.
ok @mrdalesmith. Waiting for the maintainers input.
I could not reproduce the issue.
Steps :
Set the administrative theme as claro
Uploaded files to image and media fields
No such issue was found
anjaliprasannan → made their first commit to this issue’s fork.
anjaliprasannan → made their first commit to this issue’s fork.
anjaliprasannan → made their first commit to this issue’s fork.
anjaliprasannan → made their first commit to this issue’s fork.
Screenshot of fix.
As per my understanding these are the required changes to be done. Pointing this for maintainers confirmation.
Redesign the AI Assistant Form Layout:
- Modify the existing AI Assistant configuration form to resemble the AI Agents form. This means consolidating the agent selection and creation process into a single interface.
- Replace the current "Use agent as assistant" dropdown with a more integrated field that allows both selecting an existing agent and creating a new one on the fly.
Create Agent on Save:
- When the user saves the AI Assistant configuration, implement logic to check if a "New agent" option is selected.
- If so, programmatically create a new agent using the provided details (e.g., the administrative description and selected tools).
- Automatically link this newly created agent to the AI Assistant by updating the assistant's configuration to reference the agent's ID.
Integrate Agent Selection Field:
- Add a dynamic dropdown or autocomplete field labeled "AI Agent" (as suggested in your description) that lists existing agents.
- If the user selects "New agent," display an inline form to input agent details (e.g., name, description, and tool preferences) before saving.
- Upon saving, the system should create the agent, assign it the selected tools, and connect it to the AI Assistant in one action.
@mrdalesmith Apologise, I have tried this again and I see the issue exist. Once the maintainers have a word on this, I will proceed on the fix.