wagonlips

This code works equally well to limit the number of tags displayed in the cloud with only minor changes:

add_filter('widget_tag_cloud_args','set_number_tags');
function set_number_tags($args) {
$args = array('number' => 20);
return $args;
}

Thanks, alchymyth

Ok, thanks.

Thanks, esmi. I can see from the number of posts you make that you’re very busy, and I appreciate your taking the time to look at my problem.

So, the thing I want is the Post Thumbnail feature. The way Mark Jaquith described it here. It may be that in 3.0.1 it’s being referred to as the “Feature Image” function now, but it’s not working the same way, at all.

Do you think you can help me figure out how to make it show a thumbnail in the loop but the full image on a single page?

Thanks, esmi. I’ve actually installed fresh completely clean installations of WordPress, so as to eliminate any possibility of random plugins (or anything else) from being involved. Although, I did just now increase the memory_limit in the php.ini to 64MB, just to give it a shot. But sadly, no change.

It’s looking, to me, like the functionality changed between 2.9.2 and 3.0.1, with the “Post Thumbnail” feature being renamed “Featured Image” and not really being a thumbnail feature at all anymore.

Unless, do you have Post Thumbnails working in 3.0.1?

To experiment, I downloaded and installed WordPress 2.9.2 and, like magic, the thumbnail feature appears just like all those people said it would.

The weird thing is that everything you’re supposed to do to make it work appears to have already been done in the TwentyTen theme. But I’m seeing nothing.

Oy, according to this thread, which points to this post, getting those thumbnails working again is going to require some hacking.

Third!

I have a clean installation of Twentyten 3.0.1 running and thumbnails are simply not showing up. I’ve read Mark Jaquith’s post on WordPress Thumbnail Images and Matt Brett’s post on WordPress Post Thumbnails and Matthias Kretschmann’s post on Using The New Post Thumbnail Feature and tried to follow the instructions as closely as possible, but the Post Thumbnail box is not showing up in the editor.

I’ve tried it with other themes, too. Not sure what the problem might be or how to track it down. Just getting nothing.

Further investigation reveals…
By simply printing out the contents of the wp_cycle_images array print_r(get_option('wp_cycle_images')); I discover that the thumbnails all come out looking like this: [thumbnail] => Object id #189
which is why the URLs are being truncated and why the image filenames aren’t showing up in the admin screen.
Now I just need to figure out what is causing that and/or how to fix it.

Although, I still see no image path or filename in the wp-cycle file upload screen. Confusing, but not a deal-breaker.

I am having a similar problem. Using the shortcode in a page [wp_cycle] truncates the image paths so that they look like this in the markup…

<div id="rotator">
<a href="#"><img src="/wp-content/uploads/2010/08/" width="395" height="202" class="20100826210544" alt="" /></a>
<a href="#"><img src="/wp-content/uploads/2010/08/" width="395" height="202" class="20100826210611" alt="" /></a>
<a href="#"><img src="/wp-content/uploads/2010/08/" width="395" height="202" class="20100826210654" alt="" /></a>
</div>

Not sure why. But I wonder if the filenames also not showing up in the plugin’s upload screen is related.

Hmm… it looks like Erica got it working on her site. I wonder if she’ll come back and share the fix.

Moments later… I noticed _wpnonce in the markup for the wp-cycle config page and that made me think about the keys and salts. Turns out that, although I had copied the database from the live version of the site, I had neglected to also copy the wp-config.php files at the same time to my local dev server: different keys and salts. Copied the keys and salts from the live site to the local, and now it’s working!

Cheers!

This is pretty cool, SpankMarvin. Couple things… the attributes don’t seem to do anything. I can change them to whatever but the only effect I see is fade and the rate never changes. Also, if first item could show right away, instead of waiting for a transition, that would be very cool. And to make it work I had to do it slightly different than your example directed.

[jdscycle id="optional-id" attributes="timeout:50, fx:shuffle"]
<a href=""><img src="/wp-content/uploads/2010/08/slideshow-01.jpg" /></a>
<a href=""><img src="/wp-content/uploads/2010/08/slideshow-02.jpg" /></a>
[/jdscycle]

The [item] tags just show up in the body of the page so I deleted them.

Cheers!

Because the designer wanted one of the words in the title to be bold and the other normal, I placed <strong>tags</strong> around the word in the actual page titles like so “The <strong>Story</strong>“. It worked. But now whenever someone hovers over the link the tooltip shows the entire title without interpreting the strong tags.

Based on Ivovic’s suggestion, this is what I did and it’s working for me. Of course, if your server *does not* support glob this will not work. And aside from trial and error, I’m not exactly sure how to tell if your server does.

// Header rotation script based on suggestions found in this thread: https://www.ads-software.com/support/topic/169209
$backgrounds = glob('/var/www/html/somecrazyblog.com/wp-content/uploads/header-images/*.jpg');
// Glob seems to need the full path to the target folder. Site root just wasn't working.
shuffle($backgrounds); // Shuffle the folder contents.
$string = $backgrounds[0]; // Pick one image.
// Now delete the parts of the path before the site root.
$pattern = "@/var/www/html/somecrazyblog.com@";
$replacement = "";
$newString = preg_replace($pattern, $replacement, $string);
// And finally output the styles needed to place a background image in the header.
echo "<style type='text/css'>\n";
echo "#header {background: url('".$newString."') no-repeat top left;}\n";
// Obviously, if your header doesn't use "header" as its CSS id, you will need to change that.
echo "</style>";

This goes in the head of your header.php file.

Cheers

Thanks Otto. Do you have any idea why, when using Litespeed, WordPress parses the URL and fails to figure out where to go? (Whereas the same setup on Apache just works.) Do you think the rewrite rules are actually *not* the problem? And if not, then what?

The problem I’m having is that while this set of rules works like a charm under Apache, it behaves a little too free and easy under Litespeed. Meaning:

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

…will rewrite absolutely any string at all as a directory and then slap index.php on the end of it. The actual 404 never gets served.

Very puzzling.

I don’t know about simple terms, but here’s the doc page from apache: https://httpd.apache.org/docs/1.3/mod/mod_rewrite.html and here’s a little more info also from apache: https://httpd.apache.org/docs/1.3/misc/rewriteguide.html

My interpretation of that code is:
RewriteEngine On
# Wake up the rewriting elves!
RewriteBase /
# Start with the server root.
RewriteCond %{REQUEST_FILENAME} !-f
# If the request is for a real directory (one that exists
# on the server), index.php isn’t served.
RewriteCond %{REQUEST_FILENAME} !-d
# If the request is for a file that exists already on
# the server, index.php isn’t served.
RewriteRule . /index.php [L]
# This is the rule that corresponds to the above two
# conditions. I think it will put /index.php on the
# end of any request that does not match the conditions.
# I think.

Actually, the answers for the %{REQUEST_FILENAME} bits I copied from this thread over here:
https://forum.mamboserver.com/archive/index.php/t-42366.html

This is pretty confusing stuff. Here’s a little more info in regards to permalinks: https://codex.www.ads-software.com/Using_Permalinks but I’m still trying to research some weird behavior with this exact set of rules, but using the litespeed server software.

Like a dinghy afloat on the sea of life.