Hi Doug,
Yup, that's the culprit - same as Jeff (and other's, apparently).
So it turns out this is actually a very old bug, that just one didn't cause any issues until now.
The "action_location" field in the database was changed to a varchar (of size 100) back in a late version of the 2.0.0 Beta. However, other people who *weren't* running that version still encountered the problem, which implies that it was re-introduced by mistake at some point. I haven't yet identified when it occurred (I've checked most of the main builds).
That field stores information about the hook, namely, at what location in the code/template the code should get executed. The old value for the field was "start" and "end", which covers most scenarios. So in most cases it would work fine. But both the Export Manager and File Upload fields rely on setting *different* values for that field, so simply put: neither get called! File uploads don't take place and the Export Manager doesn't show up. Same problem.
In order to fix it, we need to do a manual update to your database. I can't automate it because the data itself (i.e. the values in that field) need to be fixed in some cases.
EDIT: I'm going to review each module now and come up with a general solution that assesses what you have installed then only upgrade the pertinent rows. This'll work for other people encountering the problem. I'll post back when I have it completed.
- Ben
Yup, that's the culprit - same as Jeff (and other's, apparently).
So it turns out this is actually a very old bug, that just one didn't cause any issues until now.
The "action_location" field in the database was changed to a varchar (of size 100) back in a late version of the 2.0.0 Beta. However, other people who *weren't* running that version still encountered the problem, which implies that it was re-introduced by mistake at some point. I haven't yet identified when it occurred (I've checked most of the main builds).
That field stores information about the hook, namely, at what location in the code/template the code should get executed. The old value for the field was "start" and "end", which covers most scenarios. So in most cases it would work fine. But both the Export Manager and File Upload fields rely on setting *different* values for that field, so simply put: neither get called! File uploads don't take place and the Export Manager doesn't show up. Same problem.
In order to fix it, we need to do a manual update to your database. I can't automate it because the data itself (i.e. the values in that field) need to be fixed in some cases.
EDIT: I'm going to review each module now and come up with a general solution that assesses what you have installed then only upgrade the pertinent rows. This'll work for other people encountering the problem. I'll post back when I have it completed.
- Ben