It’s only a good pratice to adopt this naming convention. As long as you have in the header of your main file the meta (at last Plugin name: Name of Your Plugin, WordPress will automatically recognize this file for being the main one. Be aware that at the top of this file you should write … Read more
I’d guess you may have figured this out by now. Here’s my answer anyway. You say the API returns an array whose object items have label and value properties but if I try that same request I get an array whose object items have name and id properties (as you would expect when you specify … Read more
I haven’t found any solution to entirely convert dashicons- class automatically generated into fas fa-…. Having always used fa-solid or fa-regular I didn’t know you could shorten with fas and far. My mistake So I bypassed the style font-family:dashicons; adding: div.wp-menu-image.dashicons-before[class*=”fa”]::before { font-family: “Font Awesome 6 Free” !important; } In theory [class*=”fa”] include fa, fas, … Read more
Here’s the right code I made a mistake with s param function custom_search_query($query) { if (!is_admin() && $query->is_main_query() && $query->is_search()) { $search_query = get_search_query(); // Retrieve the search query $api_url=”https://api.adenwalla.in/api/search/data”; $args = array( ‘body’ => json_encode(array(‘query’ => $search_query)), ‘headers’ => array(‘Content-Type’ => ‘application/json’), ‘timeout’ => 60 ); $response = wp_remote_post($api_url, $args); $body = wp_remote_retrieve_body($response); $results … Read more
Yes, there is a difference and it is possible for a plugin to know when it is deactivated or deleted. For deactivation the plugin may register a deactivation callback using register_deactivation_hook(). For deletion the plugin may either register a deletion callback using register_uninstall_hook() or include a uninstall.php file in its base folder. There’s an important … Read more
Yes, I would suspect that your current solution may cause performance issues, if the number of comments gets high. To make the calculations a little easier for your site, you could handle them before hand based on the post ID. I.e get the post ID query all of the post’s comments’ IDs (WP_Comment_Query or custom … Read more
✨ Explanation and Solution Updating the plugin to prevent standard output couldn’t be easier. No need to create a custom skin, WordPress already provides one for this case: Automatic_Upgrader_Skin Description: This skin is designed to be used when no output is intended, all output is captured and stored for the caller to process and log/email/discard. … Read more
WP CLI The easy way; use the WP CLI (also available as wp-cli.phar) to get a solid, maintainable solution for this requirement. More for this topic you will find at the command wp plugin <command> WP API If you will need a custom script is is necessary to load the WP API, via wp-load.php and … Read more
Okay I found a quick and dirty solution for the viewScript. My webpack.config.js: /** * `@wordpress/scripts` path-based name multi-block Webpack configuration. * @see https://wordpress.stackexchange.com/questions/390282 */ // Native Depedencies. const path = require(“path”); // Third-Party Dependencies. const CopyPlugin = require(“copy-webpack-plugin”); const config = require(“@wordpress/scripts/config/webpack.config.js”); /** * Resolve a series of path parts relative to `./src`. * … Read more
I think I’ve figured out the solution. The short answer is GET requests don’t usually have a body, but wp_remote_get() will take what one assigns to the body argument and make it into URL parameters. That’s why it expects an array (because each element of the array becomes a parameter added to the URL). One … Read more