I've noticed my generated campaign URL has a "+" in place of what used to be "%20" with campaign names that have spaces. example URLs: (old)...campaign=Uchealth%20Today... (new) ...campaign=Uchealth+Today...
Why this change? Will it change how the URL operates ... or did I accidentally set a preference and didn't know? Thanks for the background and input. I have tried the link and it seems to work fine. But I want to make sure it's operating as it should on the back end before I send out a newsletter to my large list.
Related
I'm trying to add param in the url, like in this example:
https://www.google.com/ > https://www.google.com/search?q=qq
Opening the last link you can see "qq" in the "q" input.
For this site it doesn't work (this is the problem):
https://www.calabriasue.it/assistenza/richiesta-assistenza-e-supporto/
https://www.calabriasue.it/assistenza/richiesta-assistenza-e-supporto/?nome=mario
Can I add url param also in the last one? I need it.
Thanks!
I tried using different input names, different params ecc but it doesn't work.
Google's server side code is designed to generate an HTML document with an input field that is prefilled with the current search term which is reads from the URL. That is why adding q=search+term to the URL populates the input field.
You can't make arbitrary third-party websites prefill inputs. They have to explicitly provide a mechanism to make it possible.
Parameters only work as long as the code for the target website is expecting to handle a parameter named "nome" with a value "mario". In the case of the google website, it is expecting a parameter named "q" and has a form input for it.
Clicking a URL sends a a GET request type, and the target site may only be accepting parameters from a POST request type. You could consider using the application known as "PostMan" to help with that.
Alternately, the target page you are viewing may be forwarded / routed from a different page which accepts parameters.
Has anyone ever used Go Integrator that Nextiva provides to send encoded urls? I have it sending a formatted variable to show the callers phone number, but any percent symbols get changed to an invalid code. Example:
websiteaddress.com/search?query=fieldvalue%3A%%Call\Contact\DisplayTel%
fieldvalue requires the colon (%3A) after to properly search the variable passed, and I added a % after %3A as without the extra % it would send the link but remove all the % symbols for the variable (Call\Contact\DisplayTel rather than the variable 916-555-1234).
For some reason when I send the URL it encodes the %3A as %03 instead, giving me a weird ASCII placeholder, showing this URL instead:
websiteaddress.com/search?query=fieldvalue%03916-555-1234
Any help would be appreciated
Figured it out. Go Integrator wants the actual characters and NOT pre-encoded URL's. Thus, the link should show:
websiteaddress.com/search?query=fieldvalue:%Call\Contact\DisplayTel%
I have a user profile with an url field that shows their website. Right now it displays it like this: http://www.userwebsite.com
How can I remove the "http://www." part on my show.html.erb file, when displaying the user profile?
You can either play string games or you can use the URI module:
require 'uri'
url = URI.parse("http://www.userwebsite.com")
url.host.split(".")[-2..-1].join(".")
The advantage of doing it this way is that you know that you've only got the host at this point, not the scheme or any other noise, such as the post-host path, etc.
It's probably easier to just split the URL and do this stuff but you'll have more error handling and special case handling that way.
In order to maintain the current set of Urls in a project, I have to be able to use the # (pound sign) in the Url. For some reason the pound sign does not appear to work normally in this project for UrlMappings.groovy.
Is there a special escape-sequence that must be used when placing # signs in UrlMappings.groovy?
Am I missing some reason why one cannot use pound signs at all?
In the following URL Mapping example, the browser goes to the correct page, but the pageName variable is null:
"/test/${urlName}#/overview"(controller:'test', action:'overview') {
pageName = "overview"
}
I thought everything after # in the url would be treated on the client side of the browsers where it tries to find a and scroll to that location.
If you dump the request containing the pound char, do you even see the data behind #?
I used a Named URL mapping and it works fine, no need to escape the "#" sign:
name test: "/#abc" (controller: 'test', action:'homepage')
EDIT: My above answer is wrong. In fact, it falls to a special case when homepage is the default action of the view.
Netbrain is right, the path after "#" will never be sent to server. In stead, I found that it's possible using "%23" instead of "#". Please take a look at here.
For example, instead of /test#/abc we should use /test%23/abc as URL mapping (both at client side & server side).
I am trying to auto-scroll to div using:
/index.php#tabletabs2?contact_added=1
when I use:
/index.php#tabletabs2
it works. How can I have both a variable and the auto-scroll working in my URL???
The query part of the URL needs to be before the #. Browsers only send the part before the # to the server. The part after is for auto-scrolling to elements via their id or name attribute, e.g.
/index.php?contact_added=1#tabletabs2
See also the "Syntax" section of Wikipedia's "Universal Resource Locator" article. Especially the description of fragment identifiers.
You have to have them in the correct order; ? goes before #:
/index.php?contact_added=1#tabletabs2