Why I cannot search words in dictionary with the url, for example
https://dictionary.cambridge.org/us/dictionary/english/Tea
returns its homepage, rather than the vocabulray page?
You can do this like this.
https://dictionary.cambridge.org/us/dictionary/english/<word>
You will get directly to the page. Please note that this is case sensitive. So you need to write tea and not Tea. Just replease the <word> with a word - If it exist then it will show you the page, if not then you will be redirected to the FrontPage. Or if you want to just use the search
https://dictionary.cambridge.org/us/spellcheck/english/?q=<word>
Related
I tried to save a query with search query string like:
"order cancellation request received for userId = 123"
I need the whole string so I quote it with double quotations in the search bar. That query works but only until I save it and share the link.
When I save it with "Save" button top of search bar, or "disk" button at the left of search bar, the page reloads and my quotations are removed; now the results are not the same because the engine matches any of the words in the query and gets me more results.
When I check the url, I see this part:
...,query:(language:kuery,query:'order%20cancellation%20request%20received%20for%20userId%20%3D%20123'),...
Apparently, there are not quotations. So I tried to add %22 as how they should be encoded in URL, but no avail.
So, why? I expect Kibana to preserve the quotations in the search term.
Or, can someone suggests another kind of syntax which is valid, correct and shareable as an URL?
Nah. I found why.
You should add %22 inside 'xxxx' so that it would look like:
...,query:(language:kuery,query:'%22order%20cancellation%20request%20received%20for%20userId%20%3D%20123%22'),...
I'm looking to find a way to replace the home page URL that Google deems as "/" in my Google Analytics reports. I know Google sets "/" as the home page but in my reports, I want it to display "Home" instead.
I haven't found any solutions through Google. I'm thinking it's through filters somehow.
I've tried going through the GA settings and did a search on filters how to change this but no solutions. Thanks!
Although I would not recommend this, you can create a filter in a view (possibly not the default one as it's bad practice) with the following fields:
Regex explaination:
^ asserts position at start of a line
\/ matches the character / literally
$ asserts position at the end of a line
Filter configuration if the SS gets lost:
Filter type: Custom
Checbox: Search and Replace
Filter field: Request URI
Search string: ^(\/)$
Replace string: Home
Remember to verify your filter and to create an additional view if you do this.
is it possible to replace the word search?
For example:
http://domain.com/search/helloWordl
to
http://domain.com/test/helloWordl
i think you just need to create a new page template and save as searchpage.php, add the correct code.
Change the form action to redirect to the page you just to create and that's it.
Read this to better understanding, you will find the correct loop and all the steps to do that.
Can I Create a reblog link programatically?
Is it against the terms of service? I can't tell...
Anatomy of a tumblr reblog link: (unique numbers made up)
http://www.tumblr.com/reblog/85728493821/7vu4jf89
In my RSS feed I have:
myblog.tumblr.com/post/85728493821
So its safe to say the 85... number is a unique post id
But what is the other code? (7vu4jf89)
The 2nd value differs for each reblog link, so its not just my unique identifier.
Arbitrary values do not work either.
I was thinking maybe its something Tumblr implemented specifically to prevent people from doing the sort of thing I'm attempting? Maybe its some sort of hash value combining my account identifier and the post?
Any insight is appreciated.
Tumblr Reblogs
Ignoring the RSS part for the moment, I believe there are two official methods to achieve a working reblog link.
Use the template variable {ReblogButton} (http://www.tumblr.com/docs/en/custom_themes#like_and_reblog_buttons)
Use the Tumblr API (http://www.tumblr.com/docs/en/api/v2#reblogging)
In reply to your question about other code. I believe this is a unique, randomly generated key, the make up of which I am not 100% sure on. The key seems be unique per post and per site.
For example, if the original reblog key is 12345678 and the post is reblogged, a new key is generated for the site that reblogged the post.
Back to the RSS part, sadly as you have probably gathered, getting the reblog key inside the RSS feed by default is impossible. My advice would be to find the permalink in the RSS feed and use an API call to return the corresponding key for a reblog.
There is a way to construct the reblog URL manually, if you have access to the post’s HTML page:
search for rk= in the HTML source code (it's in the block opened by <!-- BEGIN TUMBLR CODE -->)
copy the value of this parameter (e.g. "1234" if you find rk=1234)
now manipulate the URL:
append this value at the URL (add a slash before it, if there is none) (you can replace the slug with the value, if available)
replace "post" with "reblog"
remove the subdomain
call this crafted URL
This rk value (maybe "reblog key"?) doesn’t seem to be included in the feed.
On my site I am tracking the URL /shop/ as goal by head match. As there are some URL parameters I cannot use exact match here.
Additionally, I am tracking a goal by exact match which is a URL to subfolder: /shop/process/paid.php
The problem is that GA tracks this subfolder with the head match as well, and thus saves the URL parameters that come along with paid.php, e.g. paid.php?email=customer#home.com
How can I prevent GA to track the URL parameters?
How would the setup look like?
Thanks!
That should work with a custom filter:
admin->profile->filters->custom filter->search and replace.
Search for
/shop/process/paid.php\?.*
(that's your url with arbitrary query parameters, the "\" is an escape sign since "?" is also an control character in regular expression. Dot means any character and "*" means any number of the preceding (in that case any) character) and replace with the desired url ( /shop/process/paid.php).
There is probably a more elegant solution but like most people I'm not good at this regex stuff. This should work however.
Alternatives:
If those query parameters are nowhere needed in the tracking data you can exlude them completely in the profile settings.
You can created a profile for the subdirectory based on the directory (include filter->request uri contains "/shop" and set only this profile to remove query parameters