Changeset 789474
- Timestamp:
- 10/17/2013 07:48:47 PM (12 years ago)
- File:
-
- 1 edited
-
lips/trunk/readme.txt (modified) (6 diffs)
Legend:
- Unmodified
- Added
- Removed
-
lips/trunk/readme.txt
r669503 r789474 2 2 Contributors: bastb 3 3 Donate link: http://www.tenberge-ict.nl/tools/wordpress/lips/ 4 Tags: LinkedIn, API, OAuth, profile, zzp, freelance, cv, experience, resume, template, Smarty, templating, business, job, project, hiring, professional, stackoverflow, stackexchange, reputation, serverfault, superuser.com, curriculum, curriculum vitae, vitae, education4 Tags: LinkedIn, Linked, In, API, OAuth, profile, zzp, freelance, cv, experience, resume, template, Smarty, templating, business, job, project, hiring, professional, stackoverflow, stackexchange, reputation, serverfault, superuser.com, curriculum, curriculum vitae, vitae, education, stackoverflow 5 5 Requires at least: 3.3.1 6 6 Tested up to: 3.4.1 7 Stable tag: 0.8.1 27 Stable tag: 0.8.13 8 8 License: GPLv2 or later 9 9 License URI: http://www.gnu.org/licenses/gpl-2.0.html … … 12 12 13 13 == Description == 14 So, you've got your own WordPress site, and you're freelancing. You're maintaining a LinkedIn® profile because you have to, and you need to display your resume on your own site too. Wouldn't it be cool if you just maintain your resume at LinkedIn® and place a copy of that data on your own site and updating it would require just about pressing a button? 15 The resume page markup must, of course, match the layout of your site. Look no further, this plugin is all you need. And more. 14 So, you've got your own WordPress site, and you're freelancing. You're maintaining a LinkedIn® profile because you have to, and you need to display your resume on your own site too. Wouldn't it be cool if you just maintain your resume at LinkedIn® and place a copy of that data on your own site and updating it would require just about pressing a button? 15 The resume page markup must, of course, match the layout of your site. Look no further, this plugin is all you need. And more. 16 16 17 17 LiPS creates a local copy of your LinkedIn® Profile, using the LinkedIn® REST API to get the data. There's no page-parsing or screen-scraping, it's just your data, structured in a way it allows for automatic processing using a template. … … 20 20 21 21 The tool processes the profile data and creates a page, using the Smarty templating engine. Smarty is included in the distribution, as are two minimal templates. You can choose which page to use and which template to use. In fact, you can even create your own template. Learn how through the Donate link. 22 23 There is one more important feature. LiPS can also create posts for each position in your profile, allowing you to add more detail, such as (ex) coworkers adding their appreciation in working with you through the comments system build into WordPress™. Posts maintained by this tool are filtered from your "normal" blog stream, but you can link to them from any other page. You can use 22 23 There is one more important feature. LiPS can also create posts for each position in your profile, allowing you to add more detail, such as (ex) coworkers adding their appreciation in working with you through the comments system build into WordPress™. Posts maintained by this tool are filtered from your "normal" blog stream, but you can link to them from any other page. You can use 24 24 a different template for the post content too. 25 25 … … 44 44 45 45 = Why do I need to authorize the plugin every time I want to fetch my profile? = 46 I have not found a way to request read-only access to the profile. This means that an OAuth token is granted permission to modify your LinkedIn® data too. Saving the tokens would allow everybody with access to the blog database to perform actions on LinkedIn® on your behalf. 47 Both revoking access and just not saving the OAuth tokens is a great way to prevent that. 46 This makes sure nothing unexpected happens to your LinkedIn profile, even when the the plugin just requests read only access. 47 48 = Why does this plugin require full member access? == 49 LiPS needs access to experience, education, skills and recommendations. These sections are not available when the r_basicprofile permission is used. 48 50 49 51 == Screenshots == 50 52 51 1. The LinkedIn® Profile Sync page after initial installation. 53 1. The LinkedIn® Profile Sync page after initial installation. 52 54 2. The page changes when the OAuth token and secret are provided. 53 55 3. Authorize the plugin using the Authentication dialog box and a verifier. 54 56 55 57 == Changelog == 58 = 0.8.13 = 59 * Gets the full profile again using r_fullprofile. 56 60 = 0.8.12 = 57 61 * Displays tabs again. Reported by Neil Koch 58 * Separated the jQuery distributed css and the customizations done for this plugin. 62 * Separated the jQuery distributed css and the customizations done for this plugin. 59 63 = 0.8.11 = 60 64 * Fixed another couple of pass-by-reference fatal error. Reported by Mark Theloosen. … … 81 85 * Added support for Stack Exchange QA sites. 82 86 = 0.8.2 = 83 * Initial release. 0.8.0 was under active development 87 * Initial release. 0.8.0 was under active development 84 88 85 89 == Upgrade Notice == 86 = any = 90 = any = 87 91 This plugin uses metadata stored in the WordPress database. This metadata gets regenerated each time the plugin is activated. The template metadata has changed in 0.8.2, so you'll need to deactivate and activate the 88 plugin right after installation. This is a generic update issue .92 plugin right after installation. This is a generic update issue, not limited to any specific version. You'll need to do this when you moved your site to another subdirectory as well. 89 93 90 94 == Arbitrary section == … … 92 96 * it's probably a good idea to encrypt the OAuth authenticated tokens with 93 97 some form of a password, because anybody with access to the MySQL database 94 will have access to port of the authentication details. 98 will have access to port of the authentication details. 95 99 * verify whatever a template generates -> the page template must start with a <h1> or 96 100 <div>, same for a post.
Note: See TracChangeset
for help on using the changeset viewer.