Qlik Sense WordPress Plugin v1.3.1

A new release of the Qlik Sense WordPress Plugin is out. Version 1.3.1 brings the following tweaks and changes:

• Fixed a bug where clicking cancel on the shortcode insert popups still inserts the shortcode
• Made the plugin clean up all its settings uninstalled
• Made the plugin translation ready and included en_US and en_GB translations

If you'd like to help translate the plugin into other languages, please get in touch.

If you have the plugin installed already, the update should become available in the WordPress admin control panel of your site. Full details of how to install and use can be found here.

Qlik for WordPress Plugin v2.0

Qlik for WordPress v2.0 has just been released. This release provides the biggest improvements to date, bringing a large number of new features as well as the usual tweaks and bug fixes.

If you've tried the plugin before and found it stopped other features and plugins from working, give it another try as hopefully this issue has now be resolved.

Plugin Settings Page

The plugin now has its own settings page where you can turn on or off the otional features.

Qlik Web Syntax Highlighter v2.0

Qlik Web Syntax Highlighter v2.0 has just been released. This release provides the biggest improvements to date, bringing a large number of new features as well as the usual tweaks and bug fixes and follows:

• Added Qlik Sense connection string support
• Added the missing keywords DERIVE and FLUSHLOG
• Added support for DIRECT QUERY statements
• Fixed issue with REM comments not supporting whitespace before them
• Fixed issue with clicking cancel on shortcode prompts results in shortcode still being entered
• Fixed issue with variable declarations containing a full stop (AKA period) not highlighting correctly
• Fixed issue with backslash incorrectly operating as an escape character in strings
• Other minor highlighting improvements
• Significant speed improvements
• Added custom vector font to allow insertion of some Qlik icons
• Added the LUIicons vector font from LeonardoUI to allow insertion of all Qlik Sense UI icons
• Added optional extra line numbers to code block (should be used with caution as can prevent correct highlighting of code than spans multiple lines eg. /* */ block comments)

Qlik for Visual Studio Code v0.4.0

After my recent post regarding text editors for working with QlikView and Qlik Sense script files, Visual Studio Code was top of the wish list. There was already a Qlik VS Code extension available in the VS Marketplace, that whilst not perfect was a great start. So I reached out to it's author Xavier Hanh with an offer to collaborate on improving the syntax highlighting it offers.

I'm pleased to announce the first fruits of the collaboration, a new release of the Qlik for Visual Studio Code extension.

The Vanishing Addict

I've received a number of similar questions lately regarding the absence of any new posts over the last year or more and my sudden return. So I thought I'd address them all out in the open. Here goes....

Am I still alive? Yes, thankfully I am.

Have I given up Qlik? Are you kidding? Until they develop an effective treatment I'll remain an addict.

Text Editors for Qlik Developers

As you will no doubt have seen, I've recently been making some updates to the various Qlik syntax highlighting tools, plugins and extensions I've produced. These updates are long overdue and have added support for some of the changes and additions to QlikView and Qlik Sense over the last couple of years. Support for Direct Query statements, Qlik Sense connection strings and a small number of missing keywords are most notable.

Whilst making the updates I noticed that the language definition for UltraEdit hasn't been download anywhere near as many times as the others. It was originally produced at the request of a customer who used UltraEdit and so I never really knew how popular it was these days. This got me wondering what text editors people were using to edit Qlik script files. So curiosity get the better of me and I tweeted a quick poll to find out what people's preferences were. After 24 hours the results were in and the tweets I received were read. A huge thanks to everyone who responded!