Jump to content
Martijn Geerts

Markup RSS Enhanced

Recommended Posts

This Module didn't have it's real own thread, now it has :-)


Markup RSS Enhanced

This Module is the enhanced version of Ryan's Markup RSS Module and is completely compatible with it. In addition, this enhanced module supports the usage of enclosures a way of attaching multimedia content to RSS feeds. Give the RSS enhanced module a PageArray of pages and it will render a RSS feed from it. The Module should be used directly from your template file.

In the examples the $rss variable is used for as instance of the module.

$rss = $modules->get("MarkupRSSEnhanced");

Basic usage

In case you only need 1 feed for your site, you need to setup the defaults in the Modules config. then you can use the code below.

$items = $pages->find("limit=10, sort=-modified");  // $items, PageArray of Pages
$rss = $modules->get("MarkupRSSEnhanced");          // load the module
$rss->render($items);                               // render the feed 

Setup channel elements

The channel element describes the RSS feed. There are 3 required channel elements:

  1. title $rss->title
  2. link $rss->url
  3. description $rss->description
$rss->title = '';       // (string) Title of the feed.
$rss->url = '';         // (string) URL of the website this feed lives. Example: http://www.your-domain.com/
$rss->description = ''; // (string) Phrase or sentence describing the channel.
$rss->copyright = '';   // (string) Copyright notice for content in the channel.
$rss->ttl = '';         // (string/integer) Number of minutes that how long it can be cached.

Setup item elements

Every page from the PageArray use the item element.

$rss->itemTitleField = '';             // Fieldname to get value from
$rss->itemDescriptionField = '';       // Fieldname to get value from
$rss->itemDescriptionLength = '';      // Default 1024
$rss->itemEnclosureField = '';         // Fieldname to get file/image from
$rss->itemDateField = '';              // Fieldname to get data from
$rss->itemLinkField = '';              // Fieldname to get URL from or don't set to use $page->httpUrl
$rss->itemAuthorField = '';            // If email address is used, itemAuthorElement should be set to author
$rss->itemAuthorElement = 'dc:creator' // may be 'dc:creator' or 'author'

Item element enclosure

RSS enclosures are a way of attaching multimedia content to RSS feeds. All files with proper mime types are supported. If you asign an image field to the itemEnclosureField there are 3 extra options you could set.

  1. width The width of the image.
  2. height The height of the image.
  3. boundingbox Checking boundingbox will scale the image so that the whole image will fit in the specified width & height. This prevents cropping the image
$rss->boundingbox = 1 // (integer) 1 or 0, on or off
$rss->width = 400;    // (integer) Max width of the image, 0 for proportional
$rss->height = 300;   // (integer) Max height of the image, 0 for proportional 

Prettify the feed

Prettifying the feed is not supported by all clients.

$rss->xsl = ''; // path to xls file
$rss->css = ''; // path to css

Download on GitHub

View on the modules directory

  • Like 9

Share this post


Link to post
Share on other sites

Hi, I'm trying using this module with latest PW release but I got this error:

Error: Call to undefined function finfo_open() (line 253 of /home/ilpepe/public_html/site/modules/MarkupRSSEnhanced.module)

Share this post


Link to post
Share on other sites

What kind of environment you're running this?

Edited by Martijn Geerts
(looked at the same link as Adrian... tnx Adrian)

Share this post


Link to post
Share on other sites

so it's question of php...ok I'll try to install this fileinfo.so extension, thanks

  • Like 1

Share this post


Link to post
Share on other sites

@Martijn: maybe a check on install of the module or in the config-screen?

if( !extension_loaded('fileinfo') && !@dl('fileinfo') ) {
    // missing PHP extension
    ...
}
  • Like 3

Share this post


Link to post
Share on other sites

@Sevarf2, would you mind to try the following ?

Add a new method somewhere in the module:

    /**
     * Return Mimetype
     *
     */
    protected function mimetype($filename) {

        if (function_exists('finfo_open')) {
            $info = finfo_open(FILEINFO_MIME_TYPE);
            $mime = finfo_file($info, $filename);
            finfo_close($info);
        } else if (function_exists('mime_content_type')) {
            $mime = mime_content_type($filename);
        } else {
            $mime = 'application/octet-stream';
        }

        return $mime;
    }
And then change the code for the mime type:
/* Disable this: */
// $info = finfo_open(FILEINFO_MIME_TYPE);
// $mime = finfo_file($info, $field->filename);
// finfo_close($info);

