php Archives - Shane Rutter Blog

WooCommerce emails add reply to header

A client was having issues with bounce back due to customers entering incorrect email addresses, so I updated the outbound email address used by WooCommerce to “[email protected]”, this meant any bounce backs would go to a null mailbox instead of to their mains “[email protected]” mailbox. However, this meant when customers hit reply, it would reply to the noreply@ mailbox. Using this code, I was able to set a Reply-To header, so customers could still reply to emails.

Code

Drop this into your functions.php file and edit as required.

function woocommerceEmailAddReplyTo($headers = ”, $id = ”, $order)
{
	$replyToName = get_bloginfo(‘name’);
	$replyToEmail = get_bloginfo(‘admin_email’);

	if (is_array($headers)) {
		$headers[‘Reply-to’] = $replyToName . ‘ < ‘ . $replyToEmail . ‘>’;
	} else {
		$headers .= ‘Reply-to: ‘ . $replyToName . ‘ < ‘ . $replyToEmail . ‘>’ . “\r\n”;
	}

	return $headers;
}
add_filter(‘woocommerce_email_headers’, ‘woocommerceEmailAddReplyTo’, 10, 3);

1

2

3

4

5

6

7

8

9

10

11

12

13

14

function woocommerceEmailAddReplyTo($headers = ”, $id = ”, $order)

{

$replyToName = get_bloginfo(‘name’);

$replyToEmail = get_bloginfo(‘admin_email’);

if (is_array($headers)) {

$headers[‘Reply-to’] = $replyToName . ‘ < ‘ . $replyToEmail . ‘>’;

} else {

$headers .= ‘Reply-to: ‘ . $replyToName . ‘ < ‘ . $replyToEmail . ‘>’ . “\r\n”;

}

return $headers;

}

add_filter(‘woocommerce_email_headers’, ‘woocommerceEmailAddReplyTo’, 10, 3);

This code is provided as it and may require changes to work for your needs.

24th September 2021

WordPress include private pages in parent dropdown

WordPress only includes published pages in the parent page dropdown, I ran into an issue where both parent and child page were made private so work could be done to the pages, the child pages when edited lost their parent relationship, due to the parent page no longer appearing within the “Parent” dropdown.

Why would you need this?

In my case we wanted to make some changes to the existing pages but needed to do these changes in private until all where complete, it was not until after we re-published the pages, we found the child pages where no longer link to the parent.

Fix

Let’s add the private and pending pages to the parent dropdown menu, allowing us to pre-create pages and child / parent relationships without having to already have published the pages.

function updatePageParentSelectionDropdown($args)
{
	$args[‘post_status’] = [‘publish’, ‘private’, ‘pending’, ‘draft’];
	return $args;
}
add_filter(‘page_attributes_dropdown_pages_args’, ‘updatePageParentSelectionDropdown’);
add_filter(‘quick_edit_dropdown_pages_args’, ‘updatePageParentSelectionDropdown’);

1

2

3

4

5

6

7

function updatePageParentSelectionDropdown($args)

{

$args[‘post_status’] = [‘publish’, ‘private’, ‘pending’, ‘draft’];

return $args;

}

add_filter(‘page_attributes_dropdown_pages_args’, ‘updatePageParentSelectionDropdown’);

add_filter(‘quick_edit_dropdown_pages_args’, ‘updatePageParentSelectionDropdown’);

This code is provided as it and may require changes to work for your needs.

10th September 2021

SuiteCRM – clear / reindex search index

Came across a problem with a SuiteCRM where the search was not working correctly, returning none or unrelated results. SuiteCRM relies on an indexing service called Lucene, which handles indexing for advanced searches, as in my case, this needs to be full reindexed to work correctly.

1. Lock Files

When Lucene begins indexing it generates lock files, normally found under modules/AOD_Index/Index/Index with the extension .lock, it is save to delete these files if they are old (have an old time stamp), sometimes this is enough to fix the issue, as previous indexing attempts max have failed and left the lock file, stopping future indexing processes from starting. First try, removing these lock files and wait and see if the indexing processes continue / repair them selfs.

2. Full Reindexing

I would recommend you do a full backup of the modules/AOD_Index directory before starting, as well as a backup of the database.

Also temperarly stop cronjobs from running, as we dont want the cron indexer to kick in during this clearing process.

1. Rename index folder (can be deleted after)

From your SuiteCRM root directory:

mv modules/AOD_Index/Index/Index modules/AOD_Index/Index/Index.BACKUP

