polevaultweb

<?php 
/* 
Plugin Name: DBI Connection Fix 
Author: Delicious Brains 
Author URI: http://deliciousbrains.com 
*/ 
function dbi_connection( $transports, $args, $url ) {     
  if ( false !== strpos( $url, 'deliciousbrains.com' ) ) {        
    // Use streams as cURL results in connection refused         
    return array( 'streams', 'curl' );     

ahmadawais

/**
 * Default Body Class Styles
 */

.rtl {}
.home {}
.blog {}
.archive {}
.date {}
.search {}

barrykooij

// Mark virtual orders as complete instead of processing
function rp4wp_virtual_order_payment_complete_order_status( $order_status, $order_id ) {
	$order = new WC_Order( $order_id );

	if ( 'processing' == $order_status && ( 'on-hold' == $order->status || 'pending' == $order->status || 'failed' == $order->status ) ) {

		$virtual_order = false;

		if ( count( $order->get_items() ) > 0 ) {

aprea

the_archive_title( '<h1 class="page-title">', '</h1>' );

shadowfax92

# Author = Nikhil Venkat Sonti
# email = [email protected]
# github ID = shadowfax92
import sys
from xml.dom.minidom import _get_StringIO
from lxml import html
import requests
import os
import re
import time

chriscoyier

How WordPress Plugins Should Handle Front End Resources

This is a WORK IN PROGRESS intended for fleshing out and feedback

It's very common for people to be unhappy with how a WordPress plugin adds front end resources to their site. If a plugin needs CSS, the plugin will add a <link> element to that CSS. If the plugin needs JavaScript, it will add a <script> to that JavaScript.

Plugins do this because it works. It's damn important for a WordPress plugin to work, even in adverse conditions. They rightfully want good ratings and little customer support.

But this comes at the cost of additional HTTP requests. In optimizing front end performance of a site, reducing the number of HTTP requests is a huge thing. Front end developers want to decide and control how front end resources are being handled, and WordPress plugins don't typically make this easy on them.

georgiecel

	// awesome semantic comment

	function better_comment($comment, $args, $depth) {
		$GLOBALS['comment'] = $comment;
		extract($args, EXTR_SKIP);
		
		if ( 'article' == $args['style'] ) {
			$tag = 'article';
			$add_below = 'comment';
		} else {

gilbitron

module.exports = function(grunt) {

	// Config
	grunt.initConfig({
		pkg: grunt.file.readJSON('package.json'),

		concat: {
			scripts: {
				files: {
					'assets/dist/dunked-scripts-before.min.js': [

mahodder

add_action( 'pre_get_posts', 'custom_reverse_post_order' );
function custom_reverse_post_order( $query ) {
	if ( is_admin() )
		return;
	if ( $query->is_main_query() && is_archive() && ! is_post_type_archive() && ($query->query_vars['category_name'] == 'category-name' || $query->query_vars['category_name'] == 'category-name')  ) {
		$query->set( 'orderby', 'date' );
		$query->set( 'order', 'ASC' );
	}
}

ejdyksen

patch-edid.rb

A script to fix EDID problems on external monitors in macOS.

Instructions

1. Connect only the problem display.

2. Create this directory structure (if it doesn't already exist):