To be honest, I’m not sure if you can trust this plugin 100%. I run the test on my plugin, that is already in repo, and it showed me few false alarms. I put your code inside my plugin code and run the test again and… it didn’t show me the error you have. Also, … Read more
This command fixes “Loose comparisons”: vendor/bin/phpcbf –standard=WordPress,Universal –sniffs=Universal.Operators.StrictComparisons admin.php
The issue is that you’re attempting to store output of a method by reference to $starredgroup_products, which is not possible. This should fix it (untested): $starredgroup = $myPage->getGroup( $starredgroup ); $starredgroup_id = $starredgroup[‘groupid’]; $starredgroup_products = $myPage->getStarredProducts( $starredgroup_id );
May I know where to edit the tax rate?
I feel there is a bit of confusion — let me try and clarify some key concepts. A WordPress installation can potentially run huge amounts of 3rd party code. Code you can’t control. That leads to a high chance of naming collisions. That’s why WordPress coding standards suggest to “namespace” functions and variables declared in … Read more
I’d really like to get rid of the messages about coding style Despite not recommended, you can ignore/whitelist warnings and errors for a line or block of code using special PHPCS/WPCS comments which you can find here: Ignoring Parts of a File Whitelisting code which flags errors Working examples: ( Note: WordPress accepts all these … Read more
Yes, there is PHPCBF which can automatically fix some of them at least. However, I’d suggest ignoring Yoda conditions. There is currently a proposal to drop yoda conditions from the coding standard in favour of stricter checks against assignments in control structures, while moving slowly has been well received.
The more elaborate data is, the harder it is to both formulate and implement sanitization process. For a number this might be as simple as “integer” and (int)$number. For HTML this is highly not trivial with different possibilities of desired scope (no HTML tags? some blacklisted tags? some whitelisted tags? what about embedded scripts? CSS?) … Read more
You can use filter_input to sanitize your $_POST array. $nonce = filter_input( INPUT_POST, ‘revv_meta_box_nonce’, FILTER_SANITIZE_STRING ) use empty() to check $nonce has a value or not. You can use the same for second issue $foo = filter_input( INPUT_POST, ‘foo’, FILTER_SANITIZE_STRING ) change 3rd parameter based on your expected data in $_POST[‘foo’]. check this doc for … Read more
You can use wp_ajax action: add_action( ‘wp_ajax_my_awesome_ajax’, ‘my_awesome_func’ ); add_action( ‘wp_ajax_nopriv_my_awesome_ajax’, ‘my_awesome_func’ ); function my_awesome_func() { // Handle request with $_POST wp_die(); } You can submit contact form with jQuery post: jQuery.post( my_awesome_js.ajaxurl, { ‘action’: ‘my_awesome_ajax’, ‘data’: ‘some data’ }, function(response){ alert(response); } ); The my_awesome_js.ajaxurl you use wp_localize_script: wp_enqueue_script(‘my_awesome_js’, ‘/path/to/your/script/above.js’, array(‘jquery’)); wp_localize_script(‘my_awesome_js’, ‘my_awesome_js’, array( … Read more