TubePress changelog

• Fixed: a single video whose rendition failed to upload could freeze the entire transcoding queue. The conversion server stayed reserved for that video for the whole retry window (up to 4 hours), so no other video could start — even with the server completely idle. Importing a new file was the only way to resume.
• The reservation now only accounts for renditions that are actually ready to run, and reserves that many job slots instead of the whole server.
• Fixed: when a conversion server went into error, renditions produced from a source it had already encoded stayed stranded on that dead server instead of moving to a healthy one.

• When a video's source was re-encoded on a remote conversion server, later quality renditions could fail to download the source file and stayed stuck, reporting HTTP 404. Renditions of the same video that had already started were unaffected, so a video could end up with some qualities available and the rest permanently pending.
• Videos already stuck this way now recover automatically on their next retry — no need to re-upload anything.
• A conversion server that fails to upload a finished re-encode back to your storage no longer removes the original source file, so the job can be retried safely.

• Removing the ad code from a spot in an in-feed placement now genuinely removes the ad. Previously the spot still rendered a clickable, empty "Sponsored / Promoted" card with a blank thumbnail.
• Same fix applies to an image spot with no image selected, and to a VAST spot placed in an in-feed zone (VAST only plays inside the player).
• Affects the between-videos, related-videos, homepage, listing, category, performer, tag and gallery-listing placements.
• Ad spots that do have a code or image creative render exactly as before.

• Turning an ad zone or an ad spot off in Admin → Advertising now takes effect — previously the switch moved but the change was never saved, so the ad stayed active and kept being served.
• Deleting an ad spot now works — previously the confirmation appeared but the spot was never removed, with no error message shown.
• Root cause: the admin layout did not emit the CSRF meta tag that the Advertising scripts read, so those requests failed silently before being sent.

• New Videos → Bulk Upload page: drop any number of video files, edit the proposed titles, set the status, type, description, categories, tags, pornstars and channels for the whole batch, and start — each file becomes its own video, uploaded one after the other with per-file and overall progress, speed and time left.
• The duration and a poster thumbnail are read from each file in your browser before it is sent, so every video arrives with a thumbnail even when your server has no FFmpeg; transcoding is queued exactly as for a single upload.
• You can keep adding files while a batch runs, remove files before they are sent, cancel at any time (videos already created are kept) and retry any file that failed, with the server's reason shown on the row.
• The Help Center gained an “Upload many videos at once” guide, and the New Video page links to the bulk uploader.

• The Pause Ad placement now accepts a VAST tag URL next to HTML/JS code and image banners: pick “VAST Tag” when creating the spot and paste your ad network's in-video banner tag set to the On Pause trigger (for example an ExoClick In-Video Banner).
• The player requests the tag when the viewer pauses, shows the returned banner (non-linear creatives, ideally 300×250) centred over the paused video, and hides it as soon as playback resumes. Impressions are counted in Advertising only when the banner is actually shown.
• Saving any VAST spot without a valid http(s) tag URL now warns you instead of silently showing nothing.

• 1.1.26 was packaged with config/app.php still declaring APP_VERSION 1.1.25. Because that file is replaced by every core update, applying 1.1.26 succeeded but left the install reporting 1.1.25.
• Admin -> Updates therefore kept showing the old version and kept re-offering the same update, with no error message and nothing recorded in the update log — the update appeared to do nothing.
• 1.1.27 restores the version constant. Installs on 1.1.25, and installs that already applied 1.1.26, both converge here. No database migration is required.
• No functional change: the catalogue ownership fix shipped in 1.1.26 is unaffected and remains in place.

• Fixed: clearing the download queue in Import → Catalogue (Clear finished, delete entry, delete batch) made every already-imported video lose its IMPORTED badge and come back as available stock. Because the catalogue charges again for a video you already own, that housekeeping action could lead to paying twice for the same video.
• A video's imported state is now read from the video itself, the same way imported galleries have always worked, instead of only from the download queue rows.
• Self-healing: if your queue was already cleared, the IMPORTED badges come back as soon as you update — nothing to re-import and nothing to reconfigure.
• Purchases still in progress continue to count as imported, and deleting a video locally still puts it back on sale as before.

• If you updated to 1.1.23 and your admin panel lost all its styling, install this update — it restores it. Nothing else on your site was affected.
• Cause: 1.1.23 placed the new compiled stylesheet and scripts in a folder that the updater already running on your site does not install. The files were in the package but never reached your server, so the stylesheet returned 404.
• They now ship in a location every version of the updater has always installed, and which your web server serves directly. Verified end to end on a real install.
• All the 1.1.23 performance work is unchanged and still applies.

