-
-
Notifications
You must be signed in to change notification settings - Fork 248
New issue
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
mncvision.id EPG only captures tv shows in first page #523
Comments
After playing around with this site, i have found way to fix this.
But i am stuck at making config to do this. Can anyone help me? |
Config will need to be changed to use a GET rather than a POST. If you specify the startno then a POST will ignore that and always go back to the first page of results.
It's something of an ugly hack but you could set |
This trick will work for for channels with two or more pages, but will not work for channels with single page (majority channels in this schedule has only single page). Single page channel must be captured from |
Well spotted. I'd checked the |
After considering this one further, i just stop work on this fix. I am a coding noobie either. |
Fixed via #577 |
Already an old news and noticed it for long time, but this issue happened randomly now after next scraping. |
@freearhey I think you should look after the page number down below. If you manage to grab the page number for each iteration, you're good to go (and it should fix the EPG for a while). P.S : if you actually remove the "startno/0" parameter, you still can see the EPG, and it gives a full day stream. |
Won't work if you set to channels that usually has 2 or more pages, for example: Miao Mi, France 24 P.S : If it has multiple pages, you can set "startno" to any number you want as long as its value doesn't exceed total shows in one channel and a day. |
Fixed in #1156 |
Hello, i have just noticed that mncvision.id EPG does not capture any shows in second page and onwards.
Basically, it only captures 50 first programs each day.
The text was updated successfully, but these errors were encountered: