tarciozemel

/* @see https://twitter.com/csswizardry/status/1616451810004242432 */

head,
script[async][defer],
script[async][defer]::before {
  display: block !important;
}

script[async][defer]::before {
  background-color: white !important;

tarciozemel

const docWidth = document.documentElement.offsetWidth

document.querySelectorAll('*').forEach(el => {
    if (el.offsetWidth > docWidth) {
      console.log(el)
    }
})

tarciozemel

There are times notifications aren't wanted about either a changed repo file or a new file that needs to be added to the repo. However, adding the name of the file to .gitignore might not be a good option, either. For example, locally-generated files that other users aren't likely to generate (e.g., files created by an editor) or files of experimental test code might not be appropriate to appear in a .gitignore file.

In those cases, use one of these solutions:

0. If the file is a changed repo file

   Use the command:

   git update-index --assume-unchanged "$FILE"

tarciozemel

/* Headers out of order (i.e. h2 before h1 etc.)
   Result: dotted blue outline
   @see https://twitter.com/Una/status/1277652897606635523
*/
h2 ~ h1,
h3 ~ h1,
h4 ~ h1,
h5 ~ h1,
h6 ~ h1,
h3 ~ h2,

tarciozemel

function slugify(text) {
  return text.toString().toLowerCase().trim()
	.normalize('NFD') 				 // separate accent from letter
	.replace(/[\u0300-\u036f]/g, '') // remove all separated accents
	.replace(/\s+/g, '-')            // replace spaces with -
	.replace(/&/g, '-and-')          // replace & with 'and'
	.replace(/[^\w\-]+/g, '')        // remove all non-word chars
	.replace(/\-\-+/g, '-')          // replace multiple '-' with single '-'
}

tarciozemel

//
// Returns first element that matches CSS selector {expr}.
// Querying can optionally be restricted to {container}’s descendants
//

function $( expr, container ) {
    return typeof expr === 'string' ? ( container || document ).querySelector( expr ) : expr || null;
}

//

tarciozemel

function emailEncode($e)
{
    $email_len = strlen($e);

    for ($i = 0; $i < $email_len; $i++) {
        $output .= '&#'.ord($e[$i]).';';
    }

    return $output;
}

tarciozemel

Create a new repository on the command line
-------------------------------------------

touch README.md
git init
git add README.md
git commit -m "first commit"
git remote add origin [SSH GIT ADDRESS]
git push -u origin master

tarciozemel

# MAINTENANCE-PAGE REDIRECT
<IfModule mod_rewrite.c>
    RewriteEngine on
    RewriteCond %{REMOTE_ADDR} !^123.456.789.000 # whatismyip.com
    RewriteCond %{REQUEST_URI} !/maintenance.html$ [NC]
    RewriteCond %{REQUEST_URI} !\.(jpe?g?|png|gif) [NC]
    RewriteRule .* /maintenance.html [R=302,L]
</IfModule>

tarciozemel

//
// By default, WordPress comes with a handy search but it only search in post 
// titles and contents. If you are working on a custom post type, you most 
// probably using custom fields to store its attributes. For example, A 
// Property custom post type would have address, city and state custom fields. 
// You may have used WP_Query object with meta_query setup, But, it does not 
// work. If you do not use “s” attribute, it will overwrite the default search 
// and If you use it, it will not return the expected results. This snippet will 
// use posts_clauses filter to inject the meta query that will combine with the 
// WordPress’s default search parameter.