Mark, I hate to say it, but you’re going about this the wrong way. PHP files in your plug-in should never be accessed directly in this way. Instead, they should be loaded from within WordPress just like everything else. Here are some alternative paths you could take: Create an admin page that displays your stats … Read more
Is this ok or should I just store it in an array form so I can just directly access it without using json_decode? In your case store it directly means store it serialized. Because $data is an array and cannot be stored as is, but converted to a string. Even if you access it directly … Read more
Because you’re using a namespace in this class, you need to add a \ in front of the WP_Query call to tell PHP that it’s in the global namespace and not the namespace of this class. Try this: $query = new \WP_Query($args);
I’ve been trying to work out the issue for months now, and have made several adjustments to try to solve the problem. In short: Yes, we know there’s a problem. No, I don’t know how to fix it yet. You can stop reporting it already. Current workaround: ANY commit of any kind should trigger it … Read more
The easiest way is a two step approach: Release your plug-in to the public. Once it’s live, you’ll start getting feedback from end users in addition to developers. If you want, release it as a “beta” version and heavily emphasize that in the readme file. Ask. There are veteran WordPress developers everywhere: here, on the … Read more
Use an auto-loader and let PHP resolve that problem for you. Then only one class will be loaded, and you don’t have to worry about doubled declarations. Example I have an (unfinished) plugin Post Notes with the following file structure: – plugin.php – php/ – Nonce_Validator.php – Save_Post_Request_Validator.php – Textarea.php – … and more This … Read more
The benefit of uninstall.php, and the reason that it was introduced, is that it allows you to isolate your uninstallation code from the rest of your plugin’s code. This means that your entire plugin doesn’t have to be loaded when it is uninstalled. That minimizes the chance that your plugin will inadvertently run code during … Read more
WordPress doesn’t provide any specific data validation functions for SUPERGLOBALS. I use the PHP filter_input function then escape it as I would any untrusted variable. $url = filter_input( INPUT_GET, ‘some_query_string’, FILTER_VALIDATE_URL ); echo ‘<a href=”‘. esc_url( $url ). ‘”>Click Me</a>’; The PHP filter input accepts: Validate filters Sanitize filters Other filters Additional Filter flags
You will need to start reading about the setting and options API, and then pull your CPT and Taxonomies into it. Have a start here: Creating Options Pages « WordPress Codex Settings API « WordPress Codex WordPress Settings API (options page) Generator Class Reference/WP List Table « WordPress Codex Custom List Table Example Plugin – … Read more
I have worked on your issue and found a solution after some Google. Note: Add the below mentioned code to theme’s functions.php or any plugin’s file. Code: This filter function will add a custom tab to the Products Data metabox <?php add_filter( ‘woocommerce_product_data_tabs’, ‘add_my_custom_product_data_tab’ , 99 , 1 ); function add_my_custom_product_data_tab( $product_data_tabs ) { $product_data_tabs[‘my-custom-tab’] … Read more