Skip to content
TheChatArchiveThe Chat Archive
Perplexitysonar-reasoning-pro-high· PerplexityHugging Face LMArena Search Arena 24K

Below is my erpnext environment. I want to update ERPNext and Frappe Framework to latest…

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with gpt-4o-search-preview-high-loc’s answer.
  1. User

    Below is my erpnext environment. I want to update ERPNext and Frappe Framework to latest versions. Provide step by step guidance

    ERPNext: v14.56.0 (version-14)

    Frappe Framework: v14.60.0 (version-14)

    Frappe HR: v16.0.0-dev (develop)

  2. Perplexity Assistant

    Based on your current environment, I'll guide you through updating ERPNext and Frappe Framework from version 14 to version 15, which is the latest stable version.

    Prerequisites Check

    Before beginning the upgrade process, verify that your system meets the requirements for ERPNext version 15:

    • Python 3.10 or 3.11 (your current Python version should be compatible)
    • Node.js 18 or higher (you'll likely need to upgrade this)
    • MariaDB 10.6.6+

    Preparation Steps

    1. Create a Backup

    Always create a full backup before upgrading:

    bench backup --with-files
    

    2. Check Node.js Version

    node --version
    

    If your Node.js version is below 18, upgrade it:

    curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.1/install.sh | bash
    source ~/.bashrc
    nvm install 18
    nvm alias default 18
    

    3. Update System Packages

    sudo apt update
    sudo apt upgrade
    

    4. Upgrade Redis

    ./env/bin/pip3 install --upgrade redis
    

    Upgrade Process

    1. Navigate to Your Bench Directory

    cd /path/to/your/frappe-bench
    

    2. Upgrade Frappe Bench

    sudo -H pip3 install --upgrade frappe-bench
    

    3. Update Bench Requirements

    bench setup requirements
    

    4. Update Bench

    bench update
    

    5. Switch to Version 15 and Upgrade

    The search results indicate that you have Frappe HR on develop branch. For proper upgrading, you should switch all components to version-15:

    bench switch-to-branch version-15 frappe erpnext hrms --upgrade
    

    Note: Frappe HR was renamed to HRMS in the newer versions[9].

    6. Migrate Database

    bench migrate --skip-failing
    

    If you encounter any errors during migration, you can run it for a specific site:

    bench --site your_site_name migrate
    

    7. Update Patches

    bench update --patch
    

    8. Build Assets and Restart Services

    bench build
    sudo supervisorctl restart all
    

    For production setups:

    sudo service nginx restart
    

    Post-Upgrade Steps

    1. Verify the Upgrade

    Check if the upgrade was successful:

    bench version
    

    This should now show ERPNext and Frappe Framework on version 15.

    2. Disable Maintenance Mode (if needed)

    If your site is stuck in maintenance mode after upgrading:

    bench --site your_site_name set-config maintenance_mode 0
    

    3. Check for Error Messages

    If you encounter the error "Failed to get method for command erpnext.e_commerce.doctype.e_commerce_settings.e_commerce_settings.is_cart_enabled," run:

    bench retry-upgrade
    

    Important Notes

    1. Some modules were separated from ERPNext in version 14, including HR and Payroll which moved to a separate app called HRMS. Since you already have Frappe HR installed, the upgrade process should handle this transition.

    2. The upgrade process does not require updating Ubuntu from 22.04 if that's what you're using.

    3. If you have custom apps, check their compatibility with version 15 before upgrading.

    4. Sometimes after upgrading, Redis might need a separate update if you encounter Redis-related errors.

    5. The HRMS repo appears to be actively maintained with recent updates to version 15.42.2 as of April 3, 2025[9].

    Following these steps should successfully upgrade your ERPNext environment to the latest version 15. Make sure to test your instance thoroughly after upgrading to ensure everything is working as expected.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.