jtwg

Do the detection client-side instead.

Awesome. I’ll be trying this out today.

Cheers!

OK, I tried a second time and that worked.

Thanks for the prompt responses!

OK, I got 1.5.1-alpha from github, now I get this error:

Warning: require_once(/home/****/webapps/****_com/wp/wp-content/plugins/wp-posts-to-posts/scb/load.php): failed to open stream: No such file or directory in /home/****/webapps/****_com/wp/wp-content/plugins/wp-posts-to-posts/posts-to-posts.php on line 17

Fatal error: require_once(): Failed opening required ‘/home/****/webapps/****_com/wp/wp-content/plugins/wp-posts-to-posts/scb/load.php’ (include_path=’.:/usr/local/share/pear54′) in /home/****/webapps/****_com/wp/wp-content/plugins/wp-posts-to-posts/posts-to-posts.php on line 17

Hm, no difference I can see. Still getting the same error.

This is the error I’m seeing in the logfile:

2013/02/17 05:48:50 [info] 10439#0: *17191091 client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: 76.102.231.80, server: foo.****.com, request: “GET /wp-admin/plugins.php?action=error_scrape&plugin=posts-to-posts/posts-to-posts.php&_wpnonce=77462a5a2b HTTP/1.1”, upstream: “https://127.0.0.1:80/wp-admin/plugins.php?action=error_scrape&plugin=posts-to-posts/posts-to-posts.php&_wpnonce=77462a5a2b”, host: “foo.****.com”, referrer: “https://foo.****.com/wp-admin/plugins.php?error=true&plugin=posts-to-posts%2Fposts-to-posts.php&_error_nonce=77462a5a2b”

Disregard due to PEBCAK.

Thanks for the response. I missed that setting.

Thanks for the reply, scribu.

Question for you: I have a table full of already established connections – will your plugin update those rows to add the connected_type if I provide it in my connection registrations? Or will the connections need to be re-created?

This is a problem I’ve run into a lot, needing to re-establish already present connections to provide missing values in the new fields.

Please advise, thanks.

P.S. agree with Dave about that I also don’t want to complain too much, for the same reasons he cites. I love this plugin, and use it on a great many sites. It’s incredibly useful. Semantic versioning and more explicit changelogs would definitely make it even more useful because the broken backwards compatibility really causes a lot of problems on production sites.

Good point. Didn’t think about the indexing.

Thanks for the response. I guess I will see if this winds up being an issue. ??

On edit: interestingly, when I updated to 1.1.5, the column size remained at 32.

It seems it should be much longer than 44 characters. If you have verbose naming conventions, 44 is still quite short. Why not make it something like 128?

I had to roll back to version 0.6.

Nope. This is broken. I’m having the same problem.

No box showing up for me either.

Still problematic.

I had a similar problem to the above. I was registering the taxonomy in its own function inside a class that I instantiate on init and the Order fields weren’t available. Pulling the register_taxonomy out into functions.php solved the problem.