🇺🇸United States @awm

We could move this to a feature request and I might give it a shot. Having search integrate with administrative views is a great feature and likely a small lift because searchApi does most of the work if I am not mistaken.

awm → created an issue.

Thanks - I traced the issue to a malformed configuration. I had nid set to be int32[] instead of integer and I also had it to sort by it.
I had to step debug to see the error response from typesense during the `->createCollection` "nid is not sortable".
Perhaps we can improve the messaging.

awm → created an issue.

> creating PHP files on the fly and run them from temp dir it's a terrible idea. Don't do that, it's a security issue.

Agreed...

I added you as a co-maintainer.

unfortunately I can't rename it. If they want to take over the name space they could

I created a new proj here
https://git.drupalcode.org/project/canto

KarlShea I can add you as a co-maintainer. Please take a look and and lets discuss there. if we can ever consolidate the modules into one, I am happy to do so.

> back to the project ownership queue to request moderation assistance.

I am not suer how to do that - feel free to move it.

I think we were in the process of attempting to take over the namespace.
https://www.drupal.org/project/canto_connector/issues/3332044 💬 Offering to maintain Canto Connector Active
but I don't mind forking the module but I'd appreciate if we keep the attributions of commits.

awm → created an issue.

correct patch file.

updated the patch to use filesystemInterface to avoid this error
TypeError: Drupal\publication_date\PublicationDateUpdate::__construct(): Argument #3 ($fileSystem) must be of type Drupal\Core\File\FileSystem, Drupal\s3fs\S3fsFileService given

I ran into this issue as well when I moved a module from contrib to custom and back. It's related to how the vendor directory is synced. Make sure to clear compser cache and dump autoload. If that does not work, run lando rebuild which re-syncs the vendor directory. 

Hi all, just following up on this. I am currently using this module with my modification on a key project and I am still interested in becoming a maintainer.

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

awm → created an issue.

any updates on this? does anyone know where to go to get maintainer-ship approved if the original maintainer is not longer active?