Scribus taking old CSV Data - some caching problem?

[prononext]

On my Scribus Generator it is taking data from a CSV Version I had changed long ago. Somehow it get's old entrys which are not existent or another value now.

Can there be a cache cleared somehow or is the problem on my side?

[berteh]

Hello. No caching is made by ScribusGenerator, and as far as I know there is no internal cache automatically done by Python.

I've experienced similar issue in a single session from the GUI in Scribus, but simply closing the script GUI and calling it again soved it. And never experienced caching problem when using the command line version of the script.

So I guess the problem comes from somewhere else. Is your CSV data still opened in another program (excel or other) that would set a lock on it ? Also kindly check the full path twice (happened to me before :/), and try it once from command line if you didn't already... as there is then no influence from Scribus then.

What's your OS and general workflow ?

have a nice day,
Berteh.

[berteh]

or are you using the option to load settings from the project ? in this case you may want to correct the path and save them again.

[prononext]

Hi my OS is Windows 10 and I open the Scribus document with variables inside then go menu>script>scribus-generator and select the csv and document. Somehow it still mixes the data.
The CSV is created in libre office with comma seperation. I closed all documents and restarted the process again, but no luck.

[prononext]

Even on anohter OS like ubuntu, a copied sla and csv file with another scribus generator version this problem is still persistent. somehow the generator sticks to some old version of the csv, which I did not find.

[berteh]

scary. I'll have to look deeper into this bug 'cause I definitely did not add any caching, even less a long term memory !

[berteh]

I'm still unable to reproduce this bug, evenmore solve it :/ did you try with scribus 1.5.4 ?

[berteh]

could you please send the problematic sla and some sample data, if not confidential ?

[berteh]

and explaining me exactly your files folder structure as well, if it is any different than "csv and output in the directory of the sla template".

[prononext]

I managed to solve the problem. The bug was, that scribus wrote the CSV path into the sla file and even when choosing a new file in the Generator it took that path. I found it by going line by line through the SLA file and removing the links to the old CSV. Strange behavior. ..

[berteh]

Maybe not so strange... I added a "save & load" functionnality to SG some time ago, that stores the current Scribus Generator settings in the source SLA file, for future use... and loads

[berteh]

(contd.)... and loads them if you click on the ↺ icon of the SG GUI or provide the -l, --load option from command line.

But these loaded settings should not be loaded by default, nor overwrite the ones explicitedly provided, unless you do one of the above... if not so that may be a bug.