Bug #2564
closed
Version 2.4.0 does not recognize user variables from the epgsearchuservars.conf file
Added by Ludi over 5 years ago.
Updated over 5 years ago.
Description
Hi,
In my epgsearchuservars.conf there is among other the following variable that I use in searchtimers for the path of the recording:
seEp
The variable has been set up to contain the season and the episode information and it works as it should on my yavdr on trusty running VDR 2.2 and a version of epgsearch from 2015. The timers created by the searchtimers using the variable have the season and episode numbers in their path.
On my VDR 2.4.0 running epgsearch 2.4.0, the timers created have the name seEp of the variable in their path instead of the content of the variable. It seems as if the variable is not recognized as a variable, but as a fixed string.
Could anybody please have a look?
Thanks in advance.
- Category changed from Bug to Support
- Assignee changed from winni to jfr
Not reproducable here. Could you please start the Plugin with -l "some_logfile" -v3 . You should see some lines in the logfile like "start evaluating expression" and your variable. Please add your complete uservars.conf and the correspondings parts of the logfile
Hi,
Thanks for the reply.
The problem went away in the meantime.
I switched to a version of the vdr-plugin-epgsearch with a different debianisation, that used /etc/... for all the configuration files of the epgsearch plugin. This epgsearch 2.4.0 package did not show the problem.
Thus, I went on reinstalling the previous debian package containing epgsearch 2.4.0, that puts some configuration files into /etc/... and others into /var/..., with symlinks in /etc/... Than, I started moving gradually the configuration files from version 2.2 into place. The problem did not occur anymore.
As I also did some editing to the files, I don't know exactly what solved the problem, sorry.
Sorry also for wasting your time.
- Status changed from New to Closed
Also available in: Atom
PDF