FarCry CMS: content publishing and support
Understand the FarCry CMS behind an existing content site. Check publishing, extensions and runtime support before maintaining or replacing it.
- Published
- Last updated
FarCry CMS is a content-management application built on FarCry Core, a framework for sites written in ColdFusion Markup Language (CFML). For an inherited retail site, the maintain-or-replace decision depends on its installed components, publishing workflow and recoverable operating setup. A familiar administration screen alone doesn’t establish that the underlying software is supported.
Identify the FarCry project and installation
Identify FarCry Core and the CMS components separately before assessing the site. The official Core project describes FarCry CMS as a plugin built on the framework. This is the web-content project, separate from the similarly named video games.
The FarCry Core site identifies Lucee and Adobe ColdFusion as supported engine families. That statement doesn’t establish compatibility with every release of either engine. Record the engine and its exact version from the running environment, alongside the Core version and installed CMS plugin version.
Ask the maintainer to produce an installation inventory from the deployed application. Include the Java version, database and web server, plus every plugin and local modification. Record where the application source and uploaded files are kept. Compare that inventory with the release records so you can distinguish the software actually running from a newer download.
For a retail site, identify which component owns product references inside buying guides. A manually entered product link, a database relationship and a custom catalogue connection have different maintenance needs. Treat a connection built for that site as implementation work unless its documented plugin establishes otherwise.
Maintain the approved store content
Trace one existing guide or policy from its editable record to the public page before giving a new editor access. FarCry’s documented framework features include a configurable administration area called Webtop, role-based permissions and content rendered through templates. The installed application determines how those pieces work together.
Use a copy of the site to walk through a real content change. For example, a hypothetical retailer wants to correct a care guide’s washing advice while retaining its existing product links. Establish the following responsibilities before changing the live guide.
- Identify the editable content type and the staff role allowed to change it. Check whether product links are fields, embedded body links or data supplied by another system.
- Find the approval and publication controls implemented for that type. Determine who can make a change visible and whether saving immediately affects the public page.
- Locate the public template and any reusable content it inserts. A developer must handle a template change if editors only control the guide’s fields.
- Publish the correction in the test copy and open the page as a signed-out visitor. Confirm the corrected advice appears, the product links still resolve and restricted content remains private.
A correct record with an outdated public page needs a rendering or cache check. A missing approval control needs an assessment of the installed workflow. Don’t assume either symptom means every FarCry installation behaves the same way.
Check support and recovery responsibilities
Assess support for the deployed combination of framework, runtime and extensions. The project homepage advertises the 7.2.12 download from 2019, while the official Core repository records development activity in 2026. Those are different signals: neither a download label nor a recent commit proves that your installation has a supported upgrade path.
The project’s support page describes community channels and commercial services through Daemon. A listing on that page isn’t a support agreement for your site. Record the named maintainer, what they cover and how a failed release reaches someone who can restore service.
Have the maintainer match the installed engine’s version to its vendor’s support lifecycle and security updates. Review plugin compatibility separately, including any locally modified copy. A working page on an old runtime isn’t evidence that the runtime still receives fixes.
Recovery needs a complete, tested set of inputs. Keep application code and configuration with the database backup and uploaded assets. Protect secrets separately and establish who has recovery access. Restore the set into an isolated environment, then verify sign-in and a representative public guide before relying on it.
Write down the release owner and rollback trigger. If a release breaks policy pages or changes permissions, the person on call needs a known working release and a recovery procedure they have practised.
Decide whether to maintain or replace it
Maintain FarCry when the required editing workflow works, a maintainer can support the installed stack and a restore has succeeded. Replacement becomes a practical choice when required content changes depend on unavailable expertise or the operating stack has no acceptable supported path.
Compare the existing workflow with a concrete requirement. For example, if policy editors must publish independently, identify the exact permission or custom approval change needed. Compare that work and ongoing maintenance with the cost of moving the content. Rebuilding a familiar screen won’t resolve an unclear approval owner.
Before replacing the system, inventory content fields and relationships alongside media and public URLs. Determine how each record can be extracted from the actual installation. Preserve the relationship between a guide and its product references, and plan redirects for URLs that change. Use the CMS migration guide for the transfer procedure once that inventory supports the decision.
Choose the route that gives your team a supported way to publish approved information and recover a failed release. Assign that responsibility before scheduling the next change.
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.