Wednesday, 17 January 2018

Qlik for WordPress Plugin v1.2

Qlik for WordPress Plugin version 1.2 has been released and included the following updates:
  • Minor bug fixes
  • Update to the Highlight.js core
If you installed the plugin from the WordPress Plugins Directory then you will be prompted to install the update next time you log in to your site's WordPress Admin portal. Alternatively, downloads and full instructions for installation and use can be found on the QlikView for WordPress page, or alternatively on the website.

Tuesday, 16 January 2018

Qlik Web Syntax Highlighter v1.2

Qlik Web Syntax Highlighter version 1.2 has been released and included the following updates:
  • Minor bug fixes
  • Update to the Highlight.js core
As always, grab the download link and full instructions from the QlikView Web Syntax Highlighter page. If you find any issues or have any suggestions, please leave me a comment below.

A new version of the Qlik for WordPress Plugin based on the Web Syntax Highlighter is planned for release shortly.

Wednesday, 17 June 2015 gets a face lift

As you can see, has started to go through a redesign. It's been something I've been planning for a while now and it isn't yet complete. Over the next few days I'll be rolling out the rest of the redesign and I'll do my best to keep any disruption to the site to a minimum. If you do find the site is down at any time, please call back a little later.

It still astonishes me the volume of traffic this site gets and I feel guilty for not finding the time to blog more than I do. This redesign will hopefully be the start of a few changes to the site which I hope will reignite my enthusiasm.

- Matt

Monday, 27 April 2015

WordPress XSS Vulnerability

A vulnerability has recently been found which affects a huge number of WordPress plugins and themes. In simple terms, it allows malicious code to be executed on any site using a theme or plugin which contains the vulnerability.

For those using my QlikView for WordPress plugin, the good news is that it isn't affected by this XSS vulnerability and so you don't need to worry. However many of the most commonly used plugins have been found to contain the vulnerability including:

Friday, 27 March 2015

The origins of data visualisation: Michael van Langren

The Chinese philosopher Confucius is thought to have said "Study the past if you would define the future". Whilst I have no intention of defining the future of data visualisation, I certainly believe that looking at its origins, successes and failures can help us to better visualise data today.

It is fairly widely accepted that the first true data visualisation was made by the Dutch cartographer, mathematician and engineer Michael van Langren. Langren served as royal mathematician to King Philip IV of Spain, and became interested in one of the most important mathematical problems of the day - how to accurately determine longitude. Being able to determine longitude was hugely important for navigation, especially at sea. There were various methods used at the time but most were known to be estimations at best.

To demonstrate the wide difference in the estimations, in 1644 Langren published a simple, single dimensional chart to demonstrate the significance of the problem to the Spanish court.

Langren drawing for the Spanish court of 1644

Thursday, 12 March 2015

QlikView Components v10.1 Released

A new version of QlikView Components (QVC) is now available. Version 10.1 brings bug fixes and improvements to additional functionality. This new release can be downloaded from:

Changes for V10.1:
  • Closed issue 23. Non-English characters not supported in log file. (Thanks to Alkopfer)
  • Qvc.Log -- New variable Qvc.Log.v.WriteToQvLog, indicated if the logging should also be written to the QlikView/Sense application log file and script progress window.
  • Closed issue 24. Qvc.IncrementalSetup failing when QVD exists but is empty. (Thanks for Luca Jonathan Panetta)
  • Qvc.SegmentedStore -- New segment type of 'day' added to create daily QVDs.

You can read the full release notes here.

Friday, 27 February 2015

Populate QlikView variables from an external file

When building multiple tiered QlikView solutions, it is often handy to be able to define global variables that are then used across all QVWs within the solution. For example, having a single variable that defines where QVDs are to be stored and loaded from, can make moving the app from a development environment to a production server a little quicker and simpler.

I'm starting to feel like a broken record saying this, but there are of course multiple ways to achieve this in QlikView. One method, and probably the most commonly used, would be to define the variables in a QlikView script file as follows:

SET vQVDPath = C:\QlikView\Data\QVDs\;

The script file can then be included in multiple QVWs by added the following line towards the start of each script: