Title: Errors I started getting with 1.4.5
Last modified: August 21, 2016

---

# Errors I started getting with 1.4.5

 *  Resolved [Klatch](https://wordpress.org/support/users/klatch/)
 * (@klatch)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/errors-i-started-getting-with-145/)
 * Since the latest upgrade, I’ve been getting errors.
 * My error log is below
 * > [28-Jan-2014 16:23:06 America/Denver] PHP Fatal error: Call to undefined function
   > add_action() in /home4/riverbf7/public_html/wp/wp-content/plugins/wp-miniaudioplayer/
   > miniAudioPlayer-admin.php on line 5
   > [28-Jan-2014 18:50:42 America/Denver] PHP Fatal error: Call to undefined function
   > register_activation_hook() in /home4/riverbf7/public_html/wp/wp-content/plugins/
   > wp-miniaudioplayer/miniAudioPlayer.php on line 12
   > [29-Jan-2014 01:31:06 America/Denver] PHP Fatal error: Call to undefined function
   > add_action() in /home4/riverbf7/public_html/wp/wp-content/plugins/wp-miniaudioplayer/
   > miniAudioPlayer-admin.php on line 5
   > [29-Jan-2014 10:52:44 America/Denver] PHP Fatal error: Call to undefined function
   > register_activation_hook() in /home4/riverbf7/public_html/wp/wp-content/plugins/
   > wp-miniaudioplayer/miniAudioPlayer.php on line 12
   > [29-Jan-2014 14:41:16 America/Denver] PHP Fatal error: Call to undefined function
   > add_action() in /home4/riverbf7/public_html/wp/wp-content/plugins/wp-miniaudioplayer/
   > miniAudioPlayer-admin.php on line 5
 * [http://wordpress.org/plugins/wp-miniaudioplayer/](http://wordpress.org/plugins/wp-miniaudioplayer/)

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

 *  Plugin Author [pupunzi](https://wordpress.org/support/users/pupunzi/)
 * (@pupunzi)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/errors-i-started-getting-with-145/#post-4559669)
 * Did you try falling back to the previous version?
    Both the errors are strange
   as the called function is declared just above and you are the first who is getting
   this errors.
 * Let me know if that persist installing a previous version of the plugin.
 * Bye,
    M
 *  Thread Starter [Klatch](https://wordpress.org/support/users/klatch/)
 * (@klatch)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/errors-i-started-getting-with-145/#post-4559670)
 * The errors have stopped now. I didn’t roll it back to an earlier version either.
 * I’ve tried recreating the issue with no luck.
 * Thanks for the great plugin.
 * Just one feature request though. Custom color option. I’ve just been modifying
   your css with my themes colors.
 * Thanks
    James
 *  Plugin Author [pupunzi](https://wordpress.org/support/users/pupunzi/)
 * (@pupunzi)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/errors-i-started-getting-with-145/#post-4559685)
 * Hi James,
    is better not to modify the plugin CSS file as it will be replaced
   with the next update. You should overwrite the plugin CSS classes in your theme
   style.css; just copy the CSS classes of the skin you want to change from the 
   plugin CSS to the style.css and there you can change the values.
 * Bye,
    Matteo

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

The topic ‘Errors I started getting with 1.4.5’ is closed to new replies.

 * ![](https://ps.w.org/wp-miniaudioplayer/assets/icon.svg?rev=983692)
 * [mb.miniAudioPlayer - an HTML5 audio player for your mp3 files](https://wordpress.org/plugins/wp-miniaudioplayer/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-miniaudioplayer/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-miniaudioplayer/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-miniaudioplayer/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-miniaudioplayer/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-miniaudioplayer/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [pupunzi](https://wordpress.org/support/users/pupunzi/)
 * Last activity: [12 years, 4 months ago](https://wordpress.org/support/topic/errors-i-started-getting-with-145/#post-4559685)
 * Status: resolved