I followed the revised instructions for installing a subtheme for Radix 2.0 at

https://drupal.org/node/1896382

When I ran compass clean && compass watch in the terminal I got

Change detected at XX:XX:XX to: ie7.scss
create assets/stylesheets/ie7.css
create assets/stylesheets/ie8.css
create assets/stylesheets/print.css
error assets/sass/screen.scss (Line 17 of _compass_radix.scss: File to import not found or unreadable: bootstrap.
Load paths:
G:/UniServer/vhosts/mysite/sites/all/themes/mysubtheme/assets/sass
C:/Ruby193/lib/ruby/gems/1.9.1/gems/compass-0.12.3/frameworks/blueprint/stylesheets
C:/Ruby193/lib/ruby/gems/1.9.1/gems/compass0.12.3/frameworks/compass/stylesheets
C:/Ruby193/lib/ruby/gems/1.9.1/gems/compass_twitter_bootstrap-2.3.1/stylesheets
C:/Ruby193/lib/ruby/gems/1.9.1/gems/compass_radix-3.0.2/stylesheets
Compass::SpriteImporter)
create assets/stylesheets/screen.css
>>> Compass is polling for changes. Press Ctrl-C to Stop.

On selecting my subtheme on my Drupal site I got

Syntax error: File to import not found or unreadable: bootstrap.
Load paths:
G:/UniServer/vhosts/mysite/sites/all/themes/mysubtheme/assets/sass
C:/Ruby193/lib/ruby/gems/1.9.1/gems/compass-0.12.3/frameworks/blueprint/stylesheets
C:/Ruby193/lib/ruby/gems/1.9.1/gems/compass0.12.3/frameworks/compass/stylesheets
C:/Ruby193/lib/ruby/gems/1.9.1/gems/compass_twitter_bootstrap-2.3.1/stylesheets
C:/Ruby193/lib/ruby/gems/1.9.1/gems/compass_radix-3.0.2/stylesheets
Compass::SpriteImporter
on line 17 of C:/Ruby193/lib/ruby/gems/compass_radix-3.0.2/stylesheets/_compass_radix.scss
from line 19 of G:/UniServer/vhosts/mysite/sites/all/themes/mysubtheme/assets/sass/screen.scss

in the header on each page. The rest of the demo site looked ok, though.

Then I went back and redid everything with Radix 3.0-alpha3. Running compass clean && compass watch in the terminal produced no errors, and neither did enabling my subtheme, but the panels in the demo were off, with text not wrapping around the images and spilling over into other panels. The bottom line is 2.0 seems like it would work better, save for the errors. Any ideas or advice?

CommentFileSizeAuthor
#2 3.0-alpha3 demo.jpg266.77 KBGrabby
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

shadcn’s picture

Can you attach an screenshot please?

Grabby’s picture

FileSize
266.77 KB

Sure thing – here goes.

shadcn’s picture

Ah ok. This is a views config. Your views row needs the .col-* grid class.

The recommended way to use this with your views is to add a col-md-* class to your views row. You can do that by clicking on settings next to Format in Views UI. Then add col-md-* to display your rows. See screenshot below.

When we integrate Radix with Panopoly, this will be supported out of the box.

Thanks ^^

Grabby’s picture

I assume col-md-12 is just an example and I have to come up with my own row class. In any case, it would be convenient to have as part of the demo. I’ve never seen a panel pane overlap onto another panel pane like this!

shadcn’s picture

Yes. This is going to be fixed when Panopoly ships with Radix bundled.

shadcn’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)

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

aanjaneyam’s picture

Status: Closed (fixed) » Needs work
aanjaneyam’s picture

I have recently installed radix over panopoly profile install. I followed the documentation. Every other thing seems to be working but the text in panels is overflowing. This happens whether I insert views in panes or just a content item. The result is as shown in image attached to #2 above. I tried the solution in #3 but it further muddles up the display rather than correcting it. I thing the problem comes from panopoly provided content settings included in panes (Full Content, Teaser and Featured) They are using boxton layout by default and boxton is not getting wrapped by the sorrounding pane/region - in current case I am using Radix Moscone Flipped.

aanjaneyam’s picture

I am using a radix subtheme using bootswatch flatly.

shadcn’s picture

Status: Needs work » Fixed

This has been fixed in latest release. We switched to Gulp also. Marking this as fixed. Feel free to reopen if not.

Status: Fixed » Closed (fixed)

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