User Experience Gone Wild: WordPress plugin compatibility issues with Safari 9

wordpress safari logo

Share this post

LinkedIn
Facebook
Twitter

On September 30 Apple released version 9 of its default web browser, Safari. The new browser version came bundled with OS X El Capitan, and is also available for Yosemite and Mavericks users. In addition to security, privacy and compatibility updates, Safari 9 also includes controls to mute audio in tabs, additional viewing options for Safari Reader and improved AutoFill compatibility.

Since version 9 was released, we’ve noticed an issue that seems to affect sites using Code Canyon’s Visual Composer page builder plugin for WordPress. We love this plugin because it makes content management so easy for our clients. The simple drag-and-drop interface is intuitive, and there’s no additional code required to ensure the content is responsive and displays beautifully on any device.

Except, devices running Safari 9 literally don’t get the picture. We began to notice certain featured images, backgrounds, even company logos in the headers of sites using Visual Composer went MIA when rendered in Safari 9.

Luckily, Code Canyon was quick to update the plugin and released version 4.7.4 on October 2 which seems to resolve the Safari 9 issues we’ve encountered so far. However, this plugin update isn’t automatic. If your site uses Visual Composer, now would be a good time to check the backend and make sure your theme and all plugins are up-to-date. Actually, real talk: it’s always a good time to check these things! Outdated themes and plugins are like neon “open” signs on your website, points of weakness that hackers can easily exploit.

If you purchase a WordPress theme that comes with premium plugins already installed, it’s a good idea to go ahead and buy the licenses for those plugins anyway. That way, if there’s an update to any of the plugins, the plugin developers will notify you, and you’ll be able to update those plugins immediately without having to wait on the theme developer to take action.

Have you noticed any other unusual compatibility issues with Safari 9 so far? Do you have any other pro tips on plugin maintenance or compatibility?

Recent Posts