[ET8x00] Crash when entering Trashcan in recordings

[twol]

That's always the problem with this kind of plugins.

I agree Rob, that it would be better if it wasn,t supplied in the format it is in (ipk), but nobody seems to want to implement it into the code ........... but it does do something that many people like and it slips into the code very easily, and so far has avoided any ViX update changes.
For me it's a no brainer, took me 5 minutes or so to update the ViX code and has run solidly since including all the V17 updates and changes.

 

[abu baniaz]

the mod would need updating

Better to merge if nobody has objection. So far it is the suspected speed issue in EPG. I have not noticed it.

 

[birdman]

So I am guessing that somewhere in this code (Added trash can sort options (by deleting time). ) there is a conflict with the Mod ??

Whereas I'd suspect that the version he has hasn't been updated to reflect that changes to UsageConfig.py in the image version he is using.

 

[abu baniaz]

Whereas I'd suspect that the version he has hasn't been updated to reflect that changes to UsageConfig.py in the image version he is using.

This is the problem. No point doing anything with the mod, because there will be changes to the same file in 017 owing to the sign post menu you are in work. (unless it is backwards compatible)

 

[twol]

Whereas I'd suspect that the version he has hasn't been updated to reflect that changes to UsageConfig.py in the image version he is using.

.... and of course you are so correct, I get so used to looking at my updated code, that I totally forget that the supplied updated ipk goes back to some time end May- start June? (Put it down to old age on my part, but still pretty stupid of me ).
Having said all that the mod is still not impacted by subsequent updates to the ViX Enimga 2 code upto and including this morning
So

 

[Ford1]

ok then guys, how do I go about altering the code to get this mod working again?

 

[Ford1]

when the problem appeared, I was running 4.10? I think, updated vis the online option on the box.

Iam, and have always used the openvix-bluehd skin.


Pressing "epg" on remote, then "green" for recordings, then I highlighted a empty folder called "pawpatrol" selected delete, the box crashed.
When pressing either "list" or entering through "epg, green" to get my PVR/MOVIE folder, highlight Trash, press enter, box crashes.
Enter "Menu" "setup" "system" "timeshift setings" box crashes
Enter "Epg" press "Green" for recordings, press "menu" Highlight "settings" press "ok" Box crashes.


Going to try and flash back to 3.2.036 and reinstall openvix_customepg mod v1.0 then add the blueHD.XML file to restore the font issue, (as this is how I had it set up last time) and see if that fixes the issue for the short term.

 

[abu baniaz]

In the image, there is a file that allows user configurations. It changes from time to time. The EPG mod uses an edited file to give the options it adds. If you perform an image update and the file is changed, you get issues. This file is going to change when 017 is going to be released, so it makes no point updating the "plugin".

The file changed in 013. So your post that there was a problem in 010 is hard to believe.

 

[twol]

Wait for 017 to go live, and then see if it is stable as there are a lot of changes .. Then lets see

 

[Ford1]

In the image, there is a file that allows user configurations. It changes from time to time. The EPG mod uses an edited file to give the options it adds. If you perform an image update and the file is changed, you get issues. This file is going to change when 017 is going to be released, so it makes no point updating the "plugin".

The file changed in 013. So your post that there was a problem in 010 is hard to believe.

As hard to belive as it is, the crash log clearly states what version of vix I was running?

 

[Ford1]

Wait for 017 to go live, and then see if it is stable as there are a lot of changes .. Then lets see

Do we have an ETA for 17?

 

[ccs]

Haven't you got a working image backup to use?
I always take an image backup before moving to a new release, just in case there's a problem.
I've only ever needed to use it once, and it takes just a few minutes to be up and running again.

 

[Ford1]

Well I had one..................
Nah I forgot to ftp the backup off the system before I did the last re-flash and re-initialisation of the hdd. its no problem, I have a 026 from ver3, and it only takes a few mins to set bsck up. Im more confused as to why the validity of my claim of being on a ver less than 013 is being questioned, when itas clear from the log in the first post?

However im assured that it is a somewhat known issue ande 017 MAY enable me to use the mod again.

I just wish someone could point me in the direction of learning to code/skin myself, I have asked before. :thumbsup:

 

[birdman]

The file changed in 013. So your post that there was a problem in 010 is hard to believe.

Except that although the log notes the version as 4.1.009, it was compiled on 27 June, which is when 4.1.015 was released (see #23).

 

[Rob van der Does]

Do we have an ETA for 17?

Sorry, but we never have. We are not on a payroll, and not under stress of commercial supervisors
We release a build when we tested changes and when we're happy with it. Sometimes that's twice a week, sometimes once a month.
So stay tuned

Anyway: a plugin that is not being maintained is not a good idea. So if you're in trouble now: just reflash, using restoring of settings & plugins (provided you don't allow this extra plugin to be installed), and you'll be good in a couple of minutes.

 

[Ford1]

Yeah, ive re-flashed back to ver 3.026 and all is good. and please, I was not being demanding in any way, I understand the way the OS is maintained and how the releases are handeled, it was just a lot of talk of .17 having the updates to avoid this problem, so figured it was out in the world being tested.

 

[abu baniaz]

Image 017 won't have a fix for the modification. The modification will have to be redone for 017 as usageconfig.py will change again because of the menu path stuff. No point doing it twice.

Every time usageconfige.py changes, the modification will have to be updated.

 

[ccs]

just reflash, using restoring of settings & plugins (provided you don't allow this extra plugin to be installed), and you'll be good in a couple of minutes.

Is it possible to be selective when restoring plugins using backup manager/wizard ? I've wondered about this before, but couldn't see a way of doing it.

 

[Rob van der Does]

Yes & no.
In general one either selects plugins to be restored or not to be restored. But as this plugin is not on the feeds, it can't be restored; unless it has been added as 'extra IPK' in the context menu of the backup manager. But even then it has to be available at the time of restoring.

 

[Ford1]

Image 017 won't have a fix for the modification. The modification will have to be redone for 017 as usageconfig.py will change again because of the menu path stuff. No point doing it twice.

Every time usageconfige.py changes, the modification will have to be updated.

Sorry I got the impression that this was either being implemented in the to native code, or the usageconfige.py would be modified to allow use of the mod.

Id like to understand this better, can ANYONE point me to someware I can get a foundation of how the coding of these systems works, and maybe ultimality I can learn how to alter the mod to work with any changes.