🇿🇦South Africa @rudolfbyker

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

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

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

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

rudolfbyker → created an issue.

Duplicate of https://www.drupal.org/project/bulksms/issues/3016603 →

I ended up doing something completely different, and standalone: https://www.drupal.org/project/oai_pmh_harvester →

Due to lack of documentation, I ended up writing https://www.drupal.org/project/oai_pmh_harvester → without depending on this module.

@fishfree I'm willing to work on this if you can find a sponsor for it. I think it will take 3 work days. Alternatively, you may submit a merge request, and I'll review it.

I think this patch needs to be re-rolled for version 3.5.

v3 clearly states that it is supposed to be compatible with Drupal 10: https://www.drupal.org/project/geolocation/releases/8.x-3.12 →

v4 is still in alpha, so I can't use that on some projects.

Thanks. I merged your patch, with one small fix to the punctuation.

Thanks!

If you think this module needs a help hook, feel free to write one and submit a merge request. Otherwise, please use the "Closed" status instead of "Postponed".

Thanks for your time! I hope this module is helpful.

Done!

I'm also running into this issue. Thanks for the patches.

I think two more things are needed here:

1. Unit tests, so that this does not regress again.
2. A way to clear the secret in the UI when editing the consumer. Currently, if you leave the field empty, it just means "don't update".

rudolfbyker → created an issue.

rudolfbyker → created an issue.

This is not possible yet. It will take considerable development and design to get this working. I don't have the time, sorry.

Is this working for you @tikaszvince ?

Thanks for the reproduction. That saved me a lot of time.

I think since the used "caseyamcl/phpoaipmh" packages requires guzzlehttp/guzzle you do not need to lock this requirement at all.

Almost correct, but not quite. If oai_pmh_harvester used guzzle directly, we would need to keep it, even if it's provided by caseyamcl/phpoaipmh. But it looks like we are not using guzzle directly, so your patch is good.

Hi, please provide steps to reproduce the problem, rather than simply pasting an error message. I need more context to be able to help you with this.

Ah, I see it has nothing to do with the PHP version. I will release version 2.0.2 with your fix.

Thanks for the patch. Which PHP version are / were you using?