We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Original issue 1955 created by Omertron on 2011-06-02T02:35:43.000Z:
I just tried to explode sets in only the Top 250 page by setting this
mjb.categories.explodeSet=Other_Top250
It did not work in version 2.4. Please allow more granular control of the index to explode in, if possible.
If you can do this, it would close issue 817 which I opened a while ago.
The text was updated successfully, but these errors were encountered:
Comment #1 originally posted by Omertron on 2011-06-20T08:20:36.000Z:
The index name is Top250
Sorry, something went wrong.
Comment #2 originally posted by Omertron on 2011-06-20T08:21:08.000Z:
Issue 817 has been merged into this issue.
Comment #3 originally posted by Omertron on 2011-06-20T08:21:36.000Z:
<empty>
Comment #4 originally posted by Omertron on 2011-06-21T20:54:00.000Z:
I now have
mjb.categories.explodeSet=Top250
in my moviejukebox.properties file but sets still show up in Top250. I'm using r2553. What revision did this fix get released with?
No branches or pull requests
Original issue 1955 created by Omertron on 2011-06-02T02:35:43.000Z:
I just tried to explode sets in only the Top 250 page by setting this
mjb.categories.explodeSet=Other_Top250
It did not work in version 2.4. Please allow more granular control of the index to explode in, if possible.
If you can do this, it would close issue 817 which I opened a while ago.
The text was updated successfully, but these errors were encountered: