Posted by boombatower on August 13, 2009 at 1:29am
Jump to:
| Project: | Drupal.org infrastructure |
| Component: | Drupal.org theme |
| Category: | bug report |
| Priority: | normal |
| Assigned: | boombatower |
| Status: | closed (fixed) |
Issue Summary
As per http://d6.drupal.org/node/367072. The tr.pifr-fail on the node is overridden by
.node .project table td, .node .project table tr, .node .project-issue table td, .node .project-issue table tr {
background-color:transparent !important;
}
Comments
#1
Bad link, try: http://d6.drupal.org/node/318636.
#2
How about change the selector in project to be more descriptive.
.project-issue-summary-table
ought to be of use.
#3
If the statement is changed to:
.node .project table td, .node .project table tr,.node #project-issue-summary-table table td, .node #project-issue-summary-table table tr {
background-color: transparent !important;
}
in bluebeach/style.css it works.
#4
Changed this slightly and committed to bluebeach's trunk branch in SVN (rev 2260). However, when I tried to merge into the d.o production branch, I'm getting this:
% svnmerge.py avail2252,2260
% svnmerge.py merge -r 2252
property 'svnmerge-integrated' deleted from '.'.
svnmerge: command execution failed (exit code: 1)
svn --non-interactive propdel "svnmerge-blocked" "."
svn: Attempting to delete nonexistent property 'svnmerge-blocked'
% svnmerge.py avail
svnmerge: no integration info available
...
Future attempts to do any merges are busted at this point. The only recourse is to remove the bluebeach directory entirely, svn up it, and start over, but I get the same over again. :( I'm trying to track down someone in IRC to help me figure out if it's just my setup or something screwy in SVN itself.
Meanwhile, I applied the change locally on d.o, so if you clear your browser cache, you should see it, e.g. at http://drupal.org/node/318636
Regardless, moving this issue to a more appropriate place to discuss a bluebeach bug.
#5
Figured out my svnmerge woes (it was my local setup after all). Merged into production and officially deployed.
#6
Automatically closed -- issue fixed for 2 weeks with no activity.