What is the easiest (best) way to store edited newsletters on the backend instead of localstorage

[bwl21]

What would be the easiest way to replace localstorage by a backend

As far as I can see, it requires following steps

• backend with minimum features noted in generic "backend" save/load plugin #50
• add / substitute localstorage by the required server communication?

It appears to me that the latter issue needs to be done in index.html as well as in mosaico respectively in editor.html. Could we find another appraoch, for example:

• only one HTML - file
• Mosaico can be embedded so there is no need for an extra editor.html
• do save and load etc. outside of Mosaico, maybe by plugins (even if I did not fully understand how to write/use/remove the plugins)

Of course beyond these basic things, one could think of more advanced scenarios, but this might be discussed #50 resp. #59

[acellam]

I don't know if my solution is the best, i started hacking mosaico 2 weeks back and i made some improvements.
What i do is that i store the metadata data and template to the database using ajax against the unique id and user id from mosaico editor.
When needed for edititing, i retrieve and pass those details back to mosaico editor

[bwl21]

Did you do this in index.html? Do you have a repository or a gist to show how you did this? How do you handle "save" button of mosaico?

[acellam]

Refer to @bago comment on #18 . I followed his advice.
For this to work i added another hash to the editor url to help me identify if it is a new template or old one.
check out gist:
https://gist.github.com/mistaguy/25ae3b8ec8205ea0f3e8

and

https://gist.github.com/mistaguy/1c3d9dc981061563e7c8

[bago]

We probably can make this simpler by merging metadata+content in a single object and by providing a simple "storage" plugin solution for which "localstorage" is the bundled implementation but it should be easier to plug-in a custom implementation (most people will have to do that).

But I'm also happy that we didn't have anything "pluggable" so that some people have to put their hands in the code! I'm happy to see how other developers hack in the code and understand what they expect there ;-)

[jbalatero]

This is by far my implementation. I implemented the Save button as plugin. This implementation does not involve localstorage which means don't put hash in your url like: http://youurl.com/editor.html#hashere, just the http://youurl.com/editor.html. it's because mosaico automatically loads the localstorage plugin whenever they found a hash in the url. I hope this helps.

var plugins;
plugins = [
    // plugin for integrating save button
    function(viewModel) {
        var saveCmd = {
            name: 'Save', // l10n happens in the template
            enabled: ko.observable(true)
        };

        saveCmd.execute = function() {
            saveCmd.enabled(false);
            viewModel.metadata.changed = Date.now();
            if (typeof viewModel.metadata.key == 'undefined') {
                viewModel.metadata.key = 'generate your unique key here';
            }

            // This is the simplest for sending it as POST
            // append postData with csrfToken
            var postData = {
                csrf_token: 'yourCsrfValueHere', // this is only required if your back-end requires csrf token
                metadata: viewModel.exportMetadata()
                content: viewModel.exportJSON(),
                html: viewModel.exportHTML()
            };

            $.post( 'your url here', postData)
                .done(function() {
                    viewModel.notifier.success(viewModel.t('Successfully saved.'));
                })
                .fail(function(jqXHR, textStatus, error) {
                    console.log(textStatus);
                    console.log(error);
                    console.log(jqXHR);
                    viewModel.notifier.error(viewModel.t('Saving failed. Please try again in a few moment or contact us.'));
                })
                .always(function() {
                    saveCmd.enabled(true);
                }
            );

            // and this is the alternative by sending it as POST but the html content as blob.
            // you can ignore and remove this part.

            var formData = new FormData();
            formData.append('csrf_token', 'you csrf value here'); // this only applies if your need csrf token
            formData.append('metadata', viewModel.exportMetadata());
            formData.append('json', viewModel.exportJSON());

            // I intended to send the html as blob
            // JavaScript file-like object
            var html = new Blob([viewModel.exportHTML()], { type: 'text/html'});
            formData.append('html', html);

            // You can use the simple $.post() instead of this.
            $.ajax({
                url: 'you url here',
                type: 'POST',
                data: formData,
                processData: false,  // tell jQuery not to process the data
                contentType: false,   // tell jQuery not to set contentType
                beforeSend: function() {
                    viewModel.notifier.info(viewModel.t('Saving please wait...'));
                },
                success: function(){
                    viewModel.notifier.success(viewModel.t('Successfully saved.'));
                },
                error: function(jqXHR, textStatus, error) {
                    console.log(textStatus);
                    console.log(error);
                    console.log(jqXHR);
                    viewModel.notifier.error(viewModel.t('Saving failed. Please try again in a few moment or contact us.'));
                },
                complete: function() {
                    saveCmd.enabled(true);
                }
            });
        };

        viewModel.save = saveCmd;
    },
];

var ok = Mosaico.init(yourOptionsHere, plugins);

