A process for avoiding problems importing content type and CCK fields

I am a very new Drupal developer and wanted to import a CONTENT TYPE AND ASSOCIATED FIELDS into a website from another. Both were using the CCK. I could export but when I pasted the material in for the Import steop, the file was labled as not a proper file. I searched for others with similar problems and could find no help. Luckily I stumbled onto the solution and others might profit from my solution.

When I had tried for the first time, I had the copy content module enabled, and it should have been easy. But it was not. Drupal kept rejecting the file with an error message that Drupal did not recognize the copied material as being in the right format. After a few days of fumbeling and bumbeling, I found the problem. I had installed a WYSIWYG module and it was visible when I pasted the copied material in. I suspected that export/import routines in general expect to see ASCII and not HTML or rich text of any other kind. So I turned off the PERMISSIONS for me (administrator) to view and use WYSIWYG, and then pasted the material in. That did it. THe entire Content Type and over a dozen defined field imported perfectly. I was going to disable the WYSIWYG module, but tried the easier and later labor saving approach and just denying myself permission to use WYSIWYG . Then I reactivated my WYSIWYG use permission. Be careful and leave yourself with permission to Administer the WYSIWYG.

I'm not really sure why this should have been necessary. I thought about raising the issue with the module developers but there are two involved and they don't play well together. The two modules are the Content Copy and the WYSIWYG module. Is this the proper process? I don't know the norms yet.