Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Found this during an incompatibility scan to PHP 5.6
Comment | File | Size | Author |
---|---|---|---|
#9 | 2826297.patch | 805 bytes | Thomas Cys |
Comments
Comment #2
Thomas CysComment #3
plachThanks!
Comment #5
Thomas CysAm i doing something wrong here because my patch is failing?
Comment #8
dwebpoint CreditAttribution: dwebpoint as a volunteer commented@Thomas Cys
In order to pass test could you replace $entity = clone entity
from your patch with
$entity = clone $entity.
Comment #9
Thomas Cys@dwebpoint
I can't believe i missed that, thanks for pointing that out!
Comment #10
Thomas CysComment #12
stefanos.petrakis@gmail.comCan't believe I missed that too. Excellent catch @dwebpoint!
It is however not relevant to the failing of the tests. just ran the tests (using ET-Beta5 and i18n-1.14).
and got the 4 fails you also got from the bot (https://www.drupal.org/pift-ci-job/529800):
createTranslation, testMenuLocalization, editPage, testMenuLocalizationCustomSourceLanguage
without applying your patch.
Running the tests using i18n-1.13 did not cause the fails, with and without applying your patch.
It seems to me that the latest stable i18n is causing the EntityTranslationMenuTranslationTestCase tests to fail.
Note that this is a relatively recent update (22.10.2016) and the EntityTranslationMenuTranslationTestCase may need to be updated. And the entity_translation_i18n_menu module's code even more. But these are separate issues.
Since this patch does not seem to be causing the errors and it's actually quite easy to judge on correctness, I will RTBC this.
Comment #14
plachCommitted and pushed, thanks!