🇧🇪Belgium @tim-diels

This will need an update using the latest template.

tim-diels → created an issue.

IT would help if you provide more information in the issue summary so others don't have to look into the code to understand what the issue is about. The ticket template is there for a reason.

The MR is for 2.x

As there's a patch, this can be set to needs review.

Hi Plach, I created the issue before the biggest blocking issue was resolved.

I do understand that you are hesitated to allow other persons as maintainer. Force there is no big must at this moment to maintain extra modules. I just wanted to have the new release done. As that’s done, for me it’s ok to cancel this request.

I am already happy that the module exists and that there was a reaction.

I will do some contributions if needed, but no need to make me a maintainer if there’s follow up.

For me this can be closed.

Since the other issue is fixed. This can be reviewed also.

MR added.

Here we go, MR created.

Wrong button, oops

tim-diels → changed the visibility of the branch 3282292-support-for-entity to active.

tim-diels → changed the visibility of the branch 3282292-support-for-entity to hidden.

I'll add it to a MR

The patch from entity browser and this one together works for me. Thanks!

@arnaud-brugnon this doesn't work for me. The patch in #4 did work tho.

This needs to be in a MR.

@er.garg.karan , you opened a MR for 4.0.x but the branch is still 3.0.x. Can you please update that? I'm not able to do it for you...

I added patch from #8 to a MR. Hiding all patch files as not relevant anymore.

Credits go to zhaoyao@ciandt.com and Oscaner forthe work done.

Maybe we need to define next steps in how to proceed in this?

Hiding patch from #9 as the patch provided there is exactly the same as #8 except that the paths to the files are changed and incorrect. So lets add #8 as a MR to correctly follow up and let the pipelines run to see if there is still work to be done.

This will need more information to see what is wrong.

Can you verify if the correct packages repositories are included to fetch the modules from Drupal?

I added the patch as MR and manual testing seems to solve the issue and does not break on other parts. But maybe I'm not testing all cases.
Putting this to needs review for others to review aswel.

Added screenshot of error for direct idea of issue

I did not find a quick solution to have the messages in an own container. So for now I added them to the global container as we're going to use Toastify to print the messages in a better way. If someone wants to improve this, feel free to do so.

I added some console logs to make it clear what is happening. Also did a check on the address if not empty and then don't call the geolocation provider.

This can however be improved and show a message in the website itself. I was looking at https://www.drupal.org/node/2930536but → that will print the message on top of the webpage and is not ideally. The message should appear inside the fieldset? I would suggest on adding a message container in the fieldset and attach the messages there. But other ideas are welcome on how to tackle this.

I provided some code changes already to ✨ No visual message when geolocate returns nothing Active that handles this. Lets focus on the work done there to continue.

tim-diels → created an issue.

Added support for the module. Not sure if it needed to be in a submodule or just in the base. So didn't add any tests yet. But shouldn't be that difficult to add. But first would like a review of a maintainer on whether it needs to be a submodule or not.

tim-diels → created an issue.

tim-diels → created an issue.

tim-diels → created an issue.

tim-diels → created an issue.

tim-diels → created an issue.

This is required to get the module working.

tim-diels → created an issue.

As per last 2 comments, this will need some adjustments.

Hey Berdir, thanks for shiming in. I didn't feel like putting this on a status that is different then before without any reason given. So thats why I want back to the previous status as I didn't test it myself. But fair enough for me if you want to put it on RTBC. I did see indeed that the pipelines are failing on more MRs and are indeed not related.

@divyansh.gupta no need to double verify as this has been verified before. And setting something to RTBC when the pipelines fail is not correct. So setting this back to NW.

As there is a patch, this can be set on needs review.

Added the patch as MR and tested it out and it seems to work for what is described. The pipelines are failing, but after looking at them it seems unrelated to this change.

Let's create a MR for this so the pipelines are triggered and we can see if there is work needs to be done.

Please provide patches as MR as that will be easier for review and also triggers the pipelines for quality assurance and testing.

Please provide patches as MR as that will be easier for review and also triggers the pipelines for quality assurance and testing.

