Discussion:
[Libreoffice-bugs] [Bug 51554] Data loss risk referencing slides from external impress presentation (Menu Insert -> File, selecting link)
b***@bugs.documentfoundation.org
2015-04-01 14:41:42 UTC
Permalink
https://bugs.documentfoundation.org/show_bug.cgi?id=51554

--- Comment #9 from QA Administrators <qa-***@libreoffice.org> ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

*Test to see if the bug is still present on a currently supported version of
LibreOffice (4.4.1 or later)
https://www.libreoffice.org/download/

*If the bug is present, please leave a comment that includes the version of
LibreOffice and your operating system, and any changes you see in the bug
behavior

*If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a short comment that includes your version of
LibreOffice and Operating System

Please DO NOT

*Update the version field
*Reply via email (please reply directly on the bug tracker)
*Set the bug's Status field to RESOLVED - FIXED (this status has a
particular meaning that is not appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:

1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3)

http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to "inherited from OOo";
4b. If the bug was not present in 3.3 - add "regression" to keyword


Feel free to come ask questions or to say hello in our QA chat:
http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2015-04-01
--
You are receiving this mail because:
You are the assignee for the bug.
b***@bugs.documentfoundation.org
2016-04-16 07:28:00 UTC
Permalink
https://bugs.documentfoundation.org/show_bug.cgi?id=51554

--- Comment #10 from tommy27 <***@quipo.it> ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present on a currently supported version of
LibreOffice (5.0.5 or 5.1.2 https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of
LibreOffice and your operating system, and any changes you see in the bug
behavior

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a short comment that includes your version of
LibreOffice and Operating System

Please DO NOT

- Update the version field
- Reply via email (please reply directly on the bug tracker)
- Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:

1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3)

http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug

3. Leave a comment with your results.

4a. If the bug was present with 3.3 - set version to "inherited from OOo";
4b. If the bug was not present in 3.3 - add "regression" to keyword


Feel free to come ask questions or to say hello in our QA chat:
http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
--
You are receiving this mail because:
You are the assignee for the bug.
b***@bugs.documentfoundation.org
2017-05-22 13:25:30 UTC
Permalink
https://bugs.documentfoundation.org/show_bug.cgi?id=51554

--- Comment #11 from QA Administrators <qa-***@libreoffice.org> ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present on a currently supported version of
LibreOffice
(5.2.7 or 5.3.3 https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of
LibreOffice and
your operating system, and any changes you see in the bug behavior

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave
a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3)

http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to "inherited from OOo";
4b. If the bug was not present in 3.3 - add "regression" to keyword


Feel free to come ask questions or to say hello in our QA chat:
http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug-20170522
--
You are receiving this mail because:
You are the assignee for the bug.
b***@bugs.documentfoundation.org
2017-08-21 18:57:27 UTC
Permalink
https://bugs.documentfoundation.org/show_bug.cgi?id=51554

Thomas Lendo <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Blocks| |111948


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=111948
[Bug 111948] [META] Insert file content issues
--
You are receiving this mail because:
You are the assignee for the bug.
b***@bugs.documentfoundation.org
2018-12-08 10:32:34 UTC
Permalink
https://bugs.documentfoundation.org/show_bug.cgi?id=51554

eisa01 <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Priority|high |medium
Severity|critical |enhancement
Keywords| |needsUXEval
CC| |***@gmail.com,
| |libreoffice-ux-***@lists
| |.freedesktop.org

--- Comment #12 from eisa01 <***@gmail.com> ---
This is still present as described in the original issue. You have no way of
seeing a slide is linked to another slide in another file, and any edits you do
will be discarded if you update links on the next reopoen.

I don't think this is a bug though, but rather a feature request? So revising
the priority

Adding the UX group to make a decision, so revising

Version: 6.3.0.0.alpha0+
Build ID: beae6c7a7f163daad0d4dea63a3d403af2745fd1
CPU threads: 2; OS: Mac OS X 10.13.6; UI render: default; VCL: osx;
TinderBox: MacOSX-***@49-TDF, Branch:master, Time: 2018-12-06_23:52:29
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Calc: threaded
--
You are receiving this mail because:
You are the assignee for the bug.
b***@bugs.documentfoundation.org
2018-12-10 16:00:47 UTC
Permalink
https://bugs.documentfoundation.org/show_bug.cgi?id=51554

--- Comment #13 from Heiko Tietze <***@gmail.com> ---
The function is now located at Slide > Insert Slide from File... and the user
has to confirm the update on loading. Any change to the linked slide are stored
with the current presentation. For example, <1> <Hello World> <2> (with Hello
World linked from Untitled2) changed to "Hello New World" will be saved and
loaded unless the link is being updated.

So we have two issues, first to know what slide(s) are linked (there is no
information at the Navigator) and to support the user on update or not.

Simplest solution is to just not permit changes of linked files. Something like
a lock icon at the Navigator and at the status bar along with a message box
"You cannot edit this slide directly. Do you want to open the linked file
[Yes/No]" would be handy. Alternatively, we need to show some kind of diff as
changes could have been made on both presentations. Sounds like a lot of
effort.
--
You are receiving this mail because:
You are the assignee for the bug.
Loading...