🇺🇸United States @keiserjb

I see why there aren't any automated updates for Flexslider now. It looks like Drupal 11 moves to jquery 4. The flexslider library doesn't work with that and is no longer being developed.

I encountered a couple of other problems. In order to make it work I had to remove the ContainerInjectionInterface from DynamicPathProcessor.php.

I also needed to remove

calls:
- [setContainer, ['@service_container']]

from view_mode_page.services.yml

keiserjb → created an issue.

keiserjb → created an issue.

Thank you, I didn't turn on my work computer over the weekend.

This version of the form works for me.

public function extraAdvancedFormFields(ContentEntityInterface $entity, FieldDefinitionInterface $fieldDefinition, FormStateInterface $formState, array $defaultValues = []) {
    $form = parent::extraAdvancedFormFields($entity, $fieldDefinition, $formState, $defaultValues);
    $settings = $fieldDefinition->getConfig($entity->bundle())->getSettings();

    $form['automator_clean_up'] = [
      '#type' => 'select',
      '#title' => $this->t('Text Manipulation'),
      '#description' => $this->t('These are possible text manipulations to run on each created tag.'),
      '#options' => [
        '' => $this->t('None'),
        'lowercase' => $this->t('lowercase'),
        'uppercase' => $this->t('UPPERCASE'),
        'first_char' => $this->t('First character uppercase'),
      ],
      // Use the default value from the third-party settings or fallback to a default.
      '#default_value' => $fieldDefinition->getConfig($entity->bundle())
        ->getThirdPartySetting('ai_automators', 'automator_clean_up', 'first_char'), // Ensure fallback here
      '#weight' => 23,
    ];

    $form['automator_clean_up'] = [
      '#type' => 'select',
      '#title' => $this->t('Text Manipulation'),
      '#description' => $this->t('These are possible text manipulations to run on each created tag.'),
      '#options' => [
        '' => $this->t('None'),
        'lowercase' => $this->t('lowercase'),
        'uppercase' => $this->t('UPPERCASE'),
        'first_char' => $this->t('First character uppercase'),
      ],
      // Use the default value from the third-party settings or fallback to a default.
      '#default_value' => $fieldDefinition->getConfig($entity->bundle())
        ->getThirdPartySetting('ai_automators', 'automator_clean_up', 'first_char'), // Ensure fallback here
      '#weight' => 23,
    ];

    if ($settings['handler_settings']['auto_create']) {
      $form['automator_search_similar_tags'] = [
        '#type' => 'checkbox',
        '#title' => 'Find similar tags',
        '#description' => $this->t('This will use GPT-4 to find similar tags. Meaning if the tag "Jesus Christ" exists and the system wants to store "Jesus" it will store it as "Jesus Christ". This uses extra calls and is slower and more costly.'),
        '#default_value' => $fieldDefinition->getConfig($entity->bundle())
          ->getThirdPartySetting('ai_automators', 'automator_search_similar_tags', 1), // Ensure fallback here
        '#weight' => 23,
      ];
    }

    return $form;
  }

keiserjb → created an issue.

volkswagenchick → credited keiserjb → .

Yep, it worked. Thanks.

Mine says "TypeError: t.Model is not a constructor". I think the patch resolved it.

keiserjb → created an issue.

Based upon the behavior in here, how would any of us wish to become a customer?

Once again, I apoligize and thank you for the update.

I apologize for getting fired up but this is no longer an open source project if it is a paid service and the Drupal community cannot aid in the issue queue.

Why would I expect paid support to be any better than the support of the public project?

The community will help support this project if Opigno will let us. If not, expect a fork.

I think I've gotten this mostly working but I'm not releasing it yet. I pulled the latest dev branch to work on this. Thanks for the recent updates.

https://github.com/backdrop-contrib/scanner

So will Opigno be ready for Drupal 11? That's coming "soon" too.

Please let the community help move this project forward. It's been six months since Drupal 9 was deprecated. The development cycle is too slow, there are people who would help.

Could not agree more!

There are a lot of modules to fork. It is a pretty large undertaking.

I'll make a new issue with the altered methods if that is still a problem.

Very concerned about the status of Opigno and wondering about how the community could support this in some other way.

