Ctrl K
ComunidadGuías…

Ayuda y problemas de innoshop

Pregunta a la comunidad o invita a KiBot con contexto del repositorio.

Publicar un problema

No publiques contraseñas, tokens ni claves privadas. HostingByte aplica una redacción básica de secretos evidentes antes de guardar el texto.

Problemas en HostingByte

Todavía no hay problemas publicados.

Issues abiertas upstream

#385 Security: page template field is compiled through Blade in v0.9.2 — full detail now in a private report · 0 comentarios#384 SettingRepo::clearConfigCache() promises a reload but leaves config('inno') null for the rest of the request — every setting() after a write returns null · 0 comentarios#383 Order detail page prints the raw translation key `front/order.confirm` on the confirm button (missing __() call) · 0 comentarios#382 Plugin front-end API routes use the stateless `api` group, so auth('customer') is always null — the `front_api` group defined in bootstrap/app.php is never used · 0 comentarios#381 Every plugin toggle loses its description text: bool.blade.php passes it as a slot, but the switch-radio component never renders $slot · 0 comentarios#380 Creating a shipment from the panel never advances the order status — orders stay "paid" forever and customers get no "confirm receipt" button · 0 comentarios#379 Checkout returns 500 when a payment plugin's `available` setting is stored as a JSON string: getBillingMethods() calls in_array() without normalising the type · 0 comentarios#378 Panel form rows overflow their container by 12px: .row gutter inside .form-row without negative-margin compensation · 0 comentarios#377 Plugin settings page renders the plugin name twice (page header title + in-card heading) · 0 comentarios#376 Panel form bottom buttons: hardcoded Chinese labels, and the Back button does nothing after saving plugin settings · 0 comentarios#375 EventTrackingService writes unbounded URLs into varchar(1000) columns — analytics events are silently lost with SQLSTATE 22001 · 0 comentarios#374 /sitemap.xml returns 500 on any multi-language store: SitemapService hardcodes the non-localised route name front.home.index · 0 comentarios#373 Storefront 'view shipment traces' calls the panel API and always returns 401 for customers · 0 comentarios#372 SKU code uniqueness counts soft-deleted products — re-using a SKU code after deleting a product always fails · 0 comentarios#371 Panel account page returns 500: front_root_route('home.index') points to a route that does not exist on multi-language sites · 0 comentarios