<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-ligatures:standardcontextual;
mso-fareast-language:EN-US;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-AU" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">I have been having some issues with the memory layer saver plugin which I thought might be worth sharing.<o:p></o:p></p>
<p class="MsoNormal">I find the plugin extremely valuable, but we may be making ourselves too dependent on it because it works so well.<o:p></o:p></p>
<p class="MsoNormal">Recently the plugin was updated with a great new feature, it now saves the .mldata file containing all the memory layers within the .qgz file instead of as a sidecar file.<o:p></o:p></p>
<p class="MsoNormal">This seems to be the source of our issues with vanishing layers. We have some users with the old version of the plugin and some with the new version.<o:p></o:p></p>
<p class="MsoNormal">If an old project is opened with the updated plugin, it successfully loads the old data from the external file and moves it to the internal file.<o:p></o:p></p>
<p class="MsoNormal">If subsequently opening the project, it reads from the internal file. All good.<o:p></o:p></p>
<p class="MsoNormal">The issue is if someone opens a converted file with the older version of the plugin. It will find the old external mldata file still there. New layers added with the new version will be empty but old ones will still work. Any new layers
added with the old plugin will be added to the external mldata file.<o:p></o:p></p>
<p class="MsoNormal">If the file is then opened again with the new plugin, it seems to just use the internal mldata, and new layers added to the old file will be missing.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In short it all works great as long as all people using the file update to the new version plugin at the same time.<o:p></o:p></p>
<p class="MsoNormal">I have been able to recover lost layers by opening the qgz file with 7zip and overwriting the internal mldata file with the modified external one. Can get messy if there are multiple edits in both versions though.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Were running in circles for a while as we though the issue was with new versions of qgis rather than the plugin.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><span style="color:#1F497D;mso-ligatures:none;mso-fareast-language:EN-GB">Michael Dufty</span></b><span style="color:#1F497D;mso-ligatures:none;mso-fareast-language:EN-GB"><o:p></o:p></span></p>
</div>
</body>
</html>