Title: [Plugin: AG Custom Admin] AG custom admin cannot be activated: "require … FirePHPCore" p
Last modified: August 20, 2016

---

# [Plugin: AG Custom Admin] AG custom admin cannot be activated: "require … FirePHPCore" p

 *  Resolved [thecondordb](https://wordpress.org/support/users/thecondordb/)
 * (@thecondordb)
 * [14 years, 4 months ago](https://wordpress.org/support/topic/plugin-ag-custom-admin-ag-custom-admin-cannot-be-activated-require-firephpcore-problem/)
 * When I updated the AG custom admin plugin to the current version, I got this 
   error (while trying to reactivate the plugin):
 * **Warning: require_once(/../../../../FirePHPCore/lib/FirePHPCore/fb.php) [function.
   require-once]: failed to open stream: No such file or directory in /kunden/330468_40233/
   webseiten/wp-content/plugins/ag-custom-admin/plugin.php on line 26**
 * **Fatal error: require_once() [function.require]: Failed opening required ‘/../../../../
   FirePHPCore/lib/FirePHPCore/fb.php’ (include_path=’.:/usr/local/lib/php’) in /
   kunden/330468_40233/webseiten/wp-content/plugins/ag-custom-admin/plugin.php on
   line 26**
 * Regards,
 * Dennis aka thecondordb
 * [http://wordpress.org/extend/plugins/ag-custom-admin/](http://wordpress.org/extend/plugins/ag-custom-admin/)

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

 *  [WAP Support](https://wordpress.org/support/users/argonius/)
 * (@argonius)
 * [14 years, 4 months ago](https://wordpress.org/support/topic/plugin-ag-custom-admin-ag-custom-admin-cannot-be-activated-require-firephpcore-problem/#post-2527535)
 * I am sorry for this mistake. You could fix it by removing line 26 from ag-custom-
   admin/plugin.php, or simply download new AGCA version 1.2.5.4 with patch for 
   this issue.
 * Thanks.
 *  Thread Starter [thecondordb](https://wordpress.org/support/users/thecondordb/)
 * (@thecondordb)
 * [14 years, 4 months ago](https://wordpress.org/support/topic/plugin-ag-custom-admin-ag-custom-admin-cannot-be-activated-require-firephpcore-problem/#post-2527593)
 * I just made the automatic update to AG custom admin plugin version 1.2.5.4 and
   got this error in a Javascript alert box:
 * **AGCA – ADMIN ERROR: ReferenceError / isWPHigherOrEqualThan is not defined**
 * After that, the plugin seems to be activated but I permanently get the same error
   on every admin page. If I open the AG custom admin plugin page in my admin interface,
   the same error is displayed on the top in red color:
 * **WARNING: AG Custom Admin stops its execution because of an error. Please resolve
   this error before continue: **
 * AGCA – ADMIN ERROR: ReferenceError / isWPHigherOrEqualThan is not defined
 * The plugin became _unusable_.
 * Regards,
 * Dennis aka thecondordb
 *  [WAP Support](https://wordpress.org/support/users/argonius/)
 * (@argonius)
 * [14 years, 4 months ago](https://wordpress.org/support/topic/plugin-ag-custom-admin-ag-custom-admin-cannot-be-activated-require-firephpcore-problem/#post-2527644)
 * This problem is related to cached data. Just clear browser’s cache and try again.
 * I’m realy sorry for this. Caching problem made many headaches to me, but I finally
   found solution for this, and will include it in next release. Caching problem
   should be history.
 * I apologize for this, and problems you have been experiencing. Hope you would
   keep using AG Custom Admin in future.
 * Argonius
 *  Thread Starter [thecondordb](https://wordpress.org/support/users/thecondordb/)
 * (@thecondordb)
 * [14 years, 4 months ago](https://wordpress.org/support/topic/plugin-ag-custom-admin-ag-custom-admin-cannot-be-activated-require-firephpcore-problem/#post-2527660)
 * Thanks for the info.
 * I cleared my cache and the plugin does not report errors anymore and is usable.
 * However NOW my **admin bar is gone (white blank space)** when looking at the 
   front end of the blog (e.g. my blog home page) – if I’m in the admin interface
   the admin bar is visible and ok.
 * Regards,
 * Dennis aka thecondordb
 *  [WAP Support](https://wordpress.org/support/users/argonius/)
 * (@argonius)
 * [14 years, 4 months ago](https://wordpress.org/support/topic/plugin-ag-custom-admin-ag-custom-admin-cannot-be-activated-require-firephpcore-problem/#post-2527669)
 * That’s true. It’s not implemented yet, and is more like new feature than a bug.
   You could display admin top bar on site pages by changing
 *     ```
       function print_page()
       	{
       		?><style type="text/css">
       		#wpadminbar{
       			display:none;
       		}
       		</style><?php
       	}
       ```
   
 * to
 * `function print_page(){}`
 * on line 314 in ag-custom-admin/plugin.php
 * Problem is that styles would not be applied on it and default WordPress top bar
   styles should be applied instead.
 * This would be implement in future releases.
 * Argonius
 *  Thread Starter [thecondordb](https://wordpress.org/support/users/thecondordb/)
 * (@thecondordb)
 * [14 years, 4 months ago](https://wordpress.org/support/topic/plugin-ag-custom-admin-ag-custom-admin-cannot-be-activated-require-firephpcore-problem/#post-2527670)
 * Thanks. This worked.

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

The topic ‘[Plugin: AG Custom Admin] AG custom admin cannot be activated: "require…
FirePHPCore" p’ is closed to new replies.

 * ![](https://ps.w.org/ag-custom-admin/assets/icon.svg?rev=2928712)
 * [AGCA - Custom Dashboard & Login Page](https://wordpress.org/plugins/ag-custom-admin/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/ag-custom-admin/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/ag-custom-admin/)
 * [Active Topics](https://wordpress.org/support/plugin/ag-custom-admin/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/ag-custom-admin/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/ag-custom-admin/reviews/)

 * 6 replies
 * 2 participants
 * Last reply from: [thecondordb](https://wordpress.org/support/users/thecondordb/)
 * Last activity: [14 years, 4 months ago](https://wordpress.org/support/topic/plugin-ag-custom-admin-ag-custom-admin-cannot-be-activated-require-firephpcore-problem/#post-2527670)
 * Status: resolved