Fix: Züchter-Seiten page-container-wide (1040px) statt 680px — Wurfbörse, Zuchtkartei, Würfe, Läufigkeit (SW by-v907)

This commit is contained in:
rene 2026-05-13 19:31:01 +02:00
parent f35a0efbaf
commit cf1ed0fdbc
4 changed files with 12 additions and 12 deletions

View file

@ -406,7 +406,7 @@ async def serve_media(path: str, request: _Request):
raise _HE(404, "Nicht gefunden.") raise _HE(404, "Nicht gefunden.")
return _media_response(filepath) return _media_response(filepath)
APP_VER = "906" # muss mit APP_VER in app.js übereinstimmen APP_VER = "907" # muss mit APP_VER in app.js übereinstimmen
@app.get("/.well-known/assetlinks.json") @app.get("/.well-known/assetlinks.json")
async def assetlinks(): async def assetlinks():

View file

@ -430,21 +430,21 @@
</section> </section>
<section class="page" id="page-zuchthunde"> <section class="page" id="page-zuchthunde">
<div class="page-body page-container"></div> <div class="page-body page-container-wide"></div>
</section> </section>
<section class="page" id="page-zucht-profil"> <section class="page" id="page-zucht-profil">
<div class="page-body page-container"></div> <div class="page-body page-container-wide"></div>
</section> </section>
<section class="page" id="page-litters"> <section class="page" id="page-litters">
<div class="page-body page-container"></div> <div class="page-body page-container-wide"></div>
</section> </section>
<section class="page" id="page-laeufi"> <section class="page" id="page-laeufi">
<div class="page-body page-container"></div> <div class="page-body page-container-wide"></div>
</section> </section>
<section class="page" id="page-wurfboerse"> <section class="page" id="page-wurfboerse">
<div class="page-body page-container"></div> <div class="page-body page-container-wide"></div>
</section> </section>
<section class="page" id="page-breeder"> <section class="page" id="page-breeder">
@ -591,10 +591,10 @@
<div id="modal-container"></div> <div id="modal-container"></div>
<!-- JS: Reihenfolge ist wichtig — erst Basis, dann Features --> <!-- JS: Reihenfolge ist wichtig — erst Basis, dann Features -->
<script src="/js/api.js?v=906"></script> <script src="/js/api.js?v=907"></script>
<script src="/js/ui.js?v=906"></script> <script src="/js/ui.js?v=907"></script>
<script src="/js/app.js?v=906"></script> <script src="/js/app.js?v=907"></script>
<script src="/js/worlds.js?v=906"></script> <script src="/js/worlds.js?v=907"></script>
<!-- Feature-Seiten werden lazy geladen --> <!-- Feature-Seiten werden lazy geladen -->

View file

@ -3,7 +3,7 @@
Router, State-Management, Navigation, Initialisierung. Router, State-Management, Navigation, Initialisierung.
============================================================ */ ============================================================ */
const APP_VER = '906'; // ← bei jedem Deploy mit Frontend-Änderungen erhöhen const APP_VER = '907'; // ← bei jedem Deploy mit Frontend-Änderungen erhöhen
const APP_VERSION = '1.5.1'; // ← semantische Version, wird bei make release gesetzt const APP_VERSION = '1.5.1'; // ← semantische Version, wird bei make release gesetzt
const IS_STAGING = location.hostname === 'staging.banyaro.app'; const IS_STAGING = location.hostname === 'staging.banyaro.app';
// Cache-Bust-Parameter nach Update-Reload sofort entfernen // Cache-Bust-Parameter nach Update-Reload sofort entfernen

View file

@ -3,7 +3,7 @@
Offline-Cache + Push Notifications + Tile-Cache Offline-Cache + Push Notifications + Tile-Cache
============================================================ */ ============================================================ */
const CACHE_VERSION = 'by-v906'; const CACHE_VERSION = 'by-v907';
const CACHE_STATIC = `${CACHE_VERSION}-static`; const CACHE_STATIC = `${CACHE_VERSION}-static`;
const CACHE_TILES = 'ban-yaro-tiles-v1'; // bleibt über SW-Updates erhalten const CACHE_TILES = 'ban-yaro-tiles-v1'; // bleibt über SW-Updates erhalten
const CACHE_API = 'ban-yaro-api-v1'; // API-Response-Cache const CACHE_API = 'ban-yaro-api-v1'; // API-Response-Cache