TechGnome

did you try wp-plugins.net?

Search for Gravatar:
https://wp-plugins.net/index.php?filter=gravatar&filter_search=Go…

-tg

podz – that’s probably the coolest thing I’ve seen since Firefox on a stick….

kaf – hardy-har-har!

-tg

Personaly, I don’t see what the DNS has to do with anything.

If you are getting code, then the server isn’t processing the PHP correctly. You should not be getting the contents of the files, but the rendered HTML instead. Double check with your new host and MAKE SURE they support PHP.

-tg

I believe that WP uses the MD5 hash that’s built into mySQL… and it’s one way, which means there’s no way to de-hash it to the original text. However, if myBB is hashing its passwords too, odds are it’s the same method.

-tg

More often than not, this comes from the file (or the server) from not properly sending the right HTTP header and instead of processing the file, the server thinks it needs to send it to the client. You may want to contact your web host and see if there is something they can diagnose from their side of things.

In the meantime, Handy has the right idea, try disabling some if not all of your plugins and see if it still happens. It also wouldn’t surprise me if there’s something in common those posts have (a word, or some kind of misplaced code or something) in common even though you may not think about it at the time.

-tg

Actualy, it’s better to use & lt; (w/o spaces) for the < and & gt; — and it’s easier to remember: LessThan and GreaterThan respectively.

-tg

JUST make sure you use a DIFFERENT table prefix during the installation…..

-tg

michaelng – you can’t have it both ways. The reason for this is because WP stores the URL/URI in the database and uses that to build all the links and include files and such. So if you set it up so that you can view through localhost, no one out side will see it. If you set it up to use the dynamic dns, then it can’t be viewed as localhost. That’s simply the way it is.

In general, however, it’s not a good idea to be doing the tinkering on your live site anyways (all things being equal, something *will* go wrong.) What you may want to consider doing is creating a second WP installation that is linked to localhost (but uses a different database from your main site) and do your tweaking there. When it’s all set, simply copy the files from test to live.

-tg

It would also be nice if people checked back on their threads once in a while. I don’t know how many times I’ve replied to something… only to have weeks go by with no more word from the OP. Did it work? Did they resovle it themselves? Don’t leave us hanging! ??

-tg

Honestly, I don’t recommend deleting either one…. Search engines love that kind of stuff. Removing it may cause SEs to not properly determine your content.

But what you can do is change the CSS to use visible: hidden; which will keep the items in the code where the SE will pick it up, but render it invisible to the web browser.

-tg

Looks like this is fixed now. Marking as Resolved.

-tg

Cool, I take it that it works now. I’ll mark this as resolved.

-tg

Stop! Before you go any further hacking you files…. do this: Look in the theme folder of the theme you are using… is there a single.php? If NOT… then make a copy of index.php and rename it single.php. Then open it up and edit it. Change the_excerpt_reloaded to the_content() (again, make sure you are doing this in the single.php file NOT index.php.
Save it, upload it, and then try it again.

-tg

did you install the widgets code (not your widgets but the widgets engine itself)?

-tg

actualy it should only be in the index.php file of what ever theme you are using. If you replace the_content in any of the other files, you might get only the short version when you expect the whole post.

-tg