/* add this: */
$mime = $this->mimetype($field->filename);

  • Like 2

Share this post


Link to post
Share on other sites
The Module should be used directly from your template file.

What template file? I have rss.php in my templates directory. How is the feed accessed? I need to make a blank RSS template in PW?

Never mind that worked

Share this post


Link to post
Share on other sites

Is there a way to append $rss->itemLinkField = ''; ? For use with campaign url or other tracking methods.

E.g. such as this:

$rss->itemLinkField = 'httpUrl' . '?utm_source=RSS_Feed&utm_medium=RSS&utm_campaign=RSS_Syndication';

Except that this wont work … I have also tried:

$rss->itemLinkField = 'httpUrl';
$rss->itemLinkField .= '?utm_source=RSS_Feed&utm_medium=RSS&utm_campaign=RSS_Syndication';

Just to show what is not working, and what I am trying to achieve.

Share this post


Link to post
Share on other sites

Hey, I sent a pull request to fix parsing error with message 'unicode entity not defined' when using author field that contains unicode (Turkish) characters. I also added atom namespace and atom:link property under channel to pass W3C validation.

Share this post


Link to post
Share on other sites

I was just using this module "MarkupRSSEnhanced" to generate my rss feed.
My RSS feed specifically pulls data from 2 different templates.

Though both these templates have the same title field called 'Title', their description field varies (one has r_desc and the other has e_desc)

Is there a way where I can configure the model in such a way to pick up either of r_desc or e_desc (whichever is present on the template)
I also have the same problem with adding the image to rss also since one has field name r_pic and the other has e_pic.
PS-I cannot change the field names since I recently took over the project I am working on and it has been implemented by many others before me.
 

Edited by kongondo
Moderator Note: Moved your post to the module's support forum

Share this post


Link to post
Share on other sites

@Alex CA you can change those fields when you instantiate the module:

$rss = $modules->get("MarkupRSSEnhanced");
$rss->title = 'Title for this feed';
$rss->description = 'Description for this feed';
$rss->itemDescriptionField = 'r_desc'; // set your specific field here, e.g. r_desc or e_desc
$rss->itemEnclosureField = 'r_pic'; // or e_pic

$limit = 8;
$items = $page->children("limit={$limit}, sort=-publish_start");
$rss->render($items);

 

  • Like 1

Share this post


Link to post
Share on other sites

@Macrura
I did see how to instantiate the module. But how do I make module pick up r_desc and r_pic when it's generating the RSS feed when I select pages with template='Template1'  and then make it pick e_desc and e_pic when the template is='Template2'.
My condition for the page selector for my RSS feed is $pages->find("template=". $template1 ."|". $template2.", sort=-modified,limit=20");

Share this post


Link to post
Share on other sites

I think if i was faced with your situation, the first thing i would do (after cursing out the developer who setup that field structure) would be to add a runtime field and see if the module is able to pick up that: (in ready.php for example):

wire()->addHookProperty('Page(template=Template1)::rss_desc', function($event) {
    $page = $event->object;
    $event->return =  $page->r_desc;
});

wire()->addHookProperty('Page(template=Template2)::rss_desc', function($event) {
    $page = $event->object;
    $event->return =  $page->e_desc;
});

wire()->addHookProperty('Page(template=Template1)::rss_pic', function($event) {
    $page = $event->object;
    $event->return =  $page->r_pic;
});

wire()->addHookProperty('Page(template=Template2)::rss_pic', function($event) {
    $page = $event->object;
    $event->return =  $page->e_pic;
});

Or I would just roll my own RSS feed using a class..

Share this post


Link to post
Share on other sites

