By installing the Sphere Related Content plugin you agree to the Sphere Related Content Terms of Service listed here: http:\/\/www.sphere.com\/tosrc<\/p>\n\n
Copy the file sphere-related-content.php into your plugins directory (wp-content\/plugins\/).<\/p><\/li>\n
Login to your WordPress Admin Panel<\/p><\/li>\n
Go to the Plugins tab<\/p><\/li>\n
Activate the Sphere Related Content Widget plugin. (Click Activate in the right column).<\/p>\n\n
Now, the Sphere link will be inserted at the bottom of all posts longer than 30 words.\nFor most blogs, this works just peachy and you're done. If you're an advanced user \nand want to customize the behavior and look\/placement of the link, read on.<\/p><\/li>\n
You can now change the type\/theme of the Sphere Related Content plugin. In the admin, click on the\n\"Plugins\" menu and then click on the \"Sphere Configuration\" sub-menu for details and to \nchange your widget type. If you're in doubt about which type to use, stick with Classic.
\nMore types coming soon. When you change a type, reload one of your pages and click on the \nSphere Related Content link to see the widget type you selected.<\/p><\/li>\n
The default behavior is to place the Sphere link automatically within a tag\nat the end of posts that have more than a minimum length. You can modify the plugin's\nsphere-related-content.php file to change that behavior. There are instructions in that file,\nbut here are the basics:<\/p>\n\n
If you NEVER want Sphere links inserted automatically, or if you want to decide where to place\nthe link, rather than having it appended to your posts automatically, then set $auto_sphereit to\nFALSE below and follow the instructions in the readme to customize the look and placement of the link.<\/p>\n\n
If you want Sphere links inserted into ALL of your posts, then set $sphereit_threshold to FALSE below.<\/p>\n\n
You can always force a Sphere link to be inserted by including You can force a Sphere link NOT to be inserted by including If you're not sure what to do, leave the settings below at their default value.<\/p><\/li>\n You can always force a Sphere link to be inserted into a post by putting\n anywhere into the post's text. That comment will not be displayed, but will force\na Sphere link to be inserted for that post.<\/p><\/li>\n Conversely, You can keep a Sphere link from being inserted in a post by adding \n to that post. Again, this marker will not be displayed, but will prevent \na Sphere link from being shown for that post.<\/p><\/li>\n If you want to override the default placement of the link, you should:<\/p>\n\n i) Turn off $auto_sphereit by setting<\/p>\n\n in sphere-related-content.php (search for auto_sphereit to find that line).<\/p>\n\n ii) Put this tag anywhere with in a post context (either in your index, archive or single post templates):<\/p>\n\n If you want to wrap a block-level element around the Sphere link you can do something like this:<\/p>\n\n The enableSphereItLink() check makes sure that your<\/p>\n\n <<\/p>\n\n p> tags are only gong to show up if the Sphere link is turned on \n for that post, as decided by the length of your post or your overrides.<\/p>\n\n If you're doing your own block-level element like this, you'll want to define stules for in your CSS template, e.g.<\/p>\n\n Note these styles are an example only, you can go crazy with the styles and make it look just so in your blog.<\/p>\n\n That's it, you're ready to discover Sphere Related Content. Automatically.<\/p><\/li>\n<\/ol>\n\n\n Your WordPress theme must contain a call to the get_header() function<\/p><\/li>\n Your WordPress theme must contain a call to the the_content()function<\/p><\/li>\n<\/ol>\n\n Please contact Sphere: http:\/\/www.sphere.com\/feedback<\/p>\n\n","raw_excerpt":"Automatically show related blog posts and news articles from Sphere. NEW in this version, related video for news bloggers. You can now select from several plug-in types, see the Sphere Configuration Page<\/a> for details. More plug-in types for politics and other categories coming soon.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/47094","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=47094"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/mremy"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=47094"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=47094"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=47094"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=47094"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=47094"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=47094"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}<!--sphereit--><\/code> in the text of a post.<\/p>\n\n<!--nosphereit--><\/code> in the text of your post.<\/p>\n\n $auto_sphereit = FALSE;\n<\/code><\/pre>\n\n <?= get_sphereit_link( get_permalink(), $post->post_content ) ?>\n<\/code><\/pre>\n\n <?= (enableSphereItLink($post->post_content) ? '<p class=\"sphere\">'.get_sphereit_link(get_permalink(), $post->post_content).'<\/p>' : '') ?>\n<\/code><\/pre>\n\n .sphere {\n padding: 10px;\n margin: 10px;\n border-left: 2px solid red;\n } \n<\/code><\/pre>\n\nRequirements<\/h3>\n\n
\n
Support<\/h3>\n\n