{"id":2489,"date":"2008-02-10T16:40:29","date_gmt":"2008-02-10T16:40:29","guid":{"rendered":"https:\/\/wordpress.org\/plugins-wp\/humanized-history-for-wordpress\/"},"modified":"2008-02-26T00:03:56","modified_gmt":"2008-02-26T00:03:56","slug":"humanized-history-for-wordpress","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/humanized-history-for-wordpress\/","author":16327,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"2008.02.10","stable_tag":"trunk","tested":"2.3.3","requires":"2.0","requires_php":"","requires_plugins":"","header_name":"Humanized History","header_author":"Charles Johnson","header_description":"","assets_banners_color":"","last_updated":"2008-02-26 00:03:56","external_support_url":"","external_repository_url":"","donate_link":"http:\/\/projects.radgeek.com\/humanized-history-for-wordpress\/","header_plugin_uri":"http:\/\/projects.radgeek.com\/humanized-history-for-wordpress\/","header_author_uri":"http:\/\/projects.radgeek.com","rating":0,"author_block_rating":0,"active_installs":0,"downloads":1917,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation"],"tags":[],"upgrade_notice":[],"ratings":{"1":0,"2":0,"3":0,"4":0,"5":0},"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["2007.10.08","2007.11.29","2008.02.10"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[35327,3918,243,3893],"plugin_category":[],"plugin_contributors":[],"plugin_business_model":[],"class_list":["post-2489","plugin","type-plugin","status-publish","hentry","plugin_tags-humanized-history","plugin_tags-interface","plugin_tags-pages","plugin_tags-usability","plugin_committers-radgeek"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/humanized-history-for-wordpress.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"\n

This plugin implements a \"Humanized History\"<\/a> feature for WordPress\narchives, using some PHP glue on the back end and some unobtrusive\nJavaScript on the front-end. In JavaScript-enabled browsers, Humanized\nHistory eliminates the need for users to click on \"previous posts\" links to\nread back through your archives; instead, when users get near the bottom of\nthe current page of posts, the included JavaScript automatically displays\nmore posts for them at the bottom of the page, providing a magic endless\nscrollbar that scrolls through your entire archives, in place of traditional\npage chunking.<\/p>\n\n

Search robots and browsers without JavaScript enabled will see the same old\npages with previous page\/next page links, so you lose nothing in accessibility\nor friendliness to search engines.<\/p>\n\n

The plugin was inspired by the discussion of the concept by Aza Raskin at\nHumanized (2006-04-25): No More Pages?<\/a>. To see a sample of the feature as\nimplemented in WordPress, go to http:\/\/projects.radgeek.com\/<\/a> and scroll down\ntoward the bottom of the page.<\/p>\n\n

Don't make your readers ask you for more content. Just give it to them.<\/em><\/p>\n\n

Templates and Styling<\/h3>\n\n

If your index.php<\/code> and archive.php<\/code> templates provide previous page \/ next\npage links at the bottom of the content, you will probably want to remove these\nlinks from your templates. The plugin automatically provides its own previous\npage \/ next page links at the bottom of the front page and archive pages.<\/p>\n\n

Many WordPress templates (including the default \"Kubrick\" template) display\nposts differently depending on whether they are in archives or in search\nresults. \"Kubrick,\" for example, doesn't display the post's contents in search\nresults. If you want to keep different formats for displaying archives as\nagainst search results, then use code something like this in your\n template_post_display() function:<\/p>\n\n

function template_post_display () {\n    if (is_search()) {\n    \/\/ display post for paged search results\n} else {\n    \/\/ display post for paged archives\n}\n}\n<\/code><\/pre>\n\n
You may also want to add some styling to your template's stylesheet for the\nnavigation links that the plugin automatically generates. Here is what I use to\ndisplay the \"older posts\" link at the far left side of the content column, and\nthe \"newer posts\" link at the far right side on the same line:<\/p>\n\n
#content .navigation {\n    display: block; position: relative; list-style: none;\n    text-align: center;\n    margin-top: 10px; margin-bottom: 60px; margin-left: 0px; margin-right: 0px;\n    padding: 0;\n}\n\n#content .navigation .prev {\n    display: block; position: relative; list-style: none;\n    top: 0; bottom: auto; left: 0; right: auto; width: 45%;\n    margin: 0; padding: 0;\n    text-align: left;\n}\n\n#content .navigation .next {\n    display: block; position: absolute; list-style: none;\n    top: 0; bottom: auto; left: auto; right: 0; width: 45%;\n    margin: 0; padding: 0;\n    text-align: right;\n}\n<\/code><\/pre>\n\n
If you want to change the appearance of the \"Getting more content for you...\"\nstatus indicator, then add a rule to your CSS stylesheet for the class\n    humanized-history-getting-more. E.g., to create a dark translucent box that\nfloats over the footer material below:<\/p>\n\n
.humanized-history-getting-more {\n    position: absolute;\n    width: auto; height: auto;\n    border: 3px solid #505050;\n    padding: 0.25em 1.0em;\n    background-color: #777777;\n    opacity: 0.85;\n    z-index: 10000;\n}<h3>Feedback<\/h3>\n<\/code><\/pre>\n\n
Comments, questions, applause, brickbats, and bug reports should be directed to\nCharles Johnson at technophilia@radgeek.com<\/a>. Other ways to get in touch with\nme can be found through my web page at http:\/\/radgeek.com\/contact<\/a>. If you have\na bug or odd behavior to report, please be sure to include as much of the\nfollowing information as you can ascertain:<\/p>\n\n