Currently content readability is working for single body field of type ckeditor. We should implement it for all textarea, irrespective of entity type and for both plain text and ckeditor.

CommentFileSizeAuthor
#4 implement-for-all-text-area-3130173-4.patch21.52 KBmanojbisht_drupal
#2 implement-for-all-text-area-3130173-1.patch20.51 KBmanojbisht_drupal

Issue fork content_readability-3130173

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

    About issue forks

    Comments

    manojbisht_drupal created an issue. See original summary.

    manojbisht_drupal’s picture

    manojbisht_drupal commented
    Status: Active » Needs review
    StatusFileSize
    new implement-for-all-text-area-3130173-1.patch20.51 KB

    Please find patch attached for the same. Also i think there is some issue with dev branch of project, it is currently showing as 8.x-1.0-dev, while it should be 8.x-1.x

    roragok’s picture

    roragok commented
    Assigned: Unassigned » roragok

    Cool, something I had eventually planned on getting around too. I'll take a look at it this week.

    manojbisht_drupal’s picture

    manojbisht_drupal commented
    StatusFileSize
    new implement-for-all-text-area-3130173-4.patch21.52 KB

    Also when enabling module, it actually is not creating general profile, we have to use install hook.

    roragok’s picture

    roragok commented

    @manojbisht_drupal it should be creating the profile as a default. It has the config shipped for the general profile on fresh installs. the update is only for sites that had it enabled prior.

    roragok’s picture

    roragok commented

    I'm going to think on this a bit more. I think the widget alter is interesting, but I think the goal was to provide one score for the node. not one for each section.

    manojbisht_drupal’s picture

    manojbisht_drupal commented

    @Roragok, It was only applying to a single field (body), instead it would be great, if we have separate block for textarea. In that way content manager can check content readability of a textarea.

    jaysonjaynes’s picture

    jaysonjaynes commented

    I'm working on a website that's using blocks and Paragraphs to insert editorial design components. I want to be able to scan those textareas and don't use the traditional Body field. Will this patch work on the most-recent release or is there a plan to include this? Or am I missing some way to configure the module to look at those as well?