I'd like to cast a vote for:
- Joris Vercammen (borisson_)
- Marine Gandy (Mupsi)

I can't close the MR so left issue open for now. Can you close it?

Hi Jurgen, thanks for the great support here. I finally was able to come back to this and you're absolutely correct in your explanation to use the plain: token. Thank you so much for the help!

Hi, could you please make a release?

I'm reopening this as I got the same issue. This is due to the services file and some other files are added as .example files.
Suppose the maintainers expect us to put them in a custom module to use those? But there is no documentation about this, so would like some insight from a maintainer on why the files are added as .example and how to continue.

Hi mohamad, thanks for the quick response. Can you also add it as a (download) release (2.0.x) so we can tag the issues to the version? If you don't know what I'm talking about, just let me know. You can also ping me on slack at tim-diels

Hi mohamad, thanks for the quick response. Can you also add it as a (download) release (2.0.x) so we can tag the issues to the version? If you don't know what I'm talking about, just let me know. You can also ping me on slack at tim-diels

As mentioned in #3522879: Support Elasticsearch Connector 8.x → this will result in a breaking change and should be done in a major release.
Why is this is breaking change? We should rename the current method to msearch to match the elastic documentation and the new method should use the current search method (but changed ofcourse).

In my enthusiasm I also added the default search method. This is actually a breaking search for people extending the controller.
Therefor we should extract the method. I created a new issue for this #3523543: Add search method → .

Also the support for Elasticsearch Connector 8.0.x should be done in a major release. So can you please create a new branch for this so we can set the MR to the new branch?

tim-diels → created an issue.

Added a display widget, could use some improvement maybe as this is what I currently needed.

tim-diels → created an issue.

Added it to a MR for easier follow up. Still need to be tested.

tim-diels → made their first commit to this issue’s fork.

I'm sorry for answering so late, but can you provide a complete example on what you try to achieve so it is testable?

Ok code did not change a lot, can you point out what is still needed?

Hi Wouter, thanks for the report and the patch. Could you see if 🐛 When there's a path that is a subpath of trans_path, the getOutboundPath function messes up paths from other places Active fixes the issue? If not, you can use it as base to create a test that fails and then a fix?

Thanks a lot for this great work! Looks wonderful and tested and works as expected. Did some minor changes. Feel free to question these changes and explain why you would need them. I don't see the value of them at this moment.

Hi @steinmb, thanks for the MR, but its still in draft, so not sure if its finished? The code will change a lot with the other issue. So I'm thinking of getting back to this after the other issue has been tested and merged and see what needs to be done here? What you think?

Hi @steinmb, sorry for not being to active on this module. I've been trying to follow up on most of the modules I maintain, but most of them I did not build but got maintainer to get thing forward. I understand the frustration or irritation when things keep hanging. I'll review this module in the next days and see if I can get everything tested.

I added support for Elasticsearch Connector.

tim-diels → created an issue.

tim-diels → created an issue.

tim-diels → created an issue.

tim-diels → created an issue.

tim-diels → made their first commit to this issue’s fork.

tim-diels → created an issue.

@dhaval_panara please do not use mr diff links in your workflow. This is very dangerous! Please read https://github.com/cweagans/composer-patches/issues/347

tim-diels → changed the visibility of the branch 3366187-gin-theme-compatibility to hidden.

Found an issue when using elasticsearch to index nodes. So will need to add an extra check.

As there is no dev release, I targeted the 8.1.1 version and used the 8.x branch as thats where the latest code is added.

tim-diels → created an issue. See original summary → .

Also with the pipelines running now, there is more work to do.

I rebased both MRs but for the 2.x I rebased on the 2.3.x so that MR needs to be changed to 2.3.x instead of 2.2.x. I4m not able to do this, anyone else have this option?

Hiding the patches files as the current approach is to use MRs. There are 2 MRs that seem to solve the issue and patch from #41 looks the same as MR157.

I've tested MR156 and that provided the tokens I was looking for.

But it seems no pipelines are running? I'll rebase and see if that triggers the pipeline.

This is a big blocker for normal composer workflow. We're using this for a month now and looks like its working as expected and does not create any issues.