sam_a

Another fix ?? https://gist.github.com/2484129

Yes, I see this too in WordPress 3.3.2 + Custom Post Type UI 0.7.1 on admin.php?page=cpt_main_menu:

Uncaught TypeError: Object #<Object> has no method ‘delegate’ common.dev.js:140
(anonymous function) common.dev.js:140
(anonymous function) common.dev.js:389
Uncaught TypeError: Object #<Object> has no method ‘delegate’ wplink.dev.js:427
River wplink.dev.js:427
wpLink.init wplink.dev.js:26
n.extend.ready.n.readyList jquery.min.js:19
n.extend.each jquery.min.js:12
n.extend.ready jquery.min.js:19
n.each.n.fn.(anonymous function) jquery.min.js:19

Try https://www.ads-software.com/extend/plugins/wp-leads-mailchimp-constant-contact-and-salesforcecom-integration/ — it should do the registration integration, though not the access control.

This plugin seamlessly integrates the WordPress registration and commenting processes with the web’s most popular lead management tools, such as MailChimp, Constant Contact, and SalesForce.com

After the plugin is installed – Users can instantly join your mailing list(s) while registering with or commenting on your site. Their information is automatically sent to one (or all) of the Lead Management Systems above – MailChimp, Constant Contact, and SalesForce.com

In Chrome, at least.

I finally found the problem, in the theme stylesheet:

table { table-layout: fixed;}

Removing that declaration fixes it. Weird.

I also see the “Uncaught TypeError…” in WordPress 3.3.1 + SimpleFields 0.4:

Uncaught TypeError: Cannot read property 'canvas' of undefined (quicktags.dev.js:550)
	qt.closeAllTags (quicktags.dev.js:550)
	switchEditors.go (editor.dev.js:31)
	simple_fields_metabox_tinymce_attach (scripts.js:53)
	[…]

For those seeing TinyMCE/WYSIWG failures: try opening your browser’s console and look for javascript errors there.

@babypress, More Fields uses WordPress’s own post metadata, so you use the get_post_meta function with the key you set when creating the field.

Advanced Custom Fields has worked fine for me in 3.3.

Hi Mikko,

Around line 2006 in relevanssi_build_index(),

$custom_types = ""

is overwriting the value set earlier (around line 1988) when the public types are fetched.

Here is a diff: https://pastie.org/2827788

Hi Mikko,

Thanks for replying.

With What to include in the index: All public post types selected, posts from my public custom type don’t appear in the wp_relevanssi table. When I re-index with What to include in the index: Everything, they do appear.

(Also, when Relevanssi is deactivated, my public types appear in search results as intended.)

I’ll see if I can debug anything more… S

Is there any way I can use the front-end WYSIWYG editing mode and still keep the paragraph tags?

I just need a way to prevent FEE from doing a reverse-autop before saving, I think…

Got it, thanks.

I’ll see if I can escape based on the $type parameter if my filter function…

I’ll try it —?thanks.

I had a similar issue where all of the Media Tags interface seemed to disappear after upgrading the plugin, in both WordPress 3.1 and 3.2.

I deleted the media-tags-version option and re-activated the plugin and that seemed to fix it, oddly enough.

@max_q: I also see “Reject reason: Requested URI has a trailing slash” in the page cache debug message for my home page using 0.9.2.2 (my permalinks lack trailing slashes).

I think this is a new bug that came with a new feature — instead of rejecting all URLs with a trailing slash, 0.9.2.2 caches only URLs that match your permalink structure (i.e. with or without a trailing slash). It should skip that check for the home page URL (/), which always has a trailing slash.

What happens?

I noticed this too.