| Summary | How to control (or Understand) your GIST page's files list order. |
| Notice | not official documentation. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| <%@ Page Language="C#" %> | |
| <%@ Import Namespace="System.Diagnostics" %> | |
| <%@ Import Namespace="System.Net" %> | |
| <%@ Import Namespace="Sitecore.ContentSearch" %> | |
| <%@ Import Namespace="Sitecore.Data" %> | |
| <%@ Import Namespace="Sitecore.Data.Items" %> | |
| <script runat="server"> | |
| #region Configure actual checks here | |
| ChecksSet ChecksRun { get; set; } | |
| string[] Tags { get; set; } |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| <%@ Page Language="C#" %> | |
| <%@ Import Namespace="System.Diagnostics" %> | |
| <%@ Import Namespace="System.Net" %> | |
| <%@ Import Namespace="Sitecore.ContentSearch" %> | |
| <%@ Import Namespace="Sitecore.Data" %> | |
| <%@ Import Namespace="Sitecore.Data.Items" %> | |
| <script runat="server"> | |
| #region Configure actual checks here |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| // parse text to link-ify links, #hashtags, and @mentions | |
| // input plain old text, get out the formatted text and info | |
| // used by dankest.website and the dank platform https://github.com/cylesoft/dank | |
| function parse_text($text) { | |
| $home_url = 'https://dankest.website/'; | |
| $link_regex = '/\b(https?:\/\/)?(\S+)\.(\S+)\b/i'; | |
| $hashtag_regex = '/\#([^\s\#]+)/i'; | |
| $mention_regex = '/\@(\S+)/i'; | |
| $t = strip_tags($text); | |
| $links_found = preg_match_all($link_regex, $t, $link_matches); |
Homebrew is a package management system for OS X. You can read more about it here, or simply run
ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"to install it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| <%@ Page Language="C#" AutoEventWireup="true" %> | |
| <%@ Import Namespace="Sitecore.Jobs" %> | |
| <!DOCTYPE html> | |
| <html xmlns="http://www.w3.org/1999/xhtml"> | |
| <head id="Head1" runat="server"> | |
| <title>Running Sitecore Background Jobs</title> | |
| <meta http-equiv="refresh" content="3" /> |
- Website: http://xdebug.org/
- Related Gist: https://gist.github.com/hofmannsven/7613663
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| <?php | |
| // address to map | |
| $map_address = ""; | |
| $url = "http://maps.googleapis.com/maps/api/geocode/json?sensor=false&address=".urlencode($map_address); | |
| $lat_long = get_object_vars(json_decode(file_get_contents($url))); | |
| // pick out what we need (lat,lng) | |
| $lat_long = $lat_long['results'][0]->geometry->location->lat . "," . $lat_long['results'][0]->geometry->location->lng; |
All rules and guidelines in this document apply to PHP files unless otherwise noted. References to PHP/HTML files can be interpreted as files that primarily contain HTML, but use PHP for templating purposes.
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
Most sections are broken up into two parts:
- Overview of all rules with a quick example
- Each rule called out with examples of do's and don'ts