MokoConsulting/MokoSuiteBackup
1
0
Fork 0
Code Issues 30 Pull Requests 3 Releases 2 Wiki Activity

fix: remote destinations tab broken (cascade to dev) #209

Merged
jmiller merged 2 commits from fix/remote-destinations-modal-dev into dev 2026-07-04 22:11:36 +00:00
Conversation 0 Commits 2 Files Changed 14
+21 -15

2 Commits

Author SHA1 Message Date
gitea-actions[bot] 182f8a91fb chore(version): pre-release bump to 02.56.03-dev [skip ci]
RC Revert / Rename rc/ back to dev/ (pull_request) Has been skipped
Details
Branch Cleanup / Delete merged branch (pull_request) Successful in 3s
Details
2026-07-04 22:10:05 +00:00
jmiller 6ae38784d9 fix(profile): remote destinations tab broken — lazy-init Bootstrap modal
Universal: Pre-Release / Build Pre-Release (${{ inputs.stability || github.ref_name }}) (push) Successful in 20s
Details 
The remote destinations table stayed stuck at "Loading…" and the "Add
Destination" button did nothing. Root cause: the profile-edit DOMContentLoaded
handler instantiated the Bootstrap modal eagerly at the top
(`bootstrap.Modal.getOrCreateInstance`). In Joomla 6, Bootstrap loads as a
deferred ES module, so `bootstrap` is undefined at DOMContentLoaded — the
reference threw a ReferenceError that aborted the entire handler, so
loadRemotes() never ran and the Add button was never bound. (The purge and
stepped-backup modals worked because they resolve the modal lazily inside
click handlers.)

- Resolve the modal lazily via getModal() at click-time (matches the working modals)
- Explicitly load the bootstrap.modal web asset so window.bootstrap.Modal is registered

Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i
 2026-07-04 17:09:09 -05:00