Jili casino gcash register.Claim Your Free 999 Pesos Bonus Today

Reply To: Changing the look on a plugin

bcworkz — Wed, 16 Oct 2019 18:52:00 +0000

I don’t see anything alarming in your functions.php. You are probably correct, that the element is added by JS after your code runs. However, your while loop logic is flawed. If the element is not initially found, elm is null and your code never tries again later. Anyway, looping until something shows up is not a good approach. If you ensure your code runs after the code that adds the element, you shouldn’t have to loop until it shows up, it should already exist. Ensure your code runs late by enqueuing your script while listing the code that adds the element as a dependency. In the wp_enqueue_script() call, also specify that your script should be loaded in the footer.

If your intent is to hide this element why not just place the CSS for it in the Additional CSS panel of the customizer? Why use JS to hide it?

Reply To: Changing the look on a plugin

haffy — Thu, 17 Oct 2019 08:21:49 +0000

I tried to use JS as I wanted to do it with JS ?? To learn. And it did not work with CSS.

I have solved it by changing the CSS at the developer’s site (it′s a connected plugin with a shortcode), so it gets its CSS from there. That′s why I was trying to make a while loop to grab it when it was loaded.

Reply To: Changing the look on a plugin

bcworkz — Thu, 17 Oct 2019 16:11:05 +0000

Cool! FWIW, you can override external CSS with local inline CSS. You need to ensure your override comes after the external reference. You solved it though, that’s all that matters.