WordLift – Activating the Plugin
WordLift is a lightweight plugin that brings state-of-the-art semantic technologies to the hands of any bloggers and publishers.
WordLift, without requiring any technical skills, helps you produce richer content and organize it around your audience.
WordLift is available to all for a monthly fee. Find out more and get your activation key directly on our website.
WordLift helps you organize posts and pages adding facts, links and media to build beautifully structured websites, for both humans and search engines.
WordLift lets you create, own and publish your own knowledge graph.
WordLift publishes your content as Linked Open Data following Tim Berners-Lee‘s Linked Data Principles.
WordLift is a plug-in for online content creators to:
- Support your writing process with trustworthy and contextual facts
- Enrich content with images, links and interactive visualizations
- Keep readers engaged with relevant content recommendations
- Produce content compatible with schema.org markup, allowing search engines to best index and display your website.
- Engage readers with relevant content recommendations
- Create your own personal Wikipedia
- Publish metadata to share, sell and distribute content
WordLift brings to your publishing workflow
- The technology to self-organize content using publicly or privately available knowledge graphs
- An easy way to build datasets and full data ownership
- Support for creating web content using contextually relevant information
- Valued and free to use photos and illustrations from the Commons community ranging from maps to astronomical imagery to photographs, artworks and more
- New means to drive business growth with meaningful content discovery paths
- Content tagging for better SEO
WordLift currently supports 32 languages: Chinese, Danish, German, English, French, Italian, Dutch, Russian, Spanish, Portuguese, Swedish, Turkish, Albanian, Belarusian, Bulgarian, Catalan, Croatian, Czech, Estonian, Finnish, Hungarian, Icelandic, Indonesian, Latvian, Lithuanian, Norwegian, Polish, Romanian, Serbian, Slovak, Slovenian, Ukrainian.
The Plug-in is built on open source software.
WordLift is happily developed by WordLift, an innovative Italian startup founded in 2016 and based in downtown Rome.
Our goal is to help blogger, journalists and content creators connect and share experiences with their readers as well as structuring knowledge in machine-readable form.
For more information, contact us at email@example.com.
Why we are doing this
Our mission is an utopian one: organize the world general knowledge by providing tools that everyone can use.
In open source we trust
WordLift is built on open source software.
WordLift uses open source tools for natural language and semantic processing.
In data ownership we trust
We believe content creators should own, retain and exploit the value of the metadata they create.
- Extract the files in the wordlift subfolder
- Activate the plug-in using a WordLift key. You receive this key from us after purchasing the monthly service from our website. Once you have received the key go to the WordPress administration menu, click on Plugins / Installed Plugins. Then click on Settings on the WordLift plugin and follow the guided setup process.
WordLift – Activating the Plugin
To activate the plugin you will need a WordLift key.
WordLift is now available to all for a monthly fee.
Find out more and get your activation key directly on our website.
- Who is WordLift for?
WordLift is for all bloggers, journalists, and content marketers publishing and fighting for readers’ attention on the web.
WordLift democratizes the field, bringing to the hands of all web content creators the technology that web publisher giants such as Google, Facebook and the BBC are using to organize and monetize their content.
WordLift helps you create richer and more engaging content, optimizes it for all search engines and efficiently organizes your content creation process, allowing you to reach and speak directly to your tribe.
- Why shall I use WordLift?
Organizing web content around an internal vocabulary rather than traditional web pages helps both users and machines finding and accessing it, improving navigation, content re-use, content repurposing, and search engine rankings.
WordLift organizes content, reducing the complexity of content management and content marketing operations, letting bloggers and site owners focus on stories and communities.
WordLift enriches your content with contextual information, links, and media, from custom vocabularies and/or the wealth of open data available on the web, bringing your user experience to a new level of engagement.
WordLift connects content with cross-media discovery and recommendations widgets, increasing content quality, exposure, trustworthiness and readership engagement.
WordLift optimizes content, complementing the offer of plug-ins such as SEO Ultimate or Yoast, automatically adding schema.org markups to your text, allowing all search engines to properly index your pages and deliver more traffic to your site.
- How does it work?
The first step provides a full text analysis and suggests concepts and relationships found in open vocabularies (such as DBpedia, Wikidata, GeoNames, etc) to help writers classify and enrich their content and structure it for search engines like Google, according to schema.org vocabulary.
Writers can then create new entities, to complement the ones suggested automatically, and to be published as part of a proprietary vocabulary, acting both as a reference and a search magnet for their readers, according to the editorial plans.
WordLift also assists writers suggesting links, media and providing a set of powerful visualization widgets to connect and recommend alternative content, to boost readers’ engagement.
Finally WordLift provides means to record all these relationships in a graph database allowing search queries like “find all contents related to concept_y and relevant for target_z”.
- What are the languages supported by WordLift?
WordLift currently supports the following languages: English, 中文 (Chinese), Español (Spanish), Русский (Russian), Português (Portuguese), Français (French), Deutsch (German), Italiano (Italian), Nederlands (Dutch), Svenska (Swedish) and Dansk (Danish).
- Is there a free trial?
No. We do not offer a free trial but your monthly subscription comes with a 14-day 100% money back guarantee. If after two weeks you are not happy with WordLift, contact us and we will refund you right away, no questions asked.
We do offer free additional months though, with the purchase of our 6-month or 12-month packages. Check it out
- Who owns the structured metadata created with WordLift?
You do! We believe content creators should retain the commercial value of their content and all the data they create and exploit it through new business models based on content syndication, data-as-a-service and a stronger relationship with their audience.
You can open your datasets to the public, attaching to it a free or a commercial licence. Otherwise, use your data to feed chat bots on Facebook Messenger or Telegram, providing live feed updates on your activity and/or automatic customer service in real time.
- What happens if I stop using WordLift?
If you stop paying for your subscription, but keep the plugin on your site, all the entities, metadata and pages you created with wordlift will still be available on your site – you won’t be able to update it any longer, but they will still work just fine as they were at the moment you removed the key. The data you’ve created belongs to you and you can always request to us a data dump that is available in various machine-readable formats.
if you deactivate the plugin instead, the vocabulary (metadata, entity and pages) will disappear from your dashboard, but everything you created is stored in your website Database in WordPress, and you will be able to download it, transfer it or re-activate it again anytime from the plugin menu.
Turning off WordLift on our side, it would be like turning off all the keys and un-publish all the linked data you’ve created, not the plug-in itself, so it will be like #1 – you could get the data back from us and re-publish it as linked data on your own infrastructure.
WordLift’s technology is entirely open source: it takes development skills, infrastructure and some wisdom to nicely bring all the pieces together without our support.
Your vocabulary (article metadata and entities) are published as linked data and you can always request a data dump in any of the following formats: RDF/XML, Turtle, N3, JSON-LD.
Find more FAQ in our Wiki.
I’ve stumbled upon Wordlift when I was looking for AI for WordPress. After some discussion with a team at https://freeyork.org/, we have to decide to start using Wordlift, and we didn’t regret it ever since.
It was a bit confusing in the beginning but after some time using it, we saw a beauty of AI and power of Wordlift. Soon standard blogging will extinct and this where Wordlift comes to the rescue.
The team behind is doing an absolutely fantastic job. And I haven’t seen anyone as fast and amazingly helpful as guys at Wordlift. Grazie ragazzi!
It will take some time for you to appreciate the potential of Wordlift thoroughly but after a few days of use, you can undoubtedly see the tons of benefits and endless possibilities.
Great plugin for creating semantic data for your website and blog. As a Google manager put it recently: mobile first is yesterday, today is AI which means also enriching your content with semantic data to make it not only machine readable (that is old fashioned SEO) but machine understandable.
Using this plugin needs some basic knowledge about semantic web. That is why some might be not impressed from the first moment – you need to work with it and grow and learn over time. Though I must say, this is the first semantic web plugin for WordPress which really works. Most of the others are just enhancing content with some schema.org markups. But just adding some unrelated structure markups does not mean you are building a semantic network. This plug-in is different, it empowers you to make real connections between your content entities.
As example: just adding some structured markup data would mean adding to the name of a person the meta information that it is a person (type) and that the person is represented by an specific image and maybe that it has a birthplace. By using WordLift you start building relations, telling this person is working for a company which is located in a specific city and offering these products. In future this will be a big game changer as AI (artificial intelligence) needs exactly that data. So a bot might be able to answer in future the question, for which company this person is working, where it was born and which products it sells. Just as a very generic example.
WordLift is a great plugin for content enhancement! It helps you to enable the semantic data that enables the rich data feature suggested by Google! We are working with WordLift team for our site http://geospatialworld.net/ and are seeing a great progress in our semantic database.
We have a great support from the team that is always accessible via email, Skype support etc. and are going to impact the world of Semantic web like no other!
Uso WL da qualche mese e direi che rende il blogging ancora più efficace e divertente. In altri termini il plugin permette di applicare gli attuali strumenti del web semantico trasformando il proprio sito in una macchina da guerra. Il blog diventa più intelligente e dinamico, la visibilità sul web migliora sensibilmente così come l’esperienza di navigazione, e questo a seguito della classificazione degli articoli con la costruzione di connessioni e reti di relazioni tra entità<->articoli e entità<->entità, integrando e superando i vantaggi dei collegamenti ipertestuali. La comunicazione con gli sviluppatori è efficace e puntuale.
This plugin allows you to markup existing and new content with definitions to become the semantic hub of your industry.#
Great for SEO, and really easy to use in WordPress.
The team behind Wordlift are forward thinking and ahead of their competition.
I’ve been using Wordlift on and off from many months. I’ve encountered very few knowledge tools like this plugin: it informs your writing process, it makes you smart, and as a by product, improves the quality of your site, inter-links your content and provides semantic seo advantages. I would suggest this as the first plugin to download for any new site: build it knowledgeable, with Wordlift.
Contributors & Developers
“WordLift – Rethink Your Content Marketing” is open source software. The following people have contributed to this plugin.Contributors
- Fix: #497: Aggressive caching may serve old files.
- Fix: #496: WL highlight classes conflict with themes.
- Fix: #495: Additional left padding on entity tiles.
- Fix: #494: Cached Html Templates.
- Enhancement: #489: Revise title and description for the timeline widget.
- Enhancement: #482: Global timeline doesn’t include events bound to pages.
- Enhancement: #442: Enable WordPress Category to Organise WordLift Entities.
- Enhancement: #426: Related articles needs to be limited and/or paginated.
- Enhancement: #335: Allow more actions on entity tiles within the disambiguation widget.
- Enhancement: #427: Add Publisher field to WordLift Setting page.
- Enhancement: #398: SEO improvement: providing control over title and description of WordLift Archive pages.
- Enhancement: #355: Creating a Tag-Like Widget for articles.
- Fix: #383: Chord – text overlapping issue.
- Fix: #469: Chord Rendering Problem on Firefox.
- Fix: #464: Extend Wordlift_Log_Service’s log to support arrays.
- Enhancement: #371: Extending the list of properties for schema-org:Article.
- Enhancement: #358: Application Key Not Set – Messaging improvement is needed.
- Enhancement: #350: Entity Annotation Loop.
- Enhancement: #345: Entity suggested when analyzing the entity content itself.
- Enhancement: #305: Entity Types’ widget should be flat.
- Enhancement: #291: The calendar for startDate and endDate of an event cannot be used for historical events.
- Enhancement: #254: Timeline visualization problem.
- Fix: #448: JSON-LD not loaded with WP Fastest Cache plugin.
- Fix: #447: Enqueue of styles and JS should be more selective and limited to content editing screens.
- Fix: #446: Return value of wl_schema_get_value not always check to not be null.
- Fix: #444: Typo on the dashboard.
- Fix: #438: Autocomplete fails in metaboxes.
- Fix: #437: Some found entities lack the related text annotation.
- Fix: #278: When creating a new entity the duplicate warning appears for entity that have been trashed.
- Fix: #462: Find duplicated entities.
- Fix: #461: Entities highlighted in front-end.
- Fix: #282: Wrong entity URL.
- Fix: #439: Entity preview is redirected to a Post.
- Fix: #431: WP 4.2 yields “Call to undefined function is_subdomain_install” when saving a post.
- Fix: #430: Fix analysis selectors in WP 4.5 and lower.
- Enhancement: #429: German missing in supported languages’ list.
- Enhancement: #425: Move the traslator server-side.
- Enhancement: #417: Integrate e2e tests in WordLift.
- Enhancement: #408: Remove the Caching submodule.
- Enhancement: #397: Review WordLift’s setup process.
- Enhancement: #395: Author missing from entities edit pages.
- Enhancement: #376: Enable revisions for entities.
- Enhancement: #349: Remove all non supported languages from the Settings.
- Fix: #391: Html code messed u when using WordLift on previous posts and with Twitter embeds.
- Fix: #353: Responsive not working on the Vocabulary page on WordPress.
- Fix: #341: Special characters do not display correctly in LodLive.
- Fix: #306: Entities from the internal vocabulary are not properly detected from the analysis.
- Fix: #415: WordLift not working after updating to WP 4.7.
- Fix: #410: Triples not showing on the WordLift dashboard.
- Fix: #406: JSON-LD response corrupt.
- Enhancement: #372: The layout of the Navigator messes up with long entity titles.
- Enhancement: #365: Stop words are analyzed too.
- Enhancement: #310: Favour json-ld in place of microdata.
- Fix: #386: Linked data not saved.
- Fix: #393: JSON-LD problem with OSDS.
- Fix: #382: Analysis errors on coffee-brewing-methods.com.
- Fix: #351: Text annotations missing for found entities.
- Fix: #363: Synonyms associated to other entities.
- Fix: #368: Adding unneeded p tag for entity properties.
- Enhancement: #370: Upgrade to TimelineJS 3.x.
- Enhancement: #369: Remove the unused In-Depth file.
- Enhancement: #354: Improve the navigator Widget by adding links to the images.
- Enhancement: #352: Improve design of the TimeLine Widget.
- Enhancement: #125: Personalise the entity path.
- Enhancement: #230: Download your data.
- Enhancement: #338: Custom domains and dataset names
- Enhancement: #339: Improving the Import/Export of the user Vocabulary.
- Enhancement: #342: Data migration.
- Enhancement: #343: Disable Wikipedia images.
- Enhancement: #346: Add Telephone and URL properties.
- Fix: #340: Incompatible date widget.
- Fix: #347: Annotations mysteriously disappeared.
- Fix: #346: Double link in front-end entities.
- Fix: #265: Entity type:Person are being created before actually saving an organization’s entity.
- Fix: #336: Navigator widget doesn’t show at the end of the article unless it is also in the middle.
- Fix: #262: Posting a site URL on Google+ uses an entity title instead of the post title.
- Fix: #329: Allow to disambiguate more than one occurrences for the same entity in bottom / up disambiguation mode.
- Fix: #333: Germanic umlaut causing troubles when saving sameAs links.
- Fix: #334: New Entities/Thing created without the sameAs attribute are duplicated as Entities/Person.
- Fix: #285: Avoid unexpected alerts after content disambiguation.
- Fix: #319: Fix chord widget content filtering limit.
- Fix: #315: Activation on large web sites fails.
- Enhancement: #312: Reduce chord entities threshold to improve widget usability.
- Fix: #300: Ensure only published entities are returned as facets by faceted search widget.
- Fix: #299: Featured images are now properly updated on RL.
- Enhancement: #295: New UI refinements.
- Enhancement: #297: Detect classification scope from current entity type.
- Enhancement: #284: Disambiguation widget UI refactoring.
- Enhancement: #289: Introduced html static templates for angularjs layer components.
- Enhancement: #288: Removed selected entities tags from disambiguation widget.
- Enhancement: #283: Dbpedia topics are now mapped also on a custom taxonomy.
- Enhancement: #229: Add article classification.
- Enhancement: #294: Fix disambiguation failure use case.
- Enhancement: #280: Fix disambiguation failure use case.
- Enhancement: #279: Disambiguation fixed for entities with escaped chars contained in the uri.
- Enhancement: #276: Fix facets layout with entities long titles.
- Enhancement: #275: Exclude posts without featured image from navigator results.
- Enhancement: #274: Simplify facets layout grid.
- Enhancement: #273: Remove entity type icon and counter from facets within faceted search widget to simplify the layout.
- Enhancement: #270: Show wl-carousel controls on mouseover only.
- Enhancement: #269: Fix NaN in WL dashboard.
- Enhancement: #268: Flaoting configurable layout is now available both for navigator and faceted search.
- Enhancement: #267: Force override for entities with same schema type and label within disambiguation workflow.
- Enhancement: #264: Improve data selection strategy for navigation widget.
- Enhancement: #253: Introduce navigator and faceted search configuration.
- Enhancement: #258: Entity titles are now also published in the graph as dc:title.
- Enhancement: #147: Navigator widget works also on entity pages.
- Enhancement: #232: Navigator widget refactoring.
- Enhancement: #224: Enable entity partial match in autocomplete.
- Enhancement: #215: Allow to create multiple entities with same label and different entity types safely (without any overlapping).
- Enhancement: #130: Remove angularjs bower dependency. CDN is used instead.
- Enhancement: #263: Sorting and smart auto-limit added for entities in faceted search widget.
- Enhancement: #255: Disable entity url editing.
- Fix: #251: avoid entity duplication for entities with an updated label used in disambiguation.
- Fix: #244: Tinymce does not remain idle anymore switching between Visual and Text mode.
- Enhancement: #233: Add WordLift dashboard widget.
- Enhancement: #231: Faceted search widget is now available also for standard posts
- Enhancement: #223: Remove unavailable entity images from images suggestions.
- Enhancement: #214: Faceted search 4W revamp.
- Enhancement: #180: Enable minified js files for faceted search shortcode.
- Enhancement: #115: Filter out the current entity from the analysis results to avoid to link a given entity with itself.
- Fix: #260: Autosave disabled for entity posts to avoid unexpected entities duplication
- Fix: #259: Fix php notice on media library
- Fix: #256: Fix compatibility issue with truemag theme
- Fix: #252: Disable scrollInput on entities metaboxes datetimepickers
- Fix: #248: Include also LocalBusiness entities as suggestion for affiliation property for entities of type Person
- Fix: #246: Include also LocalBusiness entities as suggestion for location property for entities of type Event
- Fix: #243: Post status for published entities is properly preserved when used to disambiguate a post draft.
- Fix: #239: Fix disambiguation widget look & feel on WP 4.4.+
- Fix: #237: Fix disambiguation for internal entities sameAs of other entities
- Fix: #234: Fix text annotation removing for annotation containing blank html markup
- Fix: #228:
Flush properly rewrite rules on plugin activation to prevent 404 on entity pages
- Fix: #227:
Change wording for invalid or missing text selection on entity creation workflow
- Fix: #225: Return safely when get_current_screen() is not defined (yet).
- Enhancement: #151: Download and save Place coordinates from RL.
- Enhancement: #161: Geomap shows current entity if it is a Place (or child of Place).
- Enhancement: #207: Add rating score and consistency check for entities.
- Enhancement: #209: Add thumbnail preview within the entity listing.
- Enhancement: #208: Add classification scopes filter – aka 4W filter – within entity listing.
- Enhancement: #199 & #101: Improve new entity creation workflow usability within the content post editing.
- Enhancement: #171: Add related posts counter within the entity listing.
- Enhancement: #121: Improve UI consinstency
- Enhancement: #140: Add new properties for Organization
- Fix: #221: Fix de-synch between WordPress and RedLink when disambiguation is performed trough entity alternative title
- Fix: #210: Restore editable annotations to allow annotations formatting.
- Fix: #194: Add zero-width no-break space after each annotation to provide a caret container.
- Fix: #203: alternative titles are spreading to related entities, fixed.
- Fix: #200: Fix new entity form visibility with undefined current annotation.
- Fix: #194: Make text annotations within tinymce editor not editable.
- Enhancement: #196: renovate the Vocabulary icon with WordLift logo.
- Enhancement: #195: re-enable title duplicates notices.
- Enhancement: #185: cleaning up, remove the entity_view submodule.
- Enhancement: #184: for the joy of the 100,000+ active installs, we’re now compatible with the ShareThis plugin.
- Enhancement: #181: finally, you can add more titles to entities.
- Enhancement: #178: some renovation, add WordLift in the naming of the Metabox.
- Enhancement: #177: enjoy better admin notices.
- Enhancement: #176: cleaning up, remove the option “color coding on front-end”.
- Enhancement: #175: cleaning up, remove SPARQL queries menu item.
- Enhancement: #174: cleaning up, remove performance analysis menu item.
- Enhancement: #173: cleaning up, remove WordLift upper-right corner icon.
- Enhancement: #170: disable entity editing in disambiguation widget for internal entities.
- Enhancement: #159: enable both date and datetime fields for the metabox.
- Enhancement: #149: add email and organization properties to Person.
- Enhancement: #143: it is now possible to specify many additional properties for addresses.
- Fix: #189: fix entity recognition when bullet points are used.
- Fix: #122: fire related posts loading on disambiguation widget loading.
- Fix: #192: fix coordinates metabox field’s HTML.
- Fix: #150: the property schema-org:author on blog post lod view goes on error.
- Fix: #124: entity featured image updating is not properly triggered on the triple store (fix tests and apply only to published posts).
- Fix: #124: entity featured image updating is not properly triggered on the triple store.
- Fix: #183: new text for the admin notice regarding a missing WL key.
- Fix: #179: faceted search not running
- Fix: #104: cannot load more than one navigator on the same page.
- Fix: #112: chord tooltip has white background and black font to avoid themes conflicting with the widget.
- Enhancement: #145: control new entities creation from metaboxes.
- Enhancement: #134: scripts and styles source repository merged with PHP repository.
- Enhancement: #57: on the Edit Entity page the referencing posts has been restored.
- Fix: #144: changing type on WordLift doesn’t reset the property list on Redlink is now fixed.
- Fix: #141: properties when published to Redlink have no links (and no meaning) is now fixed.
- Fix: #139: single founder while expecting multiple founders is now fixed.
- Fix: #138: Uncaught TypeError: Cannot read property ‘id’ of undefined is now fixed.
- Fix: #169: entities that are not events may be displayed in the timeline.
- Fix: #168: WordPress shortcodes are displayed in timelines.
- Fix: #167: schema.org markup is wrong for implicit contents.
- Fix: #166: latitude and longitude are set to zero when not specified.
- Fix: #165: entity type is lost in quickedit mode.
- Fix: #164: timeline widget is showing unrelated events.
- Fix: #163: incorrect markup for events’ locations.
- Fix: #162: only dates are stored for startDate/endDate properties in linked data.
- Fix: #152: Entity description update from disambiguation widget is now disabled in order to prevent existing entity pages content overriding.
- Fix: #135: Sanitize filename in order to properly save entity images as entity post attachments.
- Fix: #156: Yoast compatibility issue which caused meta values to be copied to new entities created within a post is now solved.
- Fix: #148: SEO Ultimate compatibility issue which caused meta values to be copied to new entities created within a post is now solved.
- Fix: #128: now hashes in the text do not break anymore the annotations embedding after analysis execution.
- Fix: #95: WordPress image edit controls disappears after installing WordLift is now fixed.
- Enhancement: #85: now structured data are added in the entity pages for the current entity itself
- Fix: #128: now hashes in the text do not break anymore the annotations embedding after analysis execution
- Fix: #96: garbage response from api is no more returned
- Enhancement: ‘View Linked Data’ button to visualize RDF triples with LodView
- Fix #119. Now public entities status is properly preserved when linked to draft posts.
- Fix: install script in order to use branch-specific WP unit tests libs
- Fix: issue 13: authorship tagging is now shown only on single pages and posts (thanks to Kevin Polley)
- Enhancement: Twitter authentication is now back.
- Fix: change regular expression to add image itemprops for In-Depth articles to avoid conflicts with linked images and plugins such Nav Menu Images (thanks to Lee Hodson).
- Fix: removed useless references to jQuery UI libraries and conflicting CSS (thanks to Lee Hodson).
- Fix: PHP warning in RecordSetService (thanks to Kevin Polley),
- Fix: image alt attributes were incorrectly highlighted with entities (thanks to Lee Hodson).
- Fix: post thumbnail html output even if there’s no thumbnail.
- Fix: adding schema.org title using the_title filter could cause issues with theme that use this function for the img tag alt attribute value.
- Enhancement: add support for DW Focus theme.
- Fix: overlap with Facebook admin menu.
- Fix: enable authorship information only for regular posts (post type ‘post’).
- Fix: the entity page might appear in the primary menu with some themes (e.g. Twenty Thirteen).
- Fix: the entity page called without an entity parameter would return a warning.
- Fix: a warning might appear in the entity page.
- Fix: temporary disabled twitter authentication due to API changes.
- Improvement: add better support for is_single call.
- Other: fix repository versioning.
- Fix: html tagging in the title did cause issues when the post title is being used as an html attribute.
- Other: add new keywords.
- Other: add compatibility up to WordPress 3.6.
- Fix: fix a bug that would cause the interaction count to show up in the page title.
- Fix: ensure adding schema.org mark-up happens only in single post views.
- Fix: fix a bug that would cause rewrite rules to be incomplete (WordPress Framework).
- Feature: add option to disable In-Depth features.
- Feature: add new In-Depth features.
- “Registration failed: undefined (undefined)”: Fixed a configuration setting that didn’t allow some blogs to register to WordLift Services. (Many thanks to http://www.pruk2digital.com/ for helping us out finding this error).
- Added initial compatibility with WordPress 3.6 beta 1,
- Fix an issue that displayed entities alway for the most recent post.
- Fixed a ‘notice’ in the WordLift Bar,
- Changed the WordLift Bar to show entities from the most recent post in the
- Added HTML encoding of entity data on the WordLift Bar.
- WordLift Bar stays hidden for screen width <= 320px.
- WordLift Bar hides/shows automatically when the page is scrolled down.
- readme updated with links to WordLift Bar samples.
- Now featuring the experimental WordLift Bar.
- Cloud Services address changed to use standard ports to ease WordPress installations behind firewalls or proxies.
- Major release with fixes on the user registration.
- Fixed an issue that would prevent the plug-in from working. This upgrade is strongly recommended.
- Fixed an issue that would block the plug-in when discovering corrupted type formats.
(NOTE: this version does not work, please upgrade to 1.6)
- Fixed some compatibility issues with Internet Explorer.
- Added support for WordPress 3.0.x
- The entity elements are now hidden by default.
- Removed the requirement for a logs folder
- First public release