Pendulum

The event manager does the calendar work inside WordPress

Plenty of music themes let you publish an event post. Pendulum's vendor description claims more than that: an Event Manager that handles repeatable and multi-day events, a counter counting down to the next event, and an events archive that moves entries from future to past automatically once they occur. Each event can also show its location through Google Maps.

If those claims hold on your install, the touring calendar stops being a maintenance chore. A weekly residency is entered once as a repeating event rather than as fifty separate posts, a two-day festival keeps its single entry, and the archive tidies itself as dates pass. A venue that books weekly line-ups and a producer announcing a run of club nights get the most from this, because both publish dates in volume and both need the archive to age without manual editing.

What the description does not settle is how the countdown behaves when several events are scheduled at once, or how a past event's page looks once it drops into the archive. Those are the things to check on a staging copy with a handful of real dates loaded.

Tracks manager and the Scamp player, as one chain

Pendulum lists four custom post types: Portfolio, Events, Slider and Tracks Manager. Three of them — Portfolio, Slider and Tracks Manager — are sorted with drag-and-drop in the admin, which means track order is set by dragging in a list rather than by editing dates or menu weights.

That ordering feeds the Scamp Music Player. The vendor describes Scamp as supporting the SoundCloud API, so tracks can be added directly from SoundCloud, and says the player loads content into its playlist dynamically with individual cover art per track. The feature list separately covers self-hosted MP3, hosted MP3 files and Shoutcast streaming, so the track manager is not tied to one audio source. A producer streaming from SoundCloud and a label with its own MP3 library can both use the same post type.

The player is also described as scaling with the responsive layout, including on mobile and tablet. That is a claim worth verifying with real files and a real phone, since audio players are where responsive layouts most often break: a playlist that fits a desktop sidebar may need a very different arrangement on a narrow screen.

Where the music and the imagery sit on a page

Two structural choices shape how Pendulum pages feel. The first is the slide panel, a slide-out widget area the vendor says includes an invisible scroller and closes itself after the page loads. Because it is a widget area rather than a fixed template region, what sits inside it is your decision — a prompt to follow the artist elsewhere, a mailing list signup, or a short player.

The second is the header. Pendulum's headers can hold titles, images, sliders, videos and even maps, and the vendor says they are set per page, post or portfolio item. For a DJ or a club, that is the difference between a homepage that opens on a video loop and an inner page that opens on a plain title. It also means header work is repeated per page, so decide on two or three header patterns and reuse them instead of designing each page's top section from scratch.

Editing and what the demo import actually gives you

Pages are assembled in WPBakery Page Builder, which the vendor bundles and describes as drag-and-drop with no coding required. Pendulum also offers a one-click demo import: upload the demo archive, unpack it, click install, and the vendor says everything in that demo is installed along with your WordPress site.

The images are the exception, and the vendor states it plainly. Preview images are for demonstration only, and importing dummy data leaves placeholders where those images were. Treat the import as a structural starting point — layout, pages, post types — and plan to licence or shoot the photography before launch, because on a music site the visuals carry much of the promotion.

Around the builder sit the integrations the vendor lists: MailChimp for list signups, Contact Form 7 for booking and enquiry forms, and DISQUS comments that can be switched off from the admin. Translation is covered by .po, .mo and .pot files plus a claim that the administrative interface is localised too. The included-files field records layered PSD and layered PNG alongside PHP, HTML, CSS and JS files, which matters if a designer has to match the theme's graphics outside the browser.

Release upkeep and the security entry in 3.1.5

The changelog for the latest marketplace release, 3.1.5, records a fix for a critical PHP Object Injection vulnerability (rated CVSS 8.8 in the entry) in the theme panel's import functionality, together with an updated WPBakery Page Builder and Toolkit plugin. The two releases before it address PHP errors, a Safari loading-animation bug and PHP 8.3 support.

That record is the practical argument for running the current release rather than an older archive: the vulnerability described lives in the theme's own import code, not in a third-party plugin you could patch independently. It is also a reminder that a demo import is an administrative action — run it on a staging site you control, on a current version.

Separately, the marketplace compatibility field declares WordPress 6.7.x, 6.8.x and 6.9.x as supported, as observed on 4 November 2026. Those are declarations, not results from running the theme against your PHP version, plugin stack and server. Pendulum depends on a bundled page builder and expects several plugins active, so the combination you actually deploy is the one to test before it goes live.

Questions & answers