no news = good news? On our side the gateway is now in production since first of december, and we didn't have any problem so far, now with more than a hundred transactions...
Don't you think we should use the "serialize" function to store our datas into "data_text_1" and "data_text_2" instead of the painful xml dom ?
I see only advantage with this technique :
- It use 2 lines of code to store & retrieve (serialize($array) | unserialize($field)) instead of tens of lines of codes and complexe functions for XML.
- It make our extension ezp 4.0 compatible by avoiding XML use.
- Its way more flexible as "serialize" can handle any kind of var type.
that would be definitively a smarter way to store data, I agree. In my case though I have many other places now where I rely on parsing a DOM inside the order's data_text fields, when building the invoice, tracking the shipping number, keeping track of downloads etc. Now that everything is in XML, I will have a hard time to unroll this. The other (small) advantage of having XML here is the human readeable format in logs and debug sessions.
I will have to look into this issue, but for the moment I did not decide to switch to version 4: I've seen too many issues with the new version to rely on it for production servers for the moment.
So in one word: People who don't rely on the XML storage should feel free to modify the extension's code to use the binary storage, it should work without problems. If I find some time I can also update the extension here to use your code.
</Pascal>
You must be logged in to post messages in this topic!