marjinal1st / medium-editor-rails Goto Github PK

I'm using turbolinks and the jquery.turbolinks gem with rails 4. I have the following code based on the medium-test app which doesn't work when I click a link to a new page:

$(document).ready ->    
  editor = new MediumEditor(".editable");
  $(".editable").on('input', function() {
    $("#position_" + $(this).attr("data-field-id")).val($(this).html());
  });

It works well after page reload however. How do I make it turbolinks compatible?

Hey great Rails wrapper, just saved me a couple days (or weeks) getting medium-editor into rails.
Does anyone have any sample controller ruby code and subscribe js code to actually get the changes back into a Rails model?

Hi!
The bug is reproducible with:
https://github.com/marjinal1st/medium-test

Changing page prevents the tooltip from being displayed.

Workaround:

<script>
  var editor = new MediumEditor('.editable');
  editor.options.elementsContainer = false;
  $('.editable').bind('input propertychange', function(){
    $("#post_" + $(this).attr("data-field-id")).val($(this).html());
  });
</script>

I still don't know if the workaround is clean enough and doesn't produce unwanted bugs.

Any plans to upgrade to 5.22.1 (latest medium-editor release) soon?

I'm trying to use the medium-editor-insert-plugin and it doesn't work with 5.22.0, but does work with 5.22.1.

How do I use this with a form. Is there a predefined method?, or the best approach is with jQuery?

Something is adding " " to the output text and all the html tags inside don't render it correctly.

<div class="editable">
     <p>"Some <b>text</b> here."</p>
</div>

I try to change some configuration but nothing is working.
Some idea about what can produce this behavior?

Versions

• rails (5.0.6)
• medium-editor: medium-editor-rails (2.3.1)
• browser: Chrome 61.0.3163.100

https://github.com/yabwe/medium-editor/releases

I'm not sure if this dependency was added on purpose, I'm backdating to 0.9.1 for now, just thought I'd let you know.

See c949af6#diff-a4d301e47cb1e4c47485d7dc49e533dfR61, there is a class without a namespace..

The change in gem file for railties from '>= 3.0' to '~> 3.0' means this gem can no longer be utilized in Rails 4.x or later projects.