Myrating replaced rating in Collections sync'd to 4.6b beta and v5.0a but v5.0a doesn't recognise the command (unlike the two betas), so my collections are empty!
BUMP
Ok. I'm reverting back to RATING: until this is sorted.
NB. This works for me because every potential resource in my collections has a user rating e.g. type:bible rating:>0 will be a different collection to type:bible myrating:>0 unless every bible has a user rating (1 or greater).
You are correct: it is not possible to run 5.0a stable and 5.0b side-by-side with regard to resource collections. This should have been made much more explicit in the release notes; I apologise for the omission.
However, I still don't understand the purpose of rating as now implemented. Why was it so important to redefine it?
