KF5 - Updating prices doesn't work

[aga]

On 28/11/16 06:02, Cristian Oneț wrote:
> This feature (updating prices) was not working until relatively
> recently when I ported some disabled code [1]. So there might be some
> problems in that area. Could you share with use the settings of the
> quote that hags? Or could you debug to see where does the update
> process stop?
> 
> Regards,
> Cristian
> 
> [1] https://commits.kde.org/kmymoney/9ddcca03497a6fb7635ba02d41f0793c7329f876

> _________________________________________________________________

> My last email in response.

>Yes, this no longer occurs, so your commit looks to have fixed it.  Thanks.

>However, there are still some issues, but not affecting all stocks.

>I don't use finance-quote, but instead use the other method, using
>particular quote sources.  These sometimes stop working, when the
>web-site changes its format.  However, I'm having some success with
>quotes from Financial Times UK Funds.  Strangely, and outside of my
>understanding, some securities work, while others don't.

>Debugging is made more difficult because of changed behaviour on KF5.
>What used to happen was that the import from the source web-site was
>captured in a temp file, but this no longer occurs.  What happens
>instead is that it appears on the system console.  That wouldn't be too
>bad, but that doesn't occur at all for the files that I'm having trouble
>with.  My regex expressions appear to be OK as they work for other files
>from the source site.  So I'm a bit stumped, I'm afraid.

>Allan
> _________________________________________________________________

This is my follow up

I've managed to spend some time looking deeper into this and I think
I've resolved the problems.  There were different causes.  In some
cases, the investment wasn't found because it has been transferred by
the broker to a different fund, so no longer appeared in its prior form.
In some cases it wasn't found because my changes to the quotes plugin
parameters were not picked up correctly.  This was because of the move
of the resource file to a different directory.
I did find a few other issues along the way, one of which probably is
fairly long-standing, but a bit off the beaten track and not noticed
previously.  I'll document that when I've done some tidying up.

Allan