These are some readers' responses. Read the full article to see what all the fuss is about.
-
Popular
Categories
- .Net & C# (1)
- Architecture (3)
- C++ (5)
- Coding (4)
- Copyright, etc. (3)
- HTML/CSS (2)
- Java (14)
- JavaScript (6)
- JUnit (3)
- Recommendations (10)
- Risks (8)
- Software projects (2)
- SQL (4)
- Testing (6)
- Tools (5)
- Usability (2)
- Web (5)
- Web publishing (16)
- Windows (1)
- WordPress (27)
42 responses
Other comment pages: « 1 [2] 3 »
Thanks for this - it took me a month or so until I noticed the bug but it took only about 3 minutes to find your solution to it.
Thanks very much for this fix.
Green Harbor MA Captain’s Log
First, thanks for the great plugin. I’ve got it running on two of my WP 1.5.2 blogs.
I’m working on a new one that’s using WP 2.0. Is this plugin still necessary, or did the bug get fixed?
Looks as if it’ll be fixed. The comments for the relevant WordPress bug report say that the problem will be fixed in the next release — that’ll be WordPress 2.0. I’ll update this page once the new WordPrreess is officially released and I can confirm the fix.
Will there be a fix/upgrade for the new Word Press 2 template? I don’t want to upgrade to the new version until I know this plug-in is working fully for it.
Great plug-in and thanks.
Vinnie, It looks as if WordPress 2 has been fixed so that Fixback isn’t necessary. I’ll confirm that once I have tested WordPress 2.
Thank you for being generous with your resources… I hope that you will receive more than you need for your time and energy. Keep at work!
Sweet, thanks a ton Bennett for posting a link to the bug report. Just applied the patch to my 1.5.2 install and fixed the problem.
The necessary plugin (:
It is established easily and perfectly works.
Thank u so much!
Other comment pages: « 1 [2] 3 »