if (!ok) {
    alert('Something went wrong initializing the editor. Please try again or contact us!');
}

[notchris]

This feature alone would make this application 100x more useful.

[CaptainHypertext]

@jbaltero Thank you for posting that plugin, it is a lifesaver and super educational.

[bago]

@jbaltero you can use Mosaico.start method instead of Mosaico.init if you don't want to enable the "localstorage" built-in plugin login.

[GLenotre]

Newbie dev here. How do I implement this plugin? Should I just replace the saveCmd.execute = function() in mosaico.js (lines 9907-9917)?

[CaptainHypertext]

@GLenotre I was just working on this myself. You're supposed to put it in your editor.html file where Mosaico gets initialized. See line 40 where the plugins variable is commented out. Put the plugins array right there, and it will be included when Mosaico is initialized.

BUT I was actually having trouble getting it to work. The save button still isn't firing the plugin function, and I'm getting no errors. I don't know if there's anything further you have to do to get it to fire beyond what's posted up there, but any help from @jbaltero or @bago would be infinitely appreciated.

[jbalatero]

@GLenotre , @CaptainHypertext is right, go check editor.html line 40 and you should be able to get how it was implemented.

@CaptainHypertext what do you mean by save button isn't firing the plugin function? You mean the ajax? Have you debugged it by a simple jquery alert();?

[CaptainHypertext]

Thanks for replying,
Yes I have been debugging it. Here's what I have, copied from yours and modified a little bit:

var plugins = [
// plugin for integrating save button
function(viewModel) {
    console.log('PROCESS PLUGIN');

    var saveCmd = {
        name: 'Save', // l10n happens in the template
        enabled: ko.observable(true)
    };

    saveCmd.execute = function() {
        console.log('FIRE SAVE');
        saveCmd.enabled(false);
        viewModel.metadata.changed = Date.now();
        if(typeof viewModel.metadata.key == 'undefined') {
            viewModel.metadata.key = 'abcd12345';
        }

        // This is the simplest for sending it as POST
        // append postData with csrfToken
        var postData = {
            csrf_token: '0YDRwO90s3MzlnBDOB3ISx0qZ9vpwREjIPCEGOZ8', // this is only required if your back-end requires csrf token
            metadata: viewModel.exportMetadata(),
            content: viewModel.exportJSON(),
            html: viewModel.exportHTML()
        };

        $.post('http://sm.localhost/template/save', postData)
            .done(function() {
                viewModel.notifier.success(viewModel.t('Successfully saved.'));
            })
            .fail(function(jqXHR, textStatus, error) {
                console.log(textStatus);
                console.log(error);
                console.log(jqXHR);
                viewModel.notifier.error(viewModel.t('Saving failed. Please try again in a few moments or contact us.'));
            })
            .always(function() {
                saveCmd.enabled(true);
            });
    };

    viewModel.save = saveCmd;
}
];
var ok = Mosaico.init({
imgProcessorBackend: basePath + '/image',
emailProcessorBackend: basePath + '/download',
titleToken: "MOSAICO Responsive Email Designer",
fileuploadConfig: {
  url: basePath + '/upload'
}
}, plugins);

Mosaico is loading just like normal, and when I click Save, it seems to just do the normal save function, and fires no ajax, and logs no FIRE SAVE. PROCESS PLUGIN logs though.

[jbalatero]

@CaptainHypertext Have you checked your URL? make sure it doesn't contain a hash character like http://youurl.com/editor.html#hashere.

[bago]

If you don't want the "localStorage" plugin in the way just use Mosaico.start instead of Mosaico.init.

Mosaico.start({ yourmosaicooptions }, 'yourtemplatepath', undefined /* metadata */, undefined /* model */, extensions);

[CaptainHypertext]

Ah, yes, thanks guys. I think I'm starting to understand this a bit better.

Yes, I was still using the hash in the url. I removed that and started using the Mosaico.start function. It's firing the plugin function now.

On the other hand, I've lost the Test and Download buttons (I can live without them for now, though).

[bago]

Do you see the download button? Does everything else works? Do you see errors in the browser javascript console?

Add a console log after "viewModel.download = downloadCmd;" so you know that the code is executed.

[notchris]

@ShahVivek
I can confirm my template backend implementation is working, attempt building that using the modified files and let me know if you're still having trouble.

[ShahVivek]

@notchris I checked your code , but actually i am implementing it in .net.

[ShahVivek]

@bago I am not able to see download button. Everything else is works fine. I added console log after "viewModel.download = downloadCmd;" and it prints successfully.
But yes there are some errors in browser javascript console. I am trying to solve it and get you back.
Here is list of errors.

