Closed (duplicate)
Project:
Drupal core
Version:
8.0.x-dev
Component:
migration system
Priority:
Major
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
28 Aug 2015 at 18:44 UTC
Updated:
27 Sep 2015 at 16:02 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
justachris commentedComment #3
joelpittetComment #4
mile23This patch changes both migrate and migrate_drupal modules.
There are quite a few !placeholders in
Drupal\migrate_drupal\Tests\namespace, but those files seem to be generated to support migration testing and don't need to be checked for safety by Drupal 8.Looked for other !placeholders in strings using NetBeans and my eyes. (!? as a wildcard expression)
Couldn't find any.
Comment #5
mile23Comment #6
catchShouldn't we also do the tests here? Those strings don't need to be checked for safeness, but the idea is to remove usages of
!placeholderentirely eventually.Comment #7
mile23I'm not sure how the migrate tests work. I assume they're using strings generated from D6 and D7, and they might just be testing whether a conversion away from !placeholders happens or not during migration.
Comment #8
justachris commentedMy mistake on #4, migrate_drupal should have been included in the scope of this issue initially. Updated IS to clarify. This includes the tests found in those directories.
On comments #6,7 we should be careful about how !placeholder is used. In some areas of the migrate module (and other modules) they indicate using a token, which I think is out of the scope of these updates. This was also noticed in #2559459-7: Replace !placeholder with @placeholder in User module.
Additionally, can we get manual testing here to make sure that the changes don't affect escaping on the output?
Comment #9
joelpittetMay be able to test some of this easier with https://www.drupal.org/project/migrate_upgrade
@mikeryan1 pointed this out to me on IRC #drupal-migrate
Comment #10
justachris commentedPostponed on determining plan in parent #2506427: [meta] !placeholder causes strings to be escaped and makes the sanitization API harder to understand and then analyzing whether this issue still makes sense.
Comment #11
justachris commentedClosing this, splitting by module was not the ideal approach to removing !placeholder. Marking as duplicate of #2506427: [meta] !placeholder causes strings to be escaped and makes the sanitization API harder to understand, since the chosen approach is / will be outlined there, please refer to it for any additional action.
Comment #12
sutharsan commentedPatch now merged into #2506445-140: Replace !placeholder with @placeholder in t() and format_string() for non-URLs in tests.
Comment #13
xjm