We are renaming your current (old) index to Index.BACKUP, you can delete this later once you are sure everything is resolved.

2. Empty Table

Now delete all rows from the table aod_index

3. Schedules

Make sure the Optimise AOD Index and Perform Lucence Index are running as part of the schedule.

4. Wait

Make sure you have re-enabled your cronjob and wait for the indexes to rebuild. This will take a long time, but you can monitor the rebuilding process with the below command. Once it has stabilised, it should be complete.

watch du -h modules/AOD_Index/Index/Index

This code is provided as it and may require changes to work for your needs.

27th August 2021

WordPress disable XMLRPC.php for increased security

I have recently been having a few issues with bots and malicious attacks trying to breach WordPress websites via brute force attacks. From my experience 90% of the websites, I have built or worked on never utilise the xmlrpc service, which is included with WordPress, due to this I decided to simply block any access to this service via Apache, which fixes a number of security related issues.

Code

Place this in your websites .htaccess file to take effect, then simply browser to domain.com/xmlrpc.php and you now get an access denied message.

# Block XMLRPC access
<Files xmlrpc.php>
Order allow,deny
Deny from all
</Files>

1

2

3

4

5

# Block XMLRPC access

Order allow,deny

Deny from all

</Files>

What is XMLRPC?

The xmlrpc.php allows remote access to your WordPress site, it allows various tools and publishing applications to control and manage content from outside of the normal WordPress admin. For example, a publishing tool may allow you to write new blog posts using an alternative tool (instead of the WordPress admin).

Do I need it?

If you do not use any tools / services which utilise xmlrpc, then you do not need it and can apply the block in this post. For example, if you use the WordPress app to manage your website from your phone then you will need to keep XMLRPC working.

Why block XMLRPC?

Due to the nature of XMLRPC, it allows remote services to connect and perform actions on your website, this creates an additional security risk, and it is very common for malicious attacks to target XMLRPC with bruite-force attacks, trying to guess your password and / or access other services exposed by the XMLRPC protocol.

This code is provided as it and may require changes to work for your needs.

15th June 2021

cPanel – Sender x has an outgoing mail hold. Message will be reattempted later.

A client was having issues sending emails and receiving a number of alerts regarding delayed emails. After looking investigating a number of outbound emails where queued with a failure reason of:

R=enforce_mail_permissions defer (-1): “Sender their@email.com has an outgoing mail hold. Message will be reattempted later”

1	R=enforce_mail_permissions defer (-1): “Sender [email protected] has an outgoing mail hold. Message will be reattempted later”

The account in question had hit the sending limits configured within cPanel and there emails where being held.

Pre-Checks

It is important you pre-check and make sure the hold is not legitimate such as a spam attempt / hacked site, I checked the emails being sent and due to a influx in online orders there email usage per day has significantly increased.

1st Attempt

Try running the following commands under sudo / root, replaceing [accountname] with the cpanel account name of the user. Then try send an email or retry sending an email in the queue.

whmapi1 unsuspend_outgoing_email user=[accountname]
whmapi1 release_outgoing_email user=[accountname]

1 2	whmapi1 unsuspend_outgoing_email user=[accountname] whmapi1 release_outgoing_email user=[accountname]

2nd Attempt

The above worked for a couple accounts, but for one this did not work. There is 3 files depending on the type of block. Have a look in the following files below and remove the accountname / email address if present.

/etc/outgoing_mail_hold_users
/etc/outgoing_mail_suspended_users
/etc/email_send_limits

1

2

3

/etc/outgoing_mail_hold_users

/etc/outgoing_mail_suspended_users

/etc/email_send_limits

I found my user within “/etc/outgoing_mail_suspended_users” and once removed, everything went back to normal.

It is recommended a professional under takes these actions, please always backup existing files / configs.

5th January 2021

WooCommerce admin filter products by image

A client recently asked me to add a filter to the WooCommerce admin products list so they can filter items based on if the item had an image or not. This allowed them to easily find products which had missing images so they could correct.

Why not take a look how to filter by on sale items?

Code

/*
 * Woocommerce Filter by has image
 */
function custom__woocommerce_filter_by_hasimage($output) {
    global $wp_query;
    
    $selected = 0;
    if (isset($_GET[‘product_hasimage’])) {
        $selected = (int)$_GET[‘product_hasimage’];
    }
    
    $output .= ‘
		<select name=”product_hasimage” id=”dropdown_product_has_image”>
			<option value=””>Filter by image</option>
			<option value=”1″ ‘ . (($selected === 1) ? ‘selected=”selected”‘ : ”) . ‘>Has Image</option>
			<option value=”2″ ‘ . (($selected === 2) ? ‘selected=”selected”‘ : ”) . ‘>Has No Image</option>
		</select>
	‘;
    
    return $output;
}
add_action(‘woocommerce_product_filters’, ‘custom__woocommerce_filter_by_hasimage’);



