wp-code.com Report : Visit Site

Technical data of the wp-code.com

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host wp-code.com. Currently, hosted in Bulgaria and its service provider is GetClouder EOOD .

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called cloudflare containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

wordpress code snippets for wordpress theme and plugin authors how to add facebook stats to wordpress custom post types posted on december 23, 2015 written by mark barnes leave a comment when you’re creating a wordpress site with custom post types, it’s often useful to know how many likes, shares and comments each post is getting on facebook. there are one or two plugins that will give you this information, but they haven’t been updated in a while, and don’t always work too well. but it’s relatively easy to code your own. here’s the end result, as seen at the evangelical magazine site.: first, we need to write the function that will actually get the stats from facebook. facebook provides a very simple public api that requires no authentication or registration, and it returns the stats in json format. i’m storing each stat in a separate entry in post meta (as that makes it easy to sort on, which we’ll need later). but we don’t want the stats cached indefinitely, so each post also has a transient that records whether or not the stats are fresh. the transient will last for up to a week, although it the post is less than a week old, it will only last for a shorter time. with the code below, if the transient is present, we’ll read the stats from the post meta, if it’s not present, we’ll look the stats up from the facebook api. /** * gets the facebook stats for a given post id * * @param int $post_id * @return array * */ public function wcs_get_facebook_stats($post_id) { $transient_name = "wcs_fb_valid_{$post_id}"; $stats = get_transient($transient_name); if (!$stats) { $json = wp_remote_request('https://api.facebook.com/method/links.getstats?urls='.urlencode(get_permalink($post_id)).'&format=json'); $stats = json_decode(wp_remote_retrieve_body($json), true); if ($stats !== null && isset($stats[0])) { update_post_meta($post_id, 'wcs_fb_likes', $stats[0]['like_count']); update_post_meta($post_id, 'wcs_fb_comments', $stats[0]['comment_count']); update_post_meta($post_id, 'wcs_fb_shares', $stats[0]['share_count']); update_post_meta($post_id, 'wcs_fb_total', $stats[0]['total_count']); $post = get_post($post_id); $secs_since_published = time() - strtotime($post->post_date); set_transient ($transient_name, true, $secs_since_published > 604800 ? 604800 : $secs_since_published); //the transient will last for up to a week. posts that are fresh will cache their stats for a shorter time than older posts. } } return array ( 'likes' => get_post_meta($post_id, 'wcs_fb_likes', true), 'comments' => get_post_meta($post_id, 'wcs_fb_comments', true), 'shares' => get_post_meta($post_id, 'wcs_fb_shares', true), 'total' => get_post_meta($post_id, 'wcs_fb_total', true)); } now that’s done, we can set up all the filters and actions we need. there are quite a few of them, but most of them are pretty simple. i’ll explain each filter/action as we go. first, we need to tell wordpress which columns to add to which custom post type. for that, we need the manage_edit-{custom_post_type}_columns filter. in this demo, my custom post type is called wcs_article , so the filter is manage_edit-wcs_article_columns . we simply add the elements we need to the $columns array. add_filter ('manage_edit-wcs_article_columns', 'wcs_filter_columns'); /** * adds columns to the articles admin page * * filters manage_edit-wcs_article_columns * * @param mixed $columns */ function wcs_filter_columns ($columns) { $columns ['fb_likes'] = 'likes'; $columns ['fb_shares'] = 'shares'; $columns ['fb_comments'] = 'comments'; $columns ['fb_total'] = 'total'; return $columns; } next, we need to output the content of each column. we do that on the manage_{custom_post_type}_posts_custom_column , which for us is manage_wcs_article_posts_custom_column . the function checks to see whether the post has been published. if it has, it gets the stats, and then outputs whichever variable is required. add_action ('manage_wcs_article_posts_custom_column', 'wcs_output_columns', 10, 2); /** * outputs the additional columns on the articles admin page * * filters manage_wcs_article_posts_custom_column * * @param string $column * @param int $post_id */ function wcs_output_columns ($column, $post_id) { global $post; if ($post->post_status == 'publish') { $fb_stats = wcs_get_facebook_stats($post_id); if (is_array ($fb_stats) && in_array ($column, array ('fb_likes', 'fb_shares', 'fb_comments', 'fb_total'))) { echo $fb_stats[substr($column, 3)]; } } } that’s already functional, but the columns we’ve added are too wide. we can add an action to admin_head to fix that. it’s just a single line of css. add_action ('admin_head', 'wcs_add_styles_to_admin_head'); /** * adds styling to the admin head. * */ function wcs_add_styles_to_admin_head () { echo '<style type="text/css">.column-fb_likes, .column-fb_shares, .column-fb_comments, .column-fb_total {width: 10%}</style>'; } and that’s actually all that we need to display the stats. you could stop there if you want. but i find it helpful to have the columns sortable, and to do that we need a few more filters and actions. the first filter is manage_edit-{custom_post_type}_sortable_columns , which for us is manage_edit-wcs_article_sortable_columns . the filter receives a list of the columns that can be sorted, and we simply add our columns to the list. add_filter ('manage_edit-wcs_article_sortable_columns', 'wcs_make_columns_sortable'); /** * sets the custom columns to be sortable * * filters manage_edit-wcs_article_sortable_columns * * @param array $columns * @return array */ function wcs_make_columns_sortable ($columns) { $columns ['fb_likes'] = 'fb_likes'; $columns ['fb_shares'] = 'fb_shares'; $columns ['fb_comments'] = 'fb_comments'; $columns ['fb_total'] = 'fb_total'; return $columns; } the second part of this puzzle is to modify the wordpress query so that the sort actually takes place. we can do that on the pre_get_posts action. the function will check that we’re in admin mode, and that we’re on the right screen for this custom post type. if we are, and the query contains an ‘orderby’ request for one of our column names, we amend the query by setting the orderby value to meta_value_num onthe appropriate column. add_action ('pre_get_posts', 'wcs_sort_by_columns'); /** * modifies the query to sort by columns, if requested * * runs on the pre_get_posts action * * @param wp_query $query */ function wcs_sort_by_columns ($query) { if (is_admin()) { $screen = get_current_screen(); if ($screen->id == 'edit-wcs_article') { $columns = array ( 'fb_likes' => 'wcs_fb_likes', 'fb_shares' => 'wcs_fb_shares', 'fb_comments' => 'wcs_fb_comments', 'fb_total' => 'wcs_fb_total'); $orderby = $query->get('orderby'); if ($orderby && isset($columns[$orderby])) { $query->set ('meta_key', $columns[$orderby]); $query->set ('orderby','meta_value_num'); } } } } the code is now complete for adding, displaying and sorting by facebook stats. the final piece of the jigsaw is the ability to re-check the stats before the cache expires. to do that we’ll add a new action in post_row_actions . the first function filters the existing actions, and adds a new one, which i’ve labelled ‘recalc fb’. theoretically, we could just add a query parameter to the url of the current screen, but the code below also retains several existing parameters, to ensure that after the action we end back in the same place as when we began. add_filter ('post_row_actions', 'wcs_filter_post_row_actions', 10, 2); /** * adds the 'recalc_fb' row action to articles * * filters post_row_actions * * @param array $actions * @param wp_post $post * @return array */ function wcs_filter_post_row_actions ($actions, $post) { global $current_screen; if ($post->post_type == 'wcs_article') { $possible_variables = array ('paged', 'orderby', 'order', 'author', 'all_posts', 'post_status'); $arguments = array('recalc_fb' => $post->id); foreach ($possible_variables as $p) { if (isset($

URL analysis for wp-code.com

https://www.wp-code.com/tag/deprecated/
https://www.wp-code.com/tag/delete-post/
https://www.wp-code.com/tag/wp_register_style/
https://www.wp-code.com/tag/create_function/
https://www.wp-code.com/tag/lorem-ipsum/
https://www.wp-code.com/tag/excerpt/
https://www.wp-code.com/tag/wp_update_nav_menu/
https://www.wp-code.com/2014/04/
https://www.wp-code.com/tag/filter/
https://www.wp-code.com/tag/set_transient/
https://www.wp-code.com/wordpress-snippets/how-to-stop-chrome-using-a-large-font-size-after-refreshing/
https://www.wp-code.com/tag/browser/
https://www.wp-code.com/tag/synchronise/
https://www.wp-code.com/wordpress-snippets/how-to-make-sure-the-correct-domain-is-used-in-wpml/
https://www.wp-code.com/tag/widgets/

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

Domain Name: WP-CODE.COM
Registry Domain ID: 1716297354_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.cloudflare.com
Registrar URL: http://www.cloudflare.com
Updated Date: 2018-12-26T05:20:35Z
Creation Date: 2012-04-27T00:56:42Z
Registry Expiry Date: 2020-04-27T00:56:42Z
Registrar: CloudFlare, Inc.
Registrar IANA ID: 1910
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: NS1.UK47.SITEGROUND.EU
Name Server: NS2.UK47.SITEGROUND.EU
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2019-07-14T17:25:13Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.

  REGISTRAR CloudFlare, Inc.

SERVERS

  SERVER com.whois-servers.net

  ARGS domain =wp-code.com

  PORT 43

  TYPE domain

DOMAIN

  NAME wp-code.com

  CHANGED 2018-12-26

  CREATED 2012-04-27

STATUS
clientTransferProhibited https://icann.org/epp#clientTransferProhibited

NSERVER

  NS1.UK47.SITEGROUND.EU 77.104.180.47

  NS2.UK47.SITEGROUND.EU 77.104.130.147

  REGISTERED yes

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .