You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Payment Service Provider Interface's QuickPay module defines an option called Cancel URL:
Cancel URL is automatically written to data/PSPI/Config.php when webshop settings are updated:
This causes a minor problem if website is moved. If webshop settings are not updated using web interface (see image below), then Cancel URL will still point to the old website.
The work around is easy - simply hit Save in the settings section shown above after the website has been moved. The problem is, of course, that this is invisible to the user. There is no way to tell that this is the solution.
The best solution would be for SMShop to update Cancel URL before it is needed, or simply expose Cancel URL in the UI so the user can actually see it and change it. This does not prevent us from defining an initial value for the field.
Sitemagic CMS actually knows when a website has been moved, so it would be possible to invoke an event that extensions could subscribe to - perhaps via the existing extension life cycle. See code below.
Possible use case for an extension:
class SMShop extends SMExtension
{
public function OnAppMoved($oldInfo, $newInfo)
{
}
}
The text was updated successfully, but these errors were encountered:
Payment Service Provider Interface's QuickPay module defines an option called Cancel URL:
Cancel URL is automatically written to data/PSPI/Config.php when webshop settings are updated:
This causes a minor problem if website is moved. If webshop settings are not updated using web interface (see image below), then Cancel URL will still point to the old website.
The work around is easy - simply hit Save in the settings section shown above after the website has been moved. The problem is, of course, that this is invisible to the user. There is no way to tell that this is the solution.
The best solution would be for SMShop to update Cancel URL before it is needed, or simply expose Cancel URL in the UI so the user can actually see it and change it. This does not prevent us from defining an initial value for the field.
Sitemagic CMS actually knows when a website has been moved, so it would be possible to invoke an event that extensions could subscribe to - perhaps via the existing extension life cycle. See code below.
Possible use case for an extension:
The text was updated successfully, but these errors were encountered: