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 your CMS after Setka Editor infrastructure shutdown.
Last updated
Was this helpful?
This is a step-by-step guide on ensuring your content created with Setka Editor is safe in your CMS after Setka Editor infrastructure shutdown.
Last updated
Was this helpful?
To ensure robust content preservation on your CMS after the Setka Editor infrastructure shutdown this guide will do two things:
Explain which assets rely on Setka Editor CDN
Describe the steps needed to migrate mentioned assets to your CMS's CDN
images
JavaScript code for enabling interactive post elements
CSS code which enables all the styling of your articles
Make a request to to receive your list of Setka Editor posts. Here is a request example:
state
determines the publication status of the post:
Set to published
to only get published posts.
Set to draft
to get drafts.
Set to all
to get both drafts and published posts.
limit
determines the number of posts you can receive as a response. Please make sure you don't set the value too low and miss some of the posts.
If the request is successful, you will receive a response consisting of an array of posts. The response will be paginated if the number of posts is large. Below is an example API request response:
Download the assets for each post from the array. The possible types of assets are:
plugins
https://ceditor.setka.io/clients
/js_plugins/5ca41dc7f0df3e3d6170901b627d32fc/public.js
The scripts to run interactive post elements (e.g., animations, galleries, or notes).
styles
https://ceditor.setka.io/common_css
/common_css_1565603693.css
images
https://ceditor.setka.io/clients
/U8Cr2B1ZnJjyHr6e6xn_Qa7N1oqyj7cB/post_images/-tltJS8D79MI5Yltt37MCA.jpg
The images used in the post, where:
— id
— the image’s unique ID.
— url
— the link to the file.
— alt
— the alternative text.
When all assets are downloaded, store them in your infrastructure.
When all assets are downloaded and stored in your infrastructure, you need to replace all links used in the Post body and include CSS files in the Post Page. You will need a custom script tailored to your case.
Inside the Post body there might be images. If you created Posts inside Setka Cloud you’ll find srcset
generated for multiple image sizes. It’s a feature provided by Setka Cloud. Links to image variations are not provided. We suggest that you remove everything inside the srcset
HTML attribute for in <img tag>
and store the original image in your infrastructure.
Example:
You have the following piece of code:
Then change the link inside Setka Post body and remove the srcset. The result will look like this:
Check the for more filters.
The of post styles, including the common style file, the standalone style, and the layout grid file.
— sizes
— several options for the image size, depending on the device’s screen size.
Note: Getting the images
field in your response will require using .
For example: If CSS URL looks like: you should store it in your infrastructure and make it accessible via the URL on your domain, for example like this: .
You should pick the original size – in src
attribute (you can find the same link inside Post API response) and make it accessible on the URL like