BlueWombat

Starting with jekyll

2017-03-19T00:00:00+00:00

A quick walthrough of the most basic commands for installing and “developing” with Jekyll.

Requirements

You need to have Ruby installed and configured properly on your system, and you need to be somewhat comfortable firing up a Terminal window, Windows CMD, Bash, or whatever flavor you prefer.

For installing and configuring Ruby on Windows, check my other post Ruby on Windows, and follow the steps described, then come back to this post.

In case of Mac OS X, there’re multiple ways; but by far the easiest, and the one I choose, is to simply install Apple Xcode, as this will also install a set of command line dev tools, Ruby being one of them.

Installing Jekyll

Installing Jekyll is really super simple. Simply enter gem install jekyll, and wait for it to finish.

After this you might want to install a series of other gems, depending on how you want to build and package your site.

If you’re writing a blog like this one, you might want to install Octopress, and for that, simply enter gem install octopress, and after that, bootstrap your install.

You might want to use Bundler as part of your deployment process, and for that, simply enter gem install bundler, and go from there.

I’m sure that by now you’ve gotten the hang of installing gems.

Testing a Jekyll site

For testing your site locally, jekyll can compile it for your and serve it up for testing in a browser, using it’s built-in lightweight, and fairly simple, http-stack. To do this, simply open a shell, cd to the folder your project lives in, type jekyll serve and hit Enter.

Now, to prevent you from having to stopping and starting the process each time you change something, the debugging server has a watcher built-in. To utilize that, type jekyll serve -w instead, and hit Enter. Now you’ll see the process writing output to your Terminal window, each time you touch a file in your Jekyll directory. And the pages served are being updated accordingly.

Another useful CLI argument is --drafts which, you guessed it, includes the posts that currently sits in your _drafts folder, to see how your working progress looks like. The full command for debugging will then be jekyll serve -w --drafts.

And that’s it really, you now know the basics of Jekyll CLI and debugging. Naturally you can find way more eahaustive articles elsewhere, but this wasn’t intended to be a complete tutorial, merely a quick start guide.

Ruby on Windows

2017-03-18T00:00:00+00:00

Here’s a small cheat sheet for installing both the Ruby runtime, and the Ruby compiler and SDK that you can use for developing gems, and compiling gems from source, which is necessary from time to time.

Installing Ruby

First go to RubyInstaller.org and download the package Ruby 2.3.3 (x64) and install it. I recommend installing in the root of your OS drive, so C:\Ruby23-x64, check the box Add Ruby executables to your PATH, this option should make life easier later on, for instance if you want to build from CMD, or from Git BASH as I do.

Second, download the package DevKit-mingw64-64-4.7.2-20130224-1432-sfx.exe, and unpack it to C:\RubyDev.

Configuring Ruby - part one

Go to C:\RubyDev\postinstall and run the script pi.bat.

When prompted Do you wish to continue with the post install? Type y, and hit Enter.

When prompted Do you have MinGW installed? Type n, and hit Enter.

A tip will come up suggesting that if you install MinGW, install it to a specific path, this is not relevant right now, so just hit Enter.

If prompted for a conflict in MinGW version, just ignore this and hit Enter again.

Now this process is over, just hit Enter again, and the script will exit.

Configuring Ruby - part two

Start the newly installed MinGW, or any previously installed MinGW prompts, and cd to /C/RubyDev.

Run command ruby dk.rb init.

Open the file C:\RubyDev\config.yml in a text editor, and make the content like below.

# This configuration file contains the absolute path locations of all

# installed Rubies to be enhanced to work with the DevKit. This config

# file is generated by the 'ruby dk.rb init' step and may be modified

# before running the 'ruby dk.rb install' step. To include any installed

# Rubies that were not automagically discovered, simply add a line below

# the triple hyphens with the absolute path to the Ruby root directory.

#

# Example:

#

# ---

# - C:/ruby19trunk

# - C:/ruby192dev

#

---
- C:/Ruby23-x64

Finally, run the command ruby dk.rb install. If you get a warning about skipping, because you have a previous or misconfigured installtion, run the command ruby dk.rb install --force instead.

Now you’re done, and should be ready for installing and developing (with) Ruby gems :-)

Install or update certificates on Apache

2015-05-16T00:00:00+00:00

