开发者 |
daveshine
deckerweb |
---|---|
更新时间 | 2019年2月22日 06:07 |
捐献地址: | 去捐款 |
PHP版本: | 3.3 及以上 |
WordPress版本: | 5.1 |
版权: | GPL-2.0+ |
版权网址: | 版权信息 |
Backup or Transfer Settings Finally, transfer Premise settings from one site to another. Or just make backups. Third-party plugins from Premise are supported as well. Especially useful for developers to speed up their work! A great helper tool for the premium "Premise" plugin!Features, Advantages & Benefits
.JSON
file, speeds up development especially! (For example: ALL Premise main settings, plus ALL MemberAccess main settings, plus ALL Landing Page Design Sets, plus ALL Button configuritions -- very handy ;-).JSON
files of settings sections could be useful for testing purposes for developers etc.Typical Workflow Example Transfer settings from a development install to the live/ production install. 1) Prerequisites/ Requirements:2) Transfer:
- On BOTH sites/ installations you have installed & activated "Premise".
- On BOTH sites/ installations you have installed & activated this plugin, "Premise Settings Transporter".
- It's recommended to have THE VERY SAME VERSIONS installed on the original site and also the receiving site. Reason: sometimes settings differ between plugin versions. So with making sure you have the same versions installed you just ensure the correct settings are included within the export file.
- On the development install: Just make an Export file via "Premise > Import/Export" admin page:
- In the "Export" section there enable all checkboxes you need.
- Save the .JSON file to your computer.
- On the live/ production site, just import this .JSON file and you're done! ;-)
premise-settings-transporter.pot
) for translators is also always included :)premise-settings-transporter
folder to the /wp-content/plugins/
directory -- or just upload the ZIP package via 'Plugins > Add New > Upload' in your WP Admin/wp-content/languages/premise-settings-transporter/
(just create this folder) - This enables you to use fully custom translations that won't be overridden on plugin updates. Also, complete custom English wording is possible with that, just use a language file like premise-settings-transporter-en_US.mo/.po
to achieve that (for creating one see the tools on "Other Notes").Just see plugin description page for a typical workflow example.
Just make sure you have the very same versions of the Premise plugin installed on the various installations. If you have a development and live install, just make sure, both have the very same version of "Premise" installed. -- Reason: Sometimes setting field names could differ between different versions, or settings may be added or removed in newer/ older versions.
No worries, the individual "Design Settings" have a built-in export/ import feature in "Premise" already! If you have already created more than one Design just can open each one and export/ import it individually. You can export all Designs except the default one. To export the default Design just duplicate it and then it also becomes exportable ;-).
Again, no worries, the Premise "Landing Pages" are a custom post type and therefore it could be exported/ imported via WordPress own's export functionality for custom post types. Just go to "Tools > Export Data" select "Landing Pages" from the list there and make an .xml
export file for your landing pages only.
To import the "Landing Pages" .xml
file, just install & activate the official "WordPress Importer" plugin, then go to "Tools > Import Data" and upload your export file. Also very simple, yeah :).
I just ported the awesome (!) Genesis exporter feature for the Premise plugin. So, you have to applaud the developers of Genesis Framework for their awesome work, they did all the heavy lifting!