🇮🇳India @anjaliprasannan

Account created on 3 February 2020, over 5 years ago
  • Drupal Developer at QED42 
#

Recent comments

🇮🇳India anjaliprasannan

Reviewed the changes. It working fine.
Attaching before and after

🇮🇳India anjaliprasannan

anjaliprasannan made their first commit to this issue’s fork.

🇮🇳India anjaliprasannan

anjaliprasannan changed the visibility of the branch 3535100-ai-assistant-ckeditor to hidden.

🇮🇳India anjaliprasannan

anjaliprasannan made their first commit to this issue’s fork.

🇮🇳India anjaliprasannan

anjaliprasannan changed the visibility of the branch 3534675-field-widget-action to hidden.

🇮🇳India anjaliprasannan

anjaliprasannan changed the visibility of the branch 3534675-field-widget-action to active.

🇮🇳India anjaliprasannan

anjaliprasannan changed the visibility of the branch 3534675-field-widget-action to hidden.

🇮🇳India anjaliprasannan

I have reviewed the fix. Working fine.
Can be moved to RTBC

🇮🇳India anjaliprasannan

@vivek panicker I tried in new installation still and same steps as above, I do not get the translation field in field settings.

🇮🇳India anjaliprasannan

I have review the MR.
But on translation on any option selected the translated content is saved as published. It is not keeping the currect status of the original node.

Steps followed:

  1. Enabled translation for the content article.
  2. Added additional language.
  3. Moved the original content to draft state
  4. Selected the "Keep the status of original entity" option in ai translation settings and saved.
  5. tried translating article content
  6. The translated content is saved as published.
  7. Go back to ai trsnslation settings and change the option to "Create translation in draft status" and tried translating the content.
  8. The translated content is saved as published.
🇮🇳India anjaliprasannan

anjaliprasannan made their first commit to this issue’s fork.

🇮🇳India anjaliprasannan

anjaliprasannan made their first commit to this issue’s fork.

🇮🇳India anjaliprasannan

I have reviewed the branch.
Steps followed:
Add a new vocabulary, with terms Brand voice and description Speak like in conference.
Enabled Alter tone in content suggestion and checked in content edit.
Attached the ss after and before fix.

🇮🇳India anjaliprasannan

Thank you @a.dmitriiev for asking this. I have cloned the ai module and working with it. Now I tried installing the module using composer and the issue is not reproducible in stable version. You can close the ticket.

🇮🇳India anjaliprasannan

Reviewed the fix. The issue is fixed. MR LGTM. Moving to RTBC.
Steps followed:

  1. Enabled AI content suggestion module
  2. Go to the "Manage form display" page for a content type that has a text field (e.g., Article > Manage form display).
  3. Edit the widget settings for a supported field (like "Body" or any text field).
  4. In the widget settings dialog, look for the "AI Suggestions" section.
  5. You should see a "Button label" text field. Enter a custom label and save.
  6. Now, create or edit content of that type. The AI Suggestions button should appear near the field, using your custom label.
  7. Do steps 2 to 4 and leave the "Button label" text field empty
  8. Now, create or edit content of that type. The AI Suggestions button should appear near the field, with "AI suggestions" label.
🇮🇳India anjaliprasannan

@Divya
I have rechecked. The changes are reflecting properly. Attaching a working screencast.

Please checkout to the branch using this git checkout '3530683-toolbar-in-ckeditor' command then do a git pull, git drush cr to review the changes.

🇮🇳India anjaliprasannan

The issue is reproducible.

@vivek panicker
I have reviewed the functionality.

Steps followed:
Enable translation on the site, configure a new language for content types
Add a chatbot with Field Type Agent enabled
Ask the chatbot to add a field to any content type
Inspect the field

Actual output:
Chatbot responds that it has set the field as translatable.
But no "Users may translate this field" option found in the newly created field settings.
When the content is translated the new field value is not translated.

SS attached.

🇮🇳India anjaliprasannan

@divya.sejekan
I have fixed the issue. Please review.

Among your points
1. Should get error only for AI provider field
This is not valid as we discussed via slack.

2. if removed AI from the active tool bar its not allowing to save.
This I have fixed. Please review.

🇮🇳India anjaliprasannan

@sirclickalot
I have implemented the approach in #16 Please review them. I could not find a solution other than js changes. I am checking if there is a approach to remove the plugin before adding them to ckeditor.

🇮🇳India anjaliprasannan

This issue is with the Drupal core action tools in tools explorer. Should this ticket go under Drupal core issue?

🇮🇳India anjaliprasannan

Retested after new changes. Fix works fine. Code LGTM.

🇮🇳India anjaliprasannan

@sirclickalot

I'm encountering a strange issue on my local setup where CKEditor isn't functioning correctly, both on and off the issue branch. I've tried various solutions like clearing the browser cache, reinstalling Drupal fresh, and exploring AI options, but nothing has worked. As a result, I couldn't test whether another approach might resolve the issue.

I have a suggestion regarding the AI balloon menu. Instead of maintaining two separate menus (AI Assistant and AI Balloon Menu) with similar features, we could integrate the AI Balloon Menu as an option within the AI Tools settings in CKEditor, perhaps as a checkbox to enable or disable it. This way, we avoid cluttering the toolbar with two icons and keep only the AI Assistant icon. However, this raises the question of why we need the AI Assistant in the toolbar at all, as it takes up space. To address this, we could include a help text or disclaimer stating that enabling the AI Balloon Menu in the AI Assistant settings will hide the AI Assistant icon in the toolbar. What are your thoughts on this approach?

🇮🇳India anjaliprasannan

I have reviewed the Fix.
Steps followed:

  • Created a new agent to use the create content type tool
  • Created a user without administer content types permission
  • Navigated to the newly created ai agent's explorer page
  • Gave the prompt "Please create a content type with name Home and fields address, location"
  • Clicked on Run Agent

In Final Answer I am getting Error: undefined.

🇮🇳India anjaliprasannan

@thejimbirch Can you please update the steps to reproduce?

🇮🇳India anjaliprasannan

I have retested and found the issue is fixed.

🇮🇳India anjaliprasannan

anjaliprasannan made their first commit to this issue’s fork.

Production build 0.71.5 2024