@Macrura
Thanks for all the help. The addHookProperty() did not work. Another simple solution (I should've tried it earlier ) is to directly use 

$rss->itemDescriptionField='e_desc|r_desc'

Share this post


Link to post
Share on other sites

I do have another task what I am trying to solve with the help of RSS module.

Suppose my rss feed is based on a page which uses template A and it is pulling data from all templates on the website which has template B (which is say b_title and b_description). Now, I have another field in template B which has a filed type Page(lets called this field b_page) which essentially is for pages of another template (let's call it template C).This template C consists of a field called c_img. Now I want my rss feed template(A.php) to pull the title and description from template B and the image for the rss feed from template C. How do I achieve the retrieval of the image? 
I have tried representing my problem with a picture below.
 

My current code looks similar to this:

<?php

// rss-feed.php template file
// retrieve the RSS module
$rss = $modules->get("MarkupRSSEnhanced");
// configure the feed. see the actual module file for more optional config options.
$rss->title = "Latest updates";
$rss->description = "The most recent pages ";



$items = $pages->find("tempalte=". $templateB .", sort=-modified,limit=20");
$rss->itemDescriptionField = 'b_Desc';
$rss->itemEnclosureField = 'b_page[0]->c_img'; // we take the first one since this field can consist an array of pages         
// send the output of the RSS feed, and you are done
$rss->render($items); 

?>


 

s.png

Share this post


Link to post
Share on other sites

If i were faced with your issue, i would change the structure of the pages and all of that, it doesn't make sense to me; i guess it must make complete sense to someone else, whoever set it up that way, but obviously the module author(s) never accounted for this sort of setup;

You can also just roll your own RSS feed, then you don't need to be straddled with module interactions; it's not that hard to just make your own RSS class that takes into account any arbitrary structure and outputs it how you want; you could also just extend the module itself and modify the Module Class to a new one, and work from there until it works...

  • Like 1

Share this post


Link to post
Share on other sites

Hi, I just installed the enhanced module on the latest version of PW, even though it is not strictly compatible.

I am trying to set up an image from an images field as enclosure like this:

$rss->itemEnclosureField = 'post_images';

I would like it to pick the first image from the field. However, the RSS feed is not changed and there are no errors in the error log. I made sure to call the rss with:

$rss = $modules->get("MarkupRSSEnhanced");

@Macrura any ideas?

Share this post


Link to post
Share on other sites

did you set the enclosure field in the module settings; i know the module says you can set it from the api, just wondering what effect that has; also make sure the feed is not cached...

  • Like 1

Share this post


Link to post
Share on other sites

@Macrura thanks for the help. Turns out it does work, but I was doing some images substitutions in another file which made me think I was getting incorrect results (was substituting for default picture when there was none, and RSS omits the enclosure tag if there aren't any). 

Share this post


Link to post
Share on other sites
1 hour ago, Martijn Geerts said:

Have not used it with PW3, now-a-days I use DomDocument

 

Could you please share a bit more. A simple gist would be perfect))

Share this post


Link to post
Share on other sites

Hi @Ivan Gretsky

The code I gonna paste here is a copy/paste from other work so there might be glitches. And you should use your own fieldnames etc.
What you can do is:

  • Create a template and template file for RSS name it rss.
    • Template not ending with slash. (Name a the page that uses this template should end with .rss
  • In the template file something like:
<?php namespace ProcessWire;

use DomDocument;
use DOMElement;
use DateTime;

header('Content-Type: application/xml; charset=utf-8', true);
date_default_timezone_set("Europe/Amsterdam");
setlocale(LC_MONETARY, 'nl_NL');

/** @var \DateTime */
$date = new DateTime('today midnight');

$items = $pages->find("YOUR SEARCH SELECTOR DON'T FORGET TO SET LIMIT");

/**
 * Start XML Object
 *
 * @var DOMDocument
 */
$dom = new DOMDocument("1.0", "UTF-8");

$root = $dom->appendChild($dom->createElement("rss"));
$root->setAttribute("version","2.0");
$root->setAttribute("xmlns:dc","http://purl.org/dc/elements/1.1/");
$root->setAttribute("xmlns:content","http://purl.org/rss/1.0/modules/content/");
$root->setAttribute("xmlns:atom","http://www.w3.org/2005/Atom");

$link = $dom->createElement("atom:link");
$link->setAttribute("href", $page->httpUrl());
$link->setAttribute("rel","self");
$link->setAttribute("type","application/rss+xml");

$channel = $root->appendChild($dom->createElement("channel"));
$channel->appendChild($link);
$channel->appendChild($dom->createElement("title", $page->title));
$channel->appendChild($dom->createElement("description", $page->description));
$channel->appendChild($dom->createElement("link", $page->httpUrl));
$channel->appendChild($dom->createElement("language", "nl"));
$channel->appendChild($dom->createElement("lastBuildDate", $date->format(DateTime::RFC2822)));
$channel->appendChild($dom->createElement("generator", "DomDocument, ProcessWire"));

foreach ($items as $item) {
	$dateInt = (int) $item->getUnformatted("date_start");
	if (!$dateInt) $dateInt = (int) $item->modified;

	/** @var DateTime $date */
	$date = new DateTime(date("Y-m-d", $dateInt));
	/** @var DOMElement $parent */
	$itemParent = $dom->createElement("item");

	// Plain tags
	$elements = array(
		$dom->createElement("title", $item->title),
		$dom->createElement("description", htmlspecialchars($item->description)),
		$dom->createElement("link", $item->httpUrl()),
	);

	// For closure
	$image = $images->first();
	$image = $image->size(600, round(600 * 9 / 16));
	$mime = $image->ext === 'jpg'
		? "image/jpeg"
		: "image/png";

	$enclosure = $dom->createElement("enclosure");
	$enclosure->setAttribute('url', $image->httpUrl());
	$enclosure->setAttribute('type', $mime);
	$enclosure->setAttribute('length', $image->filesize);
	$elements[] = $enclosure;

	foreach ($elements as $element) $itemParent->appendChild($element);

	$channel->appendChild($itemParent);
}

echo $dom->saveXML();

When you want to place the RSS in the root you could hide it for non superusers:

/**
 * Hide RSS page
 *
 * Hide RSS page int pagelist for NON superusers
 *
 */
$wire->addHookBefore("ProcessPageList::find", function (HookEvent $event) {
	/** @var User $user */
	$user = $this->wire("user");

	if ($user->isSuperuser()) return;

	/** @var Page $page */
	$page = $event->arguments(1);
	/** @var string $baseSelector */
	$baseSelector = $event->arguments(0);

	$selector = $baseSelector . ", template!=rss";
	$event->arguments(0, $selector);
});

Hope this could be a good starting point for you.

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By joshua
      ---
      Module Directory: https://modules.processwire.com/modules/privacy-wire/
      Github: https://github.com/blaueQuelle/privacywire/
      Packagist:https://packagist.org/packages/blauequelle/privacywire
      Module Class Name: PrivacyWire
      Changelog: https://github.com/blaueQuelle/privacywire/blob/master/Changelog.md
      ---
      This module is (yet another) way for implementing a cookie management solution.
      Of course there are several other possibilities:
      - https://processwire.com/talk/topic/22920-klaro-cookie-consent-manager/
      - https://github.com/webmanufaktur/CookieManagementBanner
      - https://github.com/johannesdachsel/cookiemonster
      - https://www.oiljs.org/
      - ... and so on ...
      In this module you can configure which kind of cookie categories you want to manage:

      You can also enable the support for respecting the Do-Not-Track (DNT) header to don't annoy users, who already decided for all their browsing experience.
      Currently there are four possible cookie groups:
      - Necessary (always enabled)
      - Functional
      - Statistics
      - Marketing
      - External Media
      All groups can be renamed, so feel free to use other cookie group names. I just haven't found a way to implement a "repeater like" field as configurable module field ...
      When you want to load specific scripts ( like Google Analytics, Google Maps, ...) only after the user's content to this specific category of cookies, just use the following script syntax:
      <script type="text/plain" data-type="text/javascript" data-category="statistics" data-src="/path/to/your/statistic/script.js"></script> <script type="text/plain" data-type="text/javascript" data-category="marketing" data-src="/path/to/your/mareketing/script.js"></script> <script type="text/plain" data-type="text/javascript" data-category="external_media" data-src="/path/to/your/external-media/script.js"></script> <script type="text/plain" data-type="text/javascript" data-category="marketing">console.log("Inline scripts are also working!");</script> The data-attributes (data-type and data-category) are required to get recognized by PrivacyWire. the data-attributes are giving hints, how the script shall be loaded, if the data-category is within the cookie consents of the user. These scripts are loaded asynchronously after the user made the decision.
      If you want to give the users the possibility to change their consent, you can use the following Textformatter:
      [[privacywire-choose-cookies]] It's planned to add also other Textformatters to opt-out of specific cookie groups or delete the whole consent cookie.
      You can also add a custom link to output the banner again with a link / button with following class:
      <a href="#" class="privacywire-show-options">Show Cookie Options</a> <button class="privacywire-show-options">Show Cookie Options</button>  
      I would love to hear your feedback 🙂
      CHANGELOG
      You can find the always up-to-date changelog file here.
    • By joshua
      As we often use Matomo (former known as Piwik) instead of Google Analytics we wanted to embed Matomo not only in the template code but also via the ProcessWire backend.
      That's why I developed a tiny module for the implementation.
      The module provides the possibility to connect to an existing Matomo installation with the classical site tracking and also via the Matomo Tag Manager.
      If you have also PrivacyWire installed, you can tell MatomoWire to only load the script, if the user has accepted cookies via PrivacyWire.
      To offer an Opt-Out solution you can choose between the simple Opt-Out iFrame, delivered by your Matomo installation, or a button to choose cookies via PrivacyWire.
      You'll find the module both in the module directory and via github:
      ProcessWire Module Directory MatomoWire @ GitHub MatomoWire @ Packagist ->installable via composer require blauequelle/matomowire I'm looking forward to hear your feedback!


    • By Robin S
      If your module has a lot of config fields you might want to divide them into groups inside a tabbed interface. Here is a demonstration module showing how this can be done.
      https://github.com/Toutouwai/ModuleConfigTabs

      Thanks to @kixe for providing my starting point in this forum topic.
    • By FireWire
      Hello community!

      I want to share a new module I've been working on that I think could be a big boost for multi-language ProcessWire sites.

      Some background, I was looking for a way for our company website to be efficiently translated as working with human translators was pretty laborious and a lack of updating content created a divergence between languages. I, and several other devs here, have talked about translation integrations and have recognized the power that DeepL has. DeepL is an AI deep learning powered service that delivers translation quality beyond any automated service available. After access to the API was opened up to the US, I built Fluency, a DeepL translation integration for ProcessWire.
      Fluency brings automated translation to every multi-language field in the admin, and also provides a translation tool allowing the user to translate their text to any language without it being inside a template's field. With Fluency you can:
      Translate any plain textarea or text input Translate any CKEditor content (yes, with markup) Translate page names for fully localized URLs on every page Translate your in-template translation function wrapped strings Translate modules DeepL offers translations to the following languages: English (US), English (UK), German, French, Spanish, Portuguese (EU), Portuguese (Brazil, Italian, Dutch, Polish, Russian, Japanese, Chinese (Simplified)
      Installation and usage is completely plug and play. Whether you're building a new multi-language site, need to update a site to multi-language, or simply want to stop manually translating a site and make any language a one-click deal, it could not be easier to do it. Fluency works by having you match the languages configured in ProcessWIre to DeepL's. You can have your site translating to any or all of the languages DeepL translates to in minutes (quite literally).
      Let's break out the screenshots...
      When the default language tab is shown, a message is displayed to let users know that translation is available. Clicking on each tab shows a link that says "Translate from English". Clicking it shows an animated overlay with the word "Translating..." cycling through each language and a light gradient shift. Have a CKEditor field? All good. Fluency will translated it and use DeepL's ability to translate text within HTML tags. CKEditor fields can be translated as easily and accurately as text/textarea fields.

      Repeaters and AJAX created fields also have translation enabled thanks to a JavaScript MutationObserver that searches for multi-language fields and adds translation as they're inserted into the DOM. If there's a multi-language field on the page, it will have translation added.

      Same goes for image description fields. Multi-language SEO friendly images are good to go.

      Creating a new page from one of your templates? Translate your title, and also translate your page name for native language URLs. (Not available for Russian, Chinese, or Japanese languages due to URL limitations). These can be changed in the "Settings" tab for any page as well so whether you're translating new pages or existing pages, you control the URLs everywhere.

      Language configuration pages are no different. Translate the names of your languages and search for both Site Translation Files (including all of your modules)

      Translate all of the static text in your templates as well. Notice that the placeholders are retained. DeepL is pretty good at recognizing and keeping non-translatable strings like that. If it is changed, it's easy to fix manually.

      Fluency adds a "Translate" item to the CMS header. When clicked this opens up a modal with a full translation tool that lets the user translate any language to any language. No need to leave the admin if you need to translate content from a secondary language back to the default ProcessWire language. There is also a button to get the current API usage statistics. DeepL account owners can set billing limitations via character count to control costs. This may help larger sites or sites being retrofitted keep an eye on their usage. Fluency can be used by users having roles given the fluency-translate permission.

      It couldn't be easier to add Fluency to your new or existing website. Simply add your API key and you're shown what languages are currently available for translation from/to as provided by DeepL. This list and all configuration options are taken live from the API so when DeepL releases new languages you can add them to your site without any work. No module updates, just an easy configuration. Just match the language you configured in ProcessWire to the DeepL language you want it to be associated with and you're done. Fluency also allows you to create a list of words/phrases that will not be translated which can prevent items such as brands and company names from being translated when they shouldn't

       
      Limitations:
      No "translate page" - Translating multiple fields can be done by clicking multiple translation links on multiple fields at once but engineering a "one click page translate" is not feasible from a user experience standpoint. The time it takes to translate one field can be a second or two, but cumulatively that may take much longer (CKEditor fields are slower than plain text fields). There may be a workaround in the future but it isn't currently on the roadmap. No "translate site" - Same thing goes for translating an entire website at once. It would be great, but it would be a very intense process and take a very (very) long time. There may be a workaround in the future but it isn't on the roadmap. No current support for Inline CKEditor fields - Handling for CKEditor on-demand hasn't been implemented yet, this is planned for a future release though and can be done. I just forgot about it because I've never really used that feature personally.. Alpha release - This module is in alpha. Releases should be stable and usable, but there may be edge case issues. Test the module thoroughly and please report any bugs via a Gitlab issue on the repository or respond here. Please note that the browser plugin for Grammarly conflicts with Fluency (as it does with many web applications). To address this issue it is recommended that you disable Grammarly when using Fluency, or open the admin to edit pages in a private window where Grammarly may not be loaded. This is an issue that may not have a resolution as creating a workaround may not be possible. If you have insight as to how this may be solved please visit the Gitlab page and file a bugfix ticket.
      Requirements:
      ProcessWire  3.0+ UIKit Admin Theme That's Fluency in a nutshell. A core effort in this module is to create it so that there is nothing DeepL related hard-coded in that would require updating it when DeepL offers new languages. I would like this to be a future-friendly module that doesn't require developer work to keep it up-to-date.
      It's Free
      This is my first real module and I want to give it back to the community as thanks. This is the best CMS I've worked with (thank you Ryan & contributors) and a great community (thank you dear reader). The only cost to use this is a subscription fee for the DeepL Pro API. Find out more and sign up here.
      Download & Feedback
      Download the latest version here
      https://github.com/SkyLundy/Fluency-Translation/archive/main.zip
      Github repository:
      https://github.com/SkyLundy/Fluency-Translation
      File issues and feature requests here (your feedback and testing is greatly appreciated):
      https://github.com/SkyLundy/Fluency-Translation/issues
       
      Thank you! ¡Gracias! Ich danke Ihnen! Merci! Obrigado! Grazie! Dank u wel! Dziękuję! Спасибо! ありがとうございます! 谢谢你!

    • By Robin S
      An inputfield module that brings EasyMDE Markdown editor to ProcessWire.
      EasyMDE is a fork of SimpleMDE, for which there is an existing PW module. Inputfield EasyMDE has a few advantages though:
      EasyMDE seems to be more actively developed than SimpleMDE, which hasn't seen any updates for several years. You can define options for Inputfield EasyMDE. Inputfield EasyMDE can be used in Repeater fields and in custom fields for File/Image fields.  
      Inputfield EasyMDE
      EasyMDE (Easy Markdown Editor) as an inputfield for ProcessWire.
      EasyMDE is a Markdown editor with some nice features, allowing users who may be less experienced with Markdown to use familiar toolbar buttons and shortcuts. More information is at the EasyMDE website.

      Installation
      Install the Inputfield EasyMDE module.
      Usage
      Create a new textarea field, and in the "Inputfield Type" dropdown choose "EasyMDE". Save the field and if you like you can then configure the EasyMDE options for the field as described below.
      To convert Markdown to HTML you can install the core TextformatterMarkdownExtra module and apply the textformatter to the field. Alternatively you can use $sanitizer->entitiesMarkdown() on the field value, e.g.
      echo $sanitizer->entitiesMarkdown($page->your_field_name, ['fullMarkdown' => true]); Configuration
      On the "Input" tab of the field settings you can define EasyMDE options for the field in JSON format. Refer to the EasyMDE documentation for the available options. Keys in the JSON must be surrounded with double quotes.
      Example:
      "toolbar": ["bold", "italic", "heading", "|", "side-by-side"], "sideBySideFullscreen": false  
      https://github.com/Toutouwai/InputfieldEasyMDE
      https://processwire.com/modules/inputfield-easy-mde/
×
×
  • Create New...