Aahh...but I am not passing userphoto
I could not upload your photo. Please check the permissions of the "userimages" folder.
Coolio... Consider it an added option for the next version and thanks for the clarifications.
...In the example, disableDeleteProfile would be a SNIPPET parameter only. Such parameters cannot be altered/hi-jacked, regardless of GET/POST request unless the snippet author somehow allows them to be overwritten. Really, it’d be a PHP boolean declared at run time...
☆ A M B ☆
☆ A M B ☆
Rather cool setup via WLPE, actually.
"Hello here’s a test"
\"
<input id="wlpeUserProfileTimeZone" type="text" name="time_zone" value=""" />
//<?php $modx->db->escape( stripslashes( htmlentities( trim( $form_field ), ENT_QUOTES ) ) )
Yes. It uses $modx->getFullTableName();
It appears that &customTable automatically prepends the "modx_" (or whatever db table prefix set in config) table prefix to the custom table.
Why? Are you wanting to pull from an external db?
Is there a way to optionally remove this prefix for custom tables? Whether a parameter, or by passing the entire table name, etc?
Yeah, I think all i have is a $modx->db->escape()
Also, I tried submitting text containing quotes/apostrophes to a custom table field, and it doesn’t seem to be capturing as on might expect:
I submitted:
"Hello here’s a test"
Only thing that made it to the database was:
\"
As a result, I see nothing in the INPUT when I Try editing the profile (Here’s the HTML, NOTE: the triple quote):
<input id="wlpeUserProfileTimeZone" type="text" name="time_zone" value=""" />
This is some code I wrote for my previous "extended" scenarios:
//<?php $modx->db->escape( stripslashes( htmlentities( trim( $form_field ), ENT_QUOTES ) ) )
☆ A M B ☆
It is very strange as a developer to hear all the interesting ways people are using your software. I never would have planned for half the stuff you come up with!
That is fine by me.
No, I am not accessing an external db, rather a custom table within the MODx database instance. In fact, we have quite a few tables, some for staging, that do not use the "modx_" prefix, and this is by design.
In my example, I will be interfacing with SMF Forum and WLPE. But, since WLPE requires custom tables to use the defined prefix, I will have to keep a small modified version
Thanks
☆ A M B ☆
(as you suggested)
&customTable=`{prefix}my_extra_table`
CREATE TABLE IF NOT EXISTS ...
Excellent!
However, I did receive an error trying to create the table that already existed...you may want to alter the CREATE statement SQL toCREATE TABLE IF NOT EXISTS ...
I’m not sure how the CREATE/ALTER portion of your code will be impacted as a result of the param, but may need to consider...
I am impressed and happy with all the new doors it opens !
)