Changes between Initial Version and Version 1 of Ticket #3243
- Timestamp:
- 10/14/2006 05:45:08 AM (18 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #3243
-
Property
Status
changed from
newtoassigned
-
Property
Status
changed from
-
Ticket #3243 – Description
initial v1 6 6 7 7 1. It is safer. 8 #.Worst case scenario with assuming data to be unescaped is that it gets double slashed9 #.Worst case scenario with assuming data to be '''escaped''' is SQL injection vulnerability8 * Worst case scenario with assuming data to be unescaped is that it gets double slashed 9 * Worst case scenario with assuming data to be '''escaped''' is SQL injection vulnerability 10 10 2. Post meta has been doing it this way, for a longer time, so less code would have to change 11 11 3. It would allow code consolidation, in terms of handling arrays/objects/strings, serialization, and escape.