https://kfdani-001-site10.gtempurl.com/index.php?action=history&feed=atom&title=OpenSite%2FGuides%2FManage_extensions 2026-10-30T02:06:17Z Revision history for this page on the wiki MediaWiki 1.46.2 https://kfdani-001-site10.gtempurl.com/index.php?title=OpenSite/Guides/Manage_extensions&diff=959&oldid=prev 2026-10-29T22:08:41Z

<p>Add source-reviewed, step-by-step OpenSite user workflow</p> <p><b>New page</b></p><div>__NOTOC__<br /> {{OpenSite scope}}<br /> {{OpenSite lesson<br /> |id=opensite.help.manage-extensions<br /> |summary=Recognize extension availability and compatibility before adding code to the application.<br /> |prerequisites=A trusted extension package and instructions from its distributor. This baseline has no verified public add-on store or general end-user installer.<br /> |steps=<br /> === Identify what you received ===<br /> A plugin can contain native code, Python, or both. A workbench is a user interface environment contributed by an extension. A macro is a Python script. These names are not interchangeable.<br /> <br /> === Check compatibility ===<br /> Match SDK/host version, native ABI, architecture, compiler/runtime and Release/Debug configuration. Copying a DLL that compiled elsewhere is not a compatibility test.<br /> <br /> === Keep the package layout ===<br /> Follow the package’s documented location and restart requirements. Preserve its manifest, implementation, catalogs and runtime files. Do not guess an install folder or move only one file from a mixed package.<br /> <br /> === Read activation failures ===<br /> A provider can be unavailable, incompatible, or denied a capability. Record the extension ID/version and host build. Startup registration/discovery is not proof that every command ran.<br /> <br /> === Protect documents when a provider is missing ===<br /> Keep a backup before changing extension versions. An unavailable object may retain its payload as a placeholder. See [[OpenSite/Guides/Recover linked and unavailable objects]].<br /> <br /> === Developer route ===<br /> For the supported native sample workflow, use [[OpenSite/Guides/Build a native plugin]]. The GUI SDK’s distributable state is separate from the installed headless plugin SDK.<br /> |result=You can identify the package’s purpose and compatibility needs before attempting to use it.<br /> |limitations=In-process native/Python extensions are trusted code, not sandboxed content. Saved custom workspaces are not implemented user functionality.<br /> }}<br /> <br /> == Continue learning ==<br /> [[OpenSite/User manual|User manual]] · [[OpenSite/Tutorials|Tutorial pathways]] · [[OpenSite/Support|Get help]]<br /> <br /> &lt;div class=&quot;os-page-nav&quot;&gt;{{Docnav|OpenSite/User manual|OpenSite/Guides/Build a native plugin|OpenSite/User manual|User manual}}&lt;/div&gt;<br /> [[Category:OpenSite documentation]]</div>

BathAfrica