The original code from Alejandro caused a lot more problems than we realized after we ran it through our automated test suite for inclusion in the full release. Our automated tests cover a wide selection of scenarios of different extensions and functionality. In the very limited case of JReviews only, the code worked. Once we were testing for Autoposting, different content plugins and various other cases, we found some fatal errors that were caused due to the parsing of the ID.
We fixed those issues in a way that seemed to work with some of the JReviews issues we knew about. However, it's possible we missed some cases. As noted multiple times, it's a very tricky issue because JReviews uses the Joomla content system/tables, but many, many other extensions rely on the content tables and routing to be a very specific way. JReviews seems to change how it interacts with these, especially when it comes to routing. Also, other pages like "Tags" and "All Reviews" need to be supported, which were not considered in the original code.
We're trying to come up with a balance that works, but the original proposed solution didn't do that.
Now, if we can start again, please let us know specifically what issue you're having? Is it the same issue you were having before, exactly? Which Open Graph plugins are required to fix the problem? Are both content and jreviews, or does disabling just one of those work?
My guess is that there are some other cases on your site (you may not have even been using) which are fixed from 7.0.x as well. The more ways you can test, the more data we'll have.
Thanks,
Alex