Creating a table for such functionality in WordPress is not an efficient move. I would prefer to do this using follwoing approach. Create Custom post type for your voters info. For this you can try Generate WP post type generator. When ever user visits your site; save IP and rating in post meta using wp … Read more
Are you using the same internet connection on multiple devices? Perhaps your mobile is connected to the same wifi network. Visit http://icanhazip.com in your mobile to see its IP. As for browserstack perhaps they aren’t accepting the cookie so their IP doesn’t get recorded. You should record the timestamp as well so you can correlate … Read more
Open a Terminal or CMD and type ping www.jijojose.me then press Enter. The IP address listed it’s the server’s IP address. However You won’t be able to access you website this way (e.g. http://173.252.100.16) unless: You know the folder where it is located on the server, and your server has mod_userdir or similar extension enabled … Read more
When WordPress logs you in, it creates a cookie on your system to keep you logged in if you want. However, being logged in from another location doesn’t have much meaning in this context. When you go back to your WP site, WordPress will check for the existence of this authentication cookie on your system. … Read more
I think your problem here is the esc_url() function which is used to sanitize a lot of the URLs used in wp-core. If you have a look at the function definition in formatting.php you’ll see that the regex in line 2627 is filtering out [ and ]. But fortunately you can also see that in … Read more
If you have access to your mysql you can update the wp-options table. Before modification… $ mysql -u <db_user> –password=<db_pwd> -D <db_name> <<<“select * from wp_options where option_name in (‘siteurl’, ‘home’);” +———–+—————–+—————————————————————————————————+———-+ | option_id | option_name | option_value | autoload | +———–+—————–+—————————————————————————————————+———-+ | 1 | siteurl | http://172.17.0.2/wordpress | yes | | 2 | home … Read more
Add this to your functions.php: add_filter(‘pre_comment_user_ip’, ‘no_ips’); function no_ips($comment_author_ip){ return ”; } You’ll still have the comment_author_IP field in the db, but it will be empty… And to remove existing IP records from the db run this query: UPDATE `wp_comments` SET `comment_author_IP` = ”
You can filter ‘get_comment_author_IP’: add_filter( ‘get_comment_author_IP’, ‘wpse_77254_trim_comment_ip’ ); function wpse_77254_trim_comment_ip( $ip ) { return implode( ‘.’, array_slice(explode( ‘.’, $ip ), 2) ) . ‘…’; } Note this will fail with IPv6 addresses.
As already suggested in a comment above of mine, technically a (cookie based) session is limited to one IP at a time by using the Safer Cookies (WordPress Plugin). This does not prevent another login with the same username and password because it is a feature of WordPress to allow you to login multiple times … Read more
I usually just avoid the issue entirely every time I create a new wordpress site: define(‘WP_HOME’, “https://wordpress.stackexchange.com/”); define(‘WP_SITEURL’, “https://wordpress.stackexchange.com/”); will cause wordpress to use root-relative urls for everything. Makes site migrations to other domains far easier. Ofc, if you access your site using a folder (eg. “http://<domain>/blog“) you could change them to: define(‘WP_HOME’, ‘/blog/’); define(‘WP_SITEURL’, … Read more