Skip Navigation

[Resolved] export custom codes

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Kolkata (GMT+05:30)

This topic contains 4 replies, has 3 voices.

Last updated by fahimS-2 1 year, 10 months ago.

Assisted by: Minesh.

Author
Posts
#2568221

Tell us what you are trying to do?
In the settings of Toolset, I added a few custom codes which I got from the technical support team. Is there any way to export and import them?

#2568349

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

If you added the custom code at Toolset > Settings > Custom Code then that adds the code in individual .php files in a folder wp-content/toolset-customizations/.

To use the same snippets on another site you can simply copy those .php files to the same folder on the other site (if the folder doesn't exist—because you didn't create any custom code yet—you can first add it).

The snippets won't be active until you activate them.

#2568393

I can see that there is an index.php file in toolset-customizations folder. If I am transferring the snippets from my old site to new site and I don't have that toolset-customizations folder, do I need to move the index.php file too?

#2568399

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Yes - you can just copy the "toolset-customizations" folder from your old site to new site.

I suggest you should create code snippets first on new site with the same name as old site and then copy all the .php files. Make sure the slugs of the code snippet should be equal to the .php file name.

#2568497

My issue is resolved now. Thank you!