Title: Plugin Buggy
Last modified: July 24, 2019

---

# Plugin Buggy

 *  Resolved [phylogram](https://wordpress.org/support/users/phylogram/)
 * (@phylogram)
 * [6 years, 10 months ago](https://wordpress.org/support/topic/plugin-buggy-3/)
 * This Plugin triggers a lot of errors, which causes the folders not to load, or
   the affects the whole upload media choosing functionality of wordpress.
 *  Here are some errors from debug.log:
 * PHP Notice: Undefined index: label in [wordpress]/wp-admin/includes/media.php
   on line 1844 – like a million times
 * PHP Notice: Trying to get property ‘term_id’ of non-object in /kunden/551541_1140[
   wordpress]//wp-content/plugins/filebird/admin/class-filebird-admin.php on line
   130
 * which seems to be triggered by a sql-error.
 * My error-log is full, it is unreadable.
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fplugin-buggy-3%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

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

 *  Plugin Author [Ninja Team](https://wordpress.org/support/users/ninjateam/)
 * (@ninjateam)
 * [6 years, 10 months ago](https://wordpress.org/support/topic/plugin-buggy-3/#post-11768285)
 * Hi [@phylogram](https://wordpress.org/support/users/phylogram/)
 * Have you upgraded FileBird to the latest version 2.3?
 * If yes and still have issues, please install “Health Check & Troubleshooting”
   and give me your site info, I will help you check it.
 * Tommy
 *  Thread Starter [phylogram](https://wordpress.org/support/users/phylogram/)
 * (@phylogram)
 * [6 years, 10 months ago](https://wordpress.org/support/topic/plugin-buggy-3/#post-11768464)
 * Hi [@ninjateam](https://wordpress.org/support/users/ninjateam/), hi Tommy,
 * thank you for your reply. Unfortunately this was an expression of opinion, not
   a support question. I am sorry, if this seems rude, but I thought if you are 
   going to sell premium / pro plugins, you might want to be informed.
 * If I use your plugin for a client – and this will mean PRO is unavoidable – I
   need it to be trustable. I do not have time to check the whole thing for security
   wholes. Basic SQL-errors give me an headache (this is even just MySQL). This 
   may be neurotic, sorry, but wordpress allows badly written plugins.
 * To answer your questions:
    1. **No, this has not been not the currently latest version (2.3)**. I had installed
       it before the upgrade. However, this seems like an error, you should find and
       fix before publication, so I went for a different solution.
    2. PHP-error-messages seem to be quite sufficient to understand the cause of the
       error. I have not reviewed the code however. So I am not going to install the
       plugin you recommended, because I can read php-error-logs.
 * I appreciate, that you put the effort into providing the free part of your plugin.
   However, for providing professional services, I need a certain standard of coding.
   Debug.log should not be filled with hundreds of error messages for a every-day-
   task / the main functionality of a plugin.
 * Thank you for your time and effort. I hope your last update did solve the problems.
   By the way, sorry for my English – I am not a native.
 * Philip from [@phylogram](https://wordpress.org/support/users/phylogram/)
    -  This reply was modified 6 years, 10 months ago by [phylogram](https://wordpress.org/support/users/phylogram/).
    -  This reply was modified 6 years, 10 months ago by [phylogram](https://wordpress.org/support/users/phylogram/).
 *  Moderator [Jan Dembowski](https://wordpress.org/support/users/jdembowski/)
 * (@jdembowski)
 * Forum Moderator and Brute Squad
 * [6 years, 10 months ago](https://wordpress.org/support/topic/plugin-buggy-3/#post-11768494)
 * Side note to phylogram You don’t have to @ the author, you definitely do not 
   need to @ yourself. The spam filter thought you were spamming likely for that
   reason.
 * > thank you for your reply. Unfortunately this was an expression of opinion, 
   > not a support question.
 * Um. OK? Thank you for writing that?
 * These are support forums, not a blog or discussion forums. Do you have a problem
   that you want the volunteers (that includes the author, they’re volunteers too)
   to help you with?
 * That’s an honest question.
 *  Thread Starter [phylogram](https://wordpress.org/support/users/phylogram/)
 * (@phylogram)
 * [6 years, 10 months ago](https://wordpress.org/support/topic/plugin-buggy-3/#post-11768626)
 * Thank You for your reply. I checked something like “that’s not a support question”.
   I hope, that I did not cause any inconvenience.
 *  Plugin Author [Ninja Team](https://wordpress.org/support/users/ninjateam/)
 * (@ninjateam)
 * [6 years, 10 months ago](https://wordpress.org/support/topic/plugin-buggy-3/#post-11769945)
 * Dear Philip,
 * We try to provide the best plugin version each time it is published. Since different
   site uses different theme and plugins so a conflict may happen. Please update
   the plugin to the latest version, we hope it does not cause any error on your
   end. If you get any problem, please explain it and provide error log so we can
   help you fix it.
 * Best regards,
    Kelly

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

The topic ‘Plugin Buggy’ is closed to new replies.

 * ![](https://ps.w.org/filebird/assets/icon-128x128.gif?rev=2299145)
 * [FileBird - WordPress Media Library Folders & File Manager](https://wordpress.org/plugins/filebird/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/filebird/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/filebird/)
 * [Active Topics](https://wordpress.org/support/plugin/filebird/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/filebird/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/filebird/reviews/)

 * 5 replies
 * 3 participants
 * Last reply from: [Ninja Team](https://wordpress.org/support/users/ninjateam/)
 * Last activity: [6 years, 10 months ago](https://wordpress.org/support/topic/plugin-buggy-3/#post-11769945)
 * Status: resolved