eZ CyberMut discussions

«

Previous topic

|

Install & configuration

|

Next topic

»

Author	Message
Pascal Specht	Tuesday 27 November 2007 4:47:30 am This is the place to share technical details or questions concerning the eZ CyberMut extension. (see http://ez.no/community/contribs/workflow/ezcybermut)
Pascal Specht	Monday 03 December 2007 9:42:24 am The error messages in the checker can be corrected this way to get more information about why a paiement was rejected: $this->logger->writeTimedString('eZCyberMut : Post parameters were: '.$Verified_Result);
H-Works Agency	Wednesday 05 December 2007 10:06:03 am Great Pascal ! I am gonna use this module right away. EZP is Great
Pascal Specht	Wednesday 12 December 2007 12:34:02 pm Hey Martin, 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... Cheers, </Pascal>
Guillaume HH	Saturday 05 April 2008 1:59:34 am Hi! I'm looking for a "Société Générale" solution. Do you think I can upgrade your extension or I must to develop one "from scratch" ? Thanks Guillaume
Pascal Specht	Saturday 05 April 2008 10:47:04 am Hi Guillaume, Société Générale is part of the SIPS/ATOS solution. Martin's ezSIPS extension will therefore fit your needs. eZCyberMut will not work. </Pascal>
Guillaume HH	Tuesday 08 April 2008 3:29:07 am Ok! Thanks for the correct extension's name! ++ Guillaume
H-Works Agency	Friday 11 April 2008 4:13:01 am Hi Pascal, 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. What do you think ? EZP is Great
Pascal Specht	Friday 11 April 2008 4:59:38 am Hi Martin, 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>

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing:	Jan 31 2025 04:16:43
Script start
Timing:	Jan 31 2025 04:16:43
Module start 'layout'
Timing:	Jan 31 2025 04:16:43
Module start 'content'
Timing:	Jan 31 2025 04:16:43
Module end 'content'
Timing:	Jan 31 2025 04:16:43
Script end

Main resources:

Total runtime	0.0123 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0048	588.1484	151.2109
Module start 'layout'	0.0048	0.0025	739.3594	36.6484
Module start 'content'	0.0073	0.0037	776.0078	98.2813
Module end 'content'	0.0109	0.0013	874.2891	41.9922
Script end	0.0122		916.2813

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0021	16.9568	14	0.0001
Check MTime	0.0010	8.1886	14	0.0001
Mysql Total
Database connection	0.0007	5.8487	1	0.0007
Mysqli_queries	0.0024	19.2130	3	0.0008
Looping result	0.0000	0.0973	1	0.0000
Template Total	0.0010	8.2	1	0.0010
Template load	0.0008	6.2494	1	0.0008
Template processing	0.0002	1.9567	1	0.0002
Override
Cache load	0.0005	4.3316	1	0.0005
General
dbfile	0.0003	2.2465	8	0.0000
String conversion	0.0000	0.0584	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs