Corey Salzano

WordPress multisite allows plugins and themes to be Network Active. This prevents them from being deactivated on any site in the network.

To change a plugin from Network Active on every site to individually active on each site:

1. Manually Network Deactivate the plugin from the network plugins page. The wp network command does not yet support plugin deactivation.
2. Connect to the server via SSH and run this WP CLI command: wp site list --field=url | xargs -n1 -I % wp --url=% plugin activate hello.php (where hello.php is the plugin file or folder name)

What does the command do?

wp site list --field=url produces a list of URLs for all of the sites on the network.

The | operator passes the results from wp site list to xargs. xargs can take the output from one command and send it to another command as parameters.

The -n1 flag to xargs processes each line of output from the site list command one at a time. -n2 would send two site URLs to the next command.

wp --url=% plugin activate hello.php is the command to which xargs is passing the site URLs. It activates the Hello Dolly plugin on each site specified by URL. The % sign is our replacement character where each URL will populate.

Blocking spam on WordPress websites is heavy work. Akismet comes pre-installed on every site, but it’s not free for businesses or the only way to stop spam.

1. OOPSpam https://www.oopspam.com/
2. CleanTalk https://cleantalk.org/
3. Stop Forum Spam https://www.stopforumspam.com/
4. Project Honey Pot https://www.projecthoneypot.org/
5. Zero Spam https://www.zerospam.org

There are a ton of anti-spam WordPress plugins. The criteria for this list of alternatives is “offers an API.”

Thanks to Austin and Kerch for inspiration and help creating this list.

If you’re building blocks for WordPress, and the error TypeError: c is not a function is logged in your browser’s developer console, you may have created a TextControl component and failed to include both value and onChange attributes.

This code will cause the error:

<TextControl
	label={ __( 'Cash/trade', 'invp-payment-calculator' ) }
	id={ 'trade' }
	onChange={ changeTradeValue }
</TextControl>

This is a correct syntax:

	label={ __( 'Cash/trade', 'invp-payment-calculator' ) }
	id={ 'trade' }
	value={ attributes.trade }
	onChange={ changeTradeValue }
</TextControl>

If you see the default “Thanks for contacting us! We will get in touch with you shortly.” even if you’ve created a custom confirmation for your Gravity Form, your entry may have been marked as spam.

All entries deemed spam are shown the default message. Login and try again–logged in users will not get caught in the spam filter.

Also, visit the Entries list in the dashboard, and look for the Spam folder. Your entry may have been saved with the other Spam.

Where in the Gravity Forms source code does this happen?

plugins/gravityforms/form_display.php line 3894

If you’re building blocks for WordPress, and the error TypeError: b.map is not a function is logged in your browser’s developer console, you may have created a SelectControl component and failed to wrap the options in brackets to create an array.

This code will cause the error:

			<SelectControl
				label="Minimum Rating"
				value={ attributes.minimumRating }
				options={ 
					{ label: 'Great Deal', value: 'GREAT_PRICE' },
					{ label: 'Good Deal', value: 'GOOD_PRICE' },
					{ label: 'Fair Deal', value: 'FAIR_PRICE' }
				 }
				onChange={ onChangeMinimumRating }
			/>

This is the correct syntax:

			<SelectControl
				label="Minimum Rating"
				value={ attributes.minimumRating }
				options={ [
					{ label: 'Great Deal', value: 'GREAT_PRICE' },
					{ label: 'Good Deal', value: 'GOOD_PRICE' },
					{ label: 'Fair Deal', value: 'FAIR_PRICE' }
				] }
				onChange={ onChangeMinimumRating }
			/>

Entry approval is a Gravity View feature I use often. Even if I’m not using Gravity View on a project that needs to filter out some entries, I’ll save the same data in the $wpdb->_gf_entry_meta table to be compatible. The meta key is_approved contains one of the values in the table below.

Entry is_approved meta values

I replicated wordpress.org’s code reference system for my own project.

WordPress provides a template tag get_the_title() and it’s documented at https://developer.wordpress.org/reference/functions/get_the_title/.

A plugin I just launched provides a template tag invp_get_the_price() and it’s documented at https://inventorypresser.com/docs/reference/functions/invp_get_the_price/

I learned that the .org docs page content is generated by scanning the project source code, extracting PHPDoc comments, and parsing them into custom post types. The piece of software that does that is https://github.com/WordPress/phpdoc-parser.

Build the Data

1. Add PHPDoc comments to all classes and methods in your plugin.
2. Use a server that provides the WordPress Command Line Interface.
3. Upload your plugin to the site where you want to generate documentation.
4. Activate the phpdoc-parser plugin on the same site
5. Connect via SSH and run a wp-cli command similar to wp parser create ../../sites/inventorypress/wp-content/plugins/inventory-presser/ --user=corey
   1. Replace the path with a path to the plugin for which you want documentation.
   2. Change the user name to the name of an administrator on your site.

Build the Theme

WordPress.org uses a handful of themes at once. The developer reference pieces live in the wporg-developer theme.

Take Files from wporg-developer

SIDE NOTE: I would like to include wporg-developer in my theme or child theme instead of copying files, but step 2 below makes it hard to use wporg-developer as a dependency. It must be edited. I would enjoy having easy access to updates, and perhaps I could contribute to the theme to add necessary filters someday in the future.

How to download wordpress.org source code

This SVN command will download the whole theme. Paste the command into a terminal or command prompt window:

svn co https://meta.svn.wordpress.org/sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-developer/

Copy these files from wporg-developer into your child theme

• /inc
• /js
• /reference
• /stylesheets
• content-reference.php
• content-reference-archive.php
• functions.php (comingle it with your functions.php)

Theme Mods

1. Change option value wp_parser_root_import_dir to contain a path to the project. For me, this path points to a plugin in the wp-content/plugins folder.
2. Change get_template_directory_uri() calls to get_stylesheet_directory_uri() calls
3. Create single.php by taking a copy from the parent theme. Modify it to serve a different content template for the post types populated by phpdoc-parser. Here is a code sample that shows what to change to create a Twenty Twenty-One child theme.
4. Optional: Change “View on Trac” links
   I added two filters that wrap the URL and the text in the “View on Trac” link below the source code section of each page. These changes allow me to change the links to “View on Github” or wherever I want.
   1. wp-parser_source_url_base line 1173 of template-tags.php
   2. wp-parser_view_on_trac_link_text in a few places in template-source.php

Twenty Twenty-One Child Theme

Download a Twenty Twenty-One child theme with the files listed and mods 1-3 completed: https://github.com/csalzano/twentytwentyone-wporg-child

Also Run This Plugin

SyntaxHighlighter Evolved styles the source code editors.

Troubleshooting

Missing Source Code

If no source code is displaying, edit the option wp_parser_root_import_dir to contain a full path to the directory of the plugin. Example: /corey/sites/inventorypress/wp-content/plugins/inventory-presser

My Observations So Far

1. I love it, but I didn’t try anything else. Writing code comments is now also writing web pages and a great motivator to do it right.
2. Done! See Add-on Plugins phpdoc-parser reruns do not delete items. I need to write code that deletes functions, methods, hooks, and classes that are removed from the project.
3. Done! See Automating Updates to Docs I want to write a Github action to automate wp-parser runs on new versions of the plugin. When I push updates to the public repo, a copy of the plugin is written to the webserver, and wp-parser is run to generate new docs.

Automating Updates to Docs

Four months after I published this post, I designed a Github Action to automate the creation and updating of the docs pages. When I push to the master branch of my plugin’s repo, the plugin is deployed to the site on WP Engine where the docs pages are hosted, and the wp-cli command that generates the docs is run.

Here is the workflow file that defines the Action at Github: https://github.com/fridaysystems/inventory-presser/blob/master/.github/workflows/main.yml

It contains one job with two steps that are marked with these comments:

• # Deploy to WP Engine
• # Run phpdoc-parser to Build Documentation

Add-on Plugins

I wrote two add-on plugins to modify the behavior of phpdoc-parser.

1. phpdoc-ignorer instructs phpdoc-parser to ignore the /vendor folder in my plugin
2. phpdoc-deleter keeps track of every post created or updated by phpdoc-parser. After the run is complete, it deletes all posts that were not touched and then empty taxonomy terms.

I built a WordPress plugin that saves a copy of all Gravity Forms entries in a Google Sheet as they are received. Entries to Google Sheet is the glue between a Gravity Form and a Google Sheet.

https://entriestogooglesheet.com

This is confusing: calls to get_fields() find no Advanced Custom Fields values saved with a specific post, but calls to get_field() find values for the same post.

This happens when ACF did not insert the field values, and the secondary value with the meta_key beginning with an underscore does not exist.

The post has the values, but the Advanced Custom Fields plugin expects an additional value in a hidden field for each field.

ACF Creates a Second Key Value Pair

1. my_custom_value
2. _my_custom_value (this one is missing)