- Posts: 131
Before asking for help please read "Requesting Help and Suggestions" by clicking on that tab above here.
Question Upload duplicate media
- mac.alter
-
Topic Author
- Offline
- Junior Member
-
Less
More
3 weeks 1 day ago #1
by mac.alter
Mac.alter [update: 23 Oct 2023]
webtrees 2.1.18 | PHP Version 8.1.17 | mySQL 8.1 | MacOS 10.15.17
Upload duplicate media was created by mac.alter
I've accidentally uploaded the same image twice. it's accepted. When viewing in Manage Media, it's given a gobbly-gook generic number. Instead would be helpful to have warning that the image is already on file,
Mac.alter [update: 23 Oct 2023]
webtrees 2.1.18 | PHP Version 8.1.17 | mySQL 8.1 | MacOS 10.15.17
Please Log in or Create an account to join the conversation.
- Franz Frese
-
- Offline
- Elite Member
-
3 weeks 23 hours ago #2
by Franz Frese
see freris.de
Replied by Franz Frese on topic Upload duplicate media
Have a look how gedcom and webtrees manage media and you will understand
see freris.de
Please Log in or Create an account to join the conversation.
- mac.alter
-
Topic Author
- Offline
- Junior Member
-
Less
More
- Posts: 131
3 weeks 20 hours ago #3
by mac.alter
Mac.alter [update: 23 Oct 2023]
webtrees 2.1.18 | PHP Version 8.1.17 | mySQL 8.1 | MacOS 10.15.17
Replied by mac.alter on topic Upload duplicate media
Not sure why gedcom and webtrees handling have impact on my request. The feature - warning of duplicate or warning of no media selected -- is in kiwitrees (where I'm converting from)
Mac.alter [update: 23 Oct 2023]
webtrees 2.1.18 | PHP Version 8.1.17 | mySQL 8.1 | MacOS 10.15.17
Please Log in or Create an account to join the conversation.
- Franz Frese
-
- Offline
- Elite Member
-
3 weeks 19 hours ago #4
by Franz Frese
see freris.de
Replied by Franz Frese on topic Upload duplicate media
So now you can learn, why that is not necessary in gedcom and webtrees.
see freris.de
Please Log in or Create an account to join the conversation.
- mac.alter
-
Topic Author
- Offline
- Junior Member
-
Less
More
- Posts: 131
3 weeks 11 hours ago #5
by mac.alter
Mac.alter [update: 23 Oct 2023]
webtrees 2.1.18 | PHP Version 8.1.17 | mySQL 8.1 | MacOS 10.15.17
Replied by mac.alter on topic Upload duplicate media
Let's agree to disagree on this one.
Mac.alter [update: 23 Oct 2023]
webtrees 2.1.18 | PHP Version 8.1.17 | mySQL 8.1 | MacOS 10.15.17
Please Log in or Create an account to join the conversation.
- bertkoor
-
- Offline
- Platinum Member
-
- Greetings from Utrecht, Holland
3 weeks ago #6
by bertkoor
stamboom.BertKoor.nl runs on webtrees v1.7.13
Replied by bertkoor on topic Upload duplicate media
webtrees and kiwitrees have their differences as well, as you have learnt.
You have the choice:
1. Make a point of each and every difference
2. Accept it is not necessarily worse, just a bit different
You have the choice:
1. Make a point of each and every difference
2. Accept it is not necessarily worse, just a bit different
stamboom.BertKoor.nl runs on webtrees v1.7.13
Please Log in or Create an account to join the conversation.
- fisharebest
-
- Offline
- Administrator
-
2 weeks 6 days ago #7
by fisharebest
Greg Roach - greg@subaqua.co.uk - @fisharebest@phpc.social - fisharebest.webtrees.net
Replied by fisharebest on topic Upload duplicate media
> Instead would be helpful to have warning that the image is already on file,
A warning, and then what?
The user uploads a file "grandpa.jpg".
The system says - filename in use - choose another.
The user renames it to "grandpa1.jpg".
The system says - filename in use - choose another.
The user renames it to "grandpa2.jpg".
The system says - filename in use - choose another.
The user gives up.
The current logic assumes the user wants to upload a file more than they want to specify a filename - and it lets them do that without losing any data or overwriting existing files.
The original motivation came from Ancestry, where all downloaded images used to have the same name - x.jpeg, and I got fed up with trying to think of unique names for thousands of documents.
A warning, and then what?
The user uploads a file "grandpa.jpg".
The system says - filename in use - choose another.
The user renames it to "grandpa1.jpg".
The system says - filename in use - choose another.
The user renames it to "grandpa2.jpg".
The system says - filename in use - choose another.
The user gives up.
The current logic assumes the user wants to upload a file more than they want to specify a filename - and it lets them do that without losing any data or overwriting existing files.
The original motivation came from Ancestry, where all downloaded images used to have the same name - x.jpeg, and I got fed up with trying to think of unique names for thousands of documents.
Greg Roach - greg@subaqua.co.uk - @fisharebest@phpc.social - fisharebest.webtrees.net
Please Log in or Create an account to join the conversation.