Project Description
This Bootstrap SASS theme is intended to be used as a SASS starting point/starterkit for building Bootstrap themes. It is based on the Drupal Bootstrap Project. The only way to customize this starterkit is by coding so it is intended for advanced themers only.
This project adds a different direction and extends on the current Drupal Bootstrap project. It was built because the maintainers of the Bootstrap project have indicated that there are no plans to provide utilities for custom building of themes with their theme.
This startertheme/kit was built with support for NodeJS, Sass, Grunt or Gulp, Compass and Browsersync. This provides themers building from custom designs flexibility and a good starting point to build a professional theme.
Theme Screenshot
Installation & Git
Please see the full install/usage documentation at https://www.drupal.org/sandbox/wrender/2627564
Git Clone :
git clone --branch 7.x-3.x https://git.drupal.org/sandbox/wrender/2627564.git bootstrap_sass_starterkit
cd bootstrap_sass_starterkit
Comment | File | Size | Author |
---|---|---|---|
#17 | npm-debug.txt | 38.99 KB | bigmonmulgrew |
Comments
Comment #2
wrender CreditAttribution: wrender as a volunteer commentedComment #3
chanderbhushan CreditAttribution: chanderbhushan commentedhi @wrender
Thanks for your contribution.
thanks
Comment #4
PA robot CreditAttribution: PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpgitdrupalorgsandboxwrender2627564git
We are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)
Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #5
atul4drupal CreditAttribution: atul4drupal commentedComment #6
wrender CreditAttribution: wrender as a volunteer commentedComment #7
wrender CreditAttribution: wrender as a volunteer commentedComment #8
wrender CreditAttribution: wrender as a volunteer commentedI've fixed all of the code/formatting issues in the 7.x-3.x , and 8.x-3x branches. Please PA Robot....come baaaack.
Comment #9
wrender CreditAttribution: wrender as a volunteer commentedComment #10
wrender CreditAttribution: wrender as a volunteer commentedComment #11
wrender CreditAttribution: wrender as a volunteer commentedComment #12
wrender CreditAttribution: wrender as a volunteer commentedComment #13
wrender CreditAttribution: wrender as a volunteer commentedComment #14
wrender CreditAttribution: wrender as a volunteer commentedComment #15
bigmonmulgrew CreditAttribution: bigmonmulgrew commentedSpamming is not the way to get your project promoted. If anything it show you probably shouldnt have the ability to promote.
You can check out the automated review here
http://pareview.sh/pareview/httpgitdrupalorgsandboxwrender2627564git
Click on repeat review and if the box is blank use - http://git.drupal.org/sandbox/wrender/2627564.git
You have a lot of errors there so sort them before changing to needs review and if you make any changes run that review again.
I think your readme file needs some work. It needs breaking up a bit and maybe add numbers. Also it seems to be written as a reminder sheet for someone who knows what they are doing and not actual instructions. For example what is grunt init and where do I run it from? imagine I'm trying to make my first Drupal theme having first been introduced to Drupal a week ago.
Comment #16
klausiMinor coding standard errors and readme improvements are surely not application blockers, anything else that you found or should this be RTBC instead?
Comment #17
bigmonmulgrew CreditAttribution: bigmonmulgrew commentedNo they are non-blocking but got cut short and hadn't finished testing,
A few more notes
i have a lot of themes installed I was looking under B for Bootstrap SASS Found it under "StarterKit Bootstrap with SASS"
Need some more consistent naming conventions.
Also the installation instructions on the sandbox project page do not match the readme file
Most critically though I can't get it working using your instructions.
I got several errors when running npm install. Forgot to check if grunt was installed etc. so had to go back and start again but still got a load of errors? Should I be root? I tried to grab the log file but its not where it says it should be. Tried installing as root. Still tons of errors. I saved the command line output though, attached.
Comment #18
bigmonmulgrew CreditAttribution: bigmonmulgrew commentedOk something rather odd I just noticed. This is after I removed bootstrap_sass. My test site is now a fresh install with the youtube_import module on it. I was checking the logs and noticed a page not found error for
http://mysite.co.uk/sites/all/themes/bootstrap_sass_starterkit/node_modu...
Referres is mysite.co.uk./user/password
If I open this while logged into my site it does open a link. I'm now wondering what did this do to my webserver that it's serving files that are not there.
And also why am I getting external requests for those files?
Comment #19
wrender CreditAttribution: wrender as a volunteer commented@bigmonmulgrew thanks for the input. Yes. The readme needs to be updated to match the instructions on the project page. I will update it this week.
It appears you are running an outdated/unsupported NodeJS install. I would suggest running "(Version v4.2.x or newer recommended with NPM 3.x)" as it states in the project page instructions. This may fix the errors you are getting during install. NodeJS, Grunt or Gulp need to be installed globally first. So yes, this means you would most likely need to use root in your hosting environment.
As far as I know there would be no way for this theme to alter your web server. It sounds like you must have some other sort of configuration issue that is not related to the theme. How did you remove the bootstrap_sass theme folder? Did you assign another default theme, and then delete that folder, and then also clear your Drupal cache? Those steps would need to be done to prevent errors.
Comment #20
wrender CreditAttribution: wrender as a volunteer commentedI've updated the README, and theme title for the both 7.x and 8.x version to match the instructions on the project page. Thanks.
Comment #21
bigmonmulgrew CreditAttribution: bigmonmulgrew commentedI deleted the site database and the website files and did a fresh install of drupal. I figred out why the files were still there. It was a quirk of the browser cache. For some reason it was actually serving the files from the browser cache when I was logged into the site as admin but not when logged out. Clearing the browser cache solved that but I still find it odd that I was getting external requests for those files. Can you think of any reason for that?
Ah I never thought of the version. I didnt have nodejs or npm installed on my server so i googled it and ran the installer. Figured since 4.4 was up on the website as stable i assumed id get that version
I'll update and try again
Comment #22
wrender CreditAttribution: wrender as a volunteer commentedWere you using the browser sync enabled command? The only thing I can think of is that maybe it, Drupal, or your web browser was somehow caching the theme/node modules. But in the end I don't think it's a problem with this starterkit/theme.
If you are developing a theme, I would suggest always clearing your caches on these things each time you make any change to the theme or template files.
Hope this helps.
Comment #23
bigmonmulgrew CreditAttribution: bigmonmulgrew commentedNo I don't think so either. It just really threw me that it had the files cached for admin but not for anon. I was setup on a vanilla Drupal 7.43 With minimal install. AS soon as i get chance to reset my test site I'll test again
Comment #24
bigmonmulgrew CreditAttribution: bigmonmulgrew commentedJust tried again and got
Then getting connection reset and cant access the site unless i remove the theme
Comment #25
wrender CreditAttribution: wrender as a volunteer commentedThat is strange. I can't reproduce the error on any of my servers. Do you have the Bootstrap base theme installed from here? https://www.drupal.org/project/bootstraphttps://www.drupal.org/project/bootstrap
Comment #26
bigmonmulgrew CreditAttribution: bigmonmulgrew commentedYes I have bottstrap installed.
I'm also getting the following error in my apache error log.
[Tue Mar 29 13:27:49.106325 2016] [core:notice] [pid 1401] AH00051: child pid 6444 exit signal Segmentation fault (11), possible coredump in /etc/apache2
Comment #27
wrender CreditAttribution: wrender as a volunteer commented@bigmonmulgrew. I just tried again, and I can't reproduce this issue on my development servers. I've tested this theme on Ubuntu 14.04, Fedora 23, Centos 7, and CloudLinux 7 without issues.
Does the just the Bootstrap theme load by itself if you set it to the default theme? Are you able to try deleting the node_modules folder under the bootstrap_sass folder, and see if the issue persists?
Are you able to provide more information on your development environment/server? For Example, OS, Apache & PHP Version etc...
Comment #28
wrender CreditAttribution: wrender as a volunteer commented@bigmonmulgrew I found a bug where the presence of the /bootstrap_sass/node_modules folder seems to cause Drupal 7.43 to crash. I think this may be the bug you were pointing out. I've created an issue for it here: https://www.drupal.org/node/2705899
Basically if you delete the node_modules directory it resolves the issue, but the node_modules directory is needed when compiling the sass and bootstrap code as it contains this code.
Comment #29
Binu Varghese CreditAttribution: Binu Varghese commented@wrender, found these below issues.
1. It seems that template.php file is not being used as it appears empty. Is it serving some purpose?
2. Both gruntfile.j & gulpfile.js do not follow File-closure mode in JavaScript coding standards - https://www.drupal.org/node/172169:
Please fix these.
Comment #30
wrender CreditAttribution: wrender as a volunteer commented@Binu Varghese.
1. I don't see any requirements for the template.php file to contain data in a theme starterkit. This is a starterkit so the purpose of an empty file is to provide a starting point for someone to insert pre-processor code in. This assists a theme developer by indicating that this file can be used for inserting code.
2. Grunt and Gulp are in no way are related to Drupal itself. Drupal does not process these files in anyway. They are third party compilers and therefor use their own best practices for javascript. No closure statement is required as per Gulp or Grunt documentation. Please see: http://gruntjs.com/sample-gruntfile & https://github.com/gulpjs/gulp/blob/master/docs/getting-started.md for learning how to use Grunt or Gulp.
Comment #31
wrender CreditAttribution: wrender as a volunteer commentedComment #32
Binu Varghese CreditAttribution: Binu Varghese commented(1) In that case, it makes sense to drop a comment in the file for it being empty.
(2) Not sure about that.. would like some one to look into (2) argument.. leaving status in Needs review though..
Comment #33
wrender CreditAttribution: wrender as a volunteer commentedClosing this as a SASS starterkit has been added to the Drupal Bootstrap project.