<![CDATA[ Support/Comments for exportElementProperties - MODX Community Forums]]> https://forums.modx.com/thread/?thread=101131 <![CDATA[Support/Comments for exportElementProperties]]> https://forums.modx.com/thread/101131/support-comments-for-exportelementproperties#dis-post-545941 https://modx.com/extras/package/exportelementproperties
or
https://github.com/donShakespeare/exportElementProperties

Many of us don't deal in element properties, save an occasional pset here or there used in the frontend, by snippets and stuff.

This nonquaintance, in part, is due to MODX Extras developers relying heavily on System Settings and other byways.

But in my acute lack of overall knowledge I can only say, quite opinionatedly, that a small or large Extra's settings DO NOT belong in the System Settings.

Elements have properties, use them! Don't keep your wallet in your wife's purse, period!


But MODX has a native way to handle exportation and deportation? ahem ahem, not really see
https://forums.modx.com/thread/99541/exporting-property-set-request-uri-too-large

But there is even another more beautiful extra, xButtons, that does a more comprehensive job? ahem ahem, yes, true that.
But at the time of this writing, the extra is tantrum-prone.


Disable need for &p param in plugin's properties
Now add url parameter &p to any element Manager Page URL you are on.

example.com/manager/?a=element/plugin/update&id=21&p
example.com/manager/?a=element/template/update&id=1&p
example.com/manager/?a=element/snippet/update&id=118&p
example.com/manager/?a=element/chunk/update&id=12&p
example.com/manager/?a=element/tv/update&id=22&p

For PropertySets (go to pset page first, and add value {name of pset} to &p)
example.com/manager/?a=element/propertyset&p=myPSetName

To get desired order of JSON objects, intentionally sort your props and save
]]>
donshakespeare Oct 25, 2016, 08:47 PM https://forums.modx.com/thread/101131/support-comments-for-exportelementproperties#dis-post-545941