dansgirl165

I switched from MT to WP about a month ago, before the recent licensing issue.
I ended up going with WordPress because:

• No rebuilds
• The community and the developers. When something seems to be wrong or a bug is found, they fix it right away. Also, I was very impressed with the fact that they did communicate and did come here to help the rest of us out. ??
• The Typekey issue (I moved from Blogger because of having to depend on another server or service to post and when they were down or my comments server was down, nobody could use it. And I was not all that keen on having people have to register with a service they might not want to register with to leave a comment on my blog. Also, at the time, the rumor was that the Blacklist was going to be obsolete and there would not be a new one, but that rumor has been dispelled after I made the switch. I think the solutions that WP has for comment spam are pretty good and much simpler than having to use Typekey.)
• My wanting to get a sense of PHP and wanting to learn more about it.
• Just the fact that this program is so simple, but yet it does everything I want it to do.
• Server space. My old MT blog took up a lot of space on my server. MT grew to become more complicated than it really had to be, IMHO.

When I was looking into WP, the only disadvantage I found was not having multiple blogs on the same install. But there were so many advantages, that I decided that not having multiple blogs on the same install was something that I could live with.
I have been nothing but happy since I switched over. My husband took a look at WordPress after I got it up and running and was so impressed with it, he made the switch, too.

Thanks! ??

It’s under “My Profile” in the control panel. It’s at the bottom. ??

You’re welcome. ??

On the very first line, take out the space between the ? and the “php” part. I had the very same problem you had and once I took that space out, that fixed my problem. ??

I had the same problem when I tried installing “wp-grins”. I couldn’t figure out what was causing that error and it was driving me up the wall.
I did manage to figure out what the problem was. In my case, it was whitespace, but not whitespace before the <?php and or after the ?>. I had a space between the question mark and the php part of it. For some reason, when I went to the Wiki to see the instructions on how to create “my-hacks.php”, I somehow saw a space in between them. Once I took that space out, everything worked fine.
Don’t know if that will help you, but I thought I’d throw it in here. ??

Sorry, I haven’t gotten back to this. I was sick last week.
Anyway, yes, that’s the code from the wp-grins.php file. I did notice that after I downloaded it, all the code went for two lines and there were those boxes that Notepad sticks into a file to represent whenver someone hit “return”. So I got rid of those and made everything be on the lines they were supposed to be. That didn’t work. I’m still getting the
Parse error: parse error in /home/assorte/public_html/blog/my-hacks.php on line 2 message.
I only get this when I put the code you have to put into the ‘my-hacks’ file. I copied and pasted it and this is the code I’m supposed to put there.
<?php require_once('wp-grins.php'); ?>
This is what’s on line 2.
I’m working off the assumption that ‘wp-grins.php’ is supposed to be uploaded into the root directory, because I don’t remember seeing anything written as to where this file should go. I uploaded it and ‘my-hacks’ into my blog’s root directory.

I’ve got “my-hacks” enabled, and I uploaded it into my blog root directory. I uploaded just the file without the wp-grins code and that gives me no errors, so I know there was no whitespace where there shouldn’t be whitespace. It’s when I include the code for wp-grins is when I get the error.
I copied and pasted the code and I also tried it with typing the code exactly as it was written in the readme file, but I’m still getting this error.
My husband just asked me if maybe this hack wasn’t compatible with the version I’m running. I’m running 1.02.