<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to 1223: Prevent media file name collisions</title><link>https://sourceforge.net/p/phpgedview/feature-requests/1223/</link><description>Recent changes to 1223: Prevent media file name collisions</description><atom:link href="https://sourceforge.net/p/phpgedview/feature-requests/1223/feed.rss" rel="self"/><language>en</language><lastBuildDate>Sun, 17 Jul 2011 03:53:06 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/phpgedview/feature-requests/1223/feed.rss" rel="self" type="application/rss+xml"/><item><title>Prevent media file name collisions</title><link>https://sourceforge.net/p/phpgedview/feature-requests/1223/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Media file names REALLY need to be determined internally to prevent name collisions. Simply add a uid field to the media table and use a counter to uniquely name the physical files on the server their unique number, or append an easily strippable sequence including the number to the file name, such as my-photo.jpg -&amp;gt; my-photo_1.jpg. Store the orig. file name as you do now for display or batch exporting later. Software as complete as this shouldn't make the user come up with unique names for what could be thousands of items. You should be able to have 5 "picture of dad" images. In a collaborative tool like this, the software needs to prevent accidents like clobbering a file.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Hieber</dc:creator><pubDate>Sun, 17 Jul 2011 03:53:06 -0000</pubDate><guid>https://sourceforge.nete751c71264435082028f2421c83d4690cd154d28</guid></item></channel></rss>