May 19th, 2011, 8:12 AM
Hi Brettam,
No, not a stupid question at all! It shouldn't behave like that and it's totally not clear what's happening.
The Export Manager relies on a bunch of information being stored in sessions in order to make sense of what it should display (what fields, what order, which export group & type, etc). If, for whatever reason it doesn't have all the information is needs, it throws that error.
Generally, this is caused by PHP sessions being maxed out - or the data being stored in them gets corrupted. The only simple fix for this is to move to database sessions. It doesn't always work, but it's worth a shot.
Open up your /global/config.php and add the following line:
Then log out and in again, and try to do the export again.
- Ben
No, not a stupid question at all! It shouldn't behave like that and it's totally not clear what's happening.
The Export Manager relies on a bunch of information being stored in sessions in order to make sense of what it should display (what fields, what order, which export group & type, etc). If, for whatever reason it doesn't have all the information is needs, it throws that error.
Generally, this is caused by PHP sessions being maxed out - or the data being stored in them gets corrupted. The only simple fix for this is to move to database sessions. It doesn't always work, but it's worth a shot.
Open up your /global/config.php and add the following line:
PHP Code:
$g_session_type = "database";
Then log out and in again, and try to do the export again.
- Ben