| <?php | |
| $parent_lesson_id = learndash_get_setting( $post, 'lesson' ); | |
| $parent_lesson = get_post( $parent_lesson_id ); | |
| ?> |
| #!/bin/bash -e | |
| # Start allways the same | |
| wpuser='yourusername' | |
| wpuseremail='yourname@yourdomain.tld' | |
| wpuserpass=$(date +%s | sha256sum | base64 | head -c 16) | |
| dpprefix=$(date +%s | sha256sum | base64 | head -c 6) | |
| clear |
| <?php | |
| /* | |
| * Plugin Name: Post Likes | |
| * Description: WP REST API Post Likes | |
| * Author: Joe Hoyle | |
| * Version: 1.0 | |
| * Author URI: http://joehoyle.co.uk | |
| */ |
| <?php | |
| /** | |
| * Plugin Name: Translation Updates Table | |
| * | |
| * @author Pascal Birchler <pascal@required.ch> | |
| * @license GPL2+ | |
| */ | |
| /** | |
| * Displays a table with available translation updates. |
Whenever I write plugins or themes, there is one thing that needs a little extra attention and is quite frankly hard to get right: Translatable text. This list should helps me to find the right way fast.
Props to Alex Kirk, there list it inside a quiz.
Assume that the $username has been escaped using esc_html().
This scripts allows the export of PostFinance account flow data for YNAB 4 using Tampermonkey. The export is not based on the CSV generated by the Post as it does not adhere to the standard but makes use of the data loaded on the client side for doing said CSV export.
If Tampermonkey is installed you can click on the RAW view of the postfinance-ynab.user.js file of this Gist.
Tampermonkey should ask you whether or not you would like to install this script.
| <?php | |
| /* | |
| * Dependent Plugin Activation/Deactivation | |
| * | |
| * Sources: | |
| * 1. https://pippinsplugins.com/checking-dependent-plugin-active/ | |
| * 2. http://10up.com/blog/2012/wordpress-plug-in-self-deactivation/ | |
| * | |
| */ | |
I thought it would be pertinent to respond to some points presented by Andrey "Rarst" Savchenko in recent post Progressive Enhancement.
Unlike Rarst, I don't value progressive enhancement very highly and don't agree it's a fundamental principle of the web that should be universally employed. Quite frankly, I don't care about not supporting JavaScript, and neither does virtually anyone else. It's not that it doesn't have any value, or utility - but in a world where we don't have unlimited resources and time, one has to prioritise what we'll support and not support.
I'm a proponent of putting my ideas and creations into the world for people to make use of; and if I had to cover 100% of use cases for doing that, I wouldn't put much out there. I'm fine with losing the 1.1% of
| <?php | |
| /** | |
| * Make an internal REST request | |
| * | |
| * @global WP_REST_Server $wp_rest_server ResponseHandler instance (usually WP_REST_Server). | |
| * @param $request_or_method WP_REST_Request|string A WP_REST_Request object or a request method | |
| * @param $path (optional) if the path is not specific in the rest request, specify it here | |
| * @param $data (optional) option data for the request. | |
| * @return WP_Error|mixed |
| /** | |
| * Remove the LearnDash related scripts / styles from the homepage. | |
| */ | |
| add_action( 'wp_enqueue_scripts', 'child_manage_learndash_styles', 99 ); | |
| function child_manage_learndash_styles() { | |
| // Check if LearnDash exists to prevent fatal errors. | |
| if ( class_exists( 'SFWD_LMS' ) ) { | |
| // Make sure we are on the front page. |
