I had a calc sheet which downloaded data from internet site (stock prices) and inserted them in cells to make simple calculations. Data were automatically updated every 240 seconds. When I update LO from 5.2 to 5.3, I opened the sheet and updated data a few times. The second time I opened the same sheet, the data were no more downloaded (or the software just downloded the first lines), cells were empty and connections (results) showed error messages: !RIF. When I reinstalled LO 5.2 and opened the sheet again, I had the same error messages with empty cells. The rebuildt the sheet again in LO 5.2 and it worked properly again.
In the meanwhile I have tried to rebuild the sheet with LO 5.3 inserting the links to internet page. It downloaded the data correctly the first time, maybe a second time, but then it left the cells empty and showed the error messages.
Steps to Reproduce:
1. prepare a sheet with LO 5.2 or older version. go to the menu sheet -> link to external data.
2. insert the urls (one url per time:
for each link use at least 3 lines and choose html4 and update automatically every 240 seconds. save the sheet and close the application.
3. open the same sheet with LO 5.3 then answer 'yes' when it asks whether to update the data. wait about 10 - 15 minutes in order to update data automatically 2 or 3 times.
4. close application. re-open the sheet with LO 5.3. close application without saving.
5. re-open the sheet again with a previous version of LO; in my case the links were still not working.
cells remain empty; data are not downloaded and calculations give errors.
the sheet should update data correctly automatically and execute correctly calculations.
User Profile Reset: No
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug.
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
(Please note that the attachment will be public, remove any sensitive information before attaching it.
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Created attachment 131096 [details]
I prepared a calc sheet in two copies 'Portafoglio_Titoli (copia 1+2).ods' using LO 5.2.
I prepared a calc sheet in two copies 'Portafoglio_Titoli (copia 1+2).ods' using LO 5.2. 'copia 1' has been updated two times and saved always with LO 5.2. 'copia 2' has been prepared with LO 5.2, opened and updated, saved and closed, then reopened using LO 5.3. Final resulta are different then expected. Preparing the same sheet directly using LO 5.3 gave me the same outcome. I also add a screen of calc, the two cases, final results. Paolo
Created attachment 131097 [details]
Created attachment 131098 [details]
Created attachment 131099 [details]
2nd png img
I sent info. I don't know exactly whether LO 5.3 can't read html data or simply can't write data into cells. Paolo
Created attachment 131108 [details]
Test ODS files
When attempting to confirm the bug I did get unexpected/inconsistent behavior between 5251 & 5303 which seems like a bug but perhaps not as currently described. I did the following - examples attached.
1 Create LTED5251.ods with HTML_4 links defined at cells B1, B7 and B15.
Save as LTED5251.ods.
2 Open LTED5251.ods with 5303; Yes to update links.
All appears OK.
Save as LTED5303-save-1.ods then close.
3 Open LTED5303-save-1.ods; Yes to update links.
Observe that all rows between the 2nd & 3rd link
ranges were removed upon update.
Save as LTED5303-save-2.ods.
4 Open LTED5303-save-2.ods; Yes to update links.
No additional changes noted.
Save as LTED5303-save-3.ods.
Additional open/close cyclces show that any rows added between last and 2nd to last link ranges are removed with version 5303 (this does not occur with version 5251)
is this issue still reproducible in the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/
(In reply to Xisco Faulí from comment #8)
> Hi Paolo,
> is this issue still reproducible in the latest version of LibreOffice from
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.
For more information about our NEEDINFO policy please read the
wiki located here:
If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
Dear Bug Submitter,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):
a) Provide details of your system including your operating
system and the latest version of LibreOffice that you have
confirmed the bug to be present
b) Provide easy to reproduce steps – the simpler the better
c) Provide any test case(s) which will help us confirm the problem
d) Provide screenshots of the problem if you think it might help
e) Read all comments and provide any requested information
Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:
a) respond via email
b) update the version field in the bug or any of the other details
on the top section of our bug tracker