Migration Custom Properties from joomla 1.5 to j33

  • brunoserfe
  • Topic Author
  • Offline
  • New Member
  • New Member
More
10 years 5 months ago #1857 by brunoserfe
Hi,

I've found this article in your website => www.solidsystem.it/how-to-and-tutorials/...es-to-joomla-17.html

But I'm trying to migrate a joomla 1.5 custom properties component to a latest version of joomla 3.3.0 and seems that documentation is too old to trust in it.

In step 2 tells that for the migration need to download and install a plugin www.solidsystem.it/download/doc_download...upgrade-plugins.html but with jUpgradePro this is not possible because must be installed in a fresh joomla 3.3.0 instead of
joomla 1.5 (I need to use an obsolete version of jUpgrade?? )

Can you give me some advice and consideration that I've need to take before make a custom properties migration component?

I'm using jUpgradePro v3.3.0 with Custom Properties v3.1.5

Please I await for a quick reply soon.

Thanks!
Best Regards

Please Log in or Create an account to join the conversation.

More
10 years 5 months ago - 10 years 5 months ago #1858 by andrea_4g
The documentation you are referring to doesn't apply too well to the kind of migration you are undertaking (J1.5 -> J3.3).

Here's some advices.
Assuming that:
- you have been able to migrate Joomla articles and categories to the new J3 site
- articles kept their original IDs after the migration
- you were using Custom Properties 2.x for Joomla 1.5

you'll be able to migrate custom properties fields, values e assignments with three SQL queries, because DB tables have not changed.

Procedure:
- install Custom Properties for J 3.x on the new site
- (review and) save custom properties configuration
- run the following queries (using actual db names and prefixes)
Code:
INSERT INTO {newdb.}newprefix_custom_properties SELECT * FROM {olddb.}oldprefix_custom_properties;
Code:
INSERT INTO {newdb.}newprefix_custom_properties_fields SELECT * FROM {olddb.}oldprefix_custom_properties_fields;
Code:
INSERT INTO {newdb.}newprefix_custom_properties_values SELECT * FROM {olddb.}oldprefix_custom_properties_values;
Last edit: 10 years 5 months ago by andrea_4g.

Please Log in or Create an account to join the conversation.

  • brunoserfe
  • Topic Author
  • Offline
  • New Member
  • New Member
More
10 years 5 months ago - 10 years 5 months ago #1859 by brunoserfe
Many many thanks for the quick reply but you miss two things:

1) The table newprefix_custom_properties_fields has a new column "required" for Custom Properties 3.1.5 (The INSERT clause will not work) so you will need to export and edit the oldprefix_custom_properties_fields sql file and then import to the new joomla 3 database.

2) The modules "search and tags cloud" will not work if you not set the cpfields from the back-end administrator of Joomla 3
You need to edit each cpfield and assign a module and then save the field, in other case the module in front-end display an error message like "Component not configured: missing fields"

The question is.. Exist a way to contemplate that case during migration using some function of Custom Properties? Imagine that I've a large records in table #_custom_properties_fields I'll need to edit each field in back-end after the sql tables migration?

Thanks again for the quick reply.
Best Regards
Last edit: 10 years 5 months ago by brunoserfe.

Please Log in or Create an account to join the conversation.

More
10 years 5 months ago - 10 years 5 months ago #1860 by andrea_4g

Assuming that:
- you were using Custom Properties 2.x for Joomla 1.5

I guess you were using some 1.9.x version then, since you found differences in DB structures.

You need to adjust two queries:
Code:
INSERT INTO {newdb.}newprefix_custom_properties_values (`id`, `field_id`, `name`, `label`, `priority`, `default`, `ordering`, `article_id`) SELECT `id`, `field_id`, `name`, `label`, `priority`, `default`, `ordering`, 0 FROM {olddb.}oldprefix_custom_properties_values;
Code:
INSERT INTO {newdb.}newprefix_custom_properties_fields (`id`, `name`, `label`, `field_type`, `modules`, `published`, `required`, `access`, `ordering`, `checked_out`) SELECT `id`, `name`, `label`, `field_type`, '', `published`, 0, `access`, `ordering`, `checked_out` FROM {olddb.}oldprefix_custom_properties_fields;
You will also need to manually:
- edit each field, set the proper access level and save
- (optionally) edit each field and assign it to the relevant CP modules.

Exist a way to contemplate that case during migration using some function of Custom Properties?

There's no use for such function.
Because migration components do not migrate third party components*, there won't be any custom properties DB table to migrate data to, in the new installation.
The same apply for CP modules.

(*with the notable exception of JUpgrade + dedicated plugins, AFAIK)
Last edit: 10 years 5 months ago by andrea_4g. Reason: spelling

Please Log in or Create an account to join the conversation.

Time to create page: 0.176 seconds