Jump to content

Edit History

max.v

max.v


Update

I've already released 2 versions (a few mouths ago), but I can't run the update for the next one.  I just checked, 1.6.1 -> 1.6.2 works, 1.6.2 -> 1.6.3 does not. I have no idea why - I tried just updating the version and not touching anything else - doesn't work, also tried with an upgrade script - it doesn't executes the script.  I'm doing this in a local environment, so I used the debugger and found that it rolls back the files during executing \PrestaShop\PrestaShop\Core\Module\ModuleManager::upgrade. The new version is only installed if we uninstall the module and install it again.

It rolls back the changes during this call:

$this->hookManager->exec('actionBeforeUpgradeModule', ['moduleName' => $name, 'source' => $source]); 

So this is happening because it pulls the archive from Marketplace and installs it? But how it works with 1.6.1->1.6.2 for example.
How I can test the release candidate before it released? 

Any ideas? 

UPDATE: I installed the developer version and the update worked! So in production version I faced unexpected behaviour and have no idea why it still not working...

Thank you for your attention!

max.v

max.v


Update

I've already released 2 versions (a few mouths ago), but I can't run the update for the next one.  I just checked, 1.6.1 -> 1.6.2 works, 1.6.2 -> 1.6.3 does not. I have no idea why - I tried just updating the version and not touching anything else - doesn't work, also tried with an upgrade script - it doesn't executes the script.  I'm doing this in a local environment, so I used the debugger and found that it rolls back the files during executing \PrestaShop\PrestaShop\Core\Module\ModuleManager::upgrade. The new version is only installed if we uninstall the module and install it again.

It rolls back the changes during this call:

$this->hookManager->exec('actionBeforeUpgradeModule', ['moduleName' => $name, 'source' => $source]); 

So this is happening because it pulls the archive from Marketplace and installs it? But how it works with 1.6.1->1.6.2 for example.
How I can test the release candidate before it released? 

Any ideas? 

UPDATE: I installed the developer version and the update worked! So in production I faced unexpected behaviour and have no idea why it still not working...

Thank you for your attention!

max.v

max.v


Update

I've already released 2 versions (a few mouths ago), but I can't run the update for the next one.  I just checked, 1.6.1 -> 1.6.2 works, 1.6.2 -> 1.6.3 does not. I have no idea why - I tried just updating the version and not touching anything else - doesn't work, also tried with an upgrade script - it doesn't executes the script.  I'm doing this in a local environment, so I used the debugger and found that it rolls back the files during executing \PrestaShop\PrestaShop\Core\Module\ModuleManager::upgrade. The new version is only installed if we uninstall the module and install it again.

It rolls back the changes during this call:

$this->hookManager->exec('actionBeforeUpgradeModule', ['moduleName' => $name, 'source' => $source]); 

So this is happening because it pulls the archive from Marketplace and installs it? But how it works with 1.6.1->1.6.2 for example.
How I can test the release candidate before it released? 

Any ideas? 

Thank you for your attention!

max.v

max.v


Update

I've already released 2 versions (a few mouths ago), but I can't run the update for the next one.  I just checked, 1.6.1 -> 1.6.2 works, 1.6.2 -> 1.6.3 does not. I have no idea why - I tried just updating the version and not touching anything else - doesn't work, also tried with an upgrade script - it doesn't executes the script.  I'm doing this in a local environment, so I used the debugger and found that it rolls back the files during executing \PrestaShop\PrestaShop\Core\Module\ModuleManager::upgrade. The new version is only installed if we uninstall the module and install it again.

It rolls back the changes during this call:

$this->hookManager->exec('actionBeforeUpgradeModule', ['moduleName' => $name, 'source' => $source]); 


Don't you know what is happening? 

max.v

max.v

I've already released 2 versions (a few mouths ago), but I can't run the update for the next one.  I just checked, 1.6.1 -> 1.6.2 works, 1.6.2 -> 1.6.3 does not. I have no idea why - I tried just updating the version and not touching anything else - doesn't work, also tried with an upgrade script - it doesn't executes the script.  I'm doing this in a local environment, so I used the debugger and found that it rolls back the files before executing \PrestaShop\PrestaShop\Core\Module\ModuleManager::upgrade. The new version is only installed if we uninstall the module and install it again.

Don't you know what is happening? 

max.v

max.v

I've already released 2 versions (a few mouths ago), but I can't run the update for the next one.  I just checked, 1.6.1 -> 1.6.2 works, 1.6.2 -> 1.6.3 does not. I have no idea why - I tried just updating the version and not touching anything else - doesn't work, also tried with an upgrade script - it doesn't executes the script (the module version was updated to 1.7).  I'm doing this in a local environment, so I used the debugger and found that it rolls back the files before executing \PrestaShop\PrestaShop\Core\Module\ModuleManager::upgrade. The new version is only installed if we uninstall the module and install it again.

Don't you know what is happening? 

×
×
  • Create New...