🇮🇸Iceland @drupalviking

jjchinquist → credited drupalviking → .

drupalviking → created an issue.

jjchinquist → credited drupalviking → .

jjchinquist → credited drupalviking → .

jjchinquist → credited drupalviking → .

drupalviking → created an issue.

drupalviking → created an issue.

This is a very much needed implementation! I'm ready to help / implement, but there are some hurdles that I've been facing trying to understand the complete flow of the payments.

I opened this issue again since I just encountered this problem today, so clairly I was able to reproduce.

+2 on this, I had a problem updating to 10. The best I can go now is 10.0.0 :-(

I get similar errors:

Problem 1
    - Root composer.json requires drupal/core-recommended ^10.1, found drupal/core-recommended[10.1.0-alpha1, ..., 10.2.x-dev] but the package is fixed to 10.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
  Problem 2
    - drupal/twig_tweak is locked to version 3.2.1 and an update of this package was not requested.
    - drupal/twig_tweak 3.2.1 requires twig/twig ^2.12 || ^3.3.8 -> found twig/twig[v2.12.0, ..., 2.x-dev, v3.3.8, ..., 3.x-dev] but these were not loaded, likely because it conflicts with another require.
  Problem 3
    - drupal/core 10.0.0 requires twig/twig ^3.4.3 -> found twig/twig[v3.4.3, ..., 3.x-dev] but these were not loaded, likely because it conflicts with another require.
    - drupal/stage_file_proxy 2.1.3 requires drupal/core ^9 || ^10 -> satisfiable by drupal/core[10.0.0].
    - drupal/stage_file_proxy is locked to version 2.1.3 and an update of this package was not requested.

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
Composer [update twig/twig:3.6 --dry-run] failed, composer command failed: exit status 2. stderr=

I can concurr that the module breaks in D10 and this patch fixes the problem.

So, my time zone does not exist in this list :-( I know we are UTC, but it would be nice to have it also as it's own timezone : Europe/Reykjavik

dan2k3k4 → credited drupalviking → .

John Cook → credited drupalviking → .

The Group module seems to add another Revision local task in group.link.tasks.yml, creating a duplicate task in the Primary Tabs.

So this seems to be a bug outside of l10n. I found that one of the incidents is being added via the Group module, still haven't found what's responsible for the other, most likely it's part of a core function. Anyway, I'm closing this issue, it's not part of l10n_server.

I'm taking a look

I did add the route to the yml file and it routes as intended.

Created an issue fork

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