christianhanvey

If you are using git, so you can take advantage of static elements within MODX, you will need to be aware that simply updating your files does not mean MODX will pick that up. It will pick up changes in a file IF you the element is being called uncached.

http://forums.modx.com/forums/thread/73346/static-resources-don-t-update-without-cache-clear http://forums.modx.com/thread/73002/static-sources-caching-and-setup

This is not a big deal while working on a development site, performance is not your initial priority at that point. But when you get to deploying, you'll need to know that updating a file will not necessarily update how your site runs, and you don't want to be clearing your entire site cache. A big site would be taking a heavy server hit as its visitors trigger all pages regenerating their cache...

For an overview of MODX caching strategy, start at the documentation (of course) if you havn't already:

Flygenring

<?php
/**
 * Gets a field from a resource based on a supplied resource id, meant to be used as an output filter.
 *
 * Based on a resource ID a field can be retrieved. This can be standard fields as 'pagetitle' or 'alias',
 *  but a few custom fields are also available; 'siblingNextId', 'childrenFirstId', and 'childrenCount'.
 * Only resources that are not marked as 'deleted' or 'hidemenu', and that is marked as 'published' are returned.
 * Examples:
 * [[*id:toResourceField]] => returns the resource pagetitle
 * [[*id:toResourceField=`alias`]] => returns the resource alias

gibbs

<?php
/* 
 * Clear (refresh) MODx Cache from external PHP Script
 *
 * MODx Revolution (2.0.7-pl)
 * Daniel Gibbs
 */
 
// Path to MODx Core Directory
define("MODX_CORE_PATH", "../core/");

gubi

.fa-bounce {
    display: inline-block;
    position: relative;
    -moz-animation: bounce 1s infinite linear;
    -o-animation: bounce 1s infinite linear;
    -webkit-animation: bounce 1s infinite linear;
    animation: bounce 1s infinite linear;
}

@-webkit-keyframes bounce {

bramus

<?php

/**
 * Vimeo Thumbnail Script - Gets the poster frame for a Vimeo video id.
 * @author Bramus Van Damme <[email protected]>
 *
 * Example Request: vimeothumb.php?id=83936766
 */

// Perform a GET request to a given URL.

yangshun

function parseVideo (url) {
    // - Supported YouTube URL formats:
    //   - http://www.youtube.com/watch?v=My2FRPA3Gf8
    //   - http://youtu.be/My2FRPA3Gf8
    //   - https://youtube.googleapis.com/v/My2FRPA3Gf8
    // - Supported Vimeo URL formats:
    //   - http://vimeo.com/25451551
    //   - http://player.vimeo.com/video/25451551
    // - Also supports relative URLs:
    //   - //player.vimeo.com/video/25451551

ryanlewis

4r5e
5h1t
5hit
a55
anal
anus
ar5e
arrse
arse
ass

scottjehl

I wanted to figure out the fastest way to load non-critical CSS so that the impact on initial page drawing is minimal.

TL;DR: Here's the solution I ended up with: https://github.com/filamentgroup/loadCSS/

---

For async JavaScript file requests, we have the async attribute to make this easy, but CSS file requests have no similar standard mechanism (at least, none that will still apply the CSS after loading - here are some async CSS loading conditions that do apply when CSS is inapplicable to media: https://gist.github.com/igrigorik/2935269#file-notes-md ).

Seems there are a couple ways to load and apply a CSS file in a non-blocking manner:

hdragomir

<script type="text/javascript">
    (function () {
      "use strict";
      // once cached, the css file is stored on the client forever unless
      // the URL below is changed. Any change will invalidate the cache
      var css_href = './index_files/web-fonts.css';
      // a simple event handler wrapper
      function on(el, ev, callback) {
        if (el.addEventListener) {
          el.addEventListener(ev, callback, false);

amdbuilder

A few blocks of .htaccess code to help improve your websites performance and/or functionality.  I would recommend reading about each section and applying if required instead of applying everything.

The more code in your .htaccess the more your server needs to process BEFORE the HTML starts being served.

______________________ .htaccess starts after this line  _________________________________

## Optional - Allow cross-origin requests. ##

# http://enable-cors.org/ - http://www.w3.org/TR/cors/
# https://code.google.com/p/html5security/wiki/CrossOriginRequestSecurity