Error when importing

I'm trying to import a scraping session, and I'm getting the following error: unable to find FieldDescriptor for 'logging_level' in ClassDescriptor of scraping session.

It's a session I've imported and used previously, but I've never seen this error before. Any help you can give to resolve the problem would be appreciated.

screen-scraper version issue

Actually, the problem has to do with what version of SS you're using, compared to the version the file was exported in. Somewhere down the line, you've got a mismatch of version types. It's not a problem when you import an older scrape, but if you're importing a scrape that was done in a higher version of SS, you'll get that exact error.

Logging level has to do with a combobox located at the top right corner of the "Log" tab of a session. There's some behind-the-scenes changes that were made with that combobox, and so importing to an older version wouldn't work, since the logging_level FieldDescriptor would fail to match up, thus making the import fail altogether.

This can happen because of a more up-to-date alpha-version (unstable) update that the exporting instance of screen-scraper is using. This is usually what causes the problem. Just make sure "Upgrade to unstable versions" is checked on in your Settings menu, and that you click on Options -> Check for updates. As long as you've got the most up-to-date release of screen-scraper, you shouldn't run into this problem.

The other cause could be similar: if the scrape was exported in Pro or Enterprise version, and then you attempt to import it from a Basic version of screen-scraper, you would get the same error.

Let me know if that solves your problem!

I got the same problem. what

I got the same problem. what i did is remove the 1 and another tab within the xxx.sss file.
After that the old script can be imported by old ss version.

Yes, ultimately it's simply

Yes, ultimately it's simply an issue of there being more data in the XML of the newer version, than in the older version. A "manual" fix would be as you described. Handy if you don't have a second installation handy to revert back to a previous version. (Either that, or just update your current version to the newest alpha.)

Problem solved

Upgrading to the latest version did solve the problem.

Thanks, Tim!