Laer

[Late Addition} As I suspected, the child theme is partially to blame. I had increased the letter spacing of the site title (so it extends past the sidebar’s right edge)… and it seems the theme splits the display up, cropping the part of the title that extends.

I now just realized that the three lines are in fact a compressed menu, and that the ‘missing’ menu items are in there, instead of on the top menu.

With the theme modifications off (child theme off) I can better see what the theme is doing, as far as adjusting to the iTouch/iPad screen.

Okay, I think I got this figured out. The widening of the site name at the top left caused a bunch of elements to get pushed around and misaligned. Shrinking the title down has made everything fall back into place.

Any comments or words of wisdom are still welcome, though…

Ugh… As is seemingly traditional for me, I discover the answer literally seconds after posting on a forum!

For those of you wondering, there are discussion settings (as well as other settings) on the Edit page that may be hidden by default. Just go to the Screen Options tab at the top right of the screen to reveal a checklist allowing you to hide/display each section. To remove the comment field put on a page, just uncheck the Allow Comments item in the Discussion section.

Yes, you’re right. That seems to work. Thanks.

I think it has to be on the same level as the target script, but I’ll try that out, thanks.

Got it working now. I had to add an additional .htaccess file within the Captcha folder that contains this whitelist code:

<Files securimage_show.php>
allow from all
</Files>

This addresses the securimage_show.php script not being accessable due to the global Deny All coding higher up in the directory structure which protects the other plugins.

Thanks for your input, mbrsolution!

@mike: I’ve now managed to get input from a few people, including mbrsolution (above). Each snippet of code they have provided may be a solution, however since I’m not well-versed in that sort of coding, I can’t really tell what each example does. Each snippet I’ve received is different from the others, so I’m not sure if one is better than the other, or if any of them would even address the matter, so it’s hard to say. I have to read further on this, using some of the links some of the people provided.

Taking out the .htaccess would solve it, but I DO want to block access to the other plugins for security reasons. I’m surprised the whitelisting isn’t as easy as the global block (Deny All).

Seems like if you wanted to whitelist an IP, you would do with this:

allow from 29.xxx.xx.xxx

But, I don’t know how you would code it for a file.

The .htaccess file in my wp-contents has the following code, which seems like it might be the culprit (…I’m not a programmer, so I’m just making an educated guess here):

<Files *.php>
deny from all
</Files>

Could I add anything to this to make an exception for your contact form plugin?

Hi, Mike. Okay, so what do I need to look for and what can I try?

I know that there was some manual .htaccess modification on my part for security reasons. What needs to exist for the contact form plugin to be happy?

Actually, mine was working again a little later in the day yesterday, just on its own.

Do they check these forums for bugs/issues, or is there some other official way to report them?

Ah, okay. So, I’ll just wait it out then. I thought it was the favicon, as I just put that in last night.

Okay, thanks for the news!

Cheers!

Yep, that would work. I guess there’s no way for the stat counter to know that it’s you until you log in, so I guess that’s the only way to do it.

Thanks Simon