Missing initialization hash, redirecting to main entrypoint default.html:133:5
translateTemplate: timer started mosaico.min.js:1427
Cannot apply default value to variable when using expressions mosaico.min.js:1391:1079
ERROR: found unexpected -ko- attribute in compiled template anonymous-4586 , you probably mispelled it: Array [ "data-ko-display", "-ko-attr-width" ] mosaico.min.js:1422:3796

ERROR: found unexpected -ko- attribute in compiled template sideArticleBlock-show , you probably mispelled it: Array [ "-ko-attr-width" ] mosaico.min.js:1422:3796

translateTemplate: 282.61ms mosaico.min.js:1427
generateModel: timer started mosaico.min.js:1427
generateModel: 8.09ms mosaico.min.js:1427
generateEditors: timer started mosaico.min.js:1427
TODO EDITOR ignoring longTextStyle.linksColor property because it is not used by the template prop: linksColor type: styler level: 2 preheaderBlock mosaico.min.js:1373:4703
TODO WARN Missing label for object  theme mosaico.min.js:1373:5340
generateEditors: 37.88ms mosaico.min.js:1427
initializeViewmodel: timer started mosaico.min.js:1427
initializeViewmodel: 1.28ms mosaico.min.js:1427
This is my log after viewModel.download = downloadCmd line  default.html:120:9
applyBindings: timer started mosaico.min.js:1427
applyBindings: 1015.37ms mosaico.min.js:1427

[bago]

You probably altered the template code and broke it: "found unexpected -ko- attribute in compiled template sideArticleBlock-show". Don't mix too many changes if you want to be able to debug. So, try altering the save button without altering the rest of mosaico or the template.

[notchris]

If I take the time to write a tutorial for implementation with different backends, can it be posted on the main page?

[bago]

Can't promise anything before I see the result.
Of course if I think it will be useful I'll be happy to add it to the wiki:
https://github.com/voidlabs/mosaico/wiki/Serving-Mosaico

[mattghall]

I have successfully implemented a full PHP backend with saving and loading all done server side. I will issue a pull-request next week after some more testing.

[webportpl]

Do you have this backend?

[janober]

+1 Also interested in the php backend with storage

[notchris]

My example is a working php backend with storage @janober @webportpl

[kattapug]

@mattghall I will be interested in who you successfully implemented a full PHP backend with saving and loading all done server side.

[gordon-matt]

When I try using the .start() method instead of the init() method, I get the following error:
Missing initialization hash, redirecting to main entrypoint

and tracked it back to this error:
Error: Unable to process binding "template: function(){return 'main' }"
Message: Cannot find template with ID main

My code is as follows:

plugins = [
    // plugin for integrating save button
    function (viewModel) {
        var saveCmd = {
            name: 'Save',
            enabled: ko.observable(true)
        };

        saveCmd.execute = function () {
            saveCmd.enabled(false);
            viewModel.metadata.changed = Date.now();
            if (typeof viewModel.metadata.key == 'undefined') {
                var rnd = Math.random().toString(36).substr(2, 7);
                viewModel.metadata.key = rnd;
            }

            // This is the simplest for sending it as POST
            var postData = {
                //csrf_token: 'yourCsrfValueHere', // this is only required if your back-end requires csrf token
                metadata: viewModel.exportMetadata(),
                content: viewModel.exportJSON(),
                html: viewModel.exportHTML()
            };

            $.post('/mosaico/save', postData)
                .done(function () {
                    viewModel.notifier.success(viewModel.t('Successfully saved.'));
                })
                .fail(function (jqXHR, textStatus, error) {
                    console.log(textStatus);
                    console.log(error);
                    console.log(jqXHR);
                    viewModel.notifier.error(viewModel.t('Saving failed. Please try again in a few moments or contact us.'));
                })
                .always(function () {
                    saveCmd.enabled(true);
                });
        };

        viewModel.save = saveCmd;
    },
];

var ok = Mosaico.start({
    imgProcessorBackend: basePath + '/img/',
    emailProcessorBackend: basePath + '/dl/',
    titleToken: "MOSAICO Responsive Email Designer",
    //onSave: function (saveObject) { alert('hi'); },
    fileuploadConfig: {
        url: basePath + '/upload/'
    }
}, '/templates/versafix-1/template-versafix-1.html', undefined, undefined, plugins);

Any help much appreciated

[athulhere]

Here is a PHP/MySQL solution that saves / loads the template data from the backend. You still need to build Mosaico normally, but this example should help some people out. I also migrated Testing / Exporting away from localStorage. PHPMailer is also used in place of NodeMailer. You can find my fork here: Mosaico + Template Backend

You are just awesome . Did the most of it and that was a quick starter.

[notchris]

@athulhere Glad it helped! I haven't updated it in years so I'm happy it is still working.