| 开发者 |
materron
wajari |
|---|---|
| 更新时间 | 2026年11月12日 21:37 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
<podcast:chapters>, so podcast apps show them.[vozcaster_connect] shortcode still works./conectar to the bot and paste the address instead.
Requirements
connector-for-vozcaster folder to /wp-content/plugins/, or install via Plugins → Add New → Upload Plugin.Yes. PowerPress is a hard requirement — the plugin uses PowerPress to register episode metadata, enclosures, season and episode numbers.
Yes. Register the post type (for example "podcast", with its own /podcast/ URLs) with your theme, a few lines of code or a plugin such as Custom Post Type UI. Then create a PowerPress channel and, in its settings, limit it to that post type ("Custom Post Type"). That podcast then shows up in VozCaster like any other: its episodes are created in that post type, in the channel's feed, and never appear in the blog. Podcasts set up with PowerPress's older Post Type Podcasting keep working too.
Yes, since 1.14.0. Some hostings answer any request that is not a browser with a "checking your browser" page, so VozCaster cannot reach your site. Connect with the "Connect in Telegram" or "Connect in the app" button in wp-admin (VozCaster → Connect): it works even then. When you publish, VozCaster sends you a link to your own site; open it, press the button, and your site collects the episode from your browser. To skip that extra step, ask your hosting to allow requests to /wp-json/vozpress/ on your site.
This plugin is free and open source. The VozCaster service it connects to offers a free tier and a paid (Pro) tier. Basic episode publishing (including basic audio cleanup) works on the free tier; the Pro features — automatic transcription, a fully written article, a generated featured image and advanced noise reduction (DeepFilter) — require a Pro or Studio subscription or an episode pack. See https://vozcaster.com/en/pricing.html for the current plans.
Permanently, only in your own WordPress media library. VozCaster processes the audio on a private server operated by the author (located in Spain) and deletes the temporary files after publishing.
Your audio is never sent to a third-party AI service. Transcription runs on a local Whisper model on VozCaster's server, so the audio file itself stays on that server (and on Telegram, if you record there). To draft the episode title, description and content, VozCaster sends the transcribed text to Anthropic's Claude API. If you ask it to generate a cover image, the image prompt is sent to OpenAI's image API. These providers receive text only, and only when you request content or image generation. See the "External Services" section below for the providers and their privacy policies.
No. The VozCaster app (app.vozcaster.com) does everything the bot does, from the phone or the computer browser: record, produce and publish episodes, write blog posts, edit the podcast details and submit the feed to platforms. Telegram is just another way in, if you prefer it.
Yes. Each site needs its own installation of this plugin and its own connection: press the connect button on each site.
Yes. The plugin works with PowerPress's multi-podcast (custom channels) configuration. You switch between podcasts in the app's site settings, or with /feed in Telegram.
Until you save the table in VozCaster → Access, every role that can publish posts (Author, Editor, Administrator) publishes in every podcast, as in earlier versions. Once you save it, the table decides: for each role and podcast, "publishes", "with review" or no access. Administrators always publish everywhere, and the roles you mark as "Manages VozCaster" (for example a school's coordinators) can change the table and the classes without being WordPress administrators. The same screen lists who has connected and lets you revoke access.
Yes. Create a role for them (for example "English teachers", created in VozCaster → Access with no other plugin) and give it access in VozCaster → Access. Then add the VozCaster blocks to a page: once logged in, each person sees there the buttons to connect, the episodes waiting for their review and their classes, and never needs to open wp-admin. Avoid giving access to the whole Subscriber role if anyone can register on your site.
Yes. Set the role to "with review" for that podcast in VozCaster → Access. Its episodes are saved as "Pending review" and reach whoever publishes directly in the podcast, or only the teachers of the class they were sent to. They get an email and see it in VozCaster → Review (or the review block, or VozCaster itself), listen to it, and publish it or return it to its author with a comment. VozCaster tells the sender what happened.
A sub-category of a podcast, for a group of students: "B1.1", "A2 evening", "Mila's students". Anyone who publishes directly in the podcast can create classes in VozCaster → Classes or with the classes block, and choose who reviews each one. When a student sends an episode they pick their class (VozCaster remembers it), and only that class's teachers are asked to review it. The episode is published in the podcast's feed as usual, and the class also gets its own page and feed. At the end of the year, archive the class: its episodes stay where they are.
When VozCaster writes the text of a post with AI, the plugin shows a short notice with it so readers know. It is on by default, and you can change its text and position or turn it off in VozCaster → Episodes, or hide it on a single post from the editor. The notice is added when the post is displayed, so changes apply to all posts at once.
Go to VozCaster → Distribute in wp-admin, open Distribute to platforms in the app, or send /difundir to the bot. First it checks that the feed has everything platforms ask for (title, description, square artwork of 1400–3000 px, category, author, owner email and at least one episode). Then it lists the platforms by importance, each with its submit link, a link to find your podcast there and a status you can mark: not submitted, submitted or live. You only submit once: after that every platform picks up new episodes by itself. VozCaster also checks Apple Podcasts on its own and marks it as live when your feed appears there.
Yes, in Podcast details in the app or with /podcast in Telegram (site administrators only). It writes into the same PowerPress settings, so you can keep editing them in PowerPress too. The artwork is cropped to a square and resized to 3000 px if needed.
Not unless you ask it to. There is an optional "Published with VozCaster" credit line with a link, which is off by default and can be turned on in VozCaster → Episodes.
For documentation, see the VozCaster manual. For issues or questions, email info@potencia.pro.
<podcast:chapters> and <podcast:transcript> tags were stripped.<podcast:chapters>.<podcast:transcript>, in the podcast's language. It was saved where PowerPress does not read it.[vozcaster_connect] shortcode), next to Connect in Telegram. It opens the VozCaster web app, which records from the phone or computer and publishes here without Telegram. Same single-use code as the Telegram button.POST/DELETE /media/separator; /media/intro-outro now also reports it.[vozcaster_connect] shortcode — the "Connect in Telegram" buttons on any page of the site, with a login link for visitors and a notice for users without access. Optional feed attribute to show a single podcast./podcast shows and changes the show data PowerPress publishes in the feed — title, description, artwork, Apple Podcasts category, author/owner, owner email, language and explicit — for the main feed, custom channels and category feeds, with a checklist of what platforms need. New REST endpoint GET/POST /podcast./difundir in the bot) lists Spotify, Apple Podcasts, YouTube Music, iVoox, Amazon Music, Podcast Index, Pocket Casts, Castbox and Deezer by importance, with submit and search links and a status per platform. New REST endpoint GET/POST /distribution./conectar still works.itunes_image) — only the regular WordPress featured image. It had to be filled in by hand every time. New episodes now get it automatically from the same image (the one uploaded by the bot, or the podcast's default cover as fallback). Episodes published before this fix are unaffected — their Apple Podcasts artwork field stays empty until edited manually or the episode is republished./estilo, and stored only in the bot's own database — it now lives on the site (GET/POST /settings), so /estilo and wp-admin both read and write the same value.POST /season/increment returns next_episode_number and next_episode_in_season./temporada — it no longer requires a WordPress administrator. /temporada 4 fixes the season to a given number after a confirmation prompt; /temporada on its own shows the current season and offers a one-tap jump to the next one.enclosure field is now read with unserialize() restricted to allowed_classes => false, ruling out PHP object injection.$wpdb->prepare(), and uninstall.php carries an explicit ABSPATH guard.wp-admin/includes/media.php (which defines wp_read_audio_metadata()) was not loaded in the REST API request context, causing attachment metadata generation to fail for audio files.admin_enqueue_scripts and wp_localize_script instead of inline output.wp_parse_url() applied where flagged./episode/next-number now also returns the chapter number within the current season so the bot can name uploaded media files using the season+chapter scheme./episode/next-number includes episode_no_in_season for season-aware media file naming.assign_podcast_category() no longer creates new categories — prevents duplicate "Podcast" categories on sites with custom slugs.powerpress_general.custom_feeds — the per-podcast permissions UI in wp-admin now appears correctly on sites with PowerPress custom channels.== External Services == section to readme./temporada command in the bot./ping, /auth/verify, /media/audio, /media/image, /episode REST endpoints.wp_check_password().