| diff --git a/public/wp-content/plugins/woocommerce-shipping-table-rate/shipping-table-rate.php b/public/wp-content/plugins/woocommerce-shipping-table-rate/shipping-table-rate.php | |
| index 8a7e082..01f5e47 100644 | |
| --- a/public/wp-content/plugins/woocommerce-shipping-table-rate/shipping-table-rate.php | |
| +++ b/public/wp-content/plugins/woocommerce-shipping-table-rate/shipping-table-rate.php | |
| @@ -242,6 +242,7 @@ if ( in_array( 'woocommerce/woocommerce.php', apply_filters( 'active_plugins', g | |
| <th class="country"><?php _e('Destination countries/states', 'wc_table_rate'); ?></th> | |
| <th><?php _e('Postcode', 'wc_table_rate'); ?> <a class="tips" tip="<?php _e('(optional) Comma separated list of ZIPs/Postcodes. Accepts wildcards, e.g. P* will match a postcode of PE30.', 'wc_table_rate'); ?>">[?]</a></th> | |
| <th><?php _e('Exclude Postcode', 'wc_table_rate'); ?> <a class="tips" tip="<?php _e('(optional) Comma separated list of ZIPs/Postcodes to EXCLUDE. Accepts wildcards, e |
In August 2007 a hacker found a way to expose the PHP source code on facebook.com. He retrieved two files and then emailed them to me, and I wrote about the issue:
http://techcrunch.com/2007/08/11/facebook-source-code-leaked/
It became a big deal:
http://www.techmeme.com/070812/p1#a070812p1
The two files are index.php (the homepage) and search.php (the search page)
| // sign up | |
| account.signUp('joe@example.com', 'secret'); | |
| // sign in | |
| account.signIn('joe@example.com', 'secret'); | |
| // sign in via oauth | |
| account.signInWith('twitter'); | |
| // sign out |
| [{ | |
| "title":"Post 1", | |
| "body":"Body goes here.", | |
| "tags":["Tag 1", "Tag 2"], | |
| "slug":"post-1", | |
| "published_at":"2013-06-05T18:24:59-04:00" | |
| }, { | |
| "title":"Post 2", | |
| "body":"Body goes here.", | |
| "tags":["Tag 1", "Tag 2"], |
| # Upload gems | |
| gem "carrierwave" | |
| gem "mini_magick", "~> 3.3" | |
| gem "fog", "~> 1.3.1" |
| // ## Globals | |
| /*global $:true*/ | |
| var $ = require('gulp-load-plugins')(); | |
| var argv = require('yargs').argv; | |
| var browserSync = require('browser-sync'); | |
| var gulp = require('gulp'); | |
| var lazypipe = require('lazypipe'); | |
| var merge = require('merge-stream'); | |
| var shell = require('gulp-shell'); | |
| var runSequence = require('run-sequence'); |
React recently introduced an experimental profiler API. After discussing this API with several teams at Facebook, one common piece of feedback was that the performance information would be more useful if it could be associated with the events that caused the application to render (e.g. button click, XHR response). Tracing these events (or "interactions") would enable more powerful tooling to be built around the timing information, capable of answering questions like "What caused this really slow commit?" or "How long does it typically take for this interaction to update the DOM?".
With version 16.4.3, React added experimental support for this tracing by way of a new NPM package, scheduler. However the public API for this package is not yet finalized and will likely change with upcoming minor releases, so it should be used with caution.
| // Copyright (c) 2021 Advanced Micro Devices, Inc. All rights reserved. | |
| // | |
| // Permission is hereby granted, free of charge, to any person obtaining a copy | |
| // of this software and associated documentation files (the "Software"), to deal | |
| // in the Software without restriction, including without limitation the rights | |
| // to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | |
| // copies of the Software, and to permit persons to whom the Software is | |
| // furnished to do so, subject to the following conditions: | |
| // | |
| // The above copyright notice and this permission notice shall be included in |