I decided to write this post, as I spent some time researching this the last time I had to do it, so I figured I probably weren’t the only one out there who were kinda clueless on this.

Whether you need to install or update a certificate on an Apache instance, the process is largely the same. To sum it up you first have to create a certificate request (CSR), use the CSR during the ordering process at your favourite issuer, install it, and restart the daemon.

Create a key

If you don’t already have a keyfile you would like to use for your CSR, and later your certificate, you need to create one. This can be done with the command below. Follow the prompt to enter a passphrase, and reenter the passphrase to confirm it.

openssl genrsa -des3 -out ~/keyfile.key 2048

Create certificate request

To create the CSR run the following command, note how I pass the path of the keyfile as parameter.

openssl req -new -key ~/keyfile.key -out ~/request.csr

Order your certificate online

Whether your favorite supplier is RapidSSL, DigiCert, Symantec (formerly VeriSign), Cloudflare or whatever, the process is largely the same. You choose the certificate type, and pass the content of the request.csr file, in order to receive your certificate.

Install your certificate

If you’re updating an existing certificate, you should be able to find the existing config lines with this command.

grep -i -r "SSLCert" /etc/httpd/

Look for the following lines.

SSLCertificateFile /etc/pki/tls/certs/certificate.crt
SSLCertificateKeyFile /etc/pki/tls/private/keyfile.key
SSLCertificateChainFile /etc/pki/tls/certs/CertificateAuthority.crt

If you’re on the other hand configuring from scratch, you most likely won’t have those lines to look for, though you may have them as samples. But you should be able to locate your config file at the following path.

/etc/httpd/sites-enabled/00-sitename

Add the lines noted above, and copy your certificate files and private key to the paths listed.

Restart httpd

That should be it, now all you have to do is issue a restart of the httpd with the command below.

sudo service httpd restart

Now, you’ll notice that the daemon asks for the passphrase of the private key used for the certificate, and that’s no good. To remove the passphrase from the private key, run the command below.

openssl rsa -in ~/keyfile.key -out ~/keyfile_nopwd.key

Now you need to copy over the new private key to the destination noted in your config. Once done, try issuing another httpd restart. This time around is should just restart, without prompting for passphrase, and you’re golden.

Now grab a Miller, and kick back :-)

My favorite Visual Studio Extensions

2014-11-17T00:00:00+00:00

This post is just a little list of my daily used must-have extensions for Visual Studio, it may or may not get updated in the future.

Utilities

These try to enhance the experience of using the great IDE that Visual Studio is.

SaveAllTheTime (Free)

It does exactly as it’s named, it makes sure to call the save command on open files every few seconds to amke sure those gnarly BSOD’s doesn’t get you down. You can find it here.

VSCommands (Commercial with non-expiring evaluation mode)

A nice little collection of IDE enhancements, such as the possibility to group items in your project without manually editing your .*proj file. Badges that indicates which branch or tag you’ve currently opened in Visual Studio. Continuous syncing of your settings to a folder of your choice, useful for backing them up in Dropbox and the like. And several other features. Find it here.

VCS extensions

These are for integrating otherwise unsupported Version Control Systems.

VisualHG (Free)

This is quite useful if you’re keeping track of your code in Mercurial, find it here.

Git Source Control Provider (Free)

Although Microsoft has official support of Git now, it still doesn’t work nearly as good as TortoiseGit in my humble opinion. This neat little plug-in integrates it quite well, and it’s by far the best experience I’ve had using Git and Visual Studio together. Find it here.

AnkhSVN

Open-Source competitor to VisualSVN that’s generally quite stable. it had a few quirks you had to work around last time I used it a couple of years ago, but generally works quite well. If Subversion’s your thing, as opposed to a more modern distributed VCS, go get this extension. Find it here.

Web tools

These aim to enhance your web development experience.

Web Essentials (Free)

This extension by Mads Kristensen of Microsoft Seattle and creator of BlogEngine.NET is quite extensive, and it includes all sorts of cool stuff like compilation of CoffeeScript, SASS, LESS, ZenCoding and much more. If you’re a web developer, you can’t be without this great extension. Find it here.

Code analysis and optimizers

These aim to improve your code, coding style and layer themselves on top of Visual Studios otherwise great IntelliSense support, taking it even further.

ReSharper (Commercial)

You’ll never get around the almighty ReSharper by JetBrains when you’re talking about Visual Studio extensions. It has far too many great features to mention them here. Go get it now, it’s an order! Find it here.

