Wallabag: Add ability to edit imported contents

[amereservant]

Issue details

This is a feature request. I'm not sure why this doesn't already exist, but I would like the ability to edit the contents of an imported article. Sometimes it doesn't import the contents correctly, or an image URL isn't correct, or I'd like to add content to it, etc. and that currently isn't possible.

It would be nice to add an edit button, like the one for the title, so the contents can be edited. A WYSIWYG editor isn't even necessary. Editing the raw code would work fine.

Thank you!

[rabyte]

I like this idea very much. This happens to me a lot, too. E.g. it would be great beeing able to remove messed up content or unnecessary footers.

I also was wondering if it is not possible already since editing the title works.
If not I guess it should be straight forward to take over the "title editing function" for the content?

Regards

[slavniyteo]

This feature doesn't seem to have a high priority so I'll write here a simple workaround to edit article's content.

There is a form to modify a title of article and it's original url. You can get there by clicking a pencil icon next to article's title. We'll modify this form.

---

Add two pieces of code: to EditEntryType.php

At the top:

use Symfony\Component\Form\Extension\Core\Type\TextareaType;

At the buildForm function, for example between 'title' and 'url' fields:

->add('content', TextareaType::class, [
    'required' => true,
    'label' => 'Content',
    'attr' => [ 'style' => 'height: 20em; padding: 10px' ]
]

After you save the file you can refresh the page and get additional field with content of the article.

Now we can modify the content of article in plain html format. I use it to fix some parsing issues. It is very useful.

[lizyn]

Add two pieces of code: to EditEntryType.php

At the top:

use Symphony\Component\Form\Extension\Core\Type\TextareaType;

@slavniyteo , Is there a typo? I think it should be use Symfony\…\… instead.

[slavniyteo]

Yes, it should be Symfony. Sorry for broken code.

вт, 25 февр. 2020 г., 17:53 lizyn [e-mail]:

Add two pieces of code: to EditEntryType.php
https://github.com/wallabag/wallabag/blob/master/src/Wallabag/CoreBundle/Form/Type/EditEntryType.php

At the top:

use SymphonyComponentFormExtensionCoreTypeTextareaType;

@slavniyteo https://github.com/slavniyteo , Is there a typo? I think it
should be use Symfony…… instead.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/wallabag/wallabag/issues/2321?email_source=notifications&email_token=AEOGMNR3BZCDZZJNPTI6NOLREUWFJA5CNFSM4CROUIV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEM4IDNA#issuecomment-590905780,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEOGMNRXBSELFHSDRMAJASTREUWFJANCNFSM4CROUIVQ
.

[3bbing]

Excellent addition! implemented it too. Thanks! I hope this gets added to the repo.
It also helps for (pdf) content that did not pull correctly or not at all - can just insert some textblocks that were remarkable from e. g. (journal) article behind a paywall that needs a library VPN or similar.

@slavniyteo did you submit it?

To make it fit seamlessly, also change the View. For Material that is
CoreBundle/Resources/views/themes/material/Entry/edit.html.twig

Insert the new _content edit_ element after the last element before the save button. At least that's where I wanted it:

<div class="input-field s12">
         {{ form_label(form.origin_url) }}
          {{ form_widget(form.origin_url) }}
 </div>

<div class="input-field s12">
       {{ form_label(form.content) }}
       {{ form_widget(form.content) }}
 </div>
<br>

{{ form_widget(form.save, {'attr': {'class': 'btn waves-effect waves-light'}}) }}

Don't forget to flush cache.

Just added as a dirty hack and not ready for a pull, it's of course nicer with WYSIWYG as the OP suggested. If you want it, just paste these two things to your preferred theme (so e. g. the same file as above) :

<script src="https://cdn.tiny.cloud/1/no-api-key/tinymce/5/tinymce.min.js" referrerpolicy="origin"></script>
(or upload yourself somewhere)
and:

<script type="text/javascript">
  tinymce.init({
    selector: '#entry_content'
  });
  </script>

In the long run, probably bloating wallabag a bit, e.g. changing to FOSCKE might be a valuable option. Or adding tinymce directly and properly adding it to the build. To be honest it would take me some time to to understand the structure of wallabag so I did just go with the hack. But it would be awesome to have it implemented properly too.
If someone gives me a hint where to put the files etc I'll give it a go. But maybe you're quicker doing it than explaining it to me ;-)