/*
 * Woocommerce Filter by on has image where statement
 */
function custom__woocommerce_filter_by_has_image_where_statement($where, $query) {
    global $wpdb;
    
    // Only trigger if required
    if (!is_admin() || $_GET[‘post_type’] != “product” || !isset($_GET[‘product_hasimage’]) || (int)$_GET[‘product_hasimage’] <= 0) {
        return $where;
    }
    
    // Is filter applied
    if ($_GET[‘product_hasimage’] > 0) {
        // What condition to check
        $condition = ‘IN’;
        if ($_GET[‘product_hasimage’] == 1) {
            $condition = ‘NOT IN’;
        }
        
        // Query
        $queryStr = ‘
            SELECT ID FROM (
                SELECT ID
                FROM djqns_posts
                WHERE ID IN (
    				SELECT tp.ID
    				FROM djqns_posts tp
    				LEFT OUTER JOIN djqns_postmeta tpm ON tpm.post_id = tp.ID AND tpm.meta_key = “_thumbnail_id”
    				WHERE 1=1
    				AND (
    					tpm.meta_value = “0”
    					OR tpm.meta_key IS NULL
    				)
    				AND tp.post_type = “product”
    				ORDER BY tp.ID
                )
                AND post_type = “product”
                ORDER BY ID
            ) tmp
		‘;
        
        $where .= ‘ AND (‘ . $wpdb->posts . ‘.ID ‘ . $condition . ‘ (‘ . $queryStr . ‘)) ‘;
    }
    
    return $where;
}
add_filter(‘posts_where’ , ‘custom__woocommerce_filter_by_has_image_where_statement’, 10, 2);

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

61

62

63

64

65

66

67

68

69

70

71

72

/*

* Woocommerce Filter by has image

*/

function custom__woocommerce_filter_by_hasimage($output) {

global $wp_query;

$selected = 0;

if (isset($_GET[‘product_hasimage’])) {

$selected = (int)$_GET[‘product_hasimage’];

}

$output .= ‘

<option value=””>Filter by image</option>

<option value=”1″ ‘ . (($selected === 1) ? ‘selected=”selected”‘ : ”) . ‘>Has Image</option>

<option value=”2″ ‘ . (($selected === 2) ? ‘selected=”selected”‘ : ”) . ‘>Has No Image</option>

</select>

‘;

return $output;

}

add_action(‘woocommerce_product_filters’, ‘custom__woocommerce_filter_by_hasimage’);

/*

* Woocommerce Filter by on has image where statement

*/

function custom__woocommerce_filter_by_has_image_where_statement($where, $query) {

global $wpdb;

// Only trigger if required

if (!is_admin() || $_GET[‘post_type’] != “product” || !isset($_GET[‘product_hasimage’]) || (int)$_GET[‘product_hasimage’] <= 0) {

return $where;

}

// Is filter applied

if ($_GET[‘product_hasimage’] > 0) {

// What condition to check

$condition = ‘IN’;

if ($_GET[‘product_hasimage’] == 1) {

$condition = ‘NOT IN’;

}

// Query

$queryStr = ‘

SELECT ID FROM (

SELECT ID

FROM djqns_posts

WHERE ID IN (

SELECT tp.ID

FROM djqns_posts tp

LEFT OUTER JOIN djqns_postmeta tpm ON tpm.post_id = tp.ID AND tpm.meta_key = “_thumbnail_id”

WHERE 1=1

AND (

tpm.meta_value = “0”

OR tpm.meta_key IS NULL

)

AND tp.post_type = “product”

ORDER BY tp.ID

)

AND post_type = “product”

ORDER BY ID

) tmp

‘;

$where .= ‘ AND (‘ . $wpdb–>posts . ‘.ID ‘ . $condition . ‘ (‘ . $queryStr . ‘)) ‘;

}

return $where;

}

add_filter(‘posts_where’ , ‘custom__woocommerce_filter_by_has_image_where_statement’, 10, 2);

This code is provided as it and may require changes to work for your needs.

17th December 2020

WooCommerce delayed webhooks using actions scheduler

