@dhavalpanchal

I am adding the patch file instead of using a PR in the composer.json file in Drupal 10.4.6 with PHP 8.3.

dhavalpanchal → created an issue.

I am adding the patch file instead of using a PR in the composer.json file for PR #11146 in Drupal 10.4.3 with PHP 8.3.

I have created a patch file instead of using merge request of jsutta in composer json file.

Adding the patch file instead of using git MR in composer json.

dhavalpanchal → created an issue.

dhavalpanchal → created an issue.

dhavalpanchal → created an issue.

dhavalpanchal → created an issue.

dhavalpanchal → created an issue.

@sourav_paul please provide issue link as well not just patch.

jurgenhaas Can you please remove the duplicate tag ?

@jurgenhaas It will be nice if you provide fix for an older version.

@jurgenhaas My project is on Drupal 10.2 and will remain on 10.2 for the next 4 months, so I cannot update the module to version 2.1.2, which supports only Drupal 10.3.

@jurgenhaas These is not duplicate it is coming up in drupal 10.2 and php8.2 version.

dhavalpanchal → created an issue.

dhavalpanchal → created an issue.

dhavalpanchal → created an issue.

dhavalpanchal → created an issue.

dhavalpanchal → created an issue.

dhavalpanchal → created an issue.

dhavalpanchal → created an issue.

dhavalpanchal → created an issue.

dhavalpanchal → created an issue.

Created D10 compatible for 1.0.0 version.

dhavalpanchal → created an issue.

I have created patch for deprecated warnings in php8.2 version.

dhavalpanchal → created an issue.

Added Drupal 11 compatibility in 1.0.2 release.

Yes, my team is also facing the same issue even when we create new account.

@naveenvalecha, to reproduce the issue:

I have followed all the necessary steps to integrate the augmentor_openai_gpt3 module:

1. Generated an OpenAI API key.
2.Created the key configuration for storing the OpenAI API key.
3. Created a new augmentor type and selected the newly created OpenAI API key.
4. Added an augmentor field to the page content type.
5. Configured the target and source fields in the selected augmentor widgets.
6. Now, when I go and try to add new content in that field, it is returning the issue I raised a concern about.

Feel free to ask if you need further assistance!

Hello, I am facing these issue when i go to add content and click on widget button on my content adding page.

I am facing these issue when i select any widget type in manage form display for augmenter field type.

I am facing these issue when i select any widget type in manage form display for augmenter field type.

dhavalpanchal → created an issue.

dhavalpanchal → created an issue.

dhavalpanchal → made their first commit to this issue’s fork.

dhavalpanchal → made their first commit to this issue’s fork.

Hello @MukhtarM please check now I have removed that extra empty folder.

Hello @MukhtarM thanks for picking up the issue. Please check now the issue is fixed.

dhavalpanchal → created an issue.

dhavalpanchal → created an issue.

dhavalpanchal → created an issue.

dhavalpanchal → made their first commit to this issue’s fork.

dhavalpanchal → created an issue.