Skip Navigation

[Resolved] Migration from old Types to new Toolset

This support ticket is created 5 years, 4 months ago. There's a good chance that you are reading advice that it now obsolete.

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
- 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 -
- 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 -

Supporter timezone: Europe/London (GMT+00:00)

This topic contains 1 reply, has 2 voices.

Last updated by Nigel 5 years, 4 months ago.

Assisted by: Nigel.

Author
Posts
#1353757
Screenshot 2019-10-02 at 11.27.53.png
Screenshot 2019-10-02 at 11.26.43.png

Hello,
I have this website hidden link where there is the old version of Types.
So, I bought the new plugin and moved, temporanelly, the website to the new URL www2.luigieinaudi.it

I ask to the support how migrate from the old to the new plugin, and they say to me this:

Here's how:
1. Buy the Toolset Presentation ($69) package
2. In your WordPress site, delete Toolset Types (don't worry, you won't lose your data, they remain in the database)
3. Download the new version of Toolset Types from your Toolset account
4. Go to Plugins -> add new and upload that new Toolset Types and activate it.
All your Types-data will appear again.

I follow this guide and seem to work all perfect!
Thank you

But I have a few questions regarding the alerts that I found in the plugin panel.

In the Toolset Dashboard there is this alert (see screenshot in attachment)
Your theme’s template file single.php for displaying Altra Pubblicazione items is missing custom fields.

What is this single.php?

In Toolset Settings there is this alert about a migration (see screenshot in attachment)
This version of Types uses a new way to store post relationships. Your site has relationships that use the old storage, so the new Toolset->Relationships menu is disabled. Types can move these relationships for you, allowing you to use the new post-relationship features. The site's content and how it displays on the front-end will not be affected.

What is this?

I have 8 post type: how can I show the content of these post types in a page with a dropdown menu?
For example: one post type name is "giornali", I want to create a page whit a dropdown menu (that have listed the 8 post type) and when the user select "giornali" the page will load all data from "giornali"

Thank you

#1354029

Nigel
Supporter

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

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

Hi there

What is this single.php?

Your theme includes a number of PHP templates for displaying different kinds of pages. The single.php template is used to display single posts (including custom posts). It won't output the custom fields you create with Toolset (or any other similar plugin).

Toolset lets you create templates for displaying posts according to your own design, including the fields you require, without having to edit the PHP template files. You can read more about that here: https://toolset.com/documentation/getting-started-with-toolset/create-templates-to-display-custom-posts/

What is this? (relationship migration)
Older versions of Types had a particular way of storing and managing post relationships. That changed significantly with Types 3.

If you have an old site with post relationships which works and you are updating but not making significant changes to, then you can likely pass on migrating to the new relationships and continue with the legacy relationships.

If you are making significant changes to the site, much like when starting a new site, you will want to use the new relationship format, and should go ahead and run the migration. You may need to update any Views or templates that output migrated data.

How can I show the content of these post types in a page with a dropdown menu?

You can't.

You can filter lists of posts by custom fields and taxonomies, but not by standard fields, including post_type.

As a workaround you could add a taxonomy where posts of each type were assigned a particular term, and then you could create a View to list any of those post types and include a filter for the taxonomy.