Title: Restore interface &#039;broken&#039;
Last modified: August 22, 2016

---

# Restore interface 'broken'

 *  Resolved [kattouf](https://wordpress.org/support/users/kattouf/)
 * (@kattouf)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/restore-interface-broken/)
 * The “Installation” pages looked broken to me. They worked but somehow the code
   where showing.
 * [https://wordpress.org/plugins/akeebabackupcore/](https://wordpress.org/plugins/akeebabackupcore/)

Viewing 5 replies - 1 through 5 (of 5 total)

 *  Plugin Author [nikosdion](https://wordpress.org/support/users/nikosdion/)
 * (@nikosdion)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/restore-interface-broken/#post-5677026)
 * You mean the restoration page? If you see the PHP code instead of the restoration
   interface this is a problem with the server you are restoring to. You should 
   contact your host about it.
 *  Thread Starter [kattouf](https://wordpress.org/support/users/kattouf/)
 * (@kattouf)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/restore-interface-broken/#post-5677039)
 * No not the php code. maybe the ajax code?
 * I mean the buttons said things like: standard_button_next
 * replace_header
 * lots of hiphenated words referring to the buttons and element.
 *  Plugin Author [nikosdion](https://wordpress.org/support/users/nikosdion/)
 * (@nikosdion)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/restore-interface-broken/#post-5677129)
 * Your host has disabled the parse_ini_file PHP function. Please contact them and
   ask them to enable this innocuous function at once. What they meant to disable
   is ini_set which is an entirely different thing. Ask them to use Google to see
   the ENORMOUS difference between the two functions. Simply put:
 * parse_ini_file reads a file or text string in INI format and converts it to an
   array. It does not have access to PHP settings and cannot set PHP settings. Therefore
   it has exactly zero (0) security implications. As a result it must never be disabled.
 * ini_set can modify the PHP runtime configuration, as if the directives applied
   with it were part of the php.ini configuration file. This could be used to modify
   memory limits, execution time limits, temporary paths and other privileged information,
   therefore it has performance and security implications. As a result it may be
   disabled on low quality hosts run by simpleminded folks who do not understand
   how to implement proper account isolation and safeguards against abuse, i.e. 
   extremely bad hosts.
 * Good hosts disable neither. Good hosts use virtualisation, chroot jails and other
   methods of account isolation. I guess your host is the exact opposite of what
   we’d call a “good” host?
 *  Plugin Author [nikosdion](https://wordpress.org/support/users/nikosdion/)
 * (@nikosdion)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/restore-interface-broken/#post-5677130)
 * PS: I assume that you are talking about the restoration script (ANGIE) and not
   Kickstart (the extraction script). If you were talking about Kickstart your host
   has nothing to do with it. Instead, you should disable NoScript or any other 
   Javascript blocker.
 *  Plugin Author [nikosdion](https://wordpress.org/support/users/nikosdion/)
 * (@nikosdion)
 * [11 years, 1 month ago](https://wordpress.org/support/topic/restore-interface-broken/#post-5677357)
 * Not an issue. Marking as resolved.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Restore interface 'broken'’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/akeebabackupcore_485a75.svg)
 * [Akeeba Backup CORE for WordPress](https://wordpress.org/plugins/akeebabackupcore/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/akeebabackupcore/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/akeebabackupcore/)
 * [Active Topics](https://wordpress.org/support/plugin/akeebabackupcore/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/akeebabackupcore/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/akeebabackupcore/reviews/)

 * 5 replies
 * 2 participants
 * Last reply from: [nikosdion](https://wordpress.org/support/users/nikosdion/)
 * Last activity: [11 years, 1 month ago](https://wordpress.org/support/topic/restore-interface-broken/#post-5677357)
 * Status: resolved