Hi,
Thanks for your reply. I will use latest version (3.0.9). I believe that
why? you've got 2.0.0 module and code.... you've been told to try your stuff with 2.2.9
change? Hope there is no data structure change happened between version 2.2.0 to 3.0.9.
LOADS of things have been changed between 2.x and 3.x - thats why its a major version release - in the first instance look at the developers docs and read the API and data structure changes - its not a 'compile it as is' process unless your module is very very simple bump your local box to 2.2.9 codebase and start there - there have been thousands of code lines change between those versions and hundreds of bugs/fixes some of which might solve your problem. i can say this though in the first instance, unless you are using 2.2.9 your issue wont get looked at as its likely tohave already been fixed since 2.2.0 alan