Reply to thread

Message

<blockquote data-quote="Dadeo" data-source="post: 634042" data-attributes="member: 27204">Nice idea 1st dead. I can confirm that from a skin perspective you can add a version tag like &lt;version&gt;1.4&lt;/version&gt;. I have used that already and it works. The issue is that I assume MPEI has to check each xml then to determine compatibility. If it is fast enough, even when we we have 50 plugins using MPEI installed, then cool!&nbsp; I can already see that updating online info is taking longer and longer with more extensions starting to use MPEI![USER=18021]dukus[/USER] - I am having a problem with the way update works.&nbsp; At present, I see no way to correct errors or add info to Descriptions (either Extension or Version) in update.xml, to add screenshots, or anything else, without creating a whole new .mpe1 file with a different name. Is that correct?&nbsp; I realize that normally you only do that when you issue a new release of an extension.&nbsp; However I am human, and sometimes make mistakes and I don't see them (especially formatting errors) until I see the results in MPEI or the Extensions Plugin.&nbsp;&nbsp; Is there any way I can fix them without issuing a new release?Am I correct that the local cache is retained until a user chooses to clean it?&nbsp; This means all extensions should all keep copies of previous releases and previous update.xml and xmp2 files or else users receive a 404 error when they try to access them?&nbsp; Maybe all we need is a better error message when a version of an extension is not longer available?&nbsp; Perhaps it could include a tip to clean the cache?</blockquote>

[QUOTE="Dadeo, post: 634042, member: 27204"] Nice idea 1st dead. I can confirm that from a skin perspective you can add a version tag like <version>1.4</version>. I have used that already and it works. The issue is that I assume MPEI has to check each xml then to determine compatibility. If it is fast enough, even when we we have 50 plugins using MPEI installed, then cool! I can already see that updating online info is taking longer and longer with more extensions starting to use MPEI! [USER=18021]dukus[/USER] - I am having a problem with the way update works. At present, I see no way to correct errors or add info to Descriptions (either Extension or Version) in update.xml, to add screenshots, or anything else, without creating a whole new .mpe1 file with a different name. Is that correct? I realize that normally you only do that when you issue a new release of an extension. However I am human, and sometimes make mistakes and I don't see them (especially formatting errors) until I see the results in MPEI or the Extensions Plugin. Is there any way I can fix them without issuing a new release? Am I correct that the local cache is retained until a user chooses to clean it? This means all extensions should all keep copies of previous releases and previous update.xml and xmp2 files or else users receive a 404 error when they try to access them? Maybe all we need is a better error message when a version of an extension is not longer available? Perhaps it could include a tip to clean the cache? [/QUOTE]

Verification