Cannot export table from database on web site (iPage)

[Former user]

Originally reported on Google Code with ID 156

What steps will reproduce the problem?
1. I select a table in my database.
2. ...click on Export tab
3. ...leave all settings as default on Export page
4. ...click Export button in Save As box
5. ...wait for file download
6. ...open and view file contents. 

What is the expected output? What do you see instead?
I expect to see an sql code representation of my table.
Instead I get: 
<div class='confirm' style='margin:20px;'>The database, '', does not exist and cannot
be created because the containing directory, '', is not writable. The application is
unusable until you make it writable.<form action='phpliteadmin.php' method='post'/><input
type='submit' value='Log Out' name='logout' class='btn'/></form></div><br/>


What version of the product are you using? v1.9.2
On what operating system? Windows 7 on an HP laptop (client); don't know the OS on
the web site (iPage)
Which Database Extension (PDO/SQLiteDatabase/SQLiteDatabase3 - see Database structure-tab
in phpLiteAdmin)? Not known


Please provide any additional information below.
Its a small table - only 12 rows by 8 cols.

Reported by lewznmymind on 2012-11-23 05:48:29

[Christopher Kramer]

Thanks for the issue and sorry for the late reply.

I was not able to reproduce this, neither with 1.9.2 nor the current development version.
Is this issue still present in 1.9.3?

It looks like the session variable $_SESSION[COOKIENAME.'currentDB'] is empty. But
I don't see any reason why it is cleared. Either the session-id doesn't get passed
or there is some bug that cleans the session variable.

Can you place a phpinfo file on the host and provide us with the output (for instructions,
see for example http://docs.simplemachines.org/index.php?topic=479.0 ).

Reported by crazy4chrissi on 2013-03-09 15:39:27

[Former user]

I have the same problem with 1.9.4. I've reverted to version 1.9.3.3 and works fine.

Reported by is2cool4me on 2013-03-20 18:15:58

[Former user]

Ok, fix in issue 195. Close this post..

Reported by is2cool4me on 2013-03-20 18:22:35

[Christopher Kramer]

Hmm well. But the original poster said he uses 1.9.2 and issue #195 has been introduced
by r350 (i.e. after the release of 1.9.2 and after the original poster of this issue
reported this issue).

It would really be much help if the original poster could give us feedback if this
issue is solved for him in 1.9.4 or if it only happens for the first db.

Reported by crazy4chrissi on 2013-03-20 19:07:43

[Christopher Kramer]

Closed due to lack of feedback.

Reported by crazy4chrissi on 2015-01-03 23:25:45 - Status changed: Invalid