| Summary | serialize problem |
| Queue | Ulaform |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | |
| Requester | david (at) tmv (dot) gov (dot) tw |
| Created | 05/31/2005 (7402 days ago) |
| Due | |
| Updated | 06/10/2005 (7392 days ago) |
| Assigned | 06/06/2005 (7396 days ago) |
| Resolved | 06/09/2005 (7393 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
New Attachment: sql.php.patch
Mean while,getField() also require to fix ,patch was attached.
David
State ⇒ Resolved
New Attachment: new_form.gif
We pass the data through Horde_Serialize(), so I'm not surprised that
it's not the original data. That's how we handle form_params, too, so
do those work for you? I'm not sure what the difference is, if you
could have a peek at the code that'd be great.
now,but some columns can't be tarnsfered to chinese string while
click edit form/field.
Screenshot for your information:
new_form.gif : New a form which form's name in chinese.
edit_form.gif : Edit that form,form's name no more in chinese.
new_field.gif : New a field which values and prompt in chinese.
edit_field.gif : Edit that field,value & prompt no more in chinese.
David
question about form_params vs. field_params?
New Attachment: serialize-in-phpshell.jpg
The length of chinese string in Horde's php-shell was serialize as 3x
by every single chinese not 2x ,i think that is why cause this issue.
Screenshot : serialize-in-phpshell.jpg will explain what i'd say.
On the other hand,running script in serialize-in-phpshell.jpg instead
of http://210.241.49.68/~txg16/serialize-in-url.php ,and this time
string length serialized correctly with 2x by every single chinese.
We pass the data through Horde_Serialize(), so I'm not surprised that
it's not the original data. That's how we handle form_params, too, so
do those work for you? I'm not sure what the difference is, if you
could have a peek at the code that'd be great.
the original multibyte string,eg. enter chinese in th form.
David
a:2:{s:6:"values";s:13:"+kHhT1lA8geo-";s:6:"prompt";s:0:"";}
string=+kHhT1lA8geo- (Not OK)
original multibyte string,eg. enter chinese in th form.
David
a:2:{s:6:"values";s:13:"+kHhT1lA8geo-";s:6:"prompt";s:0:"";}
^^^^^^^^^^^^^^^^^
State ⇒ Feedback
http://cvs.horde.org/diff.php/ulaform/lib/Driver/sql.php?r1=1.31&r2=1.32&ty=u
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ serialize problem
Queue ⇒ Ulaform
State ⇒ Unconfirmed
ulaform_fields:field_params,if use non ASCII in it.
For example,create new form with "Drop down list" type ,and use
multibyte in values.
Here are the record point to the it.
a:2:{s:6:"values";s:15:"??1,??2";s:6:"prompt";s:0:"";}
should be fixed as ==>
a:2:{s:6:"values";s:11:"??1,??2";s:6:"prompt";s:0:"";}