• The admin stylesheet is now compiled and shipped with the release. It used to be generated inside your browser on every page load by the Tailwind Play CDN — a 407 KB compiler that re-ran on every DOM change. On the Import screen this cut DOMContentLoaded from 1250 ms to 277 ms and JavaScript CPU time from 251 ms to 14 ms, measured on the same machine.
• About 440 KB of admin JavaScript (Import, help panel, support bubble, marketplace) now loads from cacheable files instead of being inlined into every page, so your browser downloads and parses it once instead of on every navigation. The Import page's HTML dropped from 664 KB to 415 KB.
• Country flags are served from your own install — the admin no longer loads anything from a third-party CDN.
• Catalogue thumbnails are cached on your server. Opening the Import screen used to re-download every thumbnail through PHP on every visit.
• Admin background requests no longer hold the PHP session lock while they contact tubepress.io. One slow call used to block every other admin request behind it — most visibly, the admin froze while an import job was running.
• Catalogue pricing refreshes in the background instead of delaying the Import page.
• The video preview player is downloaded only when you open a preview.
• The updater now installs new admin asset folders, which previously only arrived with a fresh install.

• The Top Up panel now shows what each pack really gives you: the credits you pay for, the credits offered on top, and the bonus percentage.
• You can now enter any amount instead of picking a pack. The free credits are applied automatically on the same scale as the packs, so an amount matching a pack's price gives you exactly what that pack gives.
• The credits are recalculated as you type, and the order summary tells you how many of them are free before you pay.

• The Player, Homepage, Categories and Performers tabs in Admin → Advertising were empty on new installs because their ad zones were never created. They are now, so VAST pre-roll / mid-roll / post-roll, the pause ad and the player popunder can be set up again.
• The In-Player Ads zone now appears under the Player tab instead of Watch Page, and the Interstitial, In-Page Push, Before Comments, Between Related Videos and Top of Listings zones are back.
• Existing zones and ad spots are untouched by the update.

• Large 2160p/4K jobs are now watched by their actual encoding progress instead of a fixed time limit, so a video that needs 3, 4 or 6 hours finishes instead of being reset to 0% and re-queued after about two hours.
• A job that has genuinely stopped responding is still recovered just as quickly, and remote conversion servers are covered by the same change.
• Intro/outro assembly and preview-timeline generation now report progress while they run, so long videos are no longer interrupted during those steps.

• Admin → SEO → Indexing now carries a "Minimum items required to index a taxonomy page" setting. Under that number a category, tag, pornstar, channel or album-taxonomy page is still served normally to visitors and keeps every internal link, but it is marked noindex, follow and left out of your sitemap, so search engines spend their crawl budget on your videos and albums instead.
• A page becomes indexable again and returns to the sitemap on its own as soon as it reaches the number. Nothing is stored per page and nothing has to be switched back by hand.
• An option keeps any category, pornstar or channel carrying at least 50 characters of its own description indexable even under the number, because that text is content in its own right. It is read from your default language, so a page can never be indexable in one language and withheld in another. Tags have no description field and always follow the number.
• Before you save, the panel shows live from your own database how many pages each taxonomy type would hide.
• The setting ships switched off, so an install that updates and changes nothing renders and generates exactly what it did before.
• Also fixed: on an install whose theme does not provide the SEO page, the "Discourage search engines from indexing this site" box in Settings → Branding always displayed as unticked whatever the stored value was, so saving that page could silently make a hidden site visible to search engines again.

• In a non-default language, reaching an entity by its base (untranslated) slug returned 200 with a canonical pointing at the translated URL. That alias now returns 301 to the canonical translated URL, so the duplicate consolidates instead of competing.
• Applies to /video, /category, /tag, /pornstar, /channel, /album and the four album taxonomy routes; the query string (pagination, sort) is preserved.
• Matches the behaviour the /videos/... listing routes already had. The default language, pages with no translated slug, and /embed/ URLs are unchanged.

