<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Locating pln file for published Module in Documentation</title>
    <link>https://community.graphisoft.com/t5/Documentation/Locating-pln-file-for-published-Module/m-p/121290#M65872</link>
    <description>Have just done exactly that and it seems to do the trick=) Hopefully working on the MOD file won't cause any unforseen complication down the track. Thanks Barry, thats a great suggestion!</description>
    <pubDate>Thu, 28 Feb 2013 20:05:54 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2013-02-28T20:05:54Z</dc:date>
    <item>
      <title>Locating pln file for published Module</title>
      <link>https://community.graphisoft.com/t5/Documentation/Locating-pln-file-for-published-Module/m-p/121285#M65867</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;Does anyone know how to find the details of the pln file from which the hotlinked module comes from? &lt;BR /&gt;
(e.g. I am working on a legacy project that has a module hotlinked into the file which needs changes but have no idea which pln file it comes from). Is there a way of finding out?&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 30 May 2023 11:43:04 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Locating-pln-file-for-published-Module/m-p/121285#M65867</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-05-30T11:43:04Z</dc:date>
    </item>
    <item>
      <title>Re: Locating pln file for published Module</title>
      <link>https://community.graphisoft.com/t5/Documentation/Locating-pln-file-for-published-Module/m-p/121286#M65868</link>
      <description>File &amp;gt; External Content &amp;gt; Hotlink Manager</description>
      <pubDate>Fri, 22 Feb 2013 18:37:44 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Locating-pln-file-for-published-Module/m-p/121286#M65868</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2013-02-22T18:37:44Z</dc:date>
    </item>
    <item>
      <title>Re: Locating pln file for published Module</title>
      <link>https://community.graphisoft.com/t5/Documentation/Locating-pln-file-for-published-Module/m-p/121287#M65869</link>
      <description>&lt;BLOCKQUOTE&gt;Enovate wrote:&lt;BR /&gt;Does anyone know how to find the details of the pln file from which the hotlinked module comes from? &lt;BR /&gt;
(e.g. I am working on a legacy project that has a module hotlinked into the file which needs changes but have no idea which pln file it comes from). Is there a way of finding out?&lt;/BLOCKQUOTE&gt;

If the hotlinked module is actually a PLN, then the command that Matthew gave will tell you where it is.&lt;BR /&gt;
&lt;BR /&gt;
You used the phrase 'published module' though.  I we are talking about MOD files that have been published from a PLN (e.g., detail MOD published from a master detail PLN) - then, no, there is no way to find out where it came from AFAIK.  The only idea I can think of at the moment is to do a system search based on the time stamp of the MOD file and find any PLN's with nearby date/time.&lt;BR /&gt;
&lt;BR /&gt;
MOD files don't have additional meta-data (like Project Info) attached to them that I know of.  But, this seems like a good wish... to store within a MOD the info on the file (if any) that it originated from.&lt;BR /&gt;
&lt;BR /&gt;
Cheers,&lt;BR /&gt;
Karl</description>
      <pubDate>Fri, 22 Feb 2013 19:43:48 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Locating-pln-file-for-published-Module/m-p/121287#M65869</guid>
      <dc:creator>Karl Ottenstein</dc:creator>
      <dc:date>2013-02-22T19:43:48Z</dc:date>
    </item>
    <item>
      <title>Re: Locating pln file for published Module</title>
      <link>https://community.graphisoft.com/t5/Documentation/Locating-pln-file-for-published-Module/m-p/121288#M65870</link>
      <description>That clarifies it all, thanks Karl really appreciate it, and a sound suggestion =]</description>
      <pubDate>Sat, 23 Feb 2013 20:18:14 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Locating-pln-file-for-published-Module/m-p/121288#M65870</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2013-02-23T20:18:14Z</dc:date>
    </item>
    <item>
      <title>Re: Locating pln file for published Module</title>
      <link>https://community.graphisoft.com/t5/Documentation/Locating-pln-file-for-published-Module/m-p/121289#M65871</link>
      <description>If it is a published MOD file then you might not be able to easily find the source PLN file but you should be able to open the MOD file and make changes to it and then resave back as the MOD file.&lt;BR /&gt;
This will update all hotlinks in every job to this file.&lt;BR /&gt;
&lt;BR /&gt;
Or if you just want to update it in the file you are working on then you can break the hotlink.&lt;BR /&gt;
&lt;BR /&gt;
Barry.</description>
      <pubDate>Mon, 25 Feb 2013 02:18:28 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Locating-pln-file-for-published-Module/m-p/121289#M65871</guid>
      <dc:creator>Barry Kelly</dc:creator>
      <dc:date>2013-02-25T02:18:28Z</dc:date>
    </item>
    <item>
      <title>Re: Locating pln file for published Module</title>
      <link>https://community.graphisoft.com/t5/Documentation/Locating-pln-file-for-published-Module/m-p/121290#M65872</link>
      <description>Have just done exactly that and it seems to do the trick=) Hopefully working on the MOD file won't cause any unforseen complication down the track. Thanks Barry, thats a great suggestion!</description>
      <pubDate>Thu, 28 Feb 2013 20:05:54 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Locating-pln-file-for-published-Module/m-p/121290#M65872</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2013-02-28T20:05:54Z</dc:date>
    </item>
    <item>
      <title>Re: Locating pln file for published Module</title>
      <link>https://community.graphisoft.com/t5/Documentation/Locating-pln-file-for-published-Module/m-p/121291#M65873</link>
      <description>&lt;BLOCKQUOTE&gt;Enovate wrote:&lt;BR /&gt; Hopefully working on the MOD file won't cause any unforseen complication down the track.&lt;/BLOCKQUOTE&gt;

So long as nobody finds the original PLN and re-publishes the MOD file - effectively re-setting it back to the old file.&lt;BR /&gt;
&lt;BR /&gt;
Any file or selection of elements can be saved as a MOD file so maybe it was never actually published as a MOD in the first place - it may have just been saved.&lt;BR /&gt;
A MOD file is just like a PLN except it only contains the attributes (layers, pen colours, etc.) that are associated with the elements in the file.&lt;BR /&gt;
It can be opened and edited just like any other file.&lt;BR /&gt;
There is no need to use the MOD file format - you can do the same with PLN files (i.e. hotlinking) it is just they contain all the attributes regardless of if they have been used or not and these will be brought into your new file when you insert it.&lt;BR /&gt;
Not a problem if you base all your jobs on the same template.&lt;BR /&gt;
&lt;BR /&gt;
Barry.</description>
      <pubDate>Fri, 01 Mar 2013 01:56:13 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Locating-pln-file-for-published-Module/m-p/121291#M65873</guid>
      <dc:creator>Barry Kelly</dc:creator>
      <dc:date>2013-03-01T01:56:13Z</dc:date>
    </item>
  </channel>
</rss>

