GrooveLog Blocks for Last.fm
GrooveLog Blocks for Last.fm adds block-based Last.fm listening data to your WordPress site.
The plugin currently includes a Recently Played Tracks block that displays the latest tracks from a Last.fm user. Add a username, choose how many tracks to show, and optionally include artwork and links back to Last.fm.
Features
- Display 1 to 50 recently played tracks.
- Show track names and artist names.
- Link tracks to their Last.fm pages.
- Add optional artwork using default, vinyl, cassette, or CD styles.
- Configure your Last.fm API key once for all blocks.
- Cache Last.fm responses for five minutes to reduce repeat API requests.
Recently Played Tracks
Use this block to show a list of recently played tracks from a Last.fm profile.
Block settings:
- Last.fm Username: the Last.fm username to fetch tracks for.
- Number of Tracks: the number of tracks to display. Defaults to 1.
- Include Album Art: whether to include artwork for each track. Disabled by default.
- Artwork Type: default, vinyl record, CD, or cassette tape.
- Include Link to Track: whether to link each track to Last.fm.
Set the Last.fm API key once in Settings > GrooveLog Blocks for Last.fm, then add your Last.fm username in the block sidebar.
External Services
This plugin connects to the Last.fm API to fetch recently played track data. When a page containing the Recently Played Tracks block is rendered, the plugin sends the saved Last.fm API key, the configured Last.fm username, and the requested number of tracks to https://ws.audioscrobbler.com/2.0/.
The response can include track names, artist names, Last.fm track URLs, and artwork URLs. When track artwork is enabled, visitors’ browsers may request the returned artwork image URLs directly. Responses are cached in WordPress transients for five minutes. The plugin stores the Last.fm API key in the WordPress options table and stores the Last.fm username in block attributes.
Last.fm service links:
Source Code
The distributed plugin includes compiled block assets in the build directory. The human-readable source code and build tools are available on GitHub.
To build the plugin assets from source, run npm install and npm run build.