Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Accessing versions of an entity

See original GitHub issue

@Khaledgarbaya as you wish (

So, I had the following idea: Contentful does versioning of content. In the editor you can compare versions of an entry and I assume move between them. Say you put your blogs content on Contentful. Wouldn’t it be cool if in your blog frontend could also access multiple versions of your blog posts?

Your blog’s permalinks to posts could have a format like{version}, where the {version} route parameter is the version of the entry on Contentful. If someone has a permalink to an outdated version, this would allow you to put a notification at the top of the post pointing to the latest version.

This of course would require the CDA SDK to expose the versions somehow. How hard would this be to do? Is it possible at all?


Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:5 (2 by maintainers)

github_iconTop GitHub Comments

cschagencommented, Jan 16, 2017

It is a terrible idea from a SEO point of view ot have a structure. Cause imagine you get 1000 awesome links, and then somebody updates that URL and the links now point to no mans land.

felixjungcommented, Jan 17, 2017

Well the idea was to keep all versions in tact (i.e. would always work).

Say I have a blog post foo which is at version v1. The permalink to that version would be This post gets really hot on hackernews and I update the post to v2. would still work, but the page would show a notification at the top with a link to So instead of having one page with a bunch of Update MM/DD/YYYY headlines in between, you get something that’s more like a history of your blog post. You can time travel through the states of the post.

Of course you could also have always point to the most recent version and provide links to the outdated versions. Using some text diffing library you could highlight the changes, much like diffs on Github.

I don’t know much about SEO, and maybe the above scenario would dilute the value of each version of the post. I just thought the idea was interesting from a technical or UX experience.

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to handle versions of an Entity in Database Design
You could do this by allowing document ID to not be unique, and the primary key is a combination of document ID and...
Read more >
How does the entity version property work when using JPA ...
Introduction. In this article, I'm going to show you how the JPA @Version entity property works when using Hibernate.
Read more >
Solved: get version history of entities through api?
Solved: Is it possible to lookup the histories of entities or spesific records through the api? it would be amazing if i could...
Read more >
Determine version of Entity Framework I am using?
If you go to references, click on the Entity Framework, view properties It will tell you the version number.
Read more >
How entity versioning works - Product documentation
An entity's version number is retained when cloning or using Save As to save a copy of the entity. Multiple versions of an...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found