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)
629 responses
Other comment pages: « 1 … 7 8 9 10 11 [12] 13 14 15 16 17 … 32 »
I have patched your plug-in a little. I have added strip_tags() and htmlentities() to avoid troubles with special non-HTML characters. I have also added a word-based (please rewrite to regex) blacklist and minimum length for search words. The 2nd one was neccessary because someone did also always search for “None”….
Just to let you know it.
Thanks, Quix0r. The next update will have improved WP compliance along the lines of your patch.
To avoid confusion (and to comply with the GPL) you might want to add a note to your patch stating that you have made some changes.
Opps, okay will be done this evening.
And thanks for implementing my changes.
Getting a “Fatal error: Allowed memory size of xxxxxx bytes exhausted (tried to allocate xxxxxbytes) in /wp-includes/functions.php” when posting when Search-Meter 2.1 is activated.
Going back to 1.1 !
Potaje, that’s strange since Search Meter is not invoked when you create a post. I’ve never seen this problem before in any circumstances. If you have any more information on it, I would appreciate it — specifically, the WordPress version and the line number in functions.php. Thanks in advance.
I was surprised also. Didn’t really think that Search Meter was involved in posting. Then I started looking information about the error on wordpress.org.
I tried to save some more posts getting same error with different data sizes.
Search Meter was the only thing I changed yesterday just before save a post. So I went back to 1.1 and, by now, no error appears.
It was something like this:
Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 1388608 bytes) in /wp-includes/functions.php.
I’d say line 1288 but I’m not sure about it.
Sorry ….. Wordpress 2.0.6
Potaje, this does not seem to be a problem with Search Meter, even though the problem goes away when you go back to an earlier version. I know that there are problems with some versions of PHP that can cause this kind of error during database access. I might be able to work around the problem by changing Search Meter, but unfortunately I can’t do much more without knowing the exact line number in the error message.
THanks for the plugine. Helps a lot.
I cant donate but
I can help u in one more way.
Remove Images u have placed in front of Adsense. They are against google policy which they have chaned couple of days before
Thanks for the tip, Mukund. Actually Google has had this policy for a long time; they have recently clarified it though. It doesn’t apply to this website since I use Bidvertiser instead of AdSense. (The click-through rate is ridiculously low anyway.)
Bennett, I guess the “Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 111494 bytes) in /usr/local/pem/vhosts/11880/webspace/httpdocs/blog/wp-includes/functions.php on line 1228″ error has something to do with the USA HP proxy I’m going through.
So, thanks for the fantastic (and working) plugin.
Here again, testing and translating.
I realize a redundancy. In ‘Search Meter Options’ page, under ‘notes’ appears again “To manage your search statistics, go to your Search Meter Options page.”
As I did with 1.1 version, I’ve translated 2.1 to Spanish. May I offer it in my blog (after you check it)?
Thanks Potaje. I will check and update Search Meter when I have some spare time. In the meantime, of course you can offer your translation. I also have a plan to create an internationalised version of Search Meter to make translation easier.
Other comment pages: « 1 … 7 8 9 10 11 [12] 13 14 15 16 17 … 32 »