fob

The funny thing: I think it`s broken only in 3.x versions.

Unknown titles seem to be replaced by post numbers now, still linking to other peoples blogs. Stats are mixed up and broken in several blogs. ;-(

A bit strange.It works with a single picture but does not like to insert cbox element for gallery thumbnails anymore.

Deactivating cleaner gallery, tabs and social bookmarks did not help. So it`s hard to find the problem. ??

Urgs… well, the tabs seem to work. But thanks a lot. Will have a look at it tomorrow.

P.S.: Beste Grü?e zurück. ??

Too late?

Using Hybrid I would suggest to use a function within your functions.php.

First add an empty file your template folder (sub theme), nothing in. No code, nothing. Just give it a name like “no-comments-please.php” and upload it to your server.

After that you can add something like this to your functions.php in order to call the file when pages are called:


add_filter( 'comments_template', 'remove_comments_template_on_pages', 11 );

function remove_comments_template_on_pages( $file ) {
if ( is_page() )
$file = STYLESHEETPATH . '/no-comments-please.php';
return $file;
}

After that comments will be removed from all pages. If you like you can enhance the function to do whatever you want.

Best regards and happy christmas
Oliver

Seems to be a Twitter problem. Same issue with two client blogs and different plugin solutions. Updates stopped working a view days ago.

Update:

Interesting: https://www.google.de/webhp?hl=de#hl=de&q=twitter+tools+stopped+working

I upgraded today. Issues must be fixed with a small plugin provided by FastAgent (necessary since WP Version 2.2). It furtunately works with WordPress 2.7, too:

<?php
/*
Plugin Name: Smart Trailing Slash
Plugin URI: https://www.fastagent.de/
Description: Gives permalinks a trailing slash, but removes it in permalinks with a filename extension, e.g. .html
Version: 1.0
Author: Peter Claus Lamprecht
Author URI: https://www.fastagent.de/
*/

add_filter('user_trailingslashit', 'pcl_smart_trailingslashit');

function pcl_smart_trailingslashit($string) {
	if ( '/' != substr($string, -1)) {
		$string .= '/';
	}
	if (0 < preg_match("#\.[^/]{1,}/$#", $string)) {
        $string = rtrim($string, "/");
	}
	return $string;
}
?>

Sorry Ipstenu, may be this does not look very friendly. I also could have chosen another blog for my examples. Well – it is meant friendly. Thanks for your interest in this problem.

Let`s see:

This is my home: https://www.fob-marketing.de/
This is my blog: https://www.fob-marketing.de/marketing-seo-blog/

My categories are currently looking like that:
https://www.fob-marketing.de/marketing-seo-blog-kategorie/marketing/

Tags are looking like this:
https://www.fob-marketing.de/marketing-seo-blog-tag/seo/

Artcles (Permalinks) currently look like this:
https://www.fob-marketing.de/marketing-seo-blog/broken-links-checker.html

I decided to use this kind of links because of permalink trouble with WP 2.6. Actually I ran into Google Trouble with it although I made use of mod_rewrite to rescue things where possible. May be too much…

Testing WP 2.7 there seems to be a need for an additional fix because of not being able to surf on elder blog pages again ( example: https://www.fob-marketing.de/marketing-seo-blog/page/2/ which will not work with WP 2.7 anymore), just in categories, as long as I do not add something – e.g. the date or the post number – to the permalink string of my urls (in admin settings) what I definitely do not want!

It could be as easy as you said. But unfortunately it is not. If you do not touch your homepage settings things might be very easy. If you do so you may run into trouble sooner or later because permalinks (SEO URLs) and settings for categories and tags do not like each other anymore. The easiest way to find out if it works or not is to click on your blog and try to read elder posts. If you get an error 404 you know that it is time to update your permalinks again and write several mod_rewrite rules to redirect elder posts, archives, tags and categories to the new targets. Sometimes you redefine WordPress Rules or make use of a plugin to resque your permalinks. But the day will come where you give it up and accept the new rules…

I know that you will not have this problem if you use your blog itself as your homepage or if you do not try to make the best of URLs. Using a page instead seems to be a problem as well as German permalinks that never worked acceptable without a plugin to solve this problem.

I already upgraded several times (my own blogs and customer blogs, too) and so I know what I`m talking about. I had to change the permalink structure more than one time to make the things work as they did before.

.html -> Slash variant
root variant -> sub directories
…

and with 2.7 even the sub directories will not work anymore if I don`t change the structure again. Some things work other things do not. I can not live with those that would not work for me anymore…

Edit: It is much easier if you are working with a simple blog. If you separate blog and pages working with a template for your start page it is much more difficult since Filosofo Homepage Control (plugin) should not be used anymore.

Pretty cool. ??

I am a search engine optimizer. That is why I need the single pages for each photo. Still activated “Shutter Reloaded” for additional effects on single pics. If the plugin is not necessary anymore it could be deactivated without loosing lightbox or other effects that come from Shutter out of the box.

Thanks very much! ??

Okay. I found the problem!

WordPress has a function included called “wpautop”. This function still puts <p> tags wherever it likes and where you definitely do not like to see them.

I will kill this function for galleries now. The Gallery Validation Plugin Update will be available within the next five minutes. ??

I would love to know where exactly you get the p tag error from.
Is it behind the clear tag or somewhere else?

I checked my database: no <p> tag found.
I checked if it could be an editor problem
– seems not to be the case.
I stripped the content output – <p> not found.
I double checked including a few <p> and </p>
into the output to strip it with an additional
function – everything deleted but not the <p>
which is automatically set directly behind
the gallery output (in front of the clear tag).
I double checked my templates: everything valid.

No idea why I have to put the </p> into the plugin.

Because of that I will have to leave it like it is
until anybody has an idea why the gallery inserts
the <p> where nobody wants to have it.

Another thing I`ve seen:
I forgot to put my .clear class into the stylesheet.

I always use a clear class so that people might be
able to fix line-height and other things the IE
doesn`t like. May be you want to put it into your
stylesheet (if you didn`t do that already) so that
the floating stops behind the gallery pics.