I have an implementation that adds a bee command that can be used on a new site install as well as a list that can be cut and pasted into the project installer.

Putting the Augmentor field inside the paragraph doesn't really work. Say I have a site without body fields. I only have paragraphs. If I put an Augmentor on a body paragraph to create the title of the node I can't target a field outside of the paragraph when configuring it.

I installed this patch on the dev branch of the module. An issue adding additional models was committed. https://www.drupal.org/project/augmentor_chatgpt/issues/3400720 ✨ Make available the gpt4 engine on the augmentor configuration Fixed

Because the method for getting the models is different for orhanderday and openai-php, the module breaks.

I found this thread because I'm trying to use the module with paragraphs. I could add the augmentor to the paragraph type but there may be more than one of the paragraph type and I would want the augmentor to use the data in all of the body paragraphs not just one of them.

Looking for ideas.

volkswagenchick → credited keiserjb → .

Very helpful, thank you.

Very helpful, thank you.

Very helpful, thank you.

Very helpful, thank you.

Very helpful, thank you.

I installed this patch and it changed the icon colors to black. However, I could not seem to change the color to any other color but black. I thought this would make it possible to override the icon color in css.

Yes, I agree.

A new merge request would be wonderful.

Wondering about the progress on this. I watched the presentation from DrupalCon Lille and was confused about the capabilities of of these two modules. https://youtu.be/NdkME10H8MM?si=Xo1W8sHu7EsD5Rws

Looks like this works. I finally tried it.

Thanks for getting this fix up on here. There are lots of modules that don't include a description in the annotations. This patch does fix things. I couldn't add fields on multiple sites and now I can.

Rolling back wasn't really an option. Too much had happened. That being said, I updated all the tables in my database where the langcode was und. Everything works now.

I think I found it. The langcode for all of the migrated content was set to und. I discovered that new content was set to en. Changing the database for the langcode table fixes the display. I just wish there was an easier way to update the database.

I did the migration with the UI so there weren't any custom migration files. This might be a weird scenario with the content types being Features in D7 and then migrated.

I've found that if I create new nodes, the new ones show up in the report. The old ones that were migrated do not. Perhaps I can find what is happening and trick the old nodes into resaving correctly.

I'll look at it again next week. I don't recall any errors. The report just shows zeros for the counts when they are not supposed to be zero. I made a custom module this afternoon to display the node counts and it was all correct.

Something very well could have gotten scrambled during the migration. The content types not working were Features in D7 that were unfeaturized and migrated but they seem to work other than this report.

@joseph.olstad I'm not here to debate the merits of individual projects choosing to stay on D7, move to D10, move to B, or something else entirely. The fact is, after end of life this project and the project that shall not be mentioned will have the same common goal, which is keeping contrib projects and a core with very similar codebases secure. I know I would be willing to send along anything from the modules I've ported and maintain, however most of them are so simple that it's unlikely I'd help much. There has always been collaboration about security matters between B and D7 and I'm sure an extended security team would be no different.

@joseph.olstad

That issue is closed. I was just adding an FYI where people could find actual information about the other project. Please stop sending people to the issue you created.

keiserjb → created an issue.

I do not wish to get beaten down for mentioning Backdrop here, but a more relevant link about our project and community is the chat platform that we use. Just an FYI.

https://backdrop.zulipchat.com/

keiserjb → created an issue.

I've migrated a few sites from the WP to the B so if you want the Drupal stuff you're missing in WordPress...there is a path.

Got it. No problem. I love this module. I plan on using it as a starting point for a Backdrop module when I get around to it.

I had this problem on a site upgraded from D7 to D10. On the page with all of my patterns I happened to click on "Show row weights." They were all 0. I went back to "Hide row weights." I reordered some of them. Then I went back to "Show row weights" and they all had weights. I saved the list. Then the bulk alias generation worked.

Thanks, still getting the error when trying to install rc2 but not when using the dev branch.

I've had this problem as well. I added a Media Keywords field to my media types that references a taxonomy. I upload a media item and try to fill in terms. The autocomplete dropdown is behind the media library modal.

I think some of the confusion may be that the inline editor is still not working with ckeditor5.

