Extension 'Country Specific VAT' doesn't work

English forums
1

Hello everybody,

I am using CE 4.4.6, have downloaded and installed the extension ‘Country Specific VAT’ and modified the config.inc.php like directed in README, but it doesn’t work like stated in its description. It doesn’t matter which country a customer is located to, OXID always uses the default VAT configured at Admin > Master Settings > Core Settings> Settings > VAT. What am I doing wrong?
For me it looks like that the function getUserVat in file modules/modvatselector.php will not be executed at any time. I than modified the function getUserVat in file /core/oxvatselector.php like this:

$aCountryVat = $this->getConfig()->getConfigParam( ‘aCountryVat’ );
if ($aCountryVat[$sCountryId] !== NULL) {
$ret = $aCountryVat[$sCountryId];
}
else {
$ret = $this->getConfig()->getConfigParam( ‘dDefaultVAT’ );
}

Now, it works like it should be, but this isn’t really a good way, because it’s a stupid workaround and it only works for standard products. Additionally it will be overwritten with oncoming updates from OXID. Does anyone have a clue how to get the extension working?

Best regards
Nils

2

as this extension was written by OXID themselves, maybe it would be nice to post this issue in Bugtracker

3

@Ray: Thanks for your advice, so I just dropped a post @ bugtrack.

4

Hi,

this extension was published as a module and will therefore never been overwritten by any update. On the other hand, we presently have no possibility to support it with updates during the regular development process. Usually, this kind of modules are a result of specific extensions for certain projects/jobs…

Regards

5

@Marco:
"this extension was published as a module and will therefore never been overwritten by any update."
Yes, you’re right with that. But I stated that I modified a function in the file /core/oxvatselector.php and this one - maybe - is updated with the next version.

"On the other hand, we presently have no possibility to support it with updates during the regular development process."
No problem with that.

"Usually, this kind of modules are a result of specific extensions for certain projects/jobs…"
I can’t follow this statement. No matter, if talking about a whole module or a single function, nevertheless the code should work prior to its release.
For me this sounds like “You can have this cd-tuner for your car for free”. After you had installed the device, it is said “But it will not function, because it was designed to operate in certain cars.”.