Ah, I see now.
I had a similar situation.
I needed to read email and enter it into a database. So, I had an API that would go out and grab the email. But, of course, there were all sorts of dangerous or incorrect characters and I didn’t want to put it my database without fixing it.
There is a lot of debate online about the proper way to sanitize strings or URLs for database entry. So I’ll let you wrestle with “the right way” … But…
There are a few ways to do this.
In Wappler, load the Server Data Bindings on the value you have:
Then, after you did that, click the edit icon:
Then, append .stripslashes to the end of your value.
You might have to make a “value” that grabs your data, and then edit that.
I’m not sure that will work.
ANOTHER METHOD
If you have have some PHP knowledge you could do what I did. Mine was complicated and I couldn’t just do it in Wappler.
You could write your own PHP API file that grabs the information, sanitizes it, then outputs it.
Then use the Wappler API Action (like you’re doing here) to grab the sanitized data.
Or you could use the same API Action you have right now and then make a new API that outputs what you got from Google into your own PHP file.
Then sanitize it, and give it back.
The code would look like this:
<?php
$Message = "https:\/\/lh3.googleusercontent.com\/a-\/AOh14Gjms154fm1hJhTcVFlkVkC7IVI1R-";
$Message = stripslashes($Message);
echo $Message;
?>
Of course, you would replace the URL with a variable, so something like:
<?php
$Message = $VariableFromYourWapplerValue
$Message = stripslashes($Message);
echo $Message;
?>