I think it still needs to be

use Drupal\Component\Datetime\TimeInterface;

not use Drupal\Core\Time\TimeInterface;

keiserjb → created an issue.

keiserjb → created an issue.

keiserjb → created an issue.

It was because I had Media Bulk Upload and DropzoneJS installed.

This seems to work for me on the /media/add/image page but when I add a media item from a node edit page the alt text does not get added. Trying to figure out how to fix that.

Yes, this is on the roadmap for when I revisit the module next fall. I wanted to get this out before Halloween.

I thought that it might not have enough php after reading some comments on other projects. I tried this with another project which I may resurrect. Unfortunately this is my first module on d.org. I've only release modules in Backdrop before now. It looks like this approval will need to be delayed until I contribute to Drupal more.

keiserjb → created an issue.

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

Found this patch and it solved my problem.

Well, I ran the new branch through the Coder Upgrade module https://backdropcms.org/project/coder_upgrade. I then messed around with it a little and I think it works in Backdrop.

https://github.com/keiserjb/site_audit

We'd need to make it work with Bee instead of Drush. I can loop in our Bee maintainers.

This is great. I put the release on a D7 site and it's really going to help with the upgrade. Sorry I did not know how to help more.

I don't know if this is related but I get a lot of javascript errors in my console when editing content.

Agreed, I released an Alpha.

keiserjb → created an issue. See original summary → .

I am having the same problem but not having any luck with the newest version of s3fs.

I left before the end yesterday. How far did you guys actually get and where did the code you were working on go?

Jon Pugh → credited keiserjb → .

Hmm, after patching the accordions to make them work with Bootstrap 5 I can still edit them using Layout Paragraphs. They have IDs. More investigation needed.

Patch is not applying for me. Trying to do it manually.

Trying to use Layout Paragraphs on a D10 site.

Installed the Bootstrap Paragraphs module and was experimenting. When I got to the Callout paragraph type I discovered I could not edit them after creating them. I looked in the template and sure enough, and ID was assigned to each Callout. I removed

{# Sets Unique ID for Accordion from Paragraph ID. #}
{% set paragraph_id = 'callout-' ~ paragraph.id.value %}

{# Prints Callout template. #}
<div{{ attributes.addClass(classes).setAttribute('id', paragraph_id) }}>

from the template and I can edit them now. I think accordions and tabs will not work because of the same issue.

Got it to work, another patch was messing it up.

The patch doesn't apply for me. Using the dev version of the module on 10.0.9.

Same problem. I switched to Gin and it made things better. The new window option is a possible solution. Maybe that could open in a new tab?

Installed site audit on D10. The report doesn't work and the log says

Drupal\Core\Entity\Query\QueryException: Entity queries must explicitly set whether the query should be access checked or not

Something is still amiss.

The stories.media.info.yml should also change so the submodule works.

After a few years I'm revisiting this. Looking at using Bootstrap across Drupal, Backdrop, and WordPress sites. Hopefully I can use your D7 work to get these configurations working in Backdrop.

When I turn on rules I still get a notice.

Notice: Undefined property: RulesReactionRule::$plugin in views_natural_sort_views_natural_sort_queue_rebuild_data() (line 233 of /app/sites/all/modules/views_natural_sort/views_natural_sort.module).

Interested in trying to get this working because it would probably help out the other project I work on if I could port a module with a UI.

I'm going to try and take a look at the issue for the site audit module.

Yes, that was me a second different was removed.

I finally helped out with Project Browser, secondhand though.

More excited now. Looking forward to meeting some more Drupal folks.

#6 might not play nice with the Rules module.

EntityMetadataWrapperException: Invalid data value given. Be sure it matches the required data type and format. in EntityBackdropWrapper->set() (line 761 of /app/modules/contrib/entity_plus/includes/entity_plus.wrapper.inc).

Installed the patch in Drupal 7 and the undefined property is gone. Thank you!

When it gets to the last step of the indexing the 'content' index of the array for the mime is null. I changed the line to set it to an empty string if it wasn't set. Don't know if this is correct, but the undefined index is gone and the titles are in the correct order.

'content' => (isset($entity->$field_name) ? $entity->$field_name : ""),