hedronist

I just took a quick look in Windows FF 7.0.1 and Chrome “14.0.835.202 m”, and I don’t see anything I would describe as pixelated. Try looking at your page in FF and Chrome on a Mac, and then try IE/FF/Chrome on a Windows machine. If they aren’t all identical then what you are seeing may be browser-induced (but don’t ask me how).

Oh, and it’s normally not a good idea to restart a thread that is 10 months old; just start a new one, they’re free!

To get back to work it sounds like you might need to change the DNS servers your desktop/laptop is using. Try setting the servers to 4.2.2.1 and 4.2.2.2, which are publicly accessible servers maintained by Verizon.

Note: even if this solves the problem for you, it doesn’t deal with the problems with OpenDNS. Can’t help you there.

It’s not “illegal”, but it certainly is not very nice. So go ahead and delete the code in the plugin. There are worse things out there than a few “display:none” links, but in general you should always take a look at themes and plugins you get before just blindly activating them on your site.

BTW, you don’t say what plugin contains the code shown or where you downloaded it from — both are useful to help other people avoid this type of thing.

It’s generally a bad idea to hack code you are not maintaining yourself, because that means that you now get to be the maintainer.

Look at the the HTML source of the generated page and see what CSS classes and/or ids are being used for the elements that were emitted by the shortcodes. Then in your style.css file add rules to modify these specific elements.

Not as simply as using the border attribute. One way is to insert an <div class="fancy-border">&nbsp;</div> between each post and then style that with a background with a url() value of the image and using appropriate repeat for x/y. You can do something similar with the <hr> tag. There are other ways, but you need to check them in each browser you plan to support.

You’ve run into a fundamental bug in the shortcode parsing code. You could try to deal with this by using float:left and float:right on associated classes of the shortcode-generated items, but this is (at best) a hack. Someday this will be fixed in the core code … but don’t hold your breath.

Try adding the following to your CSS for class .hentry

.hentry {
...
    border-bottom: 1px solid #000000; /* adjust color to taste */
    padding-bottom: 10px; /* to move it away from X Lovely Little Notes */
...
}

This is just a guess, but you may have a plugin that is in some sort of intermediate state after the failed upgrade/downgrade. You might try moving all of your plugins to another directory (say xplugins/) and then see if you can get into the back office. If that works, then move them back into the plugins/ directory one at a time and see which one makes things blow up. Good luck.

Well, I guess you’re welcome.

However, considering that the vast majority of the people that read posts on this site a) have nothing to do with WP releases, b) don’t know you from Adam, and c) are here only to offer their free support … considering all of that you might just want to stuff the attitude.

Supplying a link always helps.

My first guess is that you may be inserting images that look like they are 300×200 (or whatever), but the actual image file being loaded might be more like 3000×2000, which is then down-scaled by the browser.

In Firefox, right click on an image and choose Image Properties to see if this might be happening. Another avenue of attack is to install Firebug into FF, go to the page in question, hit F12, click on the Net tab, and then do a Shift-Reload of the page. It will give you all sorts of interesting timing info on the page load.

In your style.css file there is a rule h2.title. Try adding margin-top: 15px; (or whatever) and see if that helps.

By embedded I meant using <style> ... </style> in-line, rather than loading an external CSS file. You may do this yourself or it may be done by a plugin. For example, the twenty ten weaver theme (a child theme of 2010) allows a large number of style adjustments and implements them by embedding a <i>large</i> block <style> information at the front of every page. (Something which I’m not too wild about.)

Ah! You’re correct. I was not paying attention.

I shoulder-surfed up the path and https://www.friendsofgoldbutte.org/wp-content/gallery/ also returns 403, but (as expected) https://www.friendsofgoldbutte.org/wp-content/ does not.

A 403 might indicate a .htaccess problem. Another possibility is that there is a symlink (symbolic link) in the path and that those are not permitted by your hosting service.

@chooseamac:

a) you should start a new thread, not restart one that’s a few weeks old.

b) I looked at your site and all of the thumbnails + main images in the gallery are 404 (page not found). So either the URL was correct, but the images were not/could not be created (probably a permissions problem, see above), or they were created, but not in the directory referenced by the img tags (configuration / programming error). They are all of the form:

https://www.friendsofgoldbutte.org/wp-content/gallery/february-2011/thumbs/thumbs_dsc_3874.jpg which links to
https://www.friendsofgoldbutte.org/wp-content/gallery/february-2011/dsc_3874.jpg

I would go looking for those files. They might be somewhere else below wp-content/gallery, in (or below) wp-content/uploads, or maybe somewhere below wp-content/themes/rttheme13/. If you can find them, then it’s either a configuration problem with NGG, or it’s a programming error.

OK. Let’s take this conversation to email (because I hate the editor in these forums) and we can post the final answer back here to finish this thread out. Contact me at peter at techbuddy dot us