Hello.

In the file _default-variables.scss, the following code refers to the path

./THEMENAME/bootstrap/assets/stylesheets/_variables.scss

But that path does not exist. It should be

./THEMENAME/bootstrap/assets/stylesheets/bootstrap/_variables.scss

/**
 * Default Variables.
 *
 * Modify this file to provide default Bootstrap Framework variables. The
 * Bootstrap Framework will not override any variables defined here because it
 * uses the `!default` flag which will only set their default if not already
 * defined here.
 *
 * You can copy existing variables directly from the following file:
 * ./THEMENAME/bootstrap/assets/stylesheets/_variables.scss
 */

// Set the proper directory for the Bootstrap Glyphicon font.
$icon-font-path: '../bootstrap/assets/fonts/bootstrap/';
CommentFileSizeAuthor
#4 bootstrap-wrong_filepath-2849618-4.patch414 bytesrenat
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

asiby created an issue. See original summary.

asiby’s picture

Title: Misinformation is the documentation in _default-variables.scss » Wrong information in the documentation in _default-variables.scss
Issue summary: View changes
asiby’s picture

Issue summary: View changes
renat’s picture

Version: 7.x-3.10 » 8.x-3.x-dev
Status: Active » Needs review
FileSize
414 bytes

Confirm, asiby is absolutely correct. Here is the patch, so we'll be able to see it fixed sooner.

renat’s picture

Version: 8.x-3.x-dev » 7.x-3.x-dev
Aanal.addweb’s picture

Status: Needs review » Reviewed & tested by the community

@renat, Thank you for the patch, it works well.

  • markcarver committed 3cc01ec on 8.x-3.x authored by renat
    Issue #2849618 by renat, asiby: Wrong information in the documentation...

  • markcarver committed ad2e1ed on 7.x-3.x authored by renat
    Issue #2849618 by renat, asiby: Wrong information in the documentation...
markhalliwell’s picture

Status: Reviewed & tested by the community » Fixed

Ran into #2854361: Source files in SASS starterkit are underneath "sass" folder instead of "scss" when attempting to apply patch to 8.x-3.x, but fixed on both. Thanks!

Aanal.addweb’s picture

@markcarver I guess, you forgot providing me a credit for RTBC I performed. Can you please do the needful..?

markhalliwell’s picture

asiby’s picture

I do not understand that credit attribution thingy. It has Author and By. What is what in this case? Because I reported this issue, but I see that it says that author is @renat. I personally don't mind as long as things are being solved. It's just that I have my module modules to maintain and I would like to be doing the correct thing there too. :)

markhalliwell’s picture

So, yes, the whole "credit" topic is rather confusing at first. It partially due to the evolution of what we have considered as "credit" over the years.

There are actually 3 distinct areas/concepts/history of "credit" in our community, I'll try to help summarize with short descriptions/links:

First came: CSV/Git Commit Messages

  • This is the Issue #[issue number] by [comma-separated usernames]: [Short summary of the change] commit messages. It's how we track who reported the issue and all the individuals who helped on the issue.

Second came: Git --author flag

  • This is the individual who actually created said patch that was committed. This is what is displayed in the above system messages #7 and #8: "authored by"

Third came: Drupal.org's Issue/Commit Credit UI

  • This UI was heavily inspired by the original Dreditor browser extension commit credit plugin. It is now, however, a full d.o feature that stores each issue's "commit credit" values directly in d.o database. This allows for things like the "Credited on X issues fixed in the past 1 year" section on user's profiles.

    It does not, however, have any real direct ties to project repository commit messages anymore and is the only real way to retroactively credit someone. My blank comment in #11 was actually me giving @dhwani.addweb "credit" (see her profile now) for this issue. Of course, since this was a retroactive credit as she isn't actually mentioned in the repository's commit history (sorry!).

asiby’s picture

Wow. Thank you so much for these clarifications @markcarver. It confirms that not matter how much we know, what we still don't know can fill the ever expanding universe. hahahaha.

Plus, I have never noticed the "Credited on X issues fixed in the past 1 year" in the past. Maybe because I was even though I have reported bugs and tried contributing in various ways to solve some of them.

I will keep that in mind to ensure that everyone will be properly credited for what they do in the future. ;)

Thanks again.

markhalliwell’s picture

Np :D

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.