VirtueMart Forum

VirtueMart 2 + 3 + 4 => Installation, Migration & Upgrade => Topic started by: tunasashimi on February 21, 2023, 17:18:53 PM

Title: Extensions needed to update after update
Post by: tunasashimi on February 21, 2023, 17:18:53 PM
Hi

I've updated to VM 4.0.12, but I still get the this notice:
Extensions needed to update: VirtueMart   Administrator    Component    4.0.6    4.0.12


Joomla!      3.10.11
VirtueMart       4.0.12 10777
PHP Version   7.4.33
Title: Re: Extensions needed to update after update
Post by: GJC Web Design on February 22, 2023, 10:04:15 AM
try a "rebuild" of your Update Sites..
Title: Re: Extensions needed to update after update
Post by: tunasashimi on February 22, 2023, 10:35:45 AM
Hi

Rebuild Update Sites did not change anything.

Updated extension, clear cache, search updates:
Extensions needed to update: VirtueMart   Administrator    Component    4.0.6    4.0.12
Title: Re: Extensions needed to update after update
Post by: jenkinhill on February 22, 2023, 11:13:29 AM
This is the new admin template.  The 4.0.12 version is included in the VM 4.0.12.10777 package.

http://dev.virtuemart.net/attachments/download/1359/com_virtuemart.4.0.12.10777_package_or_extract.zip
Title: Re: Extensions needed to update after update
Post by: tunasashimi on February 22, 2023, 12:01:38 PM
Did install the new admin template.

Still having the same issue.
Title: Re: Extensions needed to update after update
Post by: jenkinhill on February 22, 2023, 15:21:39 PM
Check administrator/templates/vmadmin/templateDetails.xml

It should show <version>4.0.12</version>  if 4.0.12 is installed.
Title: Re: Extensions needed to update after update
Post by: tunasashimi on February 22, 2023, 15:46:01 PM
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE install PUBLIC "-//Joomla! 2.5//DTD template 1.0//EN" "https://www.joomla.org/xml/dtd/2.5/template-install.dtd">
<extension version="3.5" type="template" client="administrator" method="upgrade">
<name>vmadmin</name>
<creationDate>28 January 2021</creationDate>
<author>by the VirtueMart team</author>
<authorEmail>max@virtuemart.net</authorEmail>
<authorUrl>http://virtuemart.net</authorUrl>
<copyright>Copyright (C) 2004 - 2022 Virtuemart Team, Inc. All rights reserved.</copyright>
<license>http://www.gnu.org/copyleft/gpl.html GNU/GPL; see LICENSE.txt</license>
<version>4.0.12</version>
<description>New administration template for VirtueMart. Enable the template in the virtuemart config on the first tab, section "Advanced".</description>

<files>
<folder>html</folder>
</files>
    <updateservers>
        <!-- Note: No spaces or linebreaks allowed between the server tags -->
        <server type="extension" name="VirtueMart Administrator Template Update Site"><![CDATA[http://virtuemart.net/releases/vm3/vmadmin.xml]]></server>
    </updateservers>

</extension>
Title: Re: Extensions needed to update after update
Post by: jenkinhill on February 22, 2023, 17:03:55 PM
That's the right (4.0.12) version. So there is possibly a Joomla issue with the updater. If it is not fixed by a rebuild then I wouldn't worry, I can't see it causing a problem.
Maybe use phpMyAdmin to check the manifest_cache for vmadmin in ###_extensions table to see if that has the right version listed.
Title: Re: Extensions needed to update after update
Post by: tunasashimi on February 22, 2023, 17:20:09 PM
This is correct as well ...



{"name":"vmadmin","type":"template","creationDate":"28 January 2021","author":"by the VirtueMart team","copyright":"Copyright (C) 2004 - 2022 Virtuemart Team, Inc. All rights reserved.","authorEmail":"max@virtuemart.net","authorUrl":"http:\/\/virtuemart.net","version":"4.0.12","description":"New administration template for VirtueMart. Enable the template in the virtuemart config on the first tab, section \"Advanced\".","group":"","filename":"templateDetails"}

Title: Re: Extensions needed to update after update
Post by: jenkinhill on February 22, 2023, 17:29:33 PM
Strange cache problem maybe? Anway, all should be OK to use.
Title: Re: Extensions needed to update after update
Post by: tunasashimi on February 22, 2023, 17:36:03 PM
ok, thank you for your help.
Maybe with VM 4.0.13 this strange error has gone ...