Recently been contacted by a user who needed the ability to delay the WooCommerce webhooks by x time, this would allow other processes happening on the site to finish instead of firing the webhook straight away, for example waiting for the payment process to finalise. Delaying webhooks is not common practice, however some time special case arises!

Take a look at actions scheduler if you wish to read more into the scheduler system used by WooCommerce.

Code

The following code allows you to delay several WooCommerces webhooks by a set duration (seconds) and also run in two modes.

Single Webhook, creates 1 single webhook but delayed by x seconds.
Multi Webhook, creates 2 webhooks, the normal webhook created by WooCommerce and a second repeat webhook which runs x seconds later.

function filter_woocommerce_webhook_deliver_async($true, $instance, $arg) {
    // Replace default schedule action? (single web hook fired, with delay)
    // Or schedule a seperate delayed action (default webhook fied with a second delayed web hook)
    $singleWebhook = false;
    
    // Target webhook topics
    $targetWebhookTopics = [
        ‘order.updated’,
    ];
    
    // Delay time in seconds
    $delayTime = 300;
    
    // If order.update, we want to create a seperate delayed webhook via schedule actions
    if (in_array($instance->get_topic(), $targetWebhookTopics)) {
        $payload = [‘webhook_id’ => $instance->get_id(), arg => $arg];
        $group = $singleWebhook ? ‘woocommerce-webhooks’ : ‘woocommerce-webhooks-delayed’;
        
        // Schedule a single action to run in 5 minutes, to cause the order.update to fire (delayed)
        // Make sure to run as_next_scheduled_action so multiple instances are not scheduled if one is already scheduled
        if (as_next_scheduled_action(‘woocommerce_deliver_webhook_async’, $payload, $group) === false) {
            as_schedule_single_action(time() + $delayTime, ‘woocommerce_deliver_webhook_async’, $payload, $group);
        }
    }
    
    return $true;
};
add_filter(‘woocommerce_webhook_deliver_async’, ‘filter_woocommerce_webhook_deliver_async’, 10, 3);

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

