jeroen dost → created an issue.
Here is a patch for the suggested feature.
jeroen dost → created an issue.
I cannot reproduce the error anymore. Maybe a setting was wrong before. If I come across it again, I will update this issue.
Hi @sarwan_verma,
This does not seem to fix the problem. I still get the error. `$row['status']['data']` is of type TranslatableMarkup and should be handled like that. I don't know if it always is an object of that type, so we could check for it, but I could not get it to work. Problem starts probably because the status is not one of the statuses inSubscriptionManager getStatusLabel().
I can probably try to patch this next week.
I completely rewritten the patch. The correct languages for the domains were not used. Instead all translations were loaded. Now I reset the language property to match the languages for the domain (and reset it at the end of the generate method).
Hi Alex,
I have a rewrite for version 3.0.0-beta1.
It did not work correctly when I removed the mentioned patch. That other patch results in drush not working anymore.
Hi Alex,
I came across this patch when applying this patch
https://www.drupal.org/project/domain_simple_sitemap/issues/3380309
✨
Support Domain Language Access
Needs review
and added it to my composer file. But after this patch was applied, my drush stopped functioning. I think there still is a need for a check, but maybe a different check.
I now used only the other patch, but that did not fix my problem. Sitemaps still contain all languages.
Do you have any idea how to solve this?
Thanks,
Jeroen
P.S. I needed to rewrite the other patch, because the location of the setActiveDomain changed. I will post it there.
Jeroen Dost → created an issue.
Is there a time line for the beta and stable release? It would really help. What is needed to complete the steps?
And maybe a stable release for the basic functionality that is stable? I like this module, but can not always use it, because of the alpha state.
As @Chalk mentioned: Is it possible to merge and release a Drupal 10 version?
@mrcdrx Thanks for pointing to the other issue!
Applying the patch from #4 fixes the problem for me.
LS,
I guess, the answer will be "won't fix", because it has to be light weighted compared to Paragraphs. So we probably need to work around that. Has anyone tried to solve this problem? Copying the field from the source language when the source changes? Or a button adding this feature? Or other options?
Thanks in advance!
Jeroen Dost → created an issue.