Help Center
Search
⌃K
Comment on page

Preserve your Setka Editor content after the service shutdown

This is a step-by-step guide on ensuring your content created with Setka Editor is safe in Magento after Setka Editor infrastructure shutdown.

Introduction

To ensure robust content preservation on Magento after the Setka Editor infrastructure shutdown this guide will do two things:

Assets that rely on Setka Editor CDN

The official Setka plugin for Magento can be configured in two ways.
All the files are stored on your server by default. But you can change it in the plugin settings. This table represents where the files are stored, depending on settings:
Files
Stored by default
If Setka CDN is enabled
HTML code
Your server
Your server
CSS files of Setka styles and grids
Your server
Setka CDN
JS files of interactive elements
Your server
Setka CDN
Images
Magento media folder
Magento media folder
Setka Editor JS file
Your server
Setka CDN
Setka Editor module for Magento stores all the data on your server, unless you disable Use Setka Editor files from Local Server in the module settings.

How to preserve your data

Prerequisites

Before you proceed further, check if Setka CDN is enabled in the module settings:
  1. 1.
    Go to Admin panel > Stores > Configuration > Content Management > Setka Editor > Editor hosting.
  2. 2.
    Scroll down to the Editor files from Local Server dropdown.
  3. 3.
    If Editor files from Local Server is set to No — Setka CDN is enabled.
  4. 4.
    If Editor files from Local Server is set to Yes — Setka CDN is disabled.

If Setka CDN is enabled

Step 1. Disable the module's connection with Setka CDN

Go to Admin panel > Stores > Configuration > Content Management > Setka Editor > Editor hosting select Yes in the Editor files from Local Server dropdown. This will force the module to pull all the files from your server instead of Setka CDN.

Step 2. Pull the latest CSS and JS files to your server

Go to Download Job > Schedule. Wait and reload page until you'll see some recent date in the Last Update field.

Step 3. Replace asset URLs in posts

  1. 1.
    Check if your Setka posts use any assets, stored on Setka CDN:
    1. 1.
      Open the browser's developer tools (CMD+ALT+I on Mac OS or F12 on Windows).
    2. 2.
      Switch to the Network tab of developer tools.
    3. 3.
      Filter the list а files by ceditor.setka.io and reload the page. You will see the list of files loaded from Setka CDN. You will need to back them up:
  2. 2.
    Examine the asset's location in the Setka integration data.
  3. 3.
    Copy assets from Setka CDN to your own CDN. It is more convenient to copy the whole directory, keeping the paths.
  4. 4.
    Replace asset URLs in posts HTML from Setka CDN to your server. Since Setka keeps url structure it's enough to replace the beginning of the URL. For example https://ceditor.setka.io/clients/fYe3/css/assets/29778/img/icon.svg> -> https://your-domain.name/pub/media/setka_editor/clients/fYe3/css/assets/29778/img/icon.svg

Step 4. Uninstall the Setka Editor module

Follow these steps from the official Magento documentation to uninstall the Setka Editor module.

If Setka CDN is disabled

Step 1. Pull the latest CSS and JS files to your server

Go to Download Job > Schedule. Wait and reload the page until you'll see some recent dates in the Last Update field.

Step 2. Replace asset URLs in posts

  1. 1.
    Check if your Setka posts use any assets, stored on Setka CDN:
    1. 1.
      Open the browser's developer tools (CMD+ALT+I on Mac OS or F12 on Windows).
    2. 2.
      Switch to the Network tab of developer tools.
    3. 3.
      Filter the list а files by ceditor.setka.io and reload the page. You will see the list of files loaded from Setka CDN. You will need to back them up:
  2. 2.
    Examine the asset's location in the Setka integration data.
  3. 3.
    Copy assets from Setka CDN to your own CDN. It is more convenient to copy the whole directory.
  4. 4.
    Replace asset URLs in posts HTML from Setka CDN to your server. Since Setka keeps url structure it's enough to replace the beginning of the URL. For example https://ceditor.setka.io/clients/fYe3/css/assets/29778/img/icon.svg> -> https://your-domain.name/pub/media/setka_editor/clients/fYe3/css/assets/29778/img/icon.svg

Step 3. Uninstall the Setka Editor module

Follow these steps from the official Magento documentation to uninstall the Setka Editor module.
Previous
Setka Editor configuration page
Next - Integrations
Setka and HubSpot
Last modified 1mo ago