texaun

Thanks for responding Frederick. I recognize that and maybe I need to clarify my question and correct “is_home_page” syntax to “is_home”.

I use WordPress as a CMS for some sites and the homepage is a static page instead of a posts page. For those sites, the homepage is “is_front_page”, but it is not “is_home”…see https://codex.www.ads-software.com/Function_Reference/is_front_page.

I assume W3TC provides a direct to “is_home” (i.e., the posts page) in the page caching option that prevents homepage caching, but I need it to provide a direct for “is_front_page”. Using “^/$” in the “never cache the following pages” box resolves the problem and a static homepage is not cached.

And now I understand cache duration for pages, etc. It’s driven by the cache control policy and header lifetime. Cache control policy set to “cache with max-age” and expires header set to 300 seconds does exactly what I was seeking…sets browser cache to 300 second duration and page cache to 300 second duration.

Through trial and error and “going back to Apache school”, I figured out the code required in the “never cache the following pages” settings box to not cache the home page when a site’s blog page (is_home_page) and front page (is_front_page) are different is:

^/$

FYI, it’s in the Apache mod_rewrite documentation at the end of the RewriteCond section.

I still hope someone can give me an answer on the garbage collection question…

Just talking to myself here in case someone else has a similar problem.

dTabs is the winner. Easiest to implement although not quite optimal…yet…need to wrestle with css just a little.

And that works!…just need to delete the following except the leading and ending backticks I included to indicate the space at the end of the string. Thanks much rosecitysister!

+ "' id='TB_FullSize' title='Full Size'>Full Size</a>&nbsp;&nbsp;"

P.S. Then I remembered our dog pedigree jpgs are 768 px tall so I can’t do this until I convert them to pdfs. But it may help someone else.

Case closed!

So are you all holding out on me hoping I get it? I’m getting there. I solved question #1. A style wasn’t activated at the style editor. When I activated the default style, wallah!, a pretty gallery!

That leaves #3:
How do I remove the “full size” link in thickbox? I format all my photos to proportionate size with maximum 480px height and 640px width. So there is no need for the full size link. I stared down some of the nextGEN files and the thickbox .js and .css files among other things, but they didn’t reveal the secret.

And, alexrabe assuming you may respond, I’m also implementing wordTube. Any chance of expanding wordTube to use the the JW WMV PLAYER or writing a new plugin to make use of it?

Nevermind on #2, that was too easy…I turned off “Activate permalinks” and that fixed that problem. But help on #1 and #3 are still greatly appreciated!

Bob

After taking a closer look, is it possible my server configuration is causing items 1 and 2 (as I see nextgen.boelinger.com has a non-default permalink structure)? Here are the server settings:

* Operating System : Linux
* Server : Apache
* Memory usage : N/A
* MYSQL Version : 5.0.45-log
* SQL Mode : Not set
* PHP Version : 4.3.11
* PHP Safe Mode : Off
* PHP Allow URL fopen : On
* PHP Memory Limit : N/A
* PHP Max Upload Size : 8M
* PHP Max Post Size : 8M
* PHP Max Script Execute Time : 30s
* PHP Exif support : No
* PHP IPTC support : Yes
* PHP XML support : Yes

GD support

* GD Version : bundled (2.0.28 compatible)
* FreeType Support : Yes
* FreeType Linkage : with freetype
* T1Lib Support : No
* GIF Read Support : Yes
* GIF Create Support : Yes
* JPG Support : Yes
* PNG Support : Yes
* WBMP Support : Yes
* XBM Support : Yes
* JIS-mapped Japanese Font Support : No

I’m having a similar problem. Pages coded before upgrade seem to play fine, but the embedded video icon is a no-show at the mce page and post screens…can’t add any new media.

Per JohnLamansky:

This is caused by the “Rename ‘Blogroll’ admin menu item to ‘Links’” tweak. Disable the tweak to fix the problem. (The tweak deals with a terminology issue in WordPress 2.3, so it’s not even applicable for WordPress 2.5.)

Thanks for letting me know! In the next version of the plugin I’ll either remove that tweak (since it no longer applies) or else make it clear that it’s only intended for WP 2.3.

Please ignore this post. Added a new one to tie it directly to the plugin.

nexenator, thanks for the alternate suggestion and tip on istylr.com.

Thanks much! I just modified to “height:100px” at #searchbar to get the whole graphic in plus the right amount of brownspace below the graphic…check it out at https://www.texaustralian.com/wordpress Looks great in IE and Firefox.