Thread Starter
Cruz0r
(@cruz0r)
I forgot to add that this means that I can’t edit the project(s), only open new ones.
Update to version 1.1.2 (I just released it) and let me know if that fixed it.
Thread Starter
Cruz0r
(@cruz0r)
It didn’t – still doesn’t show projects.
Furthermore there seems to be a bug in the new version as I got:
Warning: fopen(/home/urdland/public_html/wordpress/wp-content/plugins/bugerator//bugerator.css) [function.fopen]: failed to open stream: No such file or directory in /home/urdland/public_html/wordpress/wp-content/plugins/bugerator/bugerator.php on line 4398
Warning: filesize() [function.filesize]: stat failed for /home/urdland/public_html/wordpress/wp-content/plugins/bugerator//bugerator.css in /home/urdland/public_html/wordpress/wp-content/plugins/bugerator/bugerator.php on line 4399
Warning: fread() expects parameter 1 to be resource, boolean given in /home/urdland/public_html/wordpress/wp-content/plugins/bugerator/bugerator.php on line 4399
Warning: fclose() expects parameter 1 to be resource, boolean given in /home/urdland/public_html/wordpress/wp-content/plugins/bugerator/bugerator.php on line 4400
when opening the ‘CSS/Display changes’ page. I had to manually rename bugerator-default.css to bugerator.css.
CSS: In the past I would only copy over the css file once so that if a person edited the css that the changes would stay put regardless of updates. This worked in the past but it appears that in one of the recent releases of wordpress the plugin directory files all get deleted on the update. I’ll have to research this and figure out how to deal with it. I don’t want to overwrite the default each release but if I have to I’ll include a warning in the upgrade notes and hope for the best.
As for editing projects – there are two places where these should be visible. Inside the settings of the dashboard and on the administration tab on the front end. Are you trying both?
The swirly graphic is in place while I make an AJAX call to the server. When it disappears the browser has received a response one way or the other. Is it being replaced by a 0 or is it just blank all together? Do you have any plugins that change the way that wordpress handles AJAX calls? My call names are unique (bugerator_ajax_…) so they aren’t colliding but something could be changing the behavior.
I may need to send you a new bugerator.php file for debugging so we can try to find out what is going on with your install. Who are you hosting with and what version of PHP are they using?
Since you’ve seen the swirly graphic appear and disappear I’m going to assume it isn’t your browser but you may want to try a different browser anyway just for kicks. I’ve tried multiple browsers but something could be goofing with how your browser deals with AJAX calls and javascript.
I can’t duplicate the show project problems on my test server or production server so we need to work together to figure out what is going on.
Thread Starter
Cruz0r
(@cruz0r)
Gotcha @ CSS.
Both dashboard and on front page have the same issue. The ajax response, according to the debugging information, is empty.
The only active plugin is a twitter feed plugin, I just tried deactivating it but it doesn’t make a difference. I’m hosting the website on my own server – PHP version is 5.3.4.
I don’t think it’s the browser, as I tried both Chrome and Firefox.
Thanks for pointing me in the right direction with the bugerator.php file, I’ll try to fix the bug myself. Way easier than bouncing back and forth. Will let you know when I’ve found it (hopefully!) or if not 🙂
Thread Starter
Cruz0r
(@cruz0r)
OK, I think I’ve got it narrowed down quite a bit.
This is buggy:
static function get_project_list() {
.....
$bugerator_project_display = get_option("bugerator_project_display");
$sql = "SELECT * FROM $bugerator_project_table ORDER BY FIELD(id,$bugerator_project_display)";
.....
The SQL is invalid, which causes nothing to be displayed. The actual SQL is SELECT * FROM wp_bugerator_projects ORDER BY FIELD(id,,1,2)
Notice the ‘,,1,2’. If I manually change the value of $bugerator_project_display to ‘name’, it does work. I have no idea what the right value should be but I’m guessing you do 🙂
K found it. The option bugerator_project_display was creating a new project as “,1” so instead of being 1,2 it was ,1,2.
To fix: Easy destructive way: 1- Upgrade to 1.1.3 first (Just released – I fixed the uninstall to delete the option in question). 2- Uninstall bugerator. 3- Reinstall bugerator and start over.
Or – the harder non-destructive way – in the {wp_prefix}options table find the bugerator_project_display option and change it from ,1,2 to 1,2. You still should update to 1.1.3 since I found another minor thing to fix but this will fix your database.
Also figured out the css – just need to overwrite it so backup changes before upgrading. This will always be the case so I’ll add that note with the upgrade notices from now on.
Thanks for your help. Let me know how it goes.
Thread Starter
Cruz0r
(@cruz0r)
Seems to work!
I did run in to some other bugs though.
If you try to delete a 2nd (only tried 2nd) project, the bugerator_project_display variable is emptied, which causes no projects to be displayed again 😛 If I set it to ‘1’, it will show both 1 and 2. Is there a way to really delete a project?
Small typo – somewhere in the front-end I saw ‘Update Successfull’, should be ‘successful’ with 1 ell. (When changing status of a bug)
Another small issue is the warning message when changing a bug status in the ‘list issues’ page:
Warning: array_search() expects parameter 2 to be array, null given in /home/urdland/public_html/wordpress/wp-content/plugins/bugerator/bugerator.php on line 3852
. This occurs once per selected bug to be changed.
The whole CSS editing thing has some room for improvement, why not have a textarea where a user can put custom CSS which is displayed in-line, and stored in the database? To have bugerator look good I need to tweak stuff that doesn’t fit in the ‘edit CSS’ backend options because I need to change ‘h1.bugerator’ for example, this is not a predefined editable class. Storing it in the database also solves the overwriting while updating issue.
Hope I’m not being annoying with all the bugreports 😛 Your project looks good and even in the current state I’ll be using it, it’s easy to use and many similar plugins demand coins for the feature Buginator offers!
You’re fine. You make a good tester.
K – css stuff – I’m in the “is it worth the trouble of removing the code for it” stage. Feedback has told me people who know css will just edit the css file. So I’m kinda inclined just to leave it alone for now and maybe actually remove it some day.
Array search is fixed. It is checking for email subscribers to the project and you have none so it was a null array. Its checking for that now.
Spelling is fixed. Thanks. That’s one of those words.
I’ve sent the updates to the svn trunk and my git. I’ll roll a new version in a few days (depending on if you find other bugs.)
Oh the delete – K I’m an accountant by day. The accountant in me hates the thought of data disappearing. So projects don’t exactly get “deleted” per say. I guess I could add a purge. As it is the deleted projects do not show up on the front facing project selection but only on the admin show projects and (hopefully) at the bottom of the list. So if you add a new project it should appear above the deleted one.
Although if you really want it gone the table is {wp_prefix}bugerator_projects. Just delete the row. It won’t hurt anything. If the time comes when db size or something causes a good reason to purge it I’ll be happy to write that in.
Thanks again.
Thread Starter
Cruz0r
(@cruz0r)
Nope, found no further bugs 🙂
