2gen

@oneill78 we are faced with the same problem. We created a custom role and assigned permissions using the User Role Editor. This is now broken and our custom roles and accounts with that role can no longer do their job in managing orders.

Were you able to find a solution?

I tested with the User Role Editor and gave the custom role ALL capabilities (even deprecated ones) and it still didn’t allow our custom role to modify orders.

No, the site doesn’t load the content via AJAX. If you watch the network tab in the debugger/inspector you can see the only XHR requests are the map search. The page is here:

https://debtsolutions.bdo.ca/contact-us-for-a-free-consultation/

Try something like:

if (function_exists('z_taxonomy_image_url')) { 
  echo '<img src="' . z_taxonomy_image_url( $child, $taxonomy_name, TRUE ) . '" />';
}

Note the added “TRUE” in the function call. This returns the image located at the following path if one isn’t set: /wp-content/plugins/categories-images/images/placeholder.png

Change your code to:
<?php if (function_exists(‘z_taxonomy_image_url’)) echo z_taxonomy_image_url(NULL, NULL, TRUE); ?>

The last value in the z_taxonomy_image_url() function is a flag to return the default image if none is set. The default image is located in: /wp-content/plugins/categories-images/images/placeholder.png

Your “impression timer” fix is like throwing out an anchor to keep your boat from speeding while you hold open the throttle

Harsh, but completely accurate.

While attempting to figure out why a server was going sporadically down/rebooting every day; there were many POST requests to the admin-ajax.php file. After ruling out the WordPress Heartbeat, it was finally discovered that it was AdRotate impressions timer logging impression data into the database.

False impressions.

As G P wrote, I can confirm: The “cooldown” for re-counting impressions is a false indicator that will increase even if a user has left their computer open on a page that has a rotating add.

These “impressions” place an increased load on the server from each user that has left the page open (which ranged from 5-10 users in this case) every 10 seconds (or whatever the timer is set to), each request taking between 1.5-2.5 seconds. This kept the load on the database high, and bogged down other site access by hogging server resources by flooding the server with Apache daemon to handle the ajax requests.

Not only are the impressions false, but it skews the CTR and other stats based on the inflated “shown”/”impression” counts.