- Back to Docs
- Install and Configure
- Image
- Server Upload
- Server Delete
- S3 Upload
- Resize
- Validation
- Image Manager
- Simple Server
- File
- Server Upload
- Server Delete
- S3 Upload
- Validation
- References
- Image
- File
- S3
Node.JS Image Manager
How it works
- You specify the image load options when the javascript editor is initialized on client side.
- When the Image Manger modal is displayed, the javascript editor makes a request to the server to load the images.
- Once the request hits the server, it returns the list with the images to display in the rich text editor.
- The javascript editor processes the response of the server and renders the images in its interface.
Initialize the javascript editor
To get started, the javascript editor needs to have the imageManagerLoadURL
and imageManagerDeleteURL
options so that it can interact with your server to load or delete the images listed inside the Image Manager tool. Additionally, you can set other options related to the interaction between your server and the rich text editor: imageManagerLoadMethod
, imageManagerLoadParams
, imageManagerPreloader
, imageManagerDeleteParams
.
<script> $(function() { $('.selector').froalaEditor({ // Set the image upload URL. imageManagerLoadURL: '/load_images', // Set the image delete URL. imageManagerDeleteURL: '/delete_image' }) }); </script>
Receive the load request
The server implementation is responsible for receiving the request and handling it appropriately. The WYSIWYG editor's Node.JS SDK comes with the possibility to load all the images inside a specified folder using the FroalaEditor.Image.list
method.
Note: The path of the folder from where the images are being loaded is relative to the root of your application.
FroalaEditor.Image.list('/uploads/', function(err, data) { ... });
Receive the delete request
Your server should listen for any delete request and process it accordingly. Using the code from the Editor Initialization step, makes the image path available in the body of the request: request.body.src
. The FroalaEditor.Image.delete
method from the Node.JS SDK is expecting the path of the image to remove from disk.
FroalaEditor.Image.delete(req.body.src, function(err) { ... });
Complete Example
<script> $(function() { $(function() { $('.selector').froalaEditor({ // Set the image upload URL. imageManagerLoadURL: '/load_images', // Set the image delete URL. imageManagerDeleteURL: '/delete_image' }) }); }); </script>
var express = require('express'); var app = express(); var bodyParser = require('body-parser') var path = require('path'); var fs = require('fs'); var gm = require('gm').subClass({imageMagick: true}); var FroalaEditor = require('PATH_TO_FROALA_SDK/lib/froalaEditor.js'); app.use(express.static(__dirname + '/')); app.use('/bower_components', express.static(path.join(__dirname, '../bower_components'))); app.use(bodyParser.urlencoded({ extended: false })); app.get('/load_images', function (req, res) { FroalaEditor.Image.list('/uploads/', function(err, data) { if (err) { return res.status(404).end(JSON.stringify(err)); } return res.send(data); }); }); app.post('/delete_image', function (req, res) { FroalaEditor.Image.delete(req.body.src, function(err) { if (err) { return res.status(404).end(JSON.stringify(err)); } return res.end(); }); });