mikecherim

Great job timjamz. Thanks for posting this.

*bump* again. Still unsolved.

You should make a plugin Rich ??

*Bump*

I do offer two accessible themes (see my blog’s sidebar), but I don’t plan to release this one as a free theme. Too much work to give it away.

Sorry.

In your CSS you probably have something like.

blockquote {
  text-indent : 20px;
}

Remove the text-indent part of set it to 0.

Anyone? Anyone at all. I really just need some ideas and possible places to look.

You should be able to disable the add-on and be done with it. But if you can’t.

You might be able to remove it by removing the applicable application data for your user on your machine (Windows). To find out what to remove, though, you will have to contact the maker of the add-on.

Mike

Comments on “Pages” aren’t typical but would be accommodated on the theme level. But I must ask, why would you want to allow comments of your about page? It’s not typical because it would be a strange practice (IMO).

Mike

@lenky: What jonimueller said is the proper answer. Don’t invite your plugin’s user to abuse their power because they won’t know better. You, on the other hand, now have that insight so you can choose to do the right thing and now do know better.

Good options plus bad options does equal more options, but as long as bad options are in the mix, more is not better.

Hi Lenky,

The target attribute is deprecated and it’s a bad choice to use it. If people want to open a link in a new tab or window they can, but if you force the issue they can’t override your choice. I prefer the choice left up to me. Recommendation: Remove the target attribute (as well any script used to trick the validator into letting it slide). It’s a bad practice.

The p tag is allowed within the li element, which is a child of the ul. It is invalid to place a ul within a p tag. Recommendation: produce only valid, semantic mark-up (you don’t put lists in paragraphs). One oversight on your part destroys the validity of 100s, possibly 1000s, of blogs.

As far as the source scripts, I haven’t looked at the plugin (just explaining what Natalie pointed out), but it sounds like you have script on your domain required to use your plugin. If that’s the case it consumes your bandwidth, slows processing for the user, and if your server is down (or the URL changes), the user is SOL.

Hope this helps.

Mike

Hi Rhian. That shouldn’t be a problem that I’m aware of. It seems to be checking for that default Kubrick theme header stuff, but I don’t know why the function would be undefined.

But, glad it’s working ??

Hi Rhian, as Otto noted, wp_head() is a hook to allow plugins and whatnot to insert code into the head. The link to the form styles weren’t there because wp_head() wasn’t present to allow that. I would urge you to contact the maker of the theme as nobody else should be better qualified to help. It seems to me it’s definitely a theme problem since you’d isolated it by deactivating the plugins.

By the way, if you want to fix that date function snippet, it should look like this:

<?php echo date('l d Y'); ?>

I would also encourage you to clear your error log, load the page so it goes blank, then check what’s in the error log. It may very well point to the corrupt file and code line.

I’ve been told the DB tables need to be cleared with any UTW entires and then all will be cool.

Thanks all!

@micharo: I did use wp_list_pages() and aside from the blog part of it used Pages. I used the loop for the content as is normal for a Page Template (create in Write, Page). I did made a about five templates for this site though for some odd ball stuff like blog archives, site map, contact page. Regarding the nav, I did post some info on the site for the tech-minded ??

@evenglen: It can be a bear indeed ;o