After spending two hours fucking with pushing my reset-button and clicking upload in both ReplicatorG and Makerware, I figured out how to do it from the command line. The command line was determined from running ReplicatorG on the console and trying to upgrade the firmware.
Download and install it from http://www.makerbot.com/sailfish/install/
wget http://firmware.makerbot.com/firmware/MB-mb24-2560-Sailfish-v4.4-r1029.hex
| // Edit order items table template defaults | |
| function sd_add_wc_order_email_sku( $table, $order ) { | |
| ob_start(); | |
| $template = $plain_text ? 'emails/plain/email-order-items.php' : 'emails/email-order-items.php'; | |
| wc_get_template( $template, array( | |
| 'order' => $order, | |
| 'items' => $order->get_items(), | |
| 'show_download_links' => $show_download_links, |
| <?php | |
| // put array in here | |
| $array = array ( | |
| 'key' => 'group_54624ad06f391', | |
| 'title' => 'Company List', | |
| 'fields' => array ( | |
| array ( | |
| 'key' => 'field_54624aff43237', | |
| 'label' => 'Companies', |
| <?php | |
| // filter to exclude specified post_meta from Polylang Sync ## | |
| add_filter( 'pll_copy_post_metas', 'q_pll_copy_post_metas' ); | |
| /** | |
| * Remove defined custom fields from Polylang Sync | |
| * | |
| * @since 0.1 | |
| * @param Array $metas |
| <?php | |
| class File_Streamer | |
| { | |
| private $_fileName; | |
| private $_contentLength; | |
| private $_destination; | |
| public function __construct() | |
| { | |
| if (!isset($_SERVER['HTTP_X_FILE_NAME']) |
Hi, I am a fork from https://gist.github.com/patrickhammond/4ddbe49a67e5eb1b9c03.
A high level overview for what I need to do to get most of an Android environment setup and maintained on OSX higher Catalina and Big Sur with and without Android Studio been installed.
Considering the SDK is installed under /Users/<your_user>/Library/Android/sdk folder which is the Android Studio preferred SDK location, but it works fine under /usr/local/share/android-sdk as well, which is a location pretty much used on CI mostly.
https://github.com/shyiko/jabba instead ?
| <?php | |
| add_action( 'init', function() { | |
| ini_set( 'memory_limit', '2048M' ); | |
| set_time_limit( 0 ); | |
| $posts = get_posts( [ | |
| 'post_type' => 'product', | |
| 'posts_per_page' => -1 | |
| ] ); | |
| $count = 0; |
| { | |
| "name": "project", | |
| "version": "0.0.0", | |
| "authors": [ | |
| "Eric Barnes <me@example.org>" | |
| ], | |
| "license": "MIT", | |
| "private": true, | |
| "ignore": [ | |
| "**/.*", |
Here is easy steps to try Windows 10 on ARM or Ubuntu for ARM64 on your Apple Silicon Mac. Enjoy!
NOTE: that this is current, 10/1/2021 state.
One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.
Most workflows make the following compromises:
Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.
Use production SSL certificates locally. This is annoying