Mike Walsh's random thoughts and musings …
Posts tagged Bugs
WordPress Google Form plugin v0.16 released
0This morning I uploaded a new version of my WordPress Google Form plugin. This update addresses the three items I noted in this post. I also expanded the Test Bed Form I have been using to develop and test the plugin. If you’re curious, I have added the form to a page on this site. If you run into a combination that isn’t working and I haven’t accounted for it in the test bed, please let me know and I’ll update my form.
I think I finally have Check Boxes working correctly. They were a challenge because how PHP (which WordPress uses) pass arrays of information and Python (which Google Forms use for processing) are very different. Thanks to a tip on the WordPress Hackers Mailing List to a utility called http://httpbin.org I was able to get my plugin to pass the parameters as Google expects them and everything seems to be working correctly. The update should appear in your WordPress Dashboard fairly soon.
wpGForm Bugs in v0.15
1112 days
I have been alerted to a couple of bugs in the current (v0.15) version of wpGForm that I am working on fixing.
- Select boxes do not retain their value when going back on multi-page forms. I’ve already fixed this problem in my development build.
- Check boxes are not passing their values correctly.
- Sometimes Radio buttons do not retain their values when going back on multi-page forms.
This third item is proving difficult to track down. It is odd that some questions with radio buttons work fine going back and forth between pages but others do not. If I can fix the check boxes this morning I will likely release an update that addresses the first two bugs and keep working on the third problem.
WordPress Google Form Settings Bug
0250 days
The WordPress Google Forms settings page makes use of tabs to show information about the plugin and set its options. It appears that the theme I was using, which I am in the process developing, is the culprit. It loads some new jQuery functionality from Google’s API that apparently allowed the tabs to work as I expected. I am not sure yet why the builtin WordPress jQuery functionality isn’t working correctly as I expect it should.
Now that I know where the problem is, I think it should be pretty straight forward to fix it.
WordPress 3.0 upgrade not so clean
0688 days
by Mike Walsh
in WordPress
I updated WordPress to 3.0 the other day and surprisingly, had quite a few problems. In particular, the LifeStream plugin doesn’t seem to be very happy. The update process for WordPress itself failed once but succeeded when I ran it again. I had to actually delete LifeStream and re-add it and even then, it wasn’t quite happy. The updater never returned but WordPress seems to be operating ok. This is the first time in 4+ years of using WordPress that I’ve run into anything like this. Hopefully it will not be a big issue as I have a number of sites I need to update.
wp-SwimTeam v0.2.488 – bug for scratches
702 days
There was a bug in the scratch process where if you started on the Meets tab when the Scratch action was selected, there was not a list of swimmers presented for the user to scratch. When starting on the Roster page and selecting a swimmer to scratch did work properly. The bug has been fixed and v0.2.488 is now available for download and both paths, starting with a meet or starting with a swimmer, now work correctly. The same bug would have affected Opt-In meets as well.
Early WordPress 3.0 testing
753 days
WordPress 3.0 is expected to be out sometime in May. I figured I ought to do some basic testing to see if changes to WordPress would have any significant impact on wp-SwimTeam.
I have a Linux Virtual Machine which I have set up such that I can always run the bleeding edge of WordPress – right out of the Subversion repository. When a new version of WordPress is ready to come out I update my Linux VM with the current state of WordPress and the current state of wp-SwimTeam and run some tests.
I started doing this a couple weeks ago and got busy and never finished it. This morning, I got back to it. It turns out, it didn’t run very well. Both wp-SwimTeam and phpHtmlLib plugins were calling deprecated WordPress functions. In releases prior to 3.0, there were no warnings about calling a deprecated function but 3.0 has a new warning feature. The way it is implemented, the warnings actually caused a failure with phpHtmlLib which resulted in WordPress not successfully loading.
I have fixed the problems in both plugins and committed the changes. However, I have not released new builds yet so until I do, I advise sticking with the 2.9.x release of WordPress. I expect a new build later this week at the latest.
wp-SwimTeam v0.1.456 now available
758 days
by Mike Walsh
in wp-SwimTeam
Quick turn-around on a release as there was a bug which was really bothering me. The Opt-In/Opt-Out report was pulling swimmer label from the active season regardless of which season a meet was created against. This was fine for the current season but messed up reports from any prior season.
The report now pulls swimmer labels from the season that the meet is created against so looking back a a report from last season or two seasons ago will still show correctly.
wp-SwimTeam v0.1.455 available
758 days
This afternoon I posted v0.1.455 of the wp-SwimTeam plugin. This release fixes a bug with Active vs Inactive swimmers. This bug manifested itself in incorrect generation of Roster Reports and CSV Exports. A couple other minor issues were also corrected.
Current Known Issues
760 days
Here is a list of known issues with the current (v0.1.450) release:
- Roster CSV export does not work. Fixed in v0.1.455.
- Scratch/Register lists all meets instead of only meets for active season.
- There a couple of debug strings still displayed. Fixed in v0.1.455.
- Global Update does not include Status.
- Scratch and Registration reports look at current season for swimmer labels instead of the season the meet was created for. Fixed in v0.1.456.
Roster Report Bug
761 days
by Mike Walsh
in wp-SwimTeam
There is a bug in the Roster Report CSV export feature. The exported roster will not contain any swimmers. The HTML report is fine, only the CSVExport is affected. I will try and fix this in the next day or two.
Recent Comments