brightonmike

Then create a page, called Blog, and set it as the page WordPress should display the posts on. Then create a static front page, and set that as the page WordPress displays as the homepage.

The pages are mixed up probably because you haven’t followed this process correctly.

If the quality of your photos doesn’t matter, then stop uploading 10mb big pictures. That is just asking for trouble.

Think about it, if that 10mb image is viewed 100 times, you’ve used up 1GB of bandwidth.

You can’t just add .html onto the end.

Permalinks must end with a trailing slash – nothing else.

You’re closing the container before you include the sidebar. Therefore you need to remove the closing div tags for the div class “casing” from before the sidebar.php is called, and insert the closing div tag for the “casing” class to after the sidebar.php is called.

Presuming you’re using page.php, you need to look to where it’s calling your sidebar.php. There will be a closing div tag, which is closing the container. Move it to AFTER the sidebar is called. You’ll need to do this on all files that call the sidebar.

Can’t really explain it any simpler then that – so if you still have problems, it sounds like you drastically need to brush up on your front-end coding skills.

Gluck.

You’ll need to speak to your host and ask them to enable URL re-writing. As far as I’m aware, IIS does not by default allow this.

Give the menu links background via CSS. You can target different categories in the CSS, use your browser to look at your menu. You should then be able to see the category classes being added to your menu.

You can then target these in your CSS, giving them a background (the icons). To make the icon appear above the text, give the links top padding.

To change the backgrounds/colours on hover, use the CSS “:hover” selector.

Your English is very muddled up and difficult to understand which may be why nobody has helped you. But I’ll try.

If you have static text on the blog page, but you want that on the home page, then just remove it and add it to the static page you’ll be using for the home page.

You may have also not actually created a page to use as your static home page.

You need to move “class=”left” and all its contents inside the closing tag of the “casing” div.

At the moment, you’re closing the casing div before the sidebar, and as the casing is a container, it means the sidebar shows after the casing, rather than being inside it.

Where is your WordPress installed? If it’s in the root you don’t need to add in the index.php as the site URL.

Your links are dead at the moment anyway.

If you have the ability to do so (depends on your host), you can usually allocate more memory by editing your php.ini file. If you can’t consult your host – they may be happy for your site to access more memory if it’s currently set quite low.

What about server-side caching of results? For example if you had the results for the term “hello post” cached, it would serve up the cached page instead of performing an actual search.

If you’re worried about the user not finding fresh content, you can have the cached pages refresh – just not every single time somebody searches.

Have you tried the developer tools, either in FF or Chrome, to look at the code and try to find what’s causing the pagination to disappear? You should be able to find any Javascript errors, or strange CSS happenings.

Twenty Eleven is a responsive design, meaning its size and layout adapts to different screen sizes.

When you make a child theme, you need to take that into account and make sure your added styles do not cause issues. It sounds like this is what has happened, so you need to refine your code to make it compatible.

As for IE8, this is probably because you’re using CSS3 styles? As they are not supported by IE8. When using CSS3 if you want IE8 support, you made need to include a fall back. This can be in the CSS itself, or by using IE conditional statements.

If it’s nothing to do with CSS3, then it’s probably just because your styling has some errors. Code for browser compatibility from scratch, every single time you make changes check across the browsers to make sure it works.

Remove the “wordpress” from your URL. Just tried it myself and the login page loads fine. This is in Chrome too.

Sounds like a possible re-direct loop issue – but as above ^.