Setka Editor on WordPress Installing Setka Editor WordPress plugin

Installing Setka Editor WordPress plugin

Currently, the minimum allowable version for our plugin is PHP 5.5.9. WordPress developers recommend using PHP 7.

1. Install Setka Editor plugin. If you are uploading your plugin as an archive set your WordPress account to allow uploads larger than 7MB.

2. To use all Setka Editor features and sync it with your account on editor.setka.io you will need to enter a license key. You can read more on how to create your account here.

3. You can find your license key in the CMS Integration section in your personal account on editor.setka.io.

Screen_Shot_2018-11-20_at_12.34.56.png

4. Copy your license key and paste it in Setka Editor plugin settings inside your WordPress: Plugin Settings -> Register -> I already have a license key.

Screen_Shot_2018-11-20_at_12.31.38.png

 

Setka Editor on post creation page.

Setka Editor tab on post creation page for WordPress before version 5.0.

After plugin activation, the post creation page will have a Setka Editor tab displayed.

Screen_Shot_2018-11-20_at_12.05.53.png

After switching to Setka Editor tab the editor interface will launch. If you didn't enter your license key in plugin settings, the editor will launch with a free tariff functionality, giving you an option to get familiar with the interface. After entering your license key in the bottom right corner you will see your current tariff, which will match the one, displayed in your account on editor.setka.io.

Screen_Shot_2018-11-20_at_12.06.55.png

Setka Editor block on Gutenberg post creation page (for WordPress 5.0 or later).

After plugin activation, you will be able to add a Setka Editor block on a corresponding Gutenberg post creation page.

Screen_Shot_2018-11-20_at_12.51.35.png

Setka Editor will launch inside a block.

Screen_Shot_2018-11-20_at_12.51.11.png

That's it, you now have your Setka Editor installed and activated.

If some part of the process doesn't occur as explained above, make sure to check out our "Technical Problems with WordPress Integration" post.