Include Link Sanitize tests from D7 contrib module

This is a follow-up to https://www.drupal.org/sa-contrib-2022-034, where we identified that the same vulnerability does not exist in Backdrop core. We would like to include the same sanitization tests, so that we can continue to test sanitization against any future changes to link handling.

GitHub Link:

https://github.com/backdrop/backdrop-issues/issues/5613

GitHub Issue #:

5613

Recent topics

Importing the staged config throws an error: another field with the same name already exists

Posted 2 days 13 hours ago by Francis Greaves (themetman) in How-To and Troubleshooting

Comments Enhanced

Posted 1 week 4 days ago by (izmeez) in How-To and Troubleshooting

Why not add a Github star?

Posted 1 week 5 days ago by (izmeez) in How-To and Troubleshooting

Recent comments

@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...

Posted 2 days 6 hours ago by Francis Greaves (themetman) on:

Importing the staged config throws an error: another field with the same name already exists

Thanks, I have to go out now, I will try later on and report back

Posted 2 days 12 hours ago by Francis Greaves (themetman) on:

Importing the staged config throws an error: another field with the same name already exists

Hi Francis. Yes, what config do you have in staging for it? You might have configs like: field.field.field_video_embed field.instance.node.page....

Posted 2 days 12 hours ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:

Importing the staged config throws an error: another field with the same name already exists