-
Notifications
You must be signed in to change notification settings - Fork 226
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
"add timer" not working #1558
Comments
probably a similar issue here -> #1541 |
Is this only in Classic interface? |
The getallservices json is too big for local storage. The program attribute can be removed because it's not needed here. Or we find a way to change the quota. |
Ok, maybe we should just forget this. It is too much data. For me ./api/getallservices?renameserviceforxmbc=1&nolastscanned=1 outputs 25MB. |
Just curious @Huevos - how many channels do you have?? 😮 I wonder if you'd mind sending a backup of your lamedb and bouquets that I could use for testing the modern interface? |
In mine 126322 positions including spacers. Most is from IPTV bouquets, not lamedb. I'm not sure what the user who reported it has. I've asked. |
The spacers should be removed .. I will do that. |
IPTV can be also removed but only VOD, because you may wanna create a timer for IPTV Live channel. |
Please check this: by the way .. spacer should be not in the result. |
./api/getallservices?renameserviceforxmbc=1&exclude=lastscanned,vod,program For me it takes 15 seconds for the server to respond and another 30 seconds to output the data. And then it still doesn't display. So, too much data to process on the fly. |
Works again in OpenPli 8.3 on my VU+Ultimate4k... Happy with it! |
An easy workaround is increasing the quota. On Firefox, go to |
Build at ad155b2
From Main panel click "timers", then click "add timer".
On clicking "add timer" a request is sent to "./api/getallservices?renameserviceforxmbc=1&nolastscanned=1". The request works (as shown in the attached screenshot) but the data is not processed and the screen is not updated.
Reported by an OpenViX user on the forum and verified by me in Firefox and Chrome.
The text was updated successfully, but these errors were encountered: