verify that l10n option is valid before using#8223
Closed
icewind1991 wants to merge 1 commit intomasterfrom
Closed
verify that l10n option is valid before using#8223icewind1991 wants to merge 1 commit intomasterfrom
icewind1991 wants to merge 1 commit intomasterfrom
Conversation
Signed-off-by: Robin Appelman <robin@icewind.nl>
rullzer
approved these changes
Feb 7, 2018
Member
|
I had this as well for the zimbra app: https://github.com/ZeXtras/zimbra-drive The sentry log looks like the |
Member
|
This is a working entry in the info.xml: <description>Authenticate Users by SQL</description>This is a broken one: <description lang="en">
<![CDATA[Add Nextcloud / ownCloud as Briefcase in Zimbra with the full features of both applications.]]></description>So maybe something is wrong in the parser itself. |
Member
Author
|
Superseeded by #9159 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Make sure that the option is what we expect.
Probably caused by a not 100% valid info.xml, not sure which one though, found the issue in the logs of a customer.