Fresh install of Drupal 8.2.4, first thing I attempted to do was install mBase theme. I did, and got the "The website encountered an unexpected error. Please try again later." error. I clicked "back", and checked my log, which shows:

Drupal\Core\Extension\InfoParserException: Unable to parse temporary://update-extraction-501052eb/mbase/mbase.info.yml yaml_parse(): scanning error encountered during parsing: found character that cannot start any token (line 39, column 3), context while scanning for the next token (line 39, column 3) in Drupal\Core\Extension\InfoParserDynamic->parse() (line 25 of /home/{PATH}/core/lib/Drupal/Core/Extension/InfoParserDynamic.php).

I completely uninstalled Drupal, and reinstalled, as I say, making mBase the first thing I attempted to do, after logging in, and the issue still persists.

CommentFileSizeAuthor
#12 infoparserexception-2841095-12.patch310 bytescilefen
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

BEGRAFX created an issue. See original summary.

cilefen’s picture

cilefen CreditAttribution: cilefen as a volunteer commented
Title: Installation Issue » InfoParserException: Unable to parse temporary://update-extraction-f2890d03/mbase/mbase.info.yml
Priority: Normal » Critical

Line 39 of the info.yml file starts with an '@' symbol:

libraries-override:
  @system/css: false
  system/admin: false
BEGRAFX’s picture

BEGRAFX CreditAttribution: BEGRAFX commented

Where did this @ symbol come from? As I said, fresh Drupal install, mBase fresh from Drupal.Org. How did this happen?

cilefen’s picture

cilefen CreditAttribution: cilefen as a volunteer commented

I am sure I do not know what you mean. This symbol is in the code of the mbase project, added in this commit: http://cgit.drupalcode.org/mbase/commit/mbase.info.yml?id=9c47bc83303482...

It is there it must be fixed.

BEGRAFX’s picture

BEGRAFX CreditAttribution: BEGRAFX commented

I understand, and agree; but I'm confused, as I had set up another site using the same core Drupal and the same release of mBase, and it worked fine. Clearly, something changed somewhere, but I'm trying to figure out what. I'm trying to figure out how the "@" symbol suddenly appears. I looked, and there is only one release of mBase listed on Drupal.org, unless, for some reason, the author pushed a revision of the same version, which had the @ ?

cilefen’s picture

cilefen CreditAttribution: cilefen as a volunteer commented

The unquoted '@' has been in this project from its beginning on Drupal 8 it seems. It is invalid YAML. Have you got Drupal 8.2.4 from a zip download or did you build with composer?

BEGRAFX’s picture

BEGRAFX CreditAttribution: BEGRAFX commented

All I know is, I installed mBase on an 8.2.4 site about 2 weeks ago, without issue, and then about a week ago now, I attempted to use it on another site, and got the error. I believe both instances of 8.2.4 were installed via Drush.

cilefen’s picture

cilefen CreditAttribution: cilefen as a volunteer commented

Are the composer.lock files different between the sites? In an uncanny coincidence, we just posted a utiltity app to compare composer.lock files, yesterday.

khaji00’s picture

khaji00 CreditAttribution: khaji00 commented

I'm also experiencing this issue. I'm on Drupal 8.2.5 and tried to install 8.x-1.0

cilefen’s picture

cilefen CreditAttribution: cilefen as a volunteer commented

Re #7: Oh, drush. Are they on the same platform?

BEGRAFX’s picture

BEGRAFX CreditAttribution: BEGRAFX commented

Re: #10; Don't they have to be, in order for it to work at all? Or am I misunderstanding your question?

cilefen’s picture

cilefen CreditAttribution: cilefen as a volunteer commented
Status: Active » Needs review
FileSize
infoparserexception-2841095-12.patch310 bytes

@BEGRAFX I am trying to answer #5 by determining if the Drupal core code or platform details are different. Otherwise there would be only magical explanations.

But let me be clear: This theme contains invalid YAML.

BEGRAFX’s picture

BEGRAFX CreditAttribution: BEGRAFX commented

@cilefen: Both Drush Installations were to the same host/platform, yes. Not knowing all of the intricacies of Drupal.org and how it handles revisions and such; is it possible that I downloaded a working version of mBase on (for example sake) 1/1, and then, on 1/5 someone, while perusing the code, unintentionally added the "@" and then saved it as the same version? So that when I attempted to build the next site on 1/7, and went to install mBase, the bad code was there, and caused the problem? Would Drupal.org allow identical code, with the exception of one character, to be saved with an identical version number?

cilefen’s picture

cilefen CreditAttribution: cilefen as a volunteer commented

No, no and no.

cilefen’s picture

cilefen CreditAttribution: cilefen as a volunteer commented

Anyway, I hope the patch I posted in #12 helps.

BEGRAFX’s picture

BEGRAFX CreditAttribution: BEGRAFX commented

*I* have saved a .ZIP of mBase with the offending @ removed, so it works fine when I need the base theme. However, clearly a corrected version needs to be posted for others.

vrwired’s picture

vrwired CreditAttribution: vrwired commented

FWIW, I had this *exact same* experience and used the patch to clear it up. IMO this theme is an excellent bootsrap and glad to have it working for another site based on a patch to solve whatever necessitated it.

  • 75057f1 committed on 8.x-1.x 
    Issues Fixed : #2602446, #2702039, #2679549, #2830744, #2829164, #...