Palpatine1976

Sorry! Not sure what your page is doing – but if your ‘more fields’ plugin is displaying ALL the custom fields, it’ll show the custom field “custom_post_template” and its value. This is probably because the custom_post_template doesn’t start with the _ character… I wouldn’t recommend changing plugin code because it will get overwritten with the next update.

+1

Here’s the issue and the bugfix for @shazdeh :

Issue:
——
$this->template is not HTML-class-safe (it contains a period because it is pulling the PHP file name

Fix:
—-
Replace body_class() fn on line #56 of init.php with:

function body_class( $classes ) {
	$template = sanitize_html_class( str_replace( '.', '-', $this->template ) );
	$classes[] = 'category-template-' . $template;
	return $classes;
}

Nevermind – I discovered my parent theme was overriding the body_class hook.

I also see that this plugin doesn’t add CSS classes to the body tag – your download link seems to be broken. Could you please clarify the bug fix?

Thanks!

Update: I have found the issue – it’s due to the parent theme (Thematic) hooking wp_title() with the same priority at EC.

I’ve always had this issue with EC (and the Pro version) – and it is still present in the latest version (2.0.9).

The HTML document title (the string in the <title> tag) always takes the next available event title instead of copying the standard “Upcoming Events” text, when viewing the Upcoming or Calendar views. It seems like this is a bug – could anyone else comment?

I found the filter to alter the PAGE title, but as of yet not one to hook into the <title> string.

Thanks!

I’m not sure if this is what you guys are looking for, but EC provides a filter to set the page title that you can override in your functions.php:


function childtheme_get_events_title($content) {
if (tribe_is_upcoming()) {
$content = 'Some Upcoming Title';
}
else if (tribe_is_month()) {
$content = 'Some Calendar Title';
};
return $content;
}
add_filter('tribe_get_events_title', 'childtheme_get_events_title');


This PAGE title is NOT the same thing as the HTML DOCUMENT title (i.e. the string in the <title> tag) – I’m still searching for a solution to the issue of the next Event populating the html title.

@ann Pierson
It may be old, but still helpful – thanks! Confirmed the fix seems to work in WP 3.4.1.

Would be nice if the plugin author could comment on the hook and why it’s in there – but I agree it doesn’t seem to mess anything else up that I’ve found.

Thanks!

For custom styles, activate the plugin, go to the Styles tab and add a custom CSS stylesheet (using the absolute URL). Or you can add declarations directly into the options screen, but obviously the CSS sheet is a better approach.

It says you can upload to WP and it’ll scan/find it, but I just uploaded it to my theme folder and entered the full URL. (https://example.com/wp-content/themes/theme-name/css/sheet.css or whatever)

Seemed to work for me – but yeah, it sucks that Kavin’s site has been down for weeks.

Great! Thank you for being such a responsive developer – you’re a credit to WP ??

@anmari

Hi there! Thanks for the follow up on this. I can however confirm this is a bug in amr-users. If you check out the steps below, you should be able to recreate it:

* Completely clean WordPress 3.3.x or 3.4 install
* No other plugins or customization
* Install & activate amr-users
* Create say 6 dummy user accounts ([email protected], [email protected] etc.)
* Go into Admin screen -> Users -> Users: Details report
* Set results per page to be less than the total # of dummy users (so say 4)
* Enter search term “test.com”
* It will show 4 of the 6 records, and show a “Next” button (and a Page 2 button)
* Click either NEXT or Page 2.. you’ll see the querystring now reads “test-com” – and no records are returned

Again, this bug only happens when you paginate to pages of results. The initial view is fine. I bet if you created a bunch of test account in your link in your post, and clicked “page 2” it would do the same thing.

Hopefully it’s not a tough bug!

I was finding the same result, but I think the issue is that WP stores the ID of the original image as the Featured Image… but you CHOOSE the size of image you want to pull back & display, by specifying the size in the get_post_thumbnail_id() function. (2nd parameter)

I’m having the same issue with the settings not sticking on Twitter Widget Pro. Lame!

Nice trick indeed – hopefully the plugin author can make a working 0.8 version!