The Version Checker plugin for WordPress allows Semiologic customers to manage themes and plugins from this site as if they were hosted on wordpress.org.
Installing and configuring Version Checker
To install Version Checker, download the zip from below, and browse Plugins / Add New / Upload:
Use the form to install Version Checker from its zip file, and activate it:
Browse Settings / Semiologic API Key will then become available. Enter and save your Semiologic API Key on that screen. (You'll find your Semiologic API Key on your profile page in the Semiologic members' area.)
Tools / Semiologic becomes available once you've entered your API Key:
Installing Semiologic packages
Tools / Semiologic should now be listing plenty of plugins. And the Semiologic theme to the very bottom.
Your next step is to install the remaining plugins on your site. The most convenient here is to click the Mass Install button:
Click the Mass Install button. Version Checker will then put your site in maintenance mode, and start downloading and installing the packages one by one:
It generally takes a few minutes to complete the process. Do not interrupt it. (Your site will be left in maintenance mode if you do.)
Once the process completes, you'll note that Version Checker takes a couple of additional steps for your convenience:
- It will activate a whole bunch of plugins
- Create a .htaccess file for your site if none is found
- Change file permissions as needed for the plugins to work
On completely new sites, it will also:
- Delete the sample WordPress data
- Rename your default category to "News" (i.e. for use with the Opt-In Front Page plugin)
- Configure a fancy url structure if your server supports it
Scroll down to the bottom of the page once it's done. You should see some feedback related to the activation of plugins, and a button to continue with the installation of the Semiologic theme.
Installing the Semiologic theme can take a minute or two on some servers. Its zip is rather large because it contains multitudes of skins.
Activate the theme, and you're done.
Upgrading Semiologic packages
The Semiologic theme, and the multitude of Semiologic plugins, are maintained:
- We make sure they don't break when WordPress changes its APIs
- We fix the occasional bugs and conflicts with 3rd party software
- We regularly implement improvements and enhancements
You'll notice messages in your admin area when new updates are available:
Do NOT ignore these update notifications:
- WordPress updates occasionally relate to security holes. Sites do get hacked. Sometimes in very ugly ways. Not keeping your site up to date can and will eventually put your online business in jeopardy.
- On the flip side, WordPress upgrades can and do break themes and plugins. So be sure to keep the ones you are using up to date as well.
It is best practice to first upgrade your theme and plugins; then WordPress.
Semiologic development news
We like to keep our end-users updated on what's going on, and interacting with us.
When Version Checker is active, a "Dev News" item will show to the top right of the admin area. It pulls the latest post from this site's WordPress feed on a regular basis.
(If you don't want to see it for whatever reasons, you can turn it off under Users / Your Profile.)
Quality assurance process
As part of our Quality Assurance process, we like to involve our end-users so they can test new features before we distribute them at large.
If you don't mind testing software, consider setting up a site or two so it runs bleeding edge packages instead of stable packages. You can do this under Settings / Semiologic API Key. Most users toggle this on a test site (be sure to set one up). Some also do this on their smaller sites.
Note that bleeding edge zips from this site are not nightly snapshots of the latest code base. We only release them when we consider them safe to use on live sites — this site, for instance, runs bleeding edge packages almost all the time.
The typical flow is the following when bugs or conflicts with 3rd party software are reported:
- The issue gets fixed on the spot; we release a new bleeding edge package
- It becomes available to all who use bleeding edge packages upgrade directly from within WP
- We go through a round of testing; we repeat the first two steps if needed
- We release a new stable package so the fix is available to all Semiologic users
A similar workflow applies when we introduce new features… with longer periods of testing. Thanks in advance if you participate!
This package is part of Semiologic Pro, and is access-restricted.
Bleeding Edge Zip
Frequently Asked Questions
The Semiologic forum is the best place to report issues.
Version 2.9 =
- Fix displaying of available Semiologic themes of the Tools->Semiologic installer page
- Remove pre-WP 3.7 compatibility
- WP 4.1 compat
- Added debugging support to bypass caching
- Fork wp-themes-list-table files per guidance
Version 2.8 =
- WP 4.0 compat
Version 2.7 =
- Updated the Semiologic Legacy theme notification message
- Use more full proof WP version check to alter plugin behavior instead of relying on $wp_version constant.
Version 2.6 =
- Code refactoring
- WP 3.9 compat
Version 2.5 =
- Call upgrader_process_complete filter when Mass update function completes
- Upgrade notification suppressed when conflicting plugin names between wordpress.org and external plugin sources
- Fix upgrade notification nag message with 3.8 dashboard
- WP 3.8 compat
Version 2.4.1 =
- Fix Plugin Mass Installer that got broken in 2.4
Version 2.4 =
- WP 3.6 compat
- PHP 5.4 compat
Version 2.3 =
- Roll up misc. bug fixes in past releases.
Version 2.2.4 =
- Fixed bug that could cause the Tools->Semiologic screen to show empty plugin list
Version 2.2.3 =
- Fix positioning of Semiologic Development News for WP 3.4
- Update contact information in API screen
- Change WP version detection
Version 2.2.2 =
- Fix positioning of Semiologic Development News in WP 3.5
Version 2.2.1 =
- Fix condition were future updates can fail if previous api call returned empty results
Version 2.2 =
- Fix unknown index warnings
- Remove hardcoded WP version from API call as decoded logic fixed on server
Version 2.1.8 =
- Hard code WordPress version to 3.2.1 in call to Semiologic API to get plugin and themes lists populated.
- Added fix for WP3.2+ to pass args parameter in call to _get_first_available_transport.
Version 2.1.7 =
- Improve disabling curl ssl verification.
- WP 3.1/3.2 fixes for the theme installer.
- WP 3.2 fixes.
Version 2.1.6 =
- Fix curl w/ ssl
- WP 3.1 ready
Version 2.1.5 =
- Finish fixing minor crash (affects PHP 5.3 platforms)
Version 2.1.4 =
- Fix minor crash
Version 2.1.3 =
- Fix plugin mass-upgrader for old WP installs
Version 2.1.2 =
- Fix php notice
Version 2.1.1 =
- Prevent news feed from hiding instructions during installs
Version 2.1 =
- WP 3.0 compat
- Dump WP 3.0.x update nags for WP 2.9.2 installs
Version 2.0.4 =
- Pre-flight WP 3.0 fixes
- Dodge WP transports API bugs
Version 2.0.3 =
- Fix the broken theme update link
- Play well with Ozh's Admin Drop Down Menu plugin
Version 2.0.2 =
- Disable nagging for new (i.e. not bug fixed) major versions of WP
- Improve "php 4 is outdated" nagging
Version 2.0.1 =
- Fix erroneous link in admin area
- Allow for bulk upgrade of WP.org plugins with inconsistent file names
Version 2.0 =
- Use the new API service
- Allow for theme and plugin updates
- Allow for bleeding edge package updates across the board
- Implement theme and plugin installer