Prevent IIS 7.5 Application Pool from shutting down

2014-11-13T00:00:00+00:00

If you, like me, like to encapsulate jobs in the IIS app pool, as opposed to creating scheduled tasks in Windows Task Scheduler you’ve most likely faced the same issues as I with your application pool shutting down after being inactive for some time. Read on for a guide on how to configure IIS 7.5 for having always running and auto starting app pools.

This post was inspired by the slew of posts on various blogs describing how you can configure IIS Application Initialization under IIS 8, leaving out how to do it in IIS 7.5. You see, in IIS 8 it’s a feature that can be added under “Turn Windows features on or off,” but that’s not the case with IIS 7.5, here it has to be installed through Web Platform Installer. Further complicating things this module differs from the IIS 8 version in that it doesn’t include the configuration component for IIS Manager, leaving you with editing the applicationHost.config file manually, not exactly ideal. And it’s not too well documented either. After some searching I found a guy who did his own snap-in for IIS manager, and it functions very well. Credits go where credits due, and the guy I’m referring to can be found here: MSDN Social.

The first you’d want to do, is to set the timeout of the application pool to 0 (indefinite) like so, default is 20 minutes:

Here’s a snapshot of how the application level tab of the snap-in looks like.

Here’s an example of how a working application level configuration could look like.

1
2
3
4
5
6
7
8
9
<configuration>
	<system.applicationHost>
        <applicationPools>
            <add name="DefaultAppPool" autoStart="true" managedRuntimeVersion="v4.0" startMode="AlwaysRunning">
                <processModel identityType="ApplicationPoolIdentity" idleTimeout="00:00:00" />
            </add>
        </applicationPools>
	</system.applicationHost>
</configuration>

And the path for this file is:

%windir%\System32\inetsrv\config\applicationHost.config

Here’s a screenshot of how the website level tab of the snap-in looks like.

And here’s an example of how a working website level configuration could look like.

1
2
3
4
5
6
7
<configuration>
	<system.webServer>
		<applicationInitialization remapManagedRequestsTo="" skipManagedModules="false" doAppInitAfterRestart="true">
			<add initializationPage="/" />
		</applicationInitialization>
	</system.webServer>
</configuration>

You can verify everything works as intended by manually killing your worker process (w3wp.exe) and see it how it will immediately spool back up, that’s all there is to it. Happy configuring.

Here’s the link for downloading the installer for Application Initialization for IIS 7.5 over at Microsoft, and I’ve provided a mirror for the installer here: Mirror.

Here’s the link for downloading the installer for the custom configuration snap-in over at MSDN Blogs, and a mirror is provided here: Mirror.

A better Spotify player

2014-10-19T00:00:00+00:00

Are you sick of the standard Spotify player too? That it’s hogging memory like crazy, the interface is bloated, becomes non-responsive and it lacks an equalizer? Then you’d be please to know that there is an alternative, and pretty darn good one!

