Requesting the addition of URL encoding in the string formatter. My current use case is in server connect, creating a link sent via email with values provided by users using a front-end form.

URLencode formatter was implemented in Wappler 2.6.4

on the server connect you can use Base 64 encoding/decoding. I have tried it and it worked pretty well However, there is no solution to do a similar action on the frontend

How do YOu decode? Everyone says you can do stuff but there is no documentation showing you how.

How did you overcome this @mebeingken ? Custom formatter I'm assuming? [image] Elias: on the server connect you can use Base 64 encoding/decoding. That won't work for all cases. The "+" symbol which is part of base64 is not readable in URL. Note: Just saw in another post that you realized th…

For those PHP users here you have a custom formatter for SC. <?php function formatter_urlencode($val) { return urlencode($val); } You can then format any string by appending .urlencode()

Hey Jon, Yes custom formatter is the way to go. This request is from a dark time when I was unaware of such magic, so I did a find/replace since I just wanted to be able to have a plus symbol in a url. :slight_smile:

Interesting @JonL … :slight_smile: Could you please detail where you would hook such a formatter to make it accessible within server connect ? Many thanks !

Wappler Community

URL encoding

Feature Request

Teodor March 9, 2020, 3:46pm 8

Please check:

Slugfy() Formater does not accept accentuation Bugs

If you use your own custom formatter it is better to place it in a different file and give it a unique name. Now you will loose your changes when there is an update in the current formatters. Create a file like custom.php or myFormatters.php in the formatters folder. <?php namespace lib\core; function formatter_slugify2($val) { if ($val == NULL) return NULL; $a = 'ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖØÙÚÛÜüÝÞßàáâãäåæçèéêëìíîïðñòóôõöøùúûýýþÿŔŕ"!@#$%&*()_-+={[}]/?;:.,\\\'<>°ºª'; $b = 'aaaaaaaceeeeiiii…

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled