nitriques on 3.0.x
Redirect loggued in users to AP… Add documentation about unambig… Allow numeric values in schema … (compare)
nitriques on 3.0.x
Avoid double insert (write) exe… (compare)
If anyone can help, in the limited XML Importer documentation, https://github.com/symphonists/xmlimporter, it says...
If your field expects an array of data to come from the backend/frontend, then the first mode should be ImportableField::ARRAY_VALUE
I don't know what to put for array value? Under the PHP Function portion of that field.
My data looks similar to @animaux post here... https://www.getsymphony.com/discuss/thread/36868/25/#position-489
@animaux - I am using your fork of XML Importer, and when I put
ImportableField::ARRAY_VALUE in the php function field... I get the following error...
call_user_func_array() expects parameter 1 to be a valid callback, class 'ImportableField' does not have a method 'ARRAY_VALUE'
basically treating that incoming data as an array... the documentation is not clear on how to do that.
Your fields and the XML Importer
The XMLImporter allows fields to implement a
prepareImportValue()function which will preprocess the value from XML before being passed to
processRawFieldData(). The XML Importer will check for the Field class for the
prepareImportValue()otherwise it will fall back to rudimentary processing. The
prepareImportValuefunction will be passed the value of the XPath and the
entry_id, and should return a value that your Field's
processRawFieldDatafunction can accept.
Since XMLImporter 2.1, the
prepareImportValuefunction will choose the first mode returned in the
getImportModesarray. It is anticipated that this mode will be the correct mode that will transform the XML value into a format that the field normally expects from either the Symphony backend, or from an event on the frontend. That is, if your field expects a single string value, then the first mode listed in
ImportableField::STRING_VALUE. If your field expects an array of data to come from the backend/frontend, then the first mode should be
Hi All. Hope you're all well and sane. We are instructing a round of penetration testing on one of our Symphony 2.7.10 web apps. If any of you know of specific areas which warrant attention, then please PM me and I'll ensure inclusion in the tests.
The pen tests will look for the normal weaknesses, so I am just really interested in Symphony-specific vulnerabilities.