FusionCMS: editions, editing and maintenance
Identify the original FusionCMS and its edition before assessing a retail site. Check editing and maintenance without mixing unrelated products.
- Published
- Last updated
FusionCMS is efelle creative’s content management system, with a commercial v5 platform and a separate public v6 prototype/beta project. Assess an inherited retail site against its installed edition. The public v6 code and documentation describe that project, so they cannot establish the maintenance terms or features of a commercial v5 installation.
Identify the FusionCMS project and edition
The original efelle project identifies its public repository as FusionCMS v6 Prototype/Beta. Its readme describes v5 as the commercial, closed-source platform and says v5 updates are outside that repository. That distinction determines which code and documentation apply to your site.
Start your site record with efelle as the provider, the installed version and the party responsible for maintaining it. Add the hosting account and the contract that covers the application. Products for game servers, hotel television and travel operations with similar names belong to different assessments.
For an inherited site, request the version from the installed application or its maintenance records. A repository link in an old handover is insufficient to identify the running release. Keep any local modifications beside the version record, because the unmodified product may behave differently from your site.
The repository’s older plans for future development are historical statements. Base a maintenance decision on the support available for the actual installation and its written service terms.
Maintain the site’s approved content
Assess FusionCMS editing through a guide and a policy that your retailer must maintain. The v6 beta documentation describes collections of entries with shared fieldsets, a file manager for media and user roles. Those concepts explain the beta editor. A commercial v5 site needs its own field and permission assessment.
Use a hypothetical outdoor retailer’s tent-care guide and delivery policy as sample content. The guide needs headings, explanatory text and images. Its care instructions must remain readable on a phone. The policy needs an approved delivery area and fee rule that an editor can change without altering unrelated content.
Map each piece of content to the fields available in your installation. If a field mixes policy wording with page layout, record the extra work needed to make a safe change. Upload a replacement guide image, inspect its text description and confirm that pages reusing it still display the intended image.
Test permissions with the accounts your team will use. An editor needs to make the authorised content change. A restricted account must remain unable to change site settings or publish material beyond its role. Where approval happens outside the CMS, include that handoff in the publishing procedure.
Finish the sample update at the public URL. Reload the page and compare its wording with the approved policy. A saved record inside the editor is only one stage of publication.
Check deployment and custom work
The public FusionCMS v6 project uses Laravel. Its beta requirements page lists PHP and server extensions, but those requirements belong to that documented version. They are not a recommendation for a new production server or evidence of the runtime used by v5.
Have the maintainer record the installed framework and runtime versions from the application’s dependency files and hosting configuration. Match those versions to a supported maintenance route before changing the server. Upgrading the runtime alone can leave custom code incompatible.
Inventory the site’s custom templates and modules. For each one, name the content it displays, the integration it calls and the person who can repair it. Include any connection between guides and product records. Keep catalogue prices, stock and checkout with their actual system owner.
Apply a proposed update to an isolated copy of the site. Exercise the guide edit and policy publication there, together with navigation and any custom product connection. Release only after the maintainer has a recovery procedure for the matching application code and stored content.
Plan updates and content portability
Compare FusionCMS maintenance and replacement using the available support agreement and a demonstrated recovery copy. The v6 beta backup documentation describes manual backups and scheduled jobs. Automatic operation depends on server scheduling, so a switch in the editor alone does not prove that backups run.
For your installation, inspect a completed backup and restore it into an isolated environment. Confirm that the restored guide includes its images and that the delivery policy displays correctly. Record who receives failure notices and who restores the site. Keep recovery copies separate from the running server.
Portability needs a different check. A database backup may restore the same application while requiring substantial work to move content elsewhere. Request a sample export with the guide’s fields and media, then map the policy to the receiving system. Include public addresses and redirects in the move so existing links still reach the right pages.
Retain the installation when its supported update route, editing workflow and recovery process meet your store’s needs. Choose replacement when the required maintenance or content changes make that route unsuitable. Cost the export and custom-template work before approving a move.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.