mrhaw

DECLARE @WorkingSQL		 VARCHAR(8000)
		,@NewPath		 VARCHAR(8000) = 'G:\SQL Data\' /* Root location to move files */
		,@TargetDatabase sysname	   = '%';			/* Specify a singular database, or % for All Databases */

SET NOCOUNT ON;

/* Sanitize path */
IF RIGHT(@NewPath, 1) <> '\'
BEGIN
	SET @NewPath = @NewPath + '\';

mrhaw

var svg = document.querySelector( "svg" );
var svgData = new XMLSerializer().serializeToString( svg );

var canvas = document.createElement( "canvas" );
var ctx = canvas.getContext( "2d" );

var img = document.createElement( "img" );
img.setAttribute( "src", "data:image/svg+xml;base64," + btoa( svgData ) );

img.onload = function() {

mrhaw

<?php
/**
 * A sample plugin to display the "welcome message" to all users, login for the first time in Revo manager
 *
 * @var modX $modx
 * @var array $scriptProperties
 * @var modPlugin $this
 *
 * @see modPlugin::process()
 *

mrhaw

// Dashboard widget to show number of Manager messages
$id = $modx->user->get('id');
$output = 'No messages.';
$total = $modx->getCount('modUserMessage',array(
   'recipient' => $id,
));
if($total) {
  $output = 'You have ' . $total . ' messages'; 
  $unread = $modx->getCount('modUserMessage',array(
     'recipient' => $id,

mrhaw

git remote prune origin
git branch -r --merged master | egrep -iv '(master|develop)' | sed 's/origin\///g' | xargs -n 1 git push --delete origin

mrhaw

1 - Create a *private* GitHub/Bitbucket or similar git repo. Here I assume the repo is:

	https://github.com/calkan/bash_history.git

2 - Create .history directory and initialize it for the repo:

	mkdir $HOME/.history
	cd $HOME/.history
	git init
	touch README.md 

mrhaw

<?php
// https://github.com/modxcms/revolution/issues/12580
include_once dirname(__FILE__).'/update.class.php';
/**
 * Saves a property set
 *
 * @package modx
 * @subpackage processors.element.propertyset
 */

mrhaw

Aniruddh Agarwal blogged A short tour of PHP, and this is one of the negatives he identified:

Community: I know. I said that PHPs community was an advantage to it, but it is also a disadvantage, because of BAD CODE. Beginners are not taught the best practices and they go on to write bad code and distribute it, either as answers on Stack Overflow or similar websites or blog about it, which encourages other beginners to adopt those practices. There is a lot of misinformation out there, and it is very difficult to separate the good from the bad. This is perhaps the worst thing about PHP, because PHP is an entry-level language and people learning it are usually not aware of the best practices.

This is spot on!

The existence of BAD CODE being copied and pasted by newcomers is probably the biggest source of exploitable security vulnerabilities in the entire industry.

The biggest offenders are often the highest ranking search results on Google and other search eng

mrhaw

<?
///////////////////////////////////////
// sanitize.inc.php
// Sanitization functions for PHP
// by: Gavin Zuchlinski, Jamie Pratt, Hokkaido
// webpage: http://libox.net
// Last modified: September 27, 2003
//
// Many thanks to those on the webappsec list for helping me improve these functions
///////////////////////////////////////

mrhaw

Essential JavaScript Links

A curated list by Eric Elliott and friends. Suggest links in the gist comments.

Help us turn this into a proper website!

This is a very exclusive collection of only must-have JavaScript links. I'm only listing my favorite links. Nothing else makes the cut. Feel free to suggest links if you think they're good enough to make this list. The really curious should feel free to browse the comments to find other links. I can't guarantee the quality of links in the comments.

Full Disclosure