WordPress.org

Ready to get started?Download WordPress

Forums

Fluency Admin
Fatal error: Call to undefined function submit_button()... (3 posts)

  1. LJagermaster
    Member
    Posted 3 years ago #

    The following error message is displayed where the "Submit" should be on the options page:

    Fatal error: Call to undefined function submit_button() in /.../wp-content/plugins/fluency-admin/wp-fluency-2.php on line 663

    I had a look at the line and tried changing "false" to "true" but it didn't make any difference (it's now back at "false"). Any ideas?

    Also, it seems the "Screenshots" tab when using the plugin installer doesn't load properly as screenshots aren't showing up at all.

    Thanks in advance,

    LJ

    http://wordpress.org/extend/plugins/fluency-admin/

  2. afrey
    Member
    Posted 3 years ago #

    Did you have any luck with this? I'm having the same exact problem.

  3. LJagermaster
    Member
    Posted 3 years ago #

    This error occurred while we were using version 3.0.1 of wordpress, we've only just managed to "upgrade" to the latest version - 3.1.3 - due to the amount of hacking we had to do to the previous core files (we barely have time to work on the site alone so backing up core files and noting down precisely what was changed and where took us a fair while), however, this issue seems to have been resolved by installing a more recent release of wordpress. If you're using 3.1.3 (or anything higher than 3.1) and still have this issue I'd keep on at the plugin developer for help.

    On the other hand, try deactivating all plugins except from the Fluency admin plugin, then fire up its settings page again to see if the issue is still there. If it's not then it's being caused by one of your other plugins (I know this from my own painful experiences with wordpress bugs). After this it's a case of trial and error, by activating each plugin until the issue re-occurs.

    If you have a lot of plugins like us I recommend - rather than reactivating them one at a time - you do them in alphabetical order (for example, reactivate all plugins starting with A, then reload the fluency settings page, if it seems ok, move onto the B's, etc). Once the issue re-occurs deactivate all the plugins of the last starting letter then reactivate those plugins 1 by 1 until the issue re-occurs again, the last plugin activated is the cause of it. Then pass this info onto the plugin developer (and it may help to inform the developer of the conflicting as well)...

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic