Reply to thread

Message

<blockquote data-quote="Evzen" data-source="post: 582917" data-attributes="member: 102172">Hi, I'm new here so please forgive me if I am just missing something...Just installed MP 1.1 RC1 (fresh install) and started playing a bit more with WebEPG.Using the (fixed) Czech grabber for tv.sms.cz (<a href="https://forum.team-mediaportal.com/general-development-no-feature-request-here-48/webepg-cookies-53697/" target="_blank">https://forum.team-mediaportal.com/general-development-no-feature-request-here-48/webepg-cookies-53697/</a>), which contains the very same search code as the example in the&nbsp; <a href="http://wiki.team-mediaportal.com/MediaPortal_WebEPG_Grabber" target="_blank">MediaPortal_WebEPG_Grabber</a>:[CODE]&lt;Search match=&quot;\([0-9]{1,3}[,][0-9]{0,3}\)&quot; field=&quot;#EPISODE&quot; remove=&quot;true&quot; /&gt;&lt;Search match=&quot;\([0-9]{1,3}\)&quot; field=&quot;#EPISODE&quot; remove=&quot;true&quot; /&gt;&lt;Search match=&quot;\([0-9]{1,3}[/][0-9]{0,3}\)&quot; field=&quot;#EPISODE&quot; remove=&quot;true&quot; /&gt;[/CODE]Apparently, using these the WebEPG is supposed to extract the entire string, i.e. including the brackets/comma/slash, right?But it simply doesn't... <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused&nbsp; &nbsp; :confused:" loading="lazy" data-shortname=":confused:" />What ends up written in the database (or tvguide.xml file) is only the first number, i.e. if the episode string is &quot;14/26&quot; or &quot;(123,124)&quot;, only the &quot;14&quot; or &quot;123&quot; gets extracted... <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused&nbsp; &nbsp; :confused:" loading="lazy" data-shortname=":confused:" />Done some tests and after changing the regexp to e.g. {1,1}, episode strings like the examples above are left intact... which is correct and seems like the problem is in the further processing of the extracted string before exporting to DB or XML.Now I don't know if I am doing something wrong (but what?! there is nothing I could screw up...), or if it is a pretty nasty bug in the WebEPG...But how comes nobody else would be bothered by such obvious bug? I'm totally confused... <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused&nbsp; &nbsp; :confused:" loading="lazy" data-shortname=":confused:" /></blockquote>

[QUOTE="Evzen, post: 582917, member: 102172"] Hi, I'm new here so please forgive me if I am just missing something... Just installed MP 1.1 RC1 (fresh install) and started playing a bit more with WebEPG. Using the (fixed) Czech grabber for tv.sms.cz ([url]https://forum.team-mediaportal.com/general-development-no-feature-request-here-48/webepg-cookies-53697/[/url]), which contains the very same search code as the example in the [URL="http://wiki.team-mediaportal.com/MediaPortal_WebEPG_Grabber"]MediaPortal_WebEPG_Grabber[/URL]: [CODE]<Search match="\([0-9]{1,3}[,][0-9]{0,3}\)" field="#EPISODE" remove="true" /> <Search match="\([0-9]{1,3}\)" field="#EPISODE" remove="true" /> <Search match="\([0-9]{1,3}[/][0-9]{0,3}\)" field="#EPISODE" remove="true" />[/CODE] Apparently, using these the WebEPG is supposed to extract the [B]entire string[/B], i.e. [B]including the brackets/comma/slash[/B], right? But it simply doesn't... :S What ends up written in the database (or tvguide.xml file) is [B]only the first number[/B], i.e. if the episode string is "14/26" or "(123,124)", only the "14" or "123" gets extracted... :S Done some tests and after changing the regexp to e.g. {1,1}, episode strings like the examples above are left intact... which is correct and seems like the problem is in the [B]further processing of the extracted string before exporting to DB or XML[/B]. Now I don't know if I am doing something wrong (but what?! there is nothing I could screw up...), or if it is a pretty nasty bug in the WebEPG... But how comes nobody else would be bothered by such obvious bug? I'm totally confused... :S [/QUOTE]

Verification