There is no relevant documentation of how the license key is to be used on the site or on GitHub. Is it meant to be embedded as a HTML Comment or in the JavaScript as a comment?
http://fancyapps.com/fancybox/3/#license
https://github.com/fancyapps/fancybox/issues/1032
Jut keep it, there is no need to put/use it anywhere. Obviously, if you would have to do something specific, then it would be stated.
Related
I couldn't find any api that return the article in a usable HTML form. Most of them return extracts which have very poor HTML formatting which makes them useless for anything.
There is no way to tell what Facebook did exactly, but the easiest way to grab the HTML contents of an article is by using the render action, i.e. by appending action=render to the URL:
https://en.wikipedia.org/wiki/Cooking?action=render
This produces the exact same HTML you can see on Wikipedia, but omits the non-content part (sidebar etc). If you need to reproduce the layout of an article more faithfully, you need to reuse parts of Wikipedia's CSS, and there is no easy way to do that.
Since just a few days there is a REST API for getting the html. It is available at https://rest.wikimedia.org/
Since it is so new, Facebook is probably not using it (yet) but if you want to get it for yourself I suggest you start exploring there.
I am currently writing this in my post.md
Intro to [links](http://jekyllrb.com/docs/permalinks/)
Then when I am clicking this link once the post has been published the link I am sent to is:
http://example.github.io/post-name/jekyllrb.com/docs/permalinks/
Can anyone help?
This is a gotcha. I had recently migrated from from Maruku to kramdown, which handles urls differently. You need to define
[setid]: http://www.example.com (don't forget the http://)
Then use [setid] in place of the link.
I've got a staging and live site I'm working on (not my code base). I've accidentally replaced the live server with some staging code (no backup (slap me)) and I'm getting weird urls for articles on the sites 'blog' page.
Basically everything's being called into the page correctly but the page header link is being screwed.
Rather than being
http://www.example.com/a-nice-url
it's giving me
http://www.example.com/news,recent,pr,etc
which appears to be the list of categories of the article.
Where/How can I easily fix this?
I'm only calling [[*content]] and can't find where that is.
Linking to an article I know is there with the correct url works still.
any ideas would be greatly appreciated.
I assume your blog page has some sort of listing somewhere, maybe a getResources call? If you can't find it in your blog list template (as you're saying you only see a *content), it means the list is probably "hardcoded" in the blog list resource content field.
You'll want to find the chunks being used to output each blog entry on the lists and check which page parameter is used to construct the link. It should probably be *alias, and if it is and your aliases are correct you have some deeper trouble going on.
Every single GWT example I look at contains references to $PP_OFF. See http://code.google.com/p/google-web-toolkit-doc-1-4/wiki/DevGuideStyleSheets or http://khanzeeshan.wordpress.com/2009/06/12/creating-project-for-gwt-1-5-3/ for example.
What does $PP_OFF mean?
It's a bit of defunct wiki markup. The Google Code wiki treats {{{...}}} blocks as code and attempts to pretty-print them, which doesn't always work well; $PP_OFF is, or was, an undocumented feature that's supposed to stop that happening. See http://groups.google.com/group/gwt-google-apis/msg/04ae50fdd4339294 for the only mention of this that I can find online.
You should completely ignore it wherever you see it.
(You might be wondering why it would appear on some random person's WordPress blog, which of course isn't using the Google Code wiki. The answer appears to be that the person in question just copied-and-pasted stuff from Google's documentation. See http://code.google.com/webtoolkit/doc/1.5/tutorial/create.html if you're curious about the original source which, of course, he didn't credit.)
In GraffitiCMS v1.2, I'm trying to include the comment form on my blog posts, but the submit button does nothing. Comments are enabled for the post, and I've included $macros.CommentForm() in the blog.post.view file. I've also confirmed that the necessary Ajax.ashx file exists on the root. Are there any other dependencies?
Are there any instructions posted anywhere that explain how to make this work? I've been Googling for several hours and can't find any.
NOTE: I cannot upgrade to v1.3 at this time. Hopefully on a future project.
You need to make sure you have the /__utility/js/graffiti.js and /__utility/js/prototype.js scripts linked on your page. Calling $macros.Head() should do this automatically.
It turns out that I was already doing as Jeremy H suggested, and calling $macros.Head(), but my use of jQuery was conflicting with Prototype. I resolved the problem by linking in jQuery before $macros.Head() and switching out all my jQuery $ tokens to use the actual jQuery function name.
https://learn.jquery.com/using-jquery-core/avoid-conflicts-other-libraries/