| Age | Commit message (Collapse) | Author |
|---|
|
patch you sent, it still uses get but the generated token should make a CSRF attack much harder.
git-svn-id: https://code.elgg.org/elgg/trunk@2057 36083f99-b078-4883-b0ff-0f9b5a30f544
|
|
git-svn-id: https://code.elgg.org/elgg/trunk@1962 36083f99-b078-4883-b0ff-0f9b5a30f544
|
|
git-svn-id: https://code.elgg.org/elgg/trunk@1961 36083f99-b078-4883-b0ff-0f9b5a30f544
|
|
git-svn-id: https://code.elgg.org/elgg/trunk@1900 36083f99-b078-4883-b0ff-0f9b5a30f544
|
|
git-svn-id: https://code.elgg.org/elgg/trunk@1835 36083f99-b078-4883-b0ff-0f9b5a30f544
|
|
git-svn-id: https://code.elgg.org/elgg/trunk@1806 36083f99-b078-4883-b0ff-0f9b5a30f544
|
|
git-svn-id: https://code.elgg.org/elgg/trunk@1563 36083f99-b078-4883-b0ff-0f9b5a30f544
|
|
Use the same technique as edit pages on widgets, i.e.
1) Create a new view in your plugins view/default called settings/PLUGINNAME/edit
Where PLUGINNAME is the plugin directory, eg "river" or "profile".
2) Place your edit code in edit.php, fields should save to params[fieldname].
3) The view will be passed $vars['entity'] which holds any configuration values already set in the metadata.
Note. Settings are PER SITE.
git-svn-id: https://code.elgg.org/elgg/trunk@1031 36083f99-b078-4883-b0ff-0f9b5a30f544
|
|
git-svn-id: https://code.elgg.org/elgg/trunk@1029 36083f99-b078-4883-b0ff-0f9b5a30f544
|
|
http://trac.elgg.org/elgg/ticket/20
git-svn-id: https://code.elgg.org/elgg/trunk@1027 36083f99-b078-4883-b0ff-0f9b5a30f544
|
