// Represents: GET /helpcategories · HelpCategoriesController; GET /helppages · HelpPagesController — see docs/ISYSTEM_REFERENCE.md §Batch 4 "Help categories + pages" /* CMS ▾ → Help categories + Help pages — the two screens behind the site's Help/FAQ footer. Split out of the legacy CMS bundle src/pages/HostCmsBanners.jsx, which carried thin HostCmsHelpCategories / HostCmsHelpPages stubs alongside Slideshow, Blogs and Blog categories. That bundle was being split in parallel and is now src/pages/HostCmsBannersNew.jsx, which no longer defines either component — so these are the only definitions left. index.html still loads this file AFTER it, so the ordering holds either way. Neither bundle was edited here. Real screens ----------------------------------------------------------------------------------------- Help categories · GET /helpcategories/ (unnamed route, routes/admin.php:1156-1158) → HelpCategoriesController::index L14. Siblings: getCategoriesTable L51 (legacy DataTables JSON, orphaned — no current view calls it), helpcategoryForm L164 (GET /helpcategories/form), saveHelpcategory L182 (POST /helpcategories/saveCategory?id=), delete L241 (GET /helpcategories/delete/{id}/, routes/admin.php:1602-1604). Views: admin/helpcategories/index.blade.php + _paybo-head + modals/helpcategory.blade.php (generaModalGestione → admin/utils/modal.blade.php) + forms/helpcategory.blade.php. Model App\Models\HelpCategory → table `helpcategories` (unix addedTime/updateTime). Help pages · GET /helppages/ (unnamed, routes/admin.php:1174-1176) → HelpPagesController::index L15. Siblings: getPagesTable L60 (orphaned DataTables JSON), helppageForm L265, saveHelppage L283 (POST /helppages/savePage?id=), delete L366 (GET /helppages/delete/{id}/, routes/admin.php:1605-1607). Views: admin/helppages/index.blade.php + _paybo-head + modals/helppage.blade.php + forms/helppage.blade.php (TinyMCE 5.0.16 from cdnjs). Model App\Models\HelpPage → table `helppages`. Frontend consumer: ::getHelpPages L380. Three facts drive this UI ----------------------------------------------------------------------------------------- 1. GLOBAL DATA. Neither table has a `skinid` column, so one help tree is shared by every skin. Per-skin values reach the text through PLACEHOLDER TAGS substituted at frontend render time (helpPagesTags(), HelpPagesController L162-236) — which is why the tag legend is not decoration but the only way an operator knows what can be personalised. 2. FOOTER VISIBILITY IS CATEGORY-LEVEL. `helppages` has NO status column at all; getHelpPages() (L391) selects categories with show_online = 1 AND type IN ('link','contacts'), ordered by helpcategories.priority DESC (the unqualified `priority` in that query resolves to the CATEGORY, since helppages has no priority column). 3. …and `type` is NOT editable in the admin form, so every category created through this screen is stored with type '' and can never appear in a footer. See the divergence below. Known-bug / trap policy (CLAUDE.md "Build policies") ----------------------------------------------------------------------------------------- - TRAP — non-editable `type` → permanently empty footers (reference note (3) on Help categories). DIVERGENCE: the category form here EXPOSES `type` with the two values the frontend actually consumes ('link' / 'contacts'), and the list flags every category that is marked Visible but still blocked by an empty type. The real form omits the field entirely. // UNCLEAR (reference records it too): whether production sets `type` by hand in the DB or whether a UI for it was removed. The seed below assumes by hand — 4 of 15 categories carry a value. - BUG — the placeholder-tag legend's captions are shifted in the legacy markup (HelpPagesController L182-192): [dominio-skin] is captioned "Email info", [email-info] "Email documenti", [email-documenti] "Dominio skin". Evident intent implemented: each tag is captioned with its own meaning (HHP_TAGS below). // - MISMATCH — `name_pt` on a help page is marked required by the form (obbligatorio()) but saveHelppage never validates it (L310). The form's own declaration is treated as the intent: required here, with the gap disclosed in the field hint. // - Faithfully reproduced, NOT "fixed": Search matches `name` OR `name_it` only on both screens (name_pt / name_es are never searched). The reference states this as behaviour, not as a bug, so it is implemented as-is and disclosed in the filter's tip. // - Delete is a CSRF-unprotected GET on both screens, and category delete does NOT cascade — HelpCategoriesController::delete L241-252 removes the row only, leaving its help pages with a dangling `category` id. Reproduced honestly: the delete dialog counts the pages that will be orphaned, and those pages then render "—" in the Category column of the Help pages screen. // Deliberate omissions (present in the reference, intentionally not rendered) ----------------------------------------------------------------------------------------- - stati() (0 Disabled / 1 Active, HelpCategoriesController L40 / HelpPagesController L49) and tipologieHelpcategories() / tipologieHelpPages() ('default' / 'slick') are defined but never used on these screens — no status column, no default/slick picker. - No sortable columns: both lists are a fixed ORDER BY id DESC. The legacy get*Table endpoints supported sorting, but they are dead code, so no sort affordance is offered. - No export (neither screen has one), no bulk actions (n/a), no KPI strip — the only total the real page shows is the filter-hero "Results" card, which is the HrsFilters resultLabel here. - `name_pt` is NOT a column on the Help pages list (it exists in the DB and in the form only); `addedByUser` / `updatedByUser` / `name_generico` are never exposed. - A third table `helpsubcategories` (App\Models\HelpSubcategory) has a migration but no route, controller or UI — dormant, so nothing here references it. Label policy: `backend.search`, `backend.results`, `backend.apply`, `backend.no_records`, `backend.showing`, `backend.prev`, `backend.next`, `backend.delete` are all missing from public/default-lang/en/backend.php and render as raw keys on the real screen; operator-facing English is written here and marked with a "label inferred" JSX comment. */ const { useState: hhpUseState, useMemo: hhpUseMemo, useRef: hhpUseRef } = React; /* The FNV-1a hash and the mulberry32 it seeded are GONE, not marked as exempt. Unlike the FAQ and Blogs screens — which still hash a stored path to pick a colour for an image placeholder — nothing on this screen has a presentational use for either. They existed only to generate thirty-seven sport-rules pages and their bodies, so they leave with the seed data. */ /* paginate(25) on both controllers (categories L35, pages L42). Server-rendered Prev/Next — the page size is not operator-selectable, so HrsPager gets no onPageSize. */ const HHP_PAGE_SIZE = 25; /* The four languages this feature stores. Categories have EN/IT/PT names only — there is no ES name at category level (reference note (5)); pages have all four names and all four bodies. */ const HHP_LANGS = [ { id: "en", label: "EN", full: "English", nameCol: "name", bodyCol: "content" }, { id: "it", label: "IT", full: "Italiano", nameCol: "name_it", bodyCol: "content_it" }, { id: "pt", label: "PT", full: "Português", nameCol: "name_pt", bodyCol: "content_pt" }, { id: "es", label: "ES", full: "Español", nameCol: "name_es", bodyCol: "content_es" }, ]; /* The only two `type` values getHelpPages() (HelpPagesController L391) accepts. The legacy tipologieHelpcategories() enum ('default' / 'slick') is NOT what the footer reads. */ const HHP_TYPE_OPTIONS = [ { value: "", label: "— not set" }, { value: "link", label: "link" }, { value: "contacts", label: "contacts" }, ]; /* ------------------------------------------------------------------ * * Placeholder tags — helpPagesTags(), HelpPagesController L162-236. * Captions are the corrected meanings (see the swapped-caption bug at * the top of this file); the Italian originals are label-inferred into * operator English. * ------------------------------------------------------------------ */ const HHP_TAGS = [ { tag: "[nome-skin]", cap: "Skin name" }, { tag: "[nome-societa]", cap: "Company name" }, { tag: "[email-assistenza]", cap: "Support email" }, { tag: "[dominio-skin]", cap: "Skin domain", fixed: "captioned “Email info” in the legacy legend" }, { tag: "[email-info]", cap: "Info email", fixed: "captioned “Email documenti” in the legacy legend" }, { tag: "[email-documenti]", cap: "Documents email", fixed: "captioned “Dominio skin” in the legacy legend" }, { tag: "[sede-legale]", cap: "Registered office" }, { tag: "[numero-licenza]", cap: "Licence number" }, { tag: "[responsabile]", cap: "Responsible person" }, { tag: "[indirizzo-responsabile]", cap: "Responsible person's address" }, { tag: "[company-number]", cap: "Company number" }, { tag: "[payment-processor]", cap: "Payment processor" }, { tag: "[regolamento-licenza]", cap: "Licence regulation" }, ]; /* helpPagesTags() also appends one dynamic entry per configured skin field. The pattern is shown rather than invented keys, because which fields exist is per-installation. */ const HHP_DYNAMIC_TAG = "[field-]"; const HHP_TAG_RE = new RegExp(`(${HHP_TAGS.map(t => t.tag.replace(/[[\]]/g, "\\$&")).join("|")}|\\[field-[a-z0-9_-]+\\])`, "gi"); /* Wraps every recognised tag so the preview shows what will be substituted per skin. */ const hhpMarkTags = (html) => String(html || "").replace(HHP_TAG_RE, '$1'); /* ------------------------------------------------------------------ * * Mock data — `helpcategories`. Values fake, shape real: id, name, * name_it, name_pt, priority, type, show_online. Ids skip 9 (a * "Payments" category deleted at some point) so the orphaned-pages * behaviour of the non-cascading delete is visible in the seed itself. * ------------------------------------------------------------------ */ const HHP_CAT_SEED = [ { id: 1, name: "Terms and Conditions", name_it: "Termini e condizioni", name_pt: "Termos e condições", priority: 90, type: "link", show_online: 1 }, { id: 2, name: "Privacy Policy", name_it: "Informativa sulla privacy", name_pt: "Política de privacidade", priority: 85, type: "link", show_online: 1 }, { id: 3, name: "Responsible Gaming", name_it: "Gioco responsabile", name_pt: "Jogo responsável", priority: 80, type: "link", show_online: 1 }, { id: 4, name: "Getting Started", name_it: "Come iniziare", name_pt: "Como começar", priority: 70, type: "", show_online: 1 }, { id: 5, name: "Bonus Terms", name_it: "Condizioni bonus", name_pt: "Termos de bónus", priority: 65, type: "", show_online: 1 }, { id: 6, name: "Casino Rules", name_it: "Regolamento casinò", name_pt: "Regras do casino", priority: 60, type: "", show_online: 1 }, { id: 7, name: "Complaints", name_it: "Reclami", name_pt: "Reclamações", priority: 55, type: "link", show_online: 0 }, { id: 8, name: "Affiliate Program", name_it: "Programma affiliati", name_pt: "Programa de afiliados", priority: 50, type: "", show_online: 0 }, { id: 10, name: "Money Laundering", name_it: "Norma Antiriciclaggio", name_pt: "Branqueamento de capitais", priority: 45, type: "", show_online: 1 }, { id: 11, name: "Contact Us", name_it: "Contattaci", name_pt: "Contacte-nos", priority: 40, type: "contacts", show_online: 1 }, { id: 12, name: "Cashier", name_it: "Cassa", name_pt: "Caixa", priority: 35, type: "", show_online: 1 }, { id: 13, name: "My Account", name_it: "Account", name_pt: "A minha conta", priority: 30, type: "", show_online: 1 }, { id: 14, name: "AML & KYC", name_it: "Norma Antiriciclaggio", name_pt: "AML e KYC", priority: 25, type: "", show_online: 1 }, { id: 15, name: "Sport Rules and Betting Options Pregame", name_it: "Regole sportive e opzioni di scommessa Pregame", name_pt: "Regras desportivas e opções de aposta Pré-jogo", priority: 20, type: "", show_online: 1 }, { id: 16, name: "Sport Rules and betting Options Live", name_it: "Regole sportive e opzioni di scommessa Live", name_pt: "Regras desportivas e opções de aposta Ao vivo", priority: 15, type: "", show_online: 1 }, ]; /* ------------------------------------------------------------------ * * THE DATA. This screen carried its own database too — and a bigger one * than either of its siblings. * * `hhpStore` built fifteen categories by hand and then GENERATED the pages: * thirty Pregame sport rules and seven Live ones from a table of sports in four * languages, each page's body assembled by `hhpBody` from a lead, one or two * randomly chosen middle paragraphs and a tail, all seeded on the page id so * every reload produced the same text. Both routes shared the store, so a * category deleted on one screen really did orphan its pages on the other — * a faithful reproduction of a cascade the platform does not perform. * * Replaced by reads of `help_pages` and `help_categories` with their * translations embedded. Everything downstream still sees the flat-column shape * the two forms were written against (`name`, `name_it`, `content_pt` …), so the * conversion here is the only code that knows the storage differs. * * THREE MAPPINGS WORTH STATING, because the schema is not a copy of isystem's: * * type -> placement, and 006 constrains it to link/contacts/none where * isystem stored '' for "not set". Empty becomes 'none'. * show_online -> visible, a real boolean rather than 0/1. * (nothing) -> slug, which is NOT NULL UNIQUE here and does not exist * upstream. Minted from the English name on create; never * regenerated on edit, because a slug is an address. * ------------------------------------------------------------------ */ const HHP_FETCH_MAX = 500; /* Str::slug, and the same de-dup ladder the sibling screens use. `help_pages` and `help_categories` both carry a GLOBAL unique index on slug — not per-tenant, since there is no tenant — so the check is across everything. */ const hhpSlugify = (v) => String(v || "").toLowerCase().normalize("NFD").replace(/[\u0300-\u036f]/g, "") .replace(/[^a-z0-9]+/g, "-").replace(/^-+|-+$/g, "").slice(0, 200); const hhpUniqueSlug = (rows, base, excludeId) => { const root = hhpSlugify(base) || "page"; const taken = (rows || []).filter(r => String(r.id) !== String(excludeId)).map(r => r.slug); if (taken.indexOf(root) === -1) return root; for (let i = 1; i < 500; i++) if (taken.indexOf(`${root}-${i}`) === -1) return `${root}-${i}`; return root; }; const hhpTrGet = (rows, code, field) => { const r = (rows || []).find(x => String(x.locale_code || "").toLowerCase() === code); return r ? String(r[field] || "") : ""; }; const hhpCatFromDb = (r) => ({ id: r.id, slug: r.slug || "", name: hhpTrGet(r.translations, "en", "name"), name_it: hhpTrGet(r.translations, "it", "name"), name_pt: hhpTrGet(r.translations, "pt", "name"), priority: r.priority || 0, /* 'none' is this schema's word for isystem's empty string; the form's "— not set" option keeps the upstream spelling. */ type: r.placement === "none" ? "" : (r.placement || ""), show_online: r.visible ? 1 : 0, _tr: r.translations || [], }); const hhpPageFromDb = (r) => ({ id: r.id, slug: r.slug || "", category: r.category_id, generic_name: r.generic_name || "", position: r.position || 0, name: hhpTrGet(r.translations, "en", "name"), name_it: hhpTrGet(r.translations, "it", "name"), name_pt: hhpTrGet(r.translations, "pt", "name"), name_es: hhpTrGet(r.translations, "es", "name"), /* content_en lives in the column `content` upstream (the form field is content_en); the other three keep their own names. Preserved so both forms and every renderer keep working unchanged. */ content: hhpTrGet(r.translations, "en", "content"), content_it: hhpTrGet(r.translations, "it", "content"), content_pt: hhpTrGet(r.translations, "pt", "content"), content_es: hhpTrGet(r.translations, "es", "content"), _tr: r.translations || [], }); /* Both lists, shared by the two routes. A category deleted on one screen is gone from the other after its refetch — which is what the module store was for, asked of the database instead. */ const hhpUseDb = () => { const catsFeed = useHrsFetch(() => window.sb.list("helpCategories", { limit: HHP_FETCH_MAX }), []); const pagesFeed = useHrsFetch(() => window.sb.list("helpPages", { limit: HHP_FETCH_MAX }), []); const cats = hhpUseMemo(() => (catsFeed.data || []).map(hhpCatFromDb), [catsFeed.data]); const pages = hhpUseMemo(() => (pagesFeed.data || []).map(hhpPageFromDb), [pagesFeed.data]); const truncated = [ catsFeed.meta && catsFeed.meta.total > cats.length ? "categories" : null, pagesFeed.meta && pagesFeed.meta.total > pages.length ? "pages" : null, ].filter(Boolean); return { cats, pages, truncated, loading: catsFeed.loading || pagesFeed.loading, error: catsFeed.error || pagesFeed.error, retry: () => { catsFeed.retry(); pagesFeed.retry(); }, feeds: [catsFeed, pagesFeed], }; }; /* Reconcile one parent's translations. Same contract as the FAQ and Blog versions: INSERT what is new, UPDATE what changed, DELETE what was emptied — the third being the one a naive save forgets, leaving a language the operator cleared still served to players. */ const hhpSyncTr = async ({ resource, fkColumn, parentId, existing, values, isCat }) => { const have = new Map((existing || []).map(r => [String(r.locale_code || "").toLowerCase(), r])); const failed = []; let wrote = 0, removed = 0; for (const l of HHP_LANGS) { /* Categories have EN/IT/PT names and no ES one — reference note (5). Not a gap to fill in: a Spanish category name is a field the platform has no input for, and inventing the row would put text nobody typed in front of players. */ if (isCat && l.id === "es") continue; const prev = have.get(l.id); const name = String((values.names || {})[l.id] || "").trim(); const content = isCat ? "" : String((values.bodies || {})[l.id] || ""); const keep = isCat ? !!name : !!(name || content.trim()); const body = isCat ? { name } : { name: name || null, content: content || null }; if (keep) { const res = prev && prev.id ? await window.sb.update(resource, prev.id, body) : await window.sb.create(resource, Object.assign({ [fkColumn]: parentId, locale_code: l.id }, body)); if (res && res.ok) wrote++; else failed.push(`${l.full}: ${(res && res.error && res.error.message) || "refused"}`); } else if (prev && prev.id) { const res = await window.sb.remove(resource, prev.id); if (res && res.ok) removed++; else failed.push(`${l.full} (removal): ${(res && res.error && res.error.message) || "refused"}`); } } return { wrote, removed, failed }; }; /* getHelpPages() L391: a category reaches a frontend footer only when show_online = 1 AND type IN ('link','contacts'). Pages inherit this — they have no visibility flag of their own. */ const hhpFooterOk = (c) => !!c && c.show_online === 1 && (c.type === "link" || c.type === "contacts"); const hhpCatById = (cats, id) => cats.find(c => c.id === Number(id)) || null; const hhpPageCount = (pages, catId) => pages.filter(p => Number(p.category) === Number(catId)).length; /* The header cross-links ("Help Pages" ⇄ "Categories") are plain anchors on the real screens. app.jsx resolves `active` from the URL on popstate, so pushState + a popstate event is the in-app equivalent; if the route table is unavailable the link degrades to a toast. */ const hhpGoto = (routeKey, label) => { try { const path = window.pathForActive && window.pathForActive(routeKey); if (path) { if (window.location.pathname !== path) window.history.pushState({ active: routeKey }, "", path); window.dispatchEvent(new PopStateEvent("popstate")); return; } } catch (_e) { /* fall through to the toast */ } hrsToast(`Open ${label}`, `Route "${routeKey}" is not registered in src/routes.jsx.`); }; /* ------------------------------------------------------------------ * * Shared bits * ------------------------------------------------------------------ */ const HhpModal = ({ title, sub, onClose, children, footer, wide }) => (
e.stopPropagation()}>
{title}
{sub &&
{sub}
}
{children}
{footer &&
{footer}
}
); /* `show_online` chip (index.blade.php renders Yes / No). The warning marker is the trap made visible: the flag says Yes but the empty `type` still keeps the category out of every footer. */ const HhpVisibleChip = ({ cat }) => ( {cat.show_online ? "Yes" : "No"} {cat.show_online === 1 && !hhpFooterOk(cat) && ( Marked visible, but not reachable from any footer: the frontend reader selects categories with show_online = 1 and type IN ('link','contacts'), and this row's type is {cat.type ? {cat.type} : <>empty}. The real admin form cannot set type at all — it is editable here as a deliberate divergence. )} ); /* Category cell on the Help pages list: chip, or "—" when the parent row is gone. */ const HhpCatCell = ({ cat, rawId }) => { if (!cat) return ( — Orphan: helppages.category = {rawId} points at a category row that no longer exists. Deleting a category does not cascade (HelpCategoriesController::delete L241-252), so its pages survive unreachable — no footer can ever render them. ); return ( {cat.name} {!hhpFooterOk(cat) && ( Not published: a help page has no status of its own, it inherits its category's. {cat.name} is {cat.show_online ? <>visible but typed {cat.type || "''"} : <>hidden (show_online = 0)}, so this page renders on no skin. )} ); }; /* ------------------------------------------------------------------ * * Placeholder-tag legend. The real form shows it read-only above the * editors (helpPagesTags() L162-236). Kept in the same place, but the * entries are clickable: an operator must be able to see WHICH tags * exist and get one into the body without retyping it by hand. * ------------------------------------------------------------------ */ const HhpTagPalette = ({ onInsert, disabled }) => (
Placeholder tags{/* label inferred */} {HHP_TAGS.length} fixed + dynamic
{HHP_TAGS.map(t => ( ))}
Tags are substituted when the frontend renders the page, per skin — which is how one global help tree shows the right company, licence and mailbox on every brand. They stay raw in this editor and in its preview.
); /* ------------------------------------------------------------------ * * Body editor. The real field is a TinyMCE 5.0.16 textarea (height 200, * no menubar, plugins advlist/autolink/lists/link/image/…/code, toolbar * carrying the `code` button). The exact toolbar string is not recorded * in the reference, so no formatting buttons are invented here: the * documented Source view is paired with a live preview instead. * ------------------------------------------------------------------ */ const HhpRichText = ({ value, onChange, mode, onMode, taRef, invalid, id }) => (
{[["source", "Source"], ["preview", "Preview"]].map(([m, lab]) => ( ))}
{String(value || "").length} chars
{mode === "source" ? (