Meet Spotiamp (http://spotiamp.com), a player able to play content from Spotify Premium subscription, and looks and feels like an exact copy of good old Winamp; possibly some reverse engineering was performed? It’s compatible with Winamp 2 skins, and also Winamp visualization plugins. It is created as a side project by Ludvig Strigeus, a renowned Swedish software developer also behind projects like Trac, ScummVM and more.

Make sure to check it out, you really won’t regret it, if you’re a Spotify user.

Now all there’s really left to say is; “Winamp, Winamp, it really whips the Llama’s ass!”

UPDATE: 16-05-2015

Since Spotiamp’s official website has been down for quite some time, I’ve decided to put up a mirror for it here: Mirror.

UPDATE: 15-03-2017

Find the original website at Wayback Machine.

A blast from the past

2014-10-07T00:00:00+00:00

A couple weeks ago I was at my parents house doing some cleaning. One of the tasks I undertook was that of going through all our floppy disks, save what needed to be saved, and dispose of the disks. It was actually quite an emotional thing, and yes i know it’s weird, but it was! That funny whining clacky-di-clack sound of the motor in my Mitsumi USB drive brought back some fond memories of a time that was once was.

But in the middle of the pile of 3M’s and Sony’s, I stumbled upon something I had long since forgotten. A very special disk that I instantly remembered how I got, a translucent blue disk that I once got with an action figure, when shopping with mom and grandma. Must’ve been no older than 4-5 years old. Little did I realise back then, that the toy and disk was actually a movie memorabilia from an action movie I wouldn’t see until years later, Independence Day (IMDB), one of my favorite sci-fi’s! It’s a so called ID4 Mission Disk, and this one is number 6, containing a weird little game where you need to program a satellite through a laptop, to be able to talk to extraterrestrials.

Now all I need is to find the actual toy, I hope I still have it somewhere, and regarding the disk, this is one disk I won’t dispose of.

And here it is:

And as an added bonus below you’ll find a video going the through the game contained on the disk, courtesy of: Taylor Cheatwood

Clean your Windows Logs

2014-10-06T00:00:00+00:00

I personally hate doing manual maintenance of servers and running applications as I consider such tasks rather mundane and I beleive they should be as autonomous as possible. Previously I was under the impression that even relatively simple tasks couldn’t be scripted on Windows without writing VBScripts or some fancy .Net powered Powershell scripts. Truth be told, that’s still true in most cases, but actually not when looping files, as I found out by coincidence.

Below you’ll find a couple of commands that will let you delete log files older than X days, plus a couple of complete Scheduled Task scripts ready for import.

Delete IIS logs older than 7 days

Below you’ll find the command I use to automatically delete IIS W3 logs.

forfiles /P X:\IIS_Log_Path /S /D -7 /C "cmd /c del /q @path"

If you’d like to know exactly what’s going on, just write the command below, and you’ll get all the documentation you’ll need.

forfiles /?

And here it is as a complete Scheduled Task that you can save and import directly.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
<?xml version="1.0" encoding="UTF-16"?>
<Task version="1.2" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
  <RegistrationInfo>
    <Date>2014-01-01T00:00:00.000000</Date>
    <Author>.\Administrator</Author>
  </RegistrationInfo>
  <Triggers>
    <CalendarTrigger>
      <StartBoundary>2014-01-01T03:00:00</StartBoundary>
      <Enabled>true</Enabled>
      <ScheduleByDay>
        <DaysInterval>1</DaysInterval>
      </ScheduleByDay>
    </CalendarTrigger>
  </Triggers>
  <Principals>
    <Principal id="Author">
      <UserId>.\Administrator</UserId>
      <LogonType>Password</LogonType>
      <RunLevel>LeastPrivilege</RunLevel>
    </Principal>
  </Principals>
  <Settings>
    <MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
    <DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries>
    <StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>
    <AllowHardTerminate>true</AllowHardTerminate>
    <StartWhenAvailable>false</StartWhenAvailable>
    <RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
    <IdleSettings>
      <StopOnIdleEnd>true</StopOnIdleEnd>
      <RestartOnIdle>false</RestartOnIdle>
    </IdleSettings>
    <AllowStartOnDemand>true</AllowStartOnDemand>
    <Enabled>true</Enabled>
    <Hidden>false</Hidden>
    <RunOnlyIfIdle>false</RunOnlyIfIdle>
    <WakeToRun>false</WakeToRun>
    <ExecutionTimeLimit>PT1H</ExecutionTimeLimit>
    <Priority>7</Priority>
  </Settings>
  <Actions Context="Author">
    <Exec>
      <Command>forfiles</Command>
      <Arguments>/P X:\IIS_Log_Path /S /D -7 /C "cmd /c del /q @path"</Arguments>
      <WorkingDirectory>X:\IIS_Log_Path]</WorkingDirectory>
    </Exec>
  </Actions>
</Task>

Remember to change IIS_Log_Path to point at whatever is defined as your logging root folder, and the command will automatically traverse all subfolders.

And that’s it really, that’s all it takes to cut out one more mundane task so you can focus on writing software. Enjoy!

Change commit author in Git

2014-10-05T00:00:00+00:00

If you’ve ever had a reason to change the author name and/or email of one or more commits in a Git repository then fear not, it can be done. It, quite obviously, involves rewriting the history of your repository, and involves running a BASH script that utilizes the git-filter-branch utility included in the Git installer.

The script(s)

Both of these scripts should be executed in a BASH enabled terminal prompt, with git installed and in the root folder of the repository to change.

Updating specific commits

Use this script if you have multiple committers in your repository, and you only want to change the author of specific commits

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
#!/bin/sh


