masonjames

I have a similar request. I really love this plugin, but would prefer not to have the script tags already included.

In my case, I want to load a tag with <noscript> in the body, but am unable to do so. Bummer because I actually prefer everything else about this plugin over other implementations. Would love for you to consider an option for scenarios like this.

Thanks!

Oy, that’s a lotta work for it to still not be showing 🙁

Is it possible the visual editor is disabled on your user profile? Log in, then go to Admin->Users->Your Profile and see if the box is checked for ‘Disable the visual editor when writing’.

If it IS, then you should uncheck that box. If it is not, well, you may need to look at reinstalling WordPress. You’d want to login via ftp and overwrite everything except your wp-contents folder and wp-config.php file to do that.

Hiya Jenny,

WPyogi’s advice above is good – though I know it’s frustrating to think about turning everything off and then back on again.

This error sounds like a javascript conflict. That’s normally the result of a wayward plugin or theme so deactivating them each one at a time should help you find which one is the culprit.

Another useful tool would be one like firebug, which allows you to spot errors that are loaded on the page and give hints as to what the root cause is. There’s a great writeup on Firebug here: http://www.studiopress.com/tips/using-firebug.htm

Hope this helps. Thanks!

Hiya,

That’s definitely odd. The main time we’d find that some folks see the site a certain way while others do not is either browser caching (clearing all browser cache and cookies is always a good start, then restart the browser) or when something has changed at the site’s DNS level. So, if you changed IP addresses, for example, this change can take a bit to propagate across the entire internet.

If there’s been any changes at the dns, you may try a dnscache flush (google this – it’s done differently depending on your OS) and seeing if that helps.

If it IS working for some folks and not for others (as seems to be the case here) that’d point to an issue with the hosting or registrar or local to certain folks machines – and not an issue with the WordPress software itself.

Oh, and I’ll change the category of this post for ya, no stress on that 🙂

Hiya,

When I go to your site, I get the cirtex welcome page. That indicates to me that while your DNS settings (at namecheap) are pointing to the right location, the site isn’t actually live in some way on cirtex.

Do they have a temporary location for you initially and maybe something you need to change in order to officially make the site live?

I’d say bring it up with the folks at cirtex as they can see more details and assist with getting this fixed up for you. Let us know how it goes for ya.

Hiya,

Normally when you get this error it means that something’s up with your wp-config file credentials.

Look for DB_Name, DB_USER, and DB_PASSWORD defines in wp-config and make sure those match what your actual database credentials are.

A quick way to verify would be to see if they match your old install (if there’s anyway to retrieve a copy of that).

Also, when you did the move did you make changes to the database so that everything points to blog.e3labs.org.

Here’s a tutorial a colleague of mine wrote up on how to do a database search and replace:
http://thewpvalet.com/blog/2012/08/16/heres-a-quick-way-to-search-and-replace-your-database-after-migration/

Let me know if that works for ya. Thanks!