CSD_Images

Finally nailed the problem it comes down to the .media-item .describe th being set to 140px, over-riding this class for long field titles fixes the broken layout.

Not sure what the problem was, but the fault has cleared itself. I had done the CHMOD on the right path, as I’ve had to do it on other sites so I knew that procedure worked.

The only incident that could have been related was a database rebuild but I can’t see how that’d affect directory permissions, unless it never reset the warning message?

The matter is closed for now, thanks for the response.

That’s the problem, it conflicts with some of what I do with BuddyPress hence what I said. The old way it was clear and was easy to see. Now you have to either have to use the menu bar or click on your profile name.

Don’t get me wrong I do use the menu bar, but it’s a pain when you’re doing dev work as it can interfere with the design layout.

A plug-in can aid with SEO, but a site has to be built with SEO in mind. SEO is a multi-faceted topic, from intelligently marking up your copy text, to properly naming, tagging and titling your images.

The structure of your pages is also important to aid the bot around your site. The best way to visualise this is to switch off the stylesheets and you will see what a ‘bot sees.

The key thing to note is what makes a site popular in the search engines is content, semantically correct content to be precise. I’ve seen high ranking sites that have rubbish designs but great mark up under the hood.

WP SEO helps partially with this but it’s not a single click fix, no plug-in can do this. It’s the best on the market at present, and it’s increased footfall on the sites I managed over the traditional favourite AIO.

Look in the Themes header.php file and check the title meta-tags, some themes use non-standard tags and that breaks the Theme.

It’s a pain and you can try and force re-writes or create a child theme to change the header.php.

Yoast has a small bit of info in the plug-in about this.

Thanks for the reply, I’ll monitor the situation it just knocked out the scheduled posts. I’ve flagged the question as resolved at the moment until the next batch of scheduled posts.

Fancy permalinks: /%postname%/

This is a really bad idea:

https://digwp.com/2011/06/dont-use-postname/

Not sure if it will fix your problems, but it’s an additional headache…

Chuckle, it’s always the obvious problem that blind sides you.

It’s a useful tip to remember is that echo statement, it’s solved me a few headaches as well.

Another good trick to remember is to use the following declaration in CSS to determine if you’re targeting the right element:

outline: 1px solid red;

You can change red to green/blue depending on the theme, but stick that into the element declaration and it will show what’s being targeted where.

All the best.

OK this is weird, there’s nothing on that page that resembles the output.

here’s a quick tip. To ensure you’re loading the right page under the banner temporarily add a echo statement with a keyword that you’ll recognise.

Such as:

‘<?php echo “test” ?>’

Just stick this above the content declaration.

That way we can determine what page is being loaded, but I don’t think that one is being loaded.

Can you post the code for that page via pastebin?

Is your site built off one of the Grid frameworks? If so looking for CSS pseudo-structure in your files such as name:before and name:after where name is the element in question. I’ve seen this used in a few of them.

I had this problem I got round it two ways. I created a CPT archive page which is the format of archive-CPT name

change CPT to your post type and then set the loop query to post_type=CPT name.

So for portfolio you’d have

archive-portfolio.php

and your query as:

query_posts( ‘post_type=portfolio’)

Also make sure you refresh your permalinks, just saving is enough. As you need to ensure WP is aware of the CPTs.

I’m no expert at this but a bit of tinkering yesterday gave me the solution:

Performance: General

Under minify panel enable and set to manual, leave everything else as is.

Performance: Minify

You will see the option to clear cache next to this is the help wizard.

Click on this and choose the scripts you want minified. Then check the URLs as it’s only checking for links, not for files actual existence. This caught me out as one of my files as moved by accident on the server.

Once you have chosen your files and back to the Performance interface you will see your list of files, next to that you will see delete/verify. It’s here you will check for the files existence.

Alternatively you could add each script individually and test exhaustively.

How much RAM does your host allocate to your website?

You’ll probably need to up your RAM, ideally you should have 64Mb or higher available to WordPress depending on what functionality you have going on in the background.

I use TPC! Memory Usage to give me a quick overview of how much RAM the site is using.

I installed this yesterday and it’s not the easiest of plug-ins to do so. However for doing it made the site a lot more responsive. The main problem with this plug-in isn’t the plug-in but the web servers.

With this out of the way this is some notes from the field on how I got it to play nicely:

1) Add each function one at a time and test thoroughly on all pages.

2) Minify is by far the biggest gotcha, I couldn’t get it to play ball with my CSS so I manually minified the CSS before uploading a fresh copy to the server.

3) JavaScript seems to be a pain in some ways again I had to do this manually, again testing the functionality of the site. Not a major problem for me as I don’t have much JS yet, but the order of precedence was critical for other functionality.

In browsers whilst testing use privacy mode where possible, this means you see what the users see. You could disable the option to by pass admins but it’s easier to use the browsers private modes.

Overall it took me a couple of hours to install and configure the settings and do fault diags for weird cache issues.

Export your settings once you’ve finished and keep in a safe place…