git filter-branch --env-filter '

OLD_EMAIL="your.old@email.tld"
CORRECT_NAME="Your New Name"
CORRECT_EMAIL="your.new@email.tld"

if [ "$GIT_COMMITTER_EMAIL" = "$OLD_EMAIL" ]
then
    export GIT_COMMITTER_NAME="$CORRECT_NAME"
    export GIT_COMMITTER_EMAIL="$CORRECT_EMAIL"
    export GIT_AUTHOR_NAME="$CORRECT_NAME"
    export GIT_AUTHOR_EMAIL="$CORRECT_EMAIL"
fi
if [ "$GIT_AUTHOR_EMAIL" = "$OLD_EMAIL" ]
then
    export GIT_COMMITTER_NAME="$CORRECT_NAME"
    export GIT_COMMITTER_EMAIL="$CORRECT_EMAIL"
    export GIT_AUTHOR_NAME="$CORRECT_NAME"
    export GIT_AUTHOR_EMAIL="$CORRECT_EMAIL"
fi
' --tag-name-filter cat -- --branches --tags

Updating all commits

Use this script if you only have a single committers in your repository, or if you for some reason want to change the author of all commits regardless of who committed originally.

1
2
3
4
5
6
7
8
9
10
11
12
13
#!/bin/sh


git filter-branch --env-filter '

OLD_EMAIL="your.old@email.tld"
CORRECT_NAME="Your New Namr"
CORRECT_EMAIL="your.new@email.tld"

export GIT_COMMITTER_NAME="$CORRECT_NAME"
export GIT_COMMITTER_EMAIL="$CORRECT_EMAIL"
export GIT_AUTHOR_NAME="$CORRECT_NAME"
export GIT_AUTHOR_EMAIL="$CORRECT_EMAIL"
' --tag-name-filter cat -- --branches --tags

After running one of the above scripts, and inspecting the history of the repository to make sure it’s rewritten correctly, run the below command.

1
git push --force --tags origin 'refs/heads/*'

And finally delete the temporary clone, to make sure nothing gets messed up down the road.

And that’s it, you’re done. I hope it all makes sense, and you find it useful. Feel free to comment if I can improve the post, or you’re unsure about something.

Cookiereports done right

2014-07-26T00:00:00+00:00

Err… sorta. There’s no doubt that Cookiereports is a terrible product, that I really can’t see the value of; as opposed to writing the legal stuff yourself. But for some reason clients insists on using them, so below you’ll find a nice little Umbraco MacroPartial, that will at least let you integrate it into your site a bit better than the god awful iframe solution they normally force you to use. Naturally this solution isn’t limited to Umbraco, it can be used in any MVC View or Partial View, or even in Webforms, if you care to do some minor coding yourself.

The Razor part

What’s happening below is actually quite trivial. It fetches the source for the page that normally would be embedded via an iframe, and runs a couple of Regex’ against it, to extract the body, and transform all hrefs and srcs to fully qualified Uris, since we’re no longer executing in the original domain context.

1
2
3
4
5
6
7
8
9
10
11
12
13
@using System.Text
@using System.Text.RegularExpressions
@inherits Umbraco.Web.Macros.PartialViewMacroPage
@{
    var language = Model.MacroParameters["lang"].ToString();
    var client = new WebClient();
    var html = Encoding.UTF8.GetString(client.DownloadData("http://policy.cookiereports.com/{your key goes here}-" + language + ".html"));
    var r = new Regex(@"<body[^>]*>(?<content>.*)</body>", RegexOptions.IgnoreCase | RegexOptions.Singleline);
    var body = r.Match(html).Groups["content"].Value;
    r = new Regex(@"(?<attr>src|href)=""(?<val>[^""]*)""", RegexOptions.IgnoreCase | RegexOptions.Singleline);
    body = r.Replace(body, @"${attr}=""http://policy.cookiereports.com/${val}""");
}
@Html.Raw(body)

The CSS part

