I used the Google markup tester to validate the sample markup from Google developers and it says
url: missing and required
When i replace target with url, validation is successful. Is it supposed to be target or url?
Related
I am building out an OpenAPI support for my project but I need swagger.yaml file to be available only to authorized users.
Swagger UI and Swagger Editor both seem to expect the swagger.yaml file to be accessible publicly.
I've thought of various ways of getting around it. One could be using "signed" URLs, similar to how S3 does it -- this way only people with a link can access it.
What is a good practice ?
I figured it out. On the Swagger-UI github page there is a description of the authorizations parameter that can be set in index.html:
An authorization object to be passed to swagger-js. Setting it here will trigger inclusion of any authorization or custom signing logic when fetching the swagger description file. Note the object structure should be { key: AuthorizationObject }
What I've done was setup a Node.js server that protects Swagger-UI. If the token is not set in cookies, it directs the user through the OAuth 2.0 flow, sets the cookie, and only then directs to swagger-ui.
Swagger-ui in turn has authorizations parameter set as follows:
authorizations: {
"_auth": new SwaggerClient.ApiKeyAuthorization(
"Authorization", "Bearer "+ Cookies.get("MyAccessToken"),
"header")
}
The header is then passed to the the server when downloading swagger.yaml file.
I've implemented Google Remarketing code on a client's site but it's getting an unspecified critical error in the Chrome Tag Assistant plugin. I'm sure I've followed the instructions on how to setup the custom variables correctly. Can anyone see what I've done wrong or shed some light on how to find out what the 'critical error' is?
Here is a code sample -
<script type="text/javascript">
var google_tag_params = {
ecomm_prodid: "IS-FRE-FFA",
ecomm_pagetype: "product",
ecomm_totalvalue: 19.95};
</script>
/*Rest of the Google suppplied code*/
There are lists in the associated Google Adwords account and it says "We haven't detected the AdWords tag on your website" for the Remarketing Tag details box above the lists.
Without seeing the actual page it is hard to be sure - your code snippet looks ok here, but there could be other errors in the rest of the code. If you could paste the full tag you're using or the site where we can see it in situ that would help diagnose it.
Either way, sometimes the Tag Assistant plugin gets confused by other javascript errors on the page - there are some more details on how to validate that the remarketing tag is working correctly at https://developers.google.com/adwords-remarketing-tag/verification
Message alert in Facebook developer page that my site is currently using the following deprecated features:
Social Plugins (Like Button, Like Box) without absolute URL's in their href parameter. This must be fixed before July 2013.
I'm guessing it's talking about the data-href parameter for likes, but my like buttons are being generated with the following simple code:
data-href="http://<?php echo $_SERVER["HTTP_HOST"].$_SERVER["REQUEST_URI"];?>"
And the results when viewed in the browser (looking at the HTML source) certainly look like absolute URLs to me. What is this alert actually trying to tell me? That they've scanned the site and that there are actual HREFs that have problems, or just that there might be some?
Is it referring to some other HREF parameter?
If you use absolute url in data-href attribute of this social plugin, just enable July 2013 Breaking Changes in settings of your facebook application.
In Like Button code, data-href is href for HTML5.
Absolute URL:
http://stackoverflow.com/questions/16270043/alert-says-using-deprecated-href-without-absolute-url
Relative URL
../questions/16270043/alert-says-using-deprecated-href-without-absolute-url
Social Plugins must have absolute URL your site and looks like your site has.
I got this alert from facebook:
... is currently using the following deprecated features:
Social Plugins (Like Button, Like Box) without absolute URL's in their href parameter.
The fb like and fb comment box is used on a Sharepoint site, and the URL in the href parameter is absolute.
Anyone have ideas why facebook is complaining about the code? or have a safe approach I can use to test if the code will work after the change without downtime on the plugins.
Just as #Anvesh says, I checked that my URLs was absolute, enabled the migration, waited a few minutes and tested and nothing breaked.
They should rephrase the message.
here I found of how to formulate an URL to open a compose popup window in gmail
Prefilling gmail compose screen with HTML text
it works great, but I want to go 2 steps further
I'd like to set FROM parameter. Since in my gmail account I have the option to select from which email I'd like to send... I would like to preset this if possible
I would like to do some basic HTML formatting in my body parameter...if I just add text it doesn't work
I know for certain no HTML in the body:
Is it possible to add an HTML link in the body of a MAILTO link
The hunt for a from parameter is ongoing...