dan.tee

OK – looks like it’s the Wrap/No Wrap option in the Column general options in Avada. Set the holding column that contains the Slider to Wrap and the anomaly appears. Switch it to No Wrap and it’s gone.

Ah – so this isn’t necessarily being written by AO? That hadn’t occurred to me. I’ll dig deeper. Thanks for your lightning fast reply!

Whoops! Will do ??

You sir, are amazing. Thank you.

No problem. I hope you get it sorted, and I certainly hope that there’s a little update on the way to sort this one out!

I should add that 775 is what my working folders were set to – whether it’s secure enough I can’t tell you, so it may be better to hear from someone who understands these things better than me before messing with your folder permissions too much!

OK, so I’m no uber expert either but I have managed to solve this problem on my own site. The issue appears to be that 3.7.1 has a problem in that new folders made for a new month to store uploads in are being given the wrong file permissions. This means that although WP can make the folder and put things in it, it can’t subsequently read the contents of that folder. So, change the permissions of the folder and bingo! WP can read the contents again. However, the problem simply returns at the start of the next month. I didn’t have this problem until updating to 3.7.1 and it’s reappeared like clockwork with December’s new folder being built incorrectly, following my fixing of November’s. I managed to fix both folders by using an FTP client (I’m on Mac, so used Fetch – I think Filezilla is the fave PC option?) to locate the folder and set its permissions to the same as all the others. The permissions have a cute three digit code to make it simple for us non-techies – WP was setting the folder to have 664 I think, which doesn’t work properly. Changing it to 775 works great. To do this with Fetch as your FTP program, you just navigate to the folder in question and right-click to see file info. At the bottom of the window is lots of tick boxes (don’t mess with these) just add the 3 digit code in the box. I can’t speak for FileZilla I’m afraid, but others may know? If using FTP is scary, don’t panic – all you’re doing is viewing your web server’s folder/file setup, just as you can view your own computer’s setup. You need your FTP address, your username and password. The folders you’re looking are for are in wp-content/uploads/2013/ – all new month folders (mine are called 11, 12 etc) had incorrect permissions and required fixing.

Easy. Go to search.php and find where it says something like this:
<?php include (TEMPLATEPATH . '/_/inc/meta.php' ); ?>
Either remove it or comment it out to check before removing. If you’re not familiar with PHP commenting, just put ‘//’ after the first ?php

Hope that’s what you were looking for.

the thing you need is float. This is the way to make objects appear next to each other rather than vertically. A suggested way would be this:

.image-holder {
float:left;
}
Anything contained within class=”image-holder” will now stack up to the right of the object next to it until they reach the edge of the container that they’re in.

Or you could add something like this:

.the-name-of-your-flex-width-div img {
float:left;
}

That way, any images inside your flexi div will float next to each other.

Hope that helps. Oh, and never use tables for anything but tabular data.

Well… the only thing I could find that was wrong was that I had the <?php wp_head(); ?> in my header twice (go figure?) SO i removed the extra one and the plugin worked again. But… that still doesn’t explain why it worked on one set of pages and not the other. But hey ho, it works.

To be honest, I never thought there was anything wrong with the plug-in – I just needed some help, as I know diddley-squat about php and even less about jquery.

Thanks for getting back to me though! ??

Dan

my problem is now solved

now works. working on another issue seems unwittingly to have fixed this one, which at least means it was my fault!

I know this is as cheeky as hell, but could you take a quick look at my site at https://www.danielcharlesphotography.co.uk/wp and perhaps have a crack at explaining why lightbox 1.2.2 works fine on all the gallery pages and the album pages, but won’t work on the about us page? I’ve even copied and pasted code that I know works in a gallery page onto the about us page, whereupon it stops working. The template used in both about us and albums is the same one so there’s no bits missing from the header or anything like that – at least I don’t think so!

I recently added a bit of code to my .htaccess file which solved a similar problem with the auto-upgrader not working with very similar symptoms. The code forces your server to use PHP5 instead of defaulting to 4. Here it is:
AddType x-mapp-php5 .php
Naturally, I offer no guarantee of success, not did I write this code. Add it at your own risk (if it doesn’t help, you can always take it out again)

HTH.