This is an almost exact copy of the original CSS, with only a few changes. Everything is now properly namespaced under #policy, to prevent inteference, and urls are now pointing on fully qualified Uris.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
<style type="text/css">
    #policy {
        font: 14px Arial,Helvetica,sans-serif;
        color: #553e3d;
    }

        #policy h1, #policy h2, #policy h3, #policy h4, #policy h5, #policy h6, #policy h1 a, #policy h2 a, #policy h3 a, #policy h4 a, #policy h5 a, #policy h6 a {
            color: #553e3d;
        }

        #policy h1 {
            font-size: 14px;
        }

        #policy h2 {
            font-size: 14px;
        }

        #policy h3 {
            font-size: 9.8px;
        }

        #policy h4 {
            font-size: 7.7px;
        }

        #policy h5 {
            font-size: 5.6px;
        }

        #policy h6 {
            font-size: 3.5px;
        }

        #policy h1, #policy h2, #policy p, #policy li {
            font-family: "Soho W02 Regular";
            font-size: 14px;
            line-height: 20px;
        }

        #policy .section {
            padding: 0 0 7px 0;
        }

        #policy ul.details li {
            padding: 10px 0 0 10px;
        }

    #policy-flash .screenshot {
        background: url('http://policy.cookiereports.com/i/policy/screenshot-flash') no-repeat;
        height: 300px;
    }

    #policy .pdficon {
        display: inline-block;
        background: url('http://policy.cookiereports.com/i/policy/pdf') no-repeat;
        height: 17px;
        width: 17px;
        margin-left: 4px;
    }

    #policy #policy-downloads .pdficon {
        margin: 0 4px 0 0;
    }

    #policy #policy-downloads ul {
        padding: 0;
        margin: 0;
    }

    #policy #policy-downloads li {
        list-style-type: none;
        padding: 0;
        margin: 3px 0;
    }

    #policy table.cookies {
        font-size: 0.8em;
    }

        #policy table.cookies th, table.cookies td {
            padding: 3px 9px;
        }

        #policy table.cookies th {
            vertical-align: top;
            text-align: left;
            border-bottom: 1px solid #ccc;
        }

    #policy .rtl table.cookies th {
        vertical-align: top;
        text-align: right;
    }

    #policy table.cookies td {
        vertical-align: top;
        border-bottom: 1px dotted #ccc;
    }

    #policy tr.info td {
        border-bottom: 1px solid #ccc;
    }

    #policy td.description p {
        margin-top: 0;
        padding-top: 0;
    }

    #policy td.icon .icon {
        float: left;
        margin-right: 6px;
    }

    #policy .rtl td.icon .icon {
        float: right;
        margin-left: 6px;
    }

    #policy tr.green td.icon div.icon {
        background-image: url('/i/policy/green/led');
        background-position: 0 0;
        width: 15px;
        height: 15px;
    }

    #policy tr.amber td.icon div.icon {
        background-image: url('/i/policy/green/led');
        background-position: -16px 0;
        width: 15px;
        height: 15px;
    }

    #policy tr.red td.icon div.icon {
        background-image: url('/i/policy/green/led');
        background-position: -32px 0;
        width: 15px;
        height: 15px;
    }


    #policy dl {
        margin: 10px 100px 30px 60px;
    }

    #policy dt {
        float: left;
        font-weight: bold;
    }

    #policy dd {
        margin-left: 190px;
        margin-bottom: 10px;
    }

    #policy .policy-icon-heading {
        color: inherit;
        text-decoration: none;
    }

    #policy .toggle-icon {
        margin-right: 6px;
    }
</style>

The jQuery part

This part is written from scratch to mimic the functionality of the original JavaScript provided by Cookiereports themselves. The reason for this is that aside from being very clunky, and unnecessarily complex, I had to change it anyway to recity the img src.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
<script type="text/javascript">
    $(function () {
        $("#policy .sections .section").each(function () {
            var $this = $(this), $h2 = $this.find("h2"), $desc = $this.find("*[id$='_cookies']");
            if ($desc.length > 0) {
                $h2.click(function () {
                    $desc.toggle();
                    var $img = $h2.find("img");
                    $img.attr("src", $desc.is(":visible") ? "http://policy.cookiereports.com/i/boxminus.png" : "http://policy.cookiereports.com/i/boxplus.png");
                }).prepend("<img class=\"plusminus\" src=\"http://policy.cookiereports.com/i/boxplus.png\" />&nbsp;&nbsp;").css("cursor", "pointer");
                $desc.css("display", "none");
            }
        });
    });
</script>

I hope you find it as useful as I did. And while we can easily agree that they should’ve provided us proper solution, and not let us do symptom treatment, at least it’ll get the job done.