richfranz

it is possible because i accomplished this using the custom CSS field.

turn on Floating buttons, put 0 in the position fields and write your own positioning CSS in the custom field. works just fine.

the reason is for mobile responsiveness. a div 25% from the top at 1920×1080 won’t be in the same spot at 1366×768, the two most popular resolutions in North America. you cant use a blanket position value for all resolutions.

sent same message at crestaproject.com/support with link.

thx.

when attemting to block an IP range chosen from live traffic, Wordfence wouldn’t complete the task – instead returning a popup telling me i need to type something into “Enter a reason you’re blocking this visitor pattern:” field. The problem is i had already filled the field in.

The issue first arose minutes after the update to 6.0.20

Either way the good news is it seems to be working again all of a sudden, so problem solved? ??

Cheers!

everything seems to be working now. after a few hours from upgrade to 4.3 elements re-appeared in working order.

thanks.