jeremy1606 → made their first commit to this issue’s fork.
jeremy1606 → made their first commit to this issue’s fork.
jeremy1606 → made their first commit to this issue’s fork.
jeremy1606 → made their first commit to this issue’s fork.
jeremy1606 → made their first commit to this issue’s fork.
jeremy1606 → made their first commit to this issue’s fork.
jeremy1606 → made their first commit to this issue’s fork.
jeremy1606 → made their first commit to this issue’s fork.
jeremy1606 → made their first commit to this issue’s fork.
jeremy1606 → made their first commit to this issue’s fork.
jeremy1606 → made their first commit to this issue’s fork.
jeremy1606 → made their first commit to this issue’s fork.
jeremy1606 → made their first commit to this issue’s fork.
jeremy1606 → made their first commit to this issue’s fork.
jeremy1606 → made their first commit to this issue’s fork.
jeremy1606 → made their first commit to this issue’s fork.
The problem you are facing is because resource is a reserved word in PHP since version 7.0. In this case, the warning indicates that the word resource is being used within the namespace in several classes within the Drupal migrate_example_advanced module.
The most recommended is to rename the namespace within the affected files. Currently, the namespace is defined as:
Drupal namespace Drupal\migrate_example_advanced\Plugin\resource;
You can change it to something more secure, like resources or rest_resource, for example:
Drupal namespace Drupal\migrate_example_example_advanced\Plugin\rest\rest_resource;
Then, in each file where this namespace is used, make sure to update the corresponding references.
jeremy1606 → made their first commit to this issue’s fork.
Pin an existing version of core-composer-scaffold, this is because the previous update does not work, you can manually pin the latest version of drupal/core-composer-scaffold compatible with 10.3.x
1) composer require drupal/core-composer-scaffold:^10.0 --no-update
2) composer update -W drupal/core-recommended drupal/core-dev drupal/core-composer-scaffold
This patch is giving me a mistake: patch -p1 < filefield_sources_d10compat_3336268.patch
jeremy1606 → made their first commit to this issue’s fork.
jeremy1606 → made their first commit to this issue’s fork.
I will try to test to see if they will pass.
Of course. I've already done it. Can you check it please and tell me if it's ok now?
By accident two empty commits were sent. But I managed to update the two modules with composer and they are already in versions 4.0.0 and 2.0.0 respectively.
jeremy1606 → made their first commit to this issue’s fork.
Is there still anything that needs to be done?
There are a few changes in MR 37 that still need to land. Besides that, what more needs to be done before official D11 support for v3 is available and new 3.x release tagged?
jeremy1606 → changed the visibility of the branch 3296968-automated-drupal-10 to hidden.
jeremy1606 → created an issue.
jeremy1606 → made their first commit to this issue’s fork.
jeremy1606 → made their first commit to this issue’s fork.
jeremy1606 → made their first commit to this issue’s fork.
duplicate to 3451023
jeremy1606 → created an issue.