Upgrade from 2.0.22 to 2.0.22b

[fritschle]

Installed version 2.0.22
Latest version 2.0.22b

When I upgrade I get a white page that only says "Invalid Token, in store config"
To upgrade I'm going into the Virtuemart component and clicking upgrade under Tools where it shows me there is a newer version.  Using Joomla 2.5.14

Please advise.

[digimate]

I have the same 'problem' trying to upgrade from 2.0.22a to 2.0.22.b.

Joomla 2.5.14

Please help.

[jenkinhill]

That error is caused by Akeeba updater.  See http://forum.virtuemart.net/index.php?topic=117433.msg400481#msg400481 

[digimate]

Why do you 'think' that this problem is caused by Akeeba Backup?

Switching back to the standard installer did not work for me!
Unpublishing the System Restore Points plugin did not solve the problem either.

When I click on the text that tells me there is an Virtuemart update available the link refers still to Akeeba's liveupdate ??:
http://www.my-domain-example.com/administrator/index.php?option=com_virtuemart&view=liveupdate

How to update without using live-update ?? Or am I wrong because the '&view-liveupdate' is not related to Akeeba.

Anyway... I still can't update. The error "Invalid Token, in store config" is still there.

Any help/suggestions?

Thanks in advance.

[fmlk4u]

For me the (local) upgrade (as feasibility test) seems OK, but for one particular category "keyboards" the layout is corrupted. See online the detailpage (OK, version 2.0.20b): http://new.keyboard-centrum.nl/nl/winkel/keyboards/gw-8e-gw-8l2013-04-07-20-34-59-detail

Resp. the category page: http://new.keyboard-centrum.nl/nl/winkel/keyboards and see the attachments of the local result in XAMPP after upgrade.

Weird: all other categories are OK. Btw. With again upgrade problems I fear for the future: upgrade to Joomla 3 and new virtuemart.

Compare the screenshots "Keyboard-online.jpg" and "KB-Detail_OK.jpg" with the keyboard_upgraded and kb_detail_upgraded pictures and clearly see what is wrong.



[attachment cleanup by admin]

[Maxim Pishnyak]

Why do you 'think' that this problem is caused by Akeeba Backup?

Because it's either Akeeba, or not using normal Installation routine.

[Maxim Pishnyak]

... the layout is corrupted.

It's not clear for everybody what is corrupted. Could you put some red figures on your screen shots?

Btw. With again upgrade problems I fear for the future: upgrade to Joomla 3 and new virtuemart.

Yepp. Fear the power of VM 2 and J!3!

[jenkinhill]

And just wait for VM2.1 - that will be another big leap in power!

[jenkinhill]

Why do you 'think' that this problem is caused by Akeeba Backup?

The VM devs worked this out, as the VM live updater uses Akeeba code. Seems there are some file packages it cannot hanndle, but not on every host/site.

[illing]

I have the same issue.  The update returns a message: Invalid Token, in store config  in a blank page.   However the aio update went through without any issues.   Why?   I enclose 2 screen shots.

[attachment cleanup by admin]

[Maxim Pishnyak]

Why?

Read this thread attentively.

[Milbo]

When I upgrade I get a white page that only says "Invalid Token, in store config"
To upgrade I'm going into the Virtuemart component and clicking upgrade under Tools where it shows me there is a newer version.  Using Joomla 2.5.14

This error happens as far as we know only when you use the akeeba backup with restoration points activated. Seems that the session is somehow getting a new sessionId and that Akeeba is doing that.

[fritschle]

I'm using the standard update process and I'm getting this error.  I'm having this issue on all my sites.  Using Rackspace servers.

[jenkinhill]

I'm using the standard update process

You mean Joomla's extensions manager?