Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
5.50.alpha1.mysql.tpl - Escape
grouping
(reserved word in MySQL 8.0…
….1+) Import - also export invalid as export error I found that rows that fail validation are marked 'invalid' rather than error & won't show on the preview screen. I guess I could check for invalid vs error separately - gets kinda weird though - if you leave them in the file you are importing surely they are still errors to see on the summary screen even though you knew they were invalid on the Preview? (E2E) testErrorChrome - Skip Backdrop and D8+ (much like D7) This test was added during 5.50.alpha (civicrm#23257, civicrm#22805). It's purpose is to assert that the page-chrome/site-wide-template is present on certain error-messages; however, the underlying behavior was only implemented on WordPress. It has not yet been implemented on other CMS. Before ------ * __WordPress__: Runs testErrorChrome. Expected to pass. * __Drupal 7__: Skip testErrorChrome (mostly) because it is expected to fail. * __Drupal 8+, Backdrop__: Runs testErrorChrome. Fails. After ----- * __WordPress__: Runs testErrorChrome. Expected to pass. * ___Drupal 7, Drupal 8+, Backdrop__: Skip testErrorChrome (mostly) because it is expected to fail. Comment ------- It still runs `testErrorChrome` for `permission` errors; per MM discussion, it appears that this does actually work, but we need to tune assertion for BD+D8. (E2E) `testErrorChrome` - Update to work with current wp-demo build This test was added during 5.50.alpha (civicrm#23257, civicrm#22805). It's purpose is to assert that the page-chrome/site-wide-template is present. It appears that the markup from WordPress has changed slightly. (It may be that I originally tested against an older version of WP.) In any event, this relaxes the test so that it also passes on a newer WP build. (E2E) testErrorChrome - Revise page-chrome check for all Drupal-style UFs
- Loading branch information