Bug 2003 - Restoring a backed-up database gives unrendered RXML
: Restoring a backed-up database gives unrendered RXML
Status: VERIFIED FIXED
: Roxen WebServer
Admin Interface
: 2.2
: sparc Solaris
: P3 (normal) normal
: ---
Assigned To:
: http://internal-docs:7001/dbs/restore...
:
:
  Show dependency treegraph
 
Reported: 2001-08-21 11:20 CET by
Modified: 2001-08-22 10:02 CET (History)
Scrum Prio:
In scrum?: ---
Story included in sprints:
Unplanned in sprints:


Attachments


Description From 2001-08-21 11:20:20 CET
The confirmation page in the "restore backed-up database" is not
RXML parsed, and (hence) does not work. An example I got, trying
to restore my "autodoc" database. (The ticket URL refers to the
accessed page.)

<gtext scale=0.5>Restore the following tables from the backup</gtext> <br
/><input type=hidden name=db value='&form.db:http;' /><input type=hidden
name=dir value='&form.dir:http;' /><blockquote><table><tr><td><input
name='bk_tb_errors' type=checkbox checked=checked />errors<br
/></td><td><input name='bk_tb_keywords' type=checkbox checked=checked
/>keywords<br /></td><td><input name='bk_tb_markup' type=checkbox
checked=checked />markup<br /></td><td><input name='bk_tb_tagdoc'
type=checkbox checked=checked />tagdoc<br /></td></tr><tr><td>
<input name='bk_tb_terms' type=checkbox checked=checked />terms<br
/></td></tr></table></blockquote><gtext scale='0.5'>Restore the tables to
the following database</gtext><blockquote><select name='todb'><option>2.1
manual</option><option>ac_Internal_Docs_22</option><option>ac_internal_docs_22_frontend</option><option
selected=selected>autodoc</option><option>docs</option><option>local</option><option>nd_internal_docs_22_</option><option>nd_internal_docs_22_frontend_</option><option>pc_internal_docs_22_</option><option>pc_internal_docs_22_frontend_</option><option>shared</option></select></blockquote><table
width='100%'><tr><td><submit-gbutton2 name='ok'>Ok</submit-gbutton2></td>
<td align=right><a href=''><gbutton> Cancel </gbutton></a></td>
</table>

Note

You need to log in before you can comment on or make changes to this bug.