Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show which extension has a parse error in info.xml #27028

Conversation

larssandergreen
Copy link
Contributor

Overview

This came up on chat recently.

Before

Error message and log says there is a parse error in an info.xml file, but we don't know which extension.

After

We get the path to the offending file in the error.

Comments

These errors could also come from CRM/Extensions/Mapper.php, but I think that is basically deprecated, so haven't bothered. Can add the same to that if there is some reason to do so.

@civibot
Copy link

civibot bot commented Aug 9, 2023

Thank you for contributing to CiviCRM! ❤️ We will need to test and review the PR. 👷

Introduction for new contributors
  • If this is your first PR, an admin will greenlight automated testing with the command ok to test or add to whitelist.
  • A series of tests will automatically run. You can see the results at the bottom of this page (if there are any problems, it will include a link to see what went wrong).
  • A demo site will be built where anyone can try out a version of CiviCRM that includes your changes.
  • If this process needs to be repeated, an admin will issue the command test this please to rerun tests and build a new demo site.
  • Before this PR can be merged, it needs to be reviewed. Please keep in mind that reviewers are volunteers, and their response time can vary from a few hours to a few weeks depending on their availability and their knowledge of this particular part of CiviCRM.
  • A great way to speed up this process is to "trade reviews" with someone - find an open PR that you feel able to review, and leave a comment like "I'm reviewing this now, could you please review mine?" (include a link to yours). You don't have to wait for a response to get started (and you don't have to stop at one!) the more you review, the faster this process goes for everyone 😄
  • To ensure that you are credited properly in the final release notes, please add yourself to contributor-key.yml
  • For more information about contributing, see CONTRIBUTING.md.
Quick links for reviewers

@civibot civibot bot added the master label Aug 9, 2023
@larssandergreen larssandergreen force-pushed the Show-which-extension-has-a-parse-error-in-info.xml branch from e816a07 to bb10fe1 Compare August 9, 2023 18:05
@eileenmcnaughton
Copy link
Contributor

@larssandergreen this seems sensible - is the path relative or the full file path? I'm not sure if the latter would raise security hackles (@seamuslee001 ?)

@larssandergreen larssandergreen force-pushed the Show-which-extension-has-a-parse-error-in-info.xml branch from bb10fe1 to def4803 Compare August 11, 2023 03:11
@larssandergreen
Copy link
Contributor Author

Thanks @eileenmcnaughton, it was a full path, but it is now just the directory name.

Also noticed in testing that Mapper is in fact in use, so I've covered this in there as well.

@colemanw colemanw merged commit f9c1e76 into civicrm:master Aug 11, 2023
@colemanw
Copy link
Member

Awesome, thanks @larssandergreen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants