Edd Hurst

Sorry I meant to include an image:

Hi, just wanted to confirm – has this been rolled into 3.7.2?

If not – do we have a timeline on this release?

Many thanks!

This is great – can this be rolled out to master?

I regularly have this issue with there being too many theme files included, especially on themes that use a lot of shortcodes or pull in a lot of individual function files. Normally I just grab the UL and paste it into a text editor to read all the bottom files, but given that there is a solution, it’d be great to have this rolled into the plugin.

I noted that the click-trigger is different on the pro version than the free version. If you inspect the element for the 3-line menu you can see that the ID is not the typical #click-menu.

If you use #responsive_menu_pro_button instead as your trigger, that’ll open the menu as before.

Sorry, no dice.

Uploaded the github version but still get errors above each meta box (only as admin). Not the end of the world, but obviously better not to.

Very useful thread, thanks guys for all the grep commands. Caught a load of hacked files that have been hounding me for months.

I don’t imagine it’s the theme as it was worked up until about January. Could well be the old Gold Cart not working with a current version of WordPress though, I hadn’t noted that it was out of date as it’s a premium plugin and didn’t highlight itself. I’ll let you know if it doesn’t work.

Not that it makes a wild difference, but the shop is here:

https://bit.ly/1DXIyP4

Thanks

Hi Hilary,

The reason is because you have styled your CSS on the entry-content class, and not on the P element. Given that you have put your inline content tabs outside of the entry-content div, they aren’t picking up any styling.

Just add the following styles in to one of the inline element classes, and it’ll work exactly the same. Alternatively just style the P element, and it’ll work the same throughout the site:

color: #100404;
font-size: 16px;
line-height: 180%;
font-family: georgia,serif;
background-color: #F7F4EF;

Your code is fine, I think you’re just looking in the wrong place.

There is no tab, like in the main ‘Create Post’ section of WordPress, instead – there is a button to the left of the tinyMCE box which says “Toggle”. This will toggle tinyMCE on or off, to show either a textarea or a tinyMCE’d textarea.

If you enable htmlEditor (you have), the textarea will also include the basic html options.

Ahoy there,

I’m looking to do something similar to you as well, and it’d be great to check out your code to see if I might adapt it. I’m surprised they took the functionality out of WPMU when they brought it into WP Multisite – it always seemed like such a logical thing to want to do…

Regardless, any help your code might be able to provide would be awesome.

Cheers

for what it’s worth – you would retrieve those much the same as you would a normal custom field.

<?php
$slideshow_images = get_post_custom_values('Main Image', $post->ID);
foreach ( $slideshow_images as $key => $value ) {
	echo "<div class=\"slideshow-img\">";
	echo $value;
	echo "</div>";
}
?>

I can’t remember how cft outputs a file, but in theory that would work…

The easiest way for you to do this is to use the Multiple argument. This will automatically add an extra field to your set, so you will always be able to add more fields to your slideshow.

This is also a lot neater codewise.

example:

[Main Image]
type = file
label = Upload Main Image ( 940px by 280px )
mediaLibrary = true
multiple = true
multipleButton = true

“Multiple” will allow you to add more fields so that when you upload 4 and save – it will automatically show your 4 fields and 1 empty one when you next load the page.

“MultipleButton” will allow you to manually add more fields, if you wanted to add more than one at a time.

fieldset_close is perfectly valid.

I gave up on this as a solution, it seemed that just single fieldsets were buggy enough, without trying to nest them as well. Although it would be nice to see a way of making this work in the future.

Apart from the fact that this is 7 months old, I came across this page when I had the same problem.

What I noticed was that the owner of the site had decided that they didn’t want then twenty-ten theme, and seeing as that was the default theme, the blogs defaulted to using no theme at all, hence why I got a white screen – because there were no files for it to read.

To fix this, just go to Appearances and activate a theme for the blog. A long term fix would be to re-upload twenty-ten to the themes directory, even if you don’t actually use it anywhere.

This is quite interesting, I stumbled into this very same problem this afternoon but ended up sidestepping it completely and scrapping the concept of trying to make multiple arrays sit nicely next to one another and instead used a single textarea.

I think I’ll investigate this further and see what happens…