• A language home page now emits the same slashless URL in its hreflang tags, og:url and language-switcher links as in its canonical (https://example.com/pl, not https://example.com/pl/). The self-referencing hreflang no longer contradicts the canonical.
• The sitemap advertises the same slashless language roots, so Search Console stops reporting them as alternates pointing to a different canonical.
• The default-language root keeps its bare slash (https://example.com/), and secondary video-type roots (/gay, /hentai) follow the same rule.

• On servers where the database connection collation differs from the character set default, the ad scheduling filter compared dates as text and the database refused the comparison (error 1267 Illegal mix of collations), which returned Something went wrong on every public page, even with no ad spots configured.
• Ad scheduling now compares real date and time values, so start and end windows behave exactly as before on every server.

• Daily view totals are recorded as views are counted, so Today, Avg/day, Peak, 30d total and the 30-day chart no longer drop during the day.
• The view de-duplication log keeps its short retention, so the fix adds no meaningful database growth.
• The 30-day history builds forward from this update; days before it show no data.

• The worker's GPU command dropped the output pixel format, so a source that was not already 8-bit 4:2:0 (10-bit HEVC, 4:2:2 footage) was handed to the GPU encoder in a format it cannot accept and the encode was refused.
• When a GPU encode was refused the worker retried on CPU, produced a valid file, then still reported the job as failed and discarded it. Those jobs now complete.
• The CPU retry now uses the quality settings configured for that format instead of a fixed fallback, so the fallback rendition matches the one you set up.
• The worker console and the job error message now carry FFmpeg's own reason when a GPU encode is refused.
• After updating, re-download transcode-worker.php from Settings > Transcoding > Servers and restart your worker: that script runs on your own conversion server, so a CMS update alone does not update it.

• The transcode worker now correctly detects NVIDIA NVENC, AMD AMF, Intel QSV and Apple VideoToolbox instead of silently encoding everything on the CPU: the test clip it used to check the encoder was smaller than the minimum frame size NVENC accepts, so the check failed even on a perfectly working GPU.
• A working GPU is no longer rejected just because FFmpeg printed a harmless warning while that check ran.
• When an encoder genuinely is unavailable, the worker now prints FFmpeg's own reason for it instead of a bare "not functional".
• After updating, re-download transcode-worker.php from Settings → Transcoding → Servers and restart your worker so it picks up this fix.

• AI Translate now returns the credits for anything a translation job was charged for but never delivered — a job that fails, that you stop, or that the AI service could not complete refunds what it did not produce, on its own.
• Translations you did receive are never refunded, each charge is refunded once and never more than it cost, and running Retry failed after a refund is charged again.
• The job summary now shows how much went back next to how much was used.
• Includes the 1.1.7 related-videos fix.

• The related-videos block on the watch page scored candidates by joining every published video and discarding the non-matching ones afterwards, so its cost grew with the size of the library and forced an on-disk temporary table on every view. Busy sites with large libraries could saturate MySQL from watch-page traffic alone.
• Scores now come from the category and tag indexes, and only the videos actually displayed are loaded. Measured on a 100,000-video library: 1,150 ms to 90 ms per watch page.
• The related-galleries block on album pages had the same defect and is fixed the same way.
• Ranking, ordering and the number of items shown are unchanged, and there is no database migration.

• An import whose AI title or description step kept failing retried forever and never produced the video, leaving the job stuck between downloading and rewriting. The AI pass now stops after its retries, is marked Failed with the error kept on the job, and the video is imported with its original title.
• Fixed the built-in AI prompts used when the prompt service cannot be reached: they asked for plain text while the importer expected tagged output, so every attempt failed.
• Server Health: "Pseudo-cron (last run)" always reported Never, even on sites whose background tasks were running normally. It now reports the real last run.

• The catalogue import panel opens on "Keep originals only": videos are imported as they are, with no conversion, no extra disk use and nothing queued for transcoding.
• "Stream smoothly" and "Shrink to save space" are unchanged and remain one click away.
• The "Recommended" badge has been removed, so the panel no longer pushes one outcome over the one it preselects.

• When several tags translate to the same name in your language, that name is now shown once — on the video page, on album pages and in the Tags listing.
• Nothing is merged behind the scenes: every tag keeps its own id, its own localized address and its own videos, and each one is still reachable at its own URL.
• The tag kept on screen is the one with the most videos, so the link always points to the fullest page.

• The New Video page now shows a live progress bar with the percentage, the uploaded size against the total, the current upload speed and the estimated time remaining.
• The upload reports the stage it has reached — Uploading, then Processing while the server saves the file, then Completed.
• An upload in progress can be cancelled, and the page warns you before you navigate away from one.
• A file larger than the server accepts is refused straight away, showing both sizes, instead of failing after a long upload.

• Catalogue video downloads are no longer cut off after 10 minutes. A transfer is now only abandoned when it genuinely stalls, so large files can take as long as they need.
• An interrupted download resumes from the bytes already received instead of starting over, so a brief network problem no longer wastes the whole transfer.
• Videos previously marked as failed can be requeued with "Retry all failed" in the Download Queue after updating.

• Max URLs per file (SEO -> Sitemap) works again. In 1.0.99 the field had no effect; it is now applied as an extra cap on top of Google's own limits, so it can only make files smaller.
• The Categories / Tags / Pornstars / Channels / Albums index pages added in 1.0.99 now respect the matching checkboxes. Unchecking a type removes both its sitemap file and its index page; the home page follows the Pages checkbox.
• A content type set to noindex (SEO -> Indexing) is no longer listed in the sitemap. Submitting a page you have asked Google not to index is reported as an error in Search Console. The Categories/Tags/Pornstars/Channels index pages stay listed, because the noindex option only applies to the individual pages - Albums is the exception, where the option covers the index page too.
• Turning on "Discourage search engines" now also empties the sitemaps, not just robots.txt.

Themes (simply 1.0.25, hentai 1.0.12).

• SEO -> Robots showed an example robots.txt that was out of date: it still blocked /embed/ and paginated pages, which 1.0.99 deliberately stopped blocking. Copying it into the custom box would have silently re-blocked the embed player Google needs to crawl in order to index your videos. The example now always matches what your site actually serves. Themes are not updated by a core update - install these from Admin -> Themes to get the corrected example.

• Sitemap files can no longer exceed Google's limits (50,000 URLs / 50 MB uncompressed). On a site with many tags and several languages enabled, the tag sitemap could grow past 50 MB and be rejected by Google in full; the generator now measures what it writes and splits automatically.
• Languages that have no translated slug for an item no longer produce broken URLs in the sitemap (previously these were emitted with an empty slug and also poisoned the hreflang links).
• Each sitemap file now reports its own accurate last-modified date instead of one shared date for the whole content type.
• New sitemap-hubs.xml: the Categories, Tags, Pornstars, Channels and Albums index pages, the video listing pages (New, Top rated, Most viewed, Most favorited) and the home page — in every enabled language. None of these were listed before.
• Video entries are now correct on installs using remote storage or a CDN: thumbnails and video file URLs were malformed or missing, which made those entries invalid for Google Video.
• robots.txt no longer blocks /embed/ — Google must be able to crawl the embed player to index a video. The player page itself stays noindex.
• robots.txt now also protects the login, register, profile, search and account pages in every language (only the default language was covered), and no longer blocks paginated pages.
• Sitemap files are no longer sent gzip-encoded to clients that did not ask for it.
• On large libraries, sitemap generation is now spread over several background runs instead of doing everything in one request.

Import → Catalogue — galleries.

• Galleries you have already imported are now moved to the END of the listing instead of filling the first pages, which is how the video catalogue already behaved. Nothing is hidden: the totals and page count stay exact and every gallery remains reachable.

• Import → Catalogue no longer discards galleries and videos you have already imported after a page has loaded, so pages are never left empty or half full.
• Items already in your library stay visible, greyed out and marked IMPORTED, and cannot be selected by mistake.
• The result count and the number of pages now match exactly what the browser shows.

• Album, category, tag, performer and channel sitemaps are now split into several files when they would grow past Google's size limit, and every part is listed in the sitemap index.
• The split now accounts for hreflang alternates, so multilingual sites no longer produce oversized sitemap files that Search Console rejects.
• Existing sitemap URLs keep working — an entity that still fits in a single file keeps its current filename.

• The queue counters, the active-jobs pill and the Queue tab badge now refresh on their own instead of staying frozen until you reload the page.
• Auto-refresh also starts when you open the Queue while it is empty, so newly queued videos appear without a manual refresh.
• Refresh failures are now reported in the browser console instead of being silently ignored.

• Videos with an intro or outro attached are now joined using the same frame rate, time base and audio settings as the video itself, so playback no longer stalls or buffers once the intro ends.
• The finished file is checked before it replaces the original: if its timeline or stream durations come out malformed, the original video is kept instead.

• Fixes catalogue gallery purchases that stayed at pending forever, with no attempts and no error, on servers where a background worker process cannot be started. Galleries now use the same exec-less worker the video queue has, so the queue drains without any manual step, cron or heartbeat.
• The importer now checks that a worker really started instead of assuming it did, and falls back automatically when it did not.
• PHP command-line binaries installed by cPanel and CloudLinux are now detected, so servers using those layouts can start workers normally.

• The Slug field on videos, categories, tags, pornstars, channels and albums is now saved exactly as you type it — and a page you simply re-save keeps its URL instead of silently changing it. Leave the field empty and it is still generated from the title, as before.
• Load more under the recommended videos now works on every theme, not only Simply.
• Pages no longer return a server error when a crawler adds a malformed parameter to the URL.
• AI translation jobs no longer stop with an internal error when they run in the background.

• Fixes a defect where selecting a catalogue gallery whose import had not finished, or had failed, charged your credits a second time. The purchase check now recognises a gallery that is already paid for and waiting in the import queue, and retrying a failed gallery import costs nothing.
• Deleting an ad spot reported success even when the delete was rejected, for example after a session or security token had expired. The real result is now shown instead.

• Fixes a regression in 1.0.88 where a purchased catalogue download could stay at pending with no attempts, no error and no worker running, on servers where the worker slot file could not be created. Downloads start normally again.
• If no download worker can be started at all, the queue now falls back to the exec-less workers instead of stalling.
• A worker slot whose recorded process id had been reused by an unrelated process no longer blocks the queue permanently.

• Video sitemaps now include hreflang alternate links and one entry per language when "Include hreflang alternates" is enabled, matching the categories, tags, performers, channels, albums and pages sitemaps.
• A catalogue download could stay in the queue forever, with no attempts and no error recorded, on servers where the site timezone and the database timezone differ. Downloads now retry on schedule, and any download already stuck is released when you update.
• Several catalogue workers could start for the same queue slot when downloads were triggered from more than one place at once. Only one worker now starts per slot.

• Importing got slower the more you had already imported: attaching each video to its tags and categories re-counted those tags and categories across the whole library, once per tag, for every row. A feed with 17 tags per video triggered around 21 full recounts per import.
• Counts are now adjusted by the change instead of recalculated. On a 400,000-video library with a 17-tag feed this took one row from 164 ms to 4.5 ms, and the cost no longer grows with the size of your library.

• Admin → Updates offered marketplace themes and plugins that were never installed on the site, and automatic updates would then install them without being asked. Only extensions present on your site are listed now.
• Updating an extension can no longer create one: an update for something you do not have is refused. Installing a theme or plugin from the marketplace still works exactly as before.

• The bar above the catalogue results hid both of its buttons whenever you were browsing galleries, so bulk selection was only ever available for videos. Both work for galleries now.
• Select page takes the whole page and leaves out anything you have already imported.
• Download all appears once you narrow the galleries by source, category, performer, channel, tag or image count, and tells you how many it will take. As with videos it stays hidden on the unfiltered catalogue, so a single click can never buy everything.

• A translation batch that could not finish inside one worker pass was charged in full, sent only in part, and then counted as done — the job moved on and never came back to those videos, which is how a run could report Completed with nothing failed while most translations were missing. A batch now keeps its place and resumes until it is genuinely finished.
• Resuming a batch can no longer be charged twice. The charge is now tied to the exact items it covers, and each job records what it has already paid for, so retrying, resuming or recovering from an interruption costs nothing extra.
• The credits shown against a job now match what was actually taken, and the translated counter counts videos rather than passes. A job reports Completed only when every item really is translated; anything that failed is counted as failed.
• Large libraries: the home page now issues 12 queries instead of 60, and pages that were dominated by counting videos no longer are. Measured on a one-million-video database with no caching: 498 ms down to 11 ms. Category and tag pages get the same treatment. Nothing is cached and no total is approximated on a normal-sized site.

• A gallery you imported stayed in the catalogue looking like one you had never bought. It now appears greyed out with an IMPORTED badge, cannot be selected, and is skipped by Select all — the same treatment the video catalogue already gave imported videos.
• Your credits were never at risk: the import screen already dropped galleries whose album exists before charging, the import re-checked, and the database enforced it. The protection was there; the indication was not.
• Re-buying a gallery after deleting its album locally still works and is still charged, as intended.

• The one-off repair that removes English written over your translations now claims its run atomically and works in batches. On a 29-language site it used to issue one statement per string per language — 1601 of them inside a single page view, with nothing stopping a second visitor starting the same work. The same repair is now 58 statements and finishes in well under a tenth of a second.
• A footer configuration in an unexpected shape can no longer take the front page down. Values are checked before use, so a partially written or hand-edited footer setting renders what it can instead of raising an error.
• Catalogue import: a sidebar section you collapse stays collapsed. It was springing back open every time a filter was cleared or a chip removed.
• Mobile menu: the language list can no longer run past the bottom of the drawer on a short screen — that area now scrolls.

• Admin → Languages → Edit translations showed the English text, not your translation, for every string that comes from your theme. Saving the page then stored that English over the translation for good — on a 29-language site that was 56 strings per language, including the whole Albums interface and headings such as TRENDING, WATCH IT AGAIN, More and Powered by. The editor now shows what your site shows, and saving an untouched form changes nothing.
• Installing this release repairs the entries that were already overwritten. Translations you deliberately customised are kept, including a string you chose to leave in English.
• Core updates now install the translation files. They have always been inside the update package but were never applied, so a translation fix or a newly translated string could only ever reach a brand-new install.
• Footer badges and column headings follow the site language again (18+ Only, Free Content, HD Videos, Navigation, Pages, About), and the per-language text saved for a footer logo description is now used. Your own wording is untouched.
• Catalogue import: every sidebar heading now shows how many values are behind it, and the galleries view opens on Categories instead of a column of empty headings.

• Every listing row — categories, tags, pornstars, channels (videos and albums), plus videos, albums and pages — now has a small language button beside Edit. It opens the same AI Translate window scoped to that one item, with the same language choice, field choice and price shown before anything is charged.
• On the page editor, each language tab has its own button: "Translate to FR" translates that language alone, and the default tab opens the full picker for that page.
• "Discourage search engines from indexing this site" now sits at the top of SEO → Indexing, above the per-page-type list, instead of on the Advanced tab. While it is on, the per-type list is dimmed and explains that the site-wide switch is what applies.

• "Discourage search engines from indexing this site" moved to SEO → Advanced in 1.0.70, but themes are updated on your own schedule, so an install running an older theme could end up with the setting nowhere at all. Settings now shows it again automatically whenever your theme does not yet provide it, and hides it the moment the theme does.
• Saving Settings can no longer switch that setting back on or off behind your back.

• The "AI Translate" button is now on all eleven content sections — Categories, Tags, Pornstars and Channels (for videos and for albums), plus Videos, Albums and Pages. Pick your target languages one by one or all at once, choose which fields to translate, see the exact cost before you start, and run it in the background with pause, resume, stop and retry.
• You are now charged as the run goes, only for what actually gets translated: anything already translated is skipped free of charge, and stopping a run stops the billing. A run started with a short balance tells you how far it will get and pauses cleanly when it runs out.
• Pornstar and channel NAMES are never translated — only their biography or description. Proper names are left exactly as you wrote them.
• Your site name, site description and homepage title / meta description can now differ per language. Set the default in Settings, then translate them in Languages → Edit translations → Branding; anything you leave empty falls back to the default. The translated value is used in the page title, meta description, Open Graph, Twitter card and WebSite structured data.
• Pages that do not exist now return a real 404 together with "noindex, follow" and a matching X-Robots-Tag, so a missing URL can never be indexed. Sections you switch off answer 410 Gone with the same protection.
• "Discourage search engines from indexing this site" has moved to SEO → Advanced, next to the other indexing controls, and saving Settings no longer switches it back off.

• Album Categories and Album Tags now offer the same AI translation as videos: "Translate All" in the page header, "Translate" on a selected batch, and the same price of 0.5 credits per item covering every language you have enabled.
• "Skip already translated" only spends credits on entities that are still missing a language, and "Auto-translate new ... as they are added" keeps newly created album categories and tags translated on their own.
• Album categories reuse the same shared translation dictionary as video categories, so a term you already translated on the video side costs you nothing on the album side.
• Album pornstars and album channels are deliberately not translated: those are proper names and are left exactly as you entered them.

• Ad-network banners (728x90 leaderboards, hero billboards, in-feed cards, sidebar and sticky spots) are now scaled down to fit the screen, so the whole ad stays visible on mobile.
• An ad wider than the screen can no longer widen the page itself: ad slots keep your site's width on every device, and desktop banners still display at their full size.

Large files are now uploaded in 8 MB pieces instead of 128 MB, matching what the AWS command line tool and the official S3 libraries do. Each piece is confirmed within seconds rather than holding a single connection open for minutes, which is far more forgiving of firewalls, proxies and busy storage servers.

A single upload that loses its connection is now retried up to three times before giving up. Previously only multi-part uploads retried, so one dropped connection could lose a preview or a rendition outright. Errors that will not change on a second attempt, such as a rejected key, still fail immediately instead of retrying pointlessly.

When an upload does fail, the message now tells you how much of the file actually left your server, out of how much, how long it took and at what speed. That single line usually identifies the cause on its own - whether the file was sent completely and the storage server then went quiet, or whether the connection was cut part way through. If you contact support about a storage problem, copying that one line is now enough.

Galleries now delete in batches like videos do. Measured on albums of 40 images each: about 600 albums per second, and remote storage is cleaned in one request per thousand files instead of one request per image - deleting 400 galleries went from 16,400 separate storage requests to 17.

Deleting a gallery used to leave its comments, reports, likes, view history and statistics behind for ever, because those rows were never removed. They are now cleaned up, which also stops those tables growing without bound.

Every bulk delete screen - tags, categories, pornstars, channels, their gallery equivalents, comments, pages and users - now deletes in batches instead of row by row, and reports what was really deleted. Previously the confirmation always showed the number you had selected, even if some or all of them had failed, and a large selection could silently stop half way through when the page ran out of time. If that happens now it tells you how many were left so you can finish the job.

Deleting videos in bulk was processing them one at a time, with dozens of database queries per video and, on remote storage, fourteen separate delete requests per video. Videos are now deleted in batches: measured on a 5,000-video library, bulk deletion went from about 13 videos per second to several hundred, and remote storage is cleaned in a single request per batch instead of one per file.

The batch size now tunes itself to your server. There is no setting to adjust: each batch is timed and the next one resized accordingly, so a small shared host takes smaller bites and a powerful server takes larger ones.

Reliability fixes in the same area: - A delete job could report "completed" when a batch had actually failed, leaving videos behind. - With two administrators deleting at once, one progress bar could advance the other's job. - A fast job could stop after its first batch. - Long jobs stopped after ten minutes until an admin page was reopened; they now continue on their own. - Deleted videos left rows behind for ever in the view log, the CTR statistics tables and the homepage pool. These are now cleaned up, which also keeps those tables from growing without bound.

Files over 64 MB are now uploaded in parts instead of a single request. This removes the previous 5 GB per-file limit (a hard limit of the storage protocol, not a setting), and lets very large videos - up to several terabytes - be stored.

It also makes large uploads far more reliable: each part is confirmed as it goes, and if one part fails it is retried on its own instead of restarting the whole file. Upload speed is unchanged.

Large uploads could fail with "Operation too slow" even when the transfer was perfectly healthy. A storage endpoint sitting behind a buffering gateway (nginx and similar) stays silent between the last byte it receives and its reply, for as long as it needs to store the object - several minutes for a large video. The CMS treated that silence as a dead connection and gave up after two minutes. The stall check now only applies while data is still being sent, so the storage server is free to take the time it needs.

Small files were never affected, which is why the storage Test could pass while every video import failed.

• Imports no longer fail with "Failed to upload video.mp4 to storage server" when your S3-compatible endpoint URL includes a port (for example MinIO on :9000).
• Large video uploads to S3 are no longer cut off after 5 minutes and now run to completion as long as data keeps flowing.
• The storage Test button now validates these endpoints correctly, and failed S3 uploads are recorded in the PHP error log with the HTTP status for easier diagnosis.

• The Top Up window now offers the payment methods your TubePress account actually has enabled, instead of stalling on an empty Payment step when card payment is unavailable.
• Choose from more than 50 coins and networks, with a search box and the exact amount to send — tax included — shown before you commit to anything.
• The payment step gives you a QR code, the deposit address and the amount with one-click copy, plus the memo or tag as a required field on the networks that need one.
• Your transfer is tracked live and the credits are added automatically once the network confirms, so you can close the window and come back later.
• Anything that goes wrong is now explained inside the window — coin unavailable, amount below that coin's minimum, service unreachable — instead of failing silently.

• When importing from the catalogue, choosing "Stream smoothly" or "Shrink to save space" now warns you — inline in the option's summary — if no conversion server is set up, since encoding then runs on this server and uses most of its CPU.
• Links to Settings → Transcoding → Servers so you can offload encoding to a dedicated worker.

• Video thumbnails no longer create a hidden video player for each card at page load. The hover preview player is now created the moment you first hover a card — previews look and behave exactly as before, while pages load lighter and use far less CPU, GPU and memory.
• Removed the per-card frosted-glass blur effects (duration badge, play icon) and scoped the blurred sticky header to desktop-class devices — long video grids now scroll smoothly on mobile.
• Bundles Simply theme 1.0.16, which carries these performance fixes.

• Fixed 404 errors on the category, tag and pornstar section pages in languages where the translated URL word is identical for singular and plural (Malay, Indonesian, Vietnamese, Czech, Hungarian, Italian).
• Fixed video pages, likes, comments and recommended-video loading returning 404 in Bulgarian, Indonesian, Italian, Malay, Russian, Serbian, Ukrainian and Vietnamese.

• Catalogue AI translations are now billed per target language: the import dialog shows the per-language price and the exact total for your enabled languages, for both titles and descriptions.
• You can now translate into up to 30 languages per import (video imports were previously capped at 8).
• Translations run in small batches of up to 5 languages per request, with automatic retries for any missing language — large language sets import reliably instead of failing as one giant request.
• Collected translations are saved as they arrive, so an interrupted import resumes without losing finished translations.
• The purchase summary now itemizes every AI option with live prices, including the description-translation line.

• Deleting videos — one by one, or in bulk from the Videos list — is now reliable. Before, removing a video that had any category, tag, performer or channel could silently do nothing.
• Bulk delete now runs straight from your browser with a clear progress bar, so it finishes dependably on every host (no background worker required).

• Imported videos now start downloading immediately and respect your chosen number of parallel downloads, even on brand-new sites with no visitors yet.
• You can now close a ticket (a reply reopens it) or permanently delete one, from a menu in the ticket header.
• Clicking the support chat icon when you have replies now always opens your most recently answered ticket.

• The Import catalogue now loads and switches between Videos/Galleries and Straight/Gay/Hentai near-instantly: pages are cached and prefetched in the background, with a smooth loading skeleton.
• Unread support-reply alerts now stay visible until you actually open the reply — navigating between admin pages no longer clears them — and replies that were already waiting for you light up even on a fresh browser.

• Your open support ticket now stays on screen while you move between admin pages — only the X button closes it, and reply drafts are kept per ticket until you send them.
• When our support team answers you, the red Help Center button in the sidebar now pulses with an unread counter — one click opens the reply directly.
• Unread replies are also highlighted in the ticket list, and indicators refresh automatically while you work.

• New installations now start with a refined out-of-the-box look — colours, dark mode, layout, sorting, video cards, watch page, and the navigation menu (including Albums) — plus a default logo and favicon.
• Photo-album listings and cards now have sensible built-in defaults.
• The catalogue download queue now defaults to 3 parallel downloads.

Albums now have their OWN separate taxonomy — dedicated Categories, Tags, Pornstars and Channels for albums, fully independent of your video taxonomy. Manage them under Admin > Albums (Categories / Tags / Pornstars / Channels), with front-end archive pages (/album-category, /album-tag, /album-pornstar, /album-channel) and configurable SEO patterns. Also bundles important reliability fixes: in-app updates now correctly run database migrations (a prior bug silently skipped them) and self-heal the schema on the next page load; new feature routes are delivered on update; the Studios-to-Channels rename is reconciled automatically; the ad-zone migration is idempotent. After updating, allow one page load for the database to finish applying.

Pair with Simply theme 1.0.5 (album archive templates).

Admin: create and manage albums (multi-image upload, cover selection, per-language translations, bulk actions), with a new Albums entry in the sidebar, a dashboard card + quick action, and an Albums count column in the Categories / Tags / Pornstars / Channels lists.

Front-end (your active theme): an /albums listing and single-gallery pages with a responsive, count-adaptive photo grid, a built-in lightbox, favourites, copy-link, related galleries and previous/next navigation.

Albums reuse your existing categories, tags, pornstars and channels, are fully translatable (Admin > Languages) and SEO-configurable (Admin > SEO): title/description patterns, a noindex toggle, the XML sitemap and ImageGallery structured data. Site search now returns matching albums too. Designed to scale to large libraries.

Also includes an important schema fix: the Studios-to-Channels rename is now reconciled automatically on install and update, so fresh installs and upgrades correctly create the channels tables (resolves 'Table channels does not exist' 500 errors on the video editor and imports). The migration is idempotent and preserves all existing data.

• TubePress can now be installed non-interactively from the command line with "php bin/install.php" — it provisions the database, admin account and settings in one step, so the CMS can be deployed by a script or an AI agent with no browser.
• The browser-based setup wizard is unchanged; both paths share the same install logic and produce an identical site.

• When something fails while you're signed in to the admin, the panel now shows the exact error — what went wrong and where — with a reference you can copy, instead of a vague "something went wrong" page.
• Background and bulk actions (such as importing) report the underlying error too, so a failed import is never silent.
• Visitors to your public site still see a neutral page with no technical details exposed.

• Paid plugins and themes include one year of updates with every purchase, and your installed version always keeps working — even after that window ends.
• When your update window has ended, the Updates page now shows the new version with a one-tap "Renew to update" link instead of a confusing download error.
• Fewer false "licence problem" warnings (briefly-flaky network checks are now ignored).

• The CMS now serves its own theme, admin and installer styling when the web server doesn't, so installs look correct on Apache, nginx or the PHP built-in server with no extra configuration — and existing sites get the fix on update.
• Local development now works over plain HTTP — run: php -S localhost:8000 -t public public/router.php and open http://localhost:8000 (no HTTPS required).
• Corrected the installer's theme/template symlink target and a fingerprint cookie that did not persist on plain-HTTP (localhost) installs.

• The CMS now serves its own theme, admin and installer styling when the web server doesn't, so a fresh install looks correct on Apache, nginx or the PHP built-in server with no extra configuration.
• Local development now works over plain HTTP — run: php -S localhost:8000 -t public public/router.php and open http://localhost:8000 (no HTTPS required).
• Corrected the installer's theme/template symlink target and a fingerprint cookie that did not persist on plain-HTTP (localhost) installs.

• The header storage gauge now measures the disk where TubePress is installed — its code, uploads and media — instead of the server's OS root partition, so it matches the figure shown on Settings → Storage and the dashboard.
• Local storage usage is now read live from the filesystem, so full-disk warnings and automatic storage rotation react immediately instead of waiting for the periodic health check.

• The Updates page now verifies the version installed on your site before offering or applying anything, so an update you've already installed is never shown or applied again.
• Update History & Rollback is now paginated, keeping a long list of restore points easy to browse.
• Applying an update now starts with a single click — the extra confirmation prompt has been removed.

• A new "Automatic updates" article in the Help Center explains the Settings → General toggle: it auto-applies signed CMS core and free plugin updates, backs each one up and rolls back automatically if it fails, keeps themes and paid plugins manual, and is off by default.
• The guide is also surfaced as contextual help on the Updates page.

• Setup installs into a database your hosting panel pre-created even when the database user cannot create new databases (the usual cPanel/Plesk case), and shows a clear message if it genuinely cannot.
• The database host field now accepts a port or socket (e.g. db.host:3306), so managed and remote MySQL connect without extra steps.
• Creating the admin account no longer requires the Argon2 extension — it uses bcrypt automatically when Argon2 is missing, so installation succeeds on any PHP 8.2+ server.
• Setup detects HTTPS correctly behind Cloudflare and other reverse proxies, checks that PHP sessions are writable, and creates its writable folders automatically.