function filter_woocommerce_webhook_deliver_async($true, $instance, $arg) {

// Replace default schedule action? (single web hook fired, with delay)

// Or schedule a seperate delayed action (default webhook fied with a second delayed web hook)

$singleWebhook = false;

// Target webhook topics

$targetWebhookTopics = [

‘order.updated’,

];

// Delay time in seconds

$delayTime = 300;

// If order.update, we want to create a seperate delayed webhook via schedule actions

if (in_array($instance–>get_topic(), $targetWebhookTopics)) {

$payload = [‘webhook_id’ => $instance–>get_id(), arg => $arg];

$group = $singleWebhook ? ‘woocommerce-webhooks’ : ‘woocommerce-webhooks-delayed’;

// Schedule a single action to run in 5 minutes, to cause the order.update to fire (delayed)

// Make sure to run as_next_scheduled_action so multiple instances are not scheduled if one is already scheduled

if (as_next_scheduled_action(‘woocommerce_deliver_webhook_async’, $payload, $group) === false) {

as_schedule_single_action(time() + $delayTime, ‘woocommerce_deliver_webhook_async’, $payload, $group);

}

return $true;

};

add_filter(‘woocommerce_webhook_deliver_async’, ‘filter_woocommerce_webhook_deliver_async’, 10, 3);

This code is provided as it and may require changes to work for your needs.

12th November 2020

Fix WooCommerce webhook loop when using WooCommerce API

Problem (Quick)

Updating a product via the WooCommerce API would fire an update webhook, causing a loop of webhook and API activity which never ended.

Problem

Created a script which keeps stock levels synced between WooCommerce and a stock management system, WooCommerce WebHooks are used to set products stock levels in near real time. Using WooCommerce API new stock levels are pushed to WooCommerce, however with each API push this would trigger a product updated webhook, causing my script to reinforce the stock levels via API (causing an unlimited updating loop).

Solution

We can use woocommerce_webhook_should_deliver filter to control if a webhook should be delivered.

The following example shows how I used the clients IP address (in this example my scripts server) to stop webhook delivery for any requests from that IP address, this allows my script to use the API and webhooks will never be delivered.

function custom_woocommerce_webhook_should_deliver($shouldDeliver, $webhookObject, $arg) {
	// Is this a REST request?
        if (defined(‘REST_REQUEST’) && REST_REQUEST) {
		// Determine IP address
		if (!empty($_SERVER[‘HTTP_CLIENT_IP’])) {
			//check ip from share internet
			$ip = $_SERVER[‘HTTP_CLIENT_IP’];
		} elseif (!empty($_SERVER[‘HTTP_X_FORWARDED_FOR’])) {
			// to check ip is pass from proxy
			$ip = $_SERVER[‘HTTP_X_FORWARDED_FOR’];
		} else {
			$ip = $_SERVER[‘REMOTE_ADDR’];
		}
		
		if ($ip == ‘123.123.123.123’) {
			$shouldDeliver = false;
		}
	}

	return $shouldDeliver;
}
add_filter(‘woocommerce_webhook_should_deliver’, ‘custom_woocommerce_webhook_should_deliver’, 10, 3);

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

function custom_woocommerce_webhook_should_deliver($shouldDeliver, $webhookObject, $arg) {

// Is this a REST request?

if (defined(‘REST_REQUEST’) && REST_REQUEST) {

// Determine IP address

if (!empty($_SERVER[‘HTTP_CLIENT_IP’])) {

//check ip from share internet

$ip = $_SERVER[‘HTTP_CLIENT_IP’];

} elseif (!empty($_SERVER[‘HTTP_X_FORWARDED_FOR’])) {

// to check ip is pass from proxy

$ip = $_SERVER[‘HTTP_X_FORWARDED_FOR’];

} else {

$ip = $_SERVER[‘REMOTE_ADDR’];

}

if ($ip == ‘123.123.123.123’) {

$shouldDeliver = false;

}

return $shouldDeliver;

}

add_filter(‘woocommerce_webhook_should_deliver’, ‘custom_woocommerce_webhook_should_deliver’, 10, 3);

13th March 2020

WooCommerce fix slow or delayed webhooks and achieve instant webhook firing

I’ve recently been working on a project which synced data between WooCommerce and an internal warehouse system, I was utilising the WooCommerce webhooks to achieve near real time syncing between the two systems, without having the creating API scripts to poll for data on a regular basis.

The Problem?

There was a delay ranging from couple seconds to 1 minute, WooCommerce uses a system called actions scheduler, this is an improved wordpress cron, allowing background processing to occur within WordPress for single or recurring actions. This is great and what WooCommerce utilises for its web hook system, however it is backed by the word press cron and the next load of scheduled actions will run on the next cron run (every 1 minute).

For this project, I needed the web hooks to fire as soon as the button was clicked, and a possible delay up to 1 minute was to long.

Fix

Disable async web hooks, web hooks will not fire as soon as they are created as part of the browser request.

/*
 * WooCommerce Disable async webhook delivery
 */
function custom_woocommerce_disable_async_webhook() {
	return false;
}
add_filter(‘woocommerce_webhook_deliver_async’, ‘custom_woocommerce_disable_async_webhook’);

1

2

3

4

5

6

7

/*

* WooCommerce Disable async webhook delivery

*/

function custom_woocommerce_disable_async_webhook() {

return false;

}

add_filter(‘woocommerce_webhook_deliver_async’, ‘custom_woocommerce_disable_async_webhook’);

I would recommend you test your site after doing this change, for example order webhooks will fire when a customer creates a new order, which could lead to a slow user experience.

1st October 2019

WooCommerce admin products filter by on sale

I needed the ability to filter the WooCommerce products list within admin by products which where on sale. This was to allow the client to easily find products they have put on offer within certain categories. The below code achieves this.

It does need some work, as it currently ignores the on sale start and end dates, however you should be able to easily modify it for this purpose.

/*
 * Woocommerce Filter by on sale
 */
function custom_woocommerce_filter_by_onsale($output) {
	global $wp_query;
	
    $selected = filter_input(INPUT_GET, ‘product_sale’, FILTER_VALIDATE_INT);
    if ($selected == false) {
        $selected = 0;
    }
	
	$output .= ‘
		<select id=”dropdown_product_sale” name=”product_sale”>
			<option value=””>Filter by sale</option>
			<option selected=”selected” value=”1″>On sale</option>
			<option selected=”selected” value=”2″>Not on sale</option>
		</select>
	‘;
	
	return $output;
}
add_action(‘woocommerce_product_filters’, ‘custom_woocommerce_filter_by_onsale’);



/*
 * Woocommerce Filter by on sale where statement
 */
function custom_woocommerce_filter_by_onsale_where_statement($where) {
	global $wp_query, $wpdb;

    // Get selected value
    $selected = filter_input(INPUT_GET, ‘product_sale’, FILTER_VALIDATE_INT);
    
    // Only trigger if required
    if (!is_admin() || $_GET[‘post_type’] != “product” || !$selected) {
        return $where;
    }

	$productsIDs = [];
	if ($selected == 1) {
		$querystr = ‘
			SELECT p.ID, p.post_parent
			FROM ‘ . $wpdb->posts . ‘ p
			WHERE p.ID IN (
				SELECT post_id FROM ‘ . $wpdb->postmeta . ‘ pm WHERE pm.meta_key = “_sale_price” AND pm.meta_value > \’\’
			)
		‘;
		
		$pageposts = $wpdb->get_results($querystr, OBJECT);
		
		$productsIDs = array_map(function($n){
			return $n->post_parent > 0 ? $n->post_parent : $n->ID;
		}, $pageposts);
	} elseif ($selected == 2) {
		$querystr = ‘
			SELECT p.ID, p.post_parent
			FROM ‘ . $wpdb->posts . ‘ p
			WHERE p.ID NOT IN (
				SELECT post_id FROM ‘ . $wpdb->postmeta . ‘ pm WHERE pm.meta_key = “_sale_price” AND pm.meta_value > \’\’
			)
		‘;
		
		$pageposts = $wpdb->get_results($querystr, OBJECT);
		
		$productsIDs = array_map(function($n){
			return $n->post_parent > 0 ? $n->post_parent : $n->ID;
		}, $pageposts);
	}
	
	$where .= ‘ AND ‘ . $wpdb->posts . ‘.ID IN (‘ . implode(“,”, $productsIDs) . ‘) ‘;
	
	return $where;
}
add_filter(‘posts_where’ , ‘custom_woocommerce_filter_by_onsale_where_statement’);

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

61

62

63

64

65

66

67

68

69

70

71

72

73

74

75

/*

* Woocommerce Filter by on sale

*/

function custom_woocommerce_filter_by_onsale($output) {

global $wp_query;

$selected = filter_input(INPUT_GET, ‘product_sale’, FILTER_VALIDATE_INT);

if ($selected == false) {

$selected = 0;

}

$output .= ‘

<option value=””>Filter by sale</option>

</select>

‘;

return $output;

}

add_action(‘woocommerce_product_filters’, ‘custom_woocommerce_filter_by_onsale’);

/*

* Woocommerce Filter by on sale where statement

*/

function custom_woocommerce_filter_by_onsale_where_statement($where) {

global $wp_query, $wpdb;

// Get selected value

$selected = filter_input(INPUT_GET, ‘product_sale’, FILTER_VALIDATE_INT);

// Only trigger if required

if (!is_admin() || $_GET[‘post_type’] != “product” || !$selected) {

return $where;

}

$productsIDs = [];

if ($selected == 1) {

$querystr = ‘

SELECT p.ID, p.post_parent

FROM ‘ . $wpdb–>posts . ‘ p

WHERE p.ID IN (

SELECT post_id FROM ‘ . $wpdb–>postmeta . ‘ pm WHERE pm.meta_key = “_sale_price” AND pm.meta_value > \’\’

)

‘;

$pageposts = $wpdb–>get_results($querystr, OBJECT);

$productsIDs = array_map(function($n){

return $n–>post_parent > 0 ? $n–>post_parent : $n–>ID;

}, $pageposts);

} elseif ($selected == 2) {

$querystr = ‘

SELECT p.ID, p.post_parent

FROM ‘ . $wpdb–>posts . ‘ p

WHERE p.ID NOT IN (

SELECT post_id FROM ‘ . $wpdb–>postmeta . ‘ pm WHERE pm.meta_key = “_sale_price” AND pm.meta_value > \’\’

)

‘;

$pageposts = $wpdb–>get_results($querystr, OBJECT);

$productsIDs = array_map(function($n){

return $n–>post_parent > 0 ? $n–>post_parent : $n–>ID;

}, $pageposts);

}

$where .= ‘ AND ‘ . $wpdb–>posts . ‘.ID IN (‘ . implode(“,”, $productsIDs) . ‘) ‘;

return $where;

}

add_filter(‘posts_where’ , ‘custom_woocommerce_filter_by_onsale_where_statement’);

This code is provided as it and may require changes to work for your needs.

1st May 2019

Tag: php

Code

Why would you need this?

Fix

1. Lock Files

2. Full Reindexing

Code

What is XMLRPC?

Pre-Checks

1st Attempt

2nd Attempt

Code

Code

Problem (Quick)

Problem

Solution

The Problem?

Fix