jhned

In addition to the debugging steps outlined above, I also turned on Debug mode and Development mode. Development mode did not product any information when I tested the login on the front-end. Debug mode gave me this result (I’ve removed my IP address from the logs for privacy):

s8jj6vrn936slu9mum6rqect54 — 18-09-2018 14:54:21 — Google — 0 — wsl_process_login — https://joincbr.com/rwh/wp-login.php?action=wordpress_social_authenticate&mode=login&provider=Google&redirect_to=http%3A%2F%2Fjoincbr.com%2Frwh%2F —
s8jj6vrn936slu9mum6rqect54 — 18-09-2018 14:54:21 — Google — 0 — wsl_process_login_begin_start — https://joincbr.com/rwh/wp-login.php?action=wordpress_social_authenticate&mode=login&provider=Google&redirect_to=http%3A%2F%2Fjoincbr.com%2Frwh%2F —
s8jj6vrn936slu9mum6rqect54 — 18-09-2018 14:54:22 — Google — 0 — wsl_process_login — https://joincbr.com/rwh/wp-login.php?action=wordpress_social_authenticate&mode=login&provider=Google&redirect_to=http%3A%2F%2Fjoincbr.com%2Frwh%2F&redirect_to_provider=true —
s8jj6vrn936slu9mum6rqect54 — 18-09-2018 14:54:22 — Google — 0 — wsl_process_login_begin_start — https://joincbr.com/rwh/wp-login.php?action=wordpress_social_authenticate&mode=login&provider=Google&redirect_to=http%3A%2F%2Fjoincbr.com%2Frwh%2F&redirect_to_provider=true —
s8jj6vrn936slu9mum6rqect54 — 18-09-2018 14:54:22 — Google — 0 — wsl_hook_process_login_before_hybridauth_authenticate — https://joincbr.com/rwh/wp-login.php?action=wordpress_social_authenticate&mode=login&provider=Google&redirect_to=http%3A%2F%2Fjoincbr.com%2Frwh%2F&redirect_to_provider=true —

I suspect that another hook was supposed to fire after “wsl_hook_process_login_before_hybridauth_authenticate,” but that’s as far as we got. I turned on WP_DEBUG to see if there was an error there, but got nothing.

You can email me at [email protected].

Thank you for this! I’ll put this together in a patch and put out a new release soon.

Hey @robtotw, I’d like to figure out the cause of this issue– could you give me a screenshot of what happens when you have the plugin activated? I think I know what you’re describing, but I haven’t run in to this issue myself on 4.7.1, so I’d like to make sure I know what’s happening first.

Nvm, it’s back now. Must’ve been a fluke.

Hey Kristian, thanks for the notification! I’ll need a bit of time to duplicate your setup, but should be able to get a fix for that in the next few days.

Hey Jacob,

We hadn’t really considered that yet. The way the search currently works is by matching post titles to the search query. Are you suggesting that the search could match custom field values, or custom field keys?

Either way, adding that kind of data to the search index would increase the cache size dramatically. However, we are planning on moving our search functions to use the WP REST API in the near future, so perhaps searching by custom fields in addition to post title could be a feature for when we work on that.

I’ve opened a new issue for this on the ACP Github repo, so if you have more comments/suggestions for us, feel free to add them there. Thanks for the idea!

Ok, nevermind. I did get it to work by using setup_postdata, but then I’d have to use it every time I used get_posts, which seems redundant.

I tried using do_action('the_post') instead of setup_postdata, but that did not work. Looking to find a way to make it more efficient.

I second this– I also need this plugin to work for custom post types, but it doesn’t right now. I can hack it, but it’d be nicer if the plugin would support this. You could do it by changing lines 105-107 to:

if( !post_type_supports($data['post_type'], 'author') ):
				return $data;
			endif;

Then why bother having an Autogenerate Descriptions option if the plugin is just going to generate a description regardless?

Lol, nope. Was kinda hoping somebody from the plugin would check it out.

Oh, really? I’ve been using the MP6 plugin, but I thought it was only for CSS modifications, not PHP modifications. I think I’ll probably just write a patch for it, but wanted to see if anybody else has tried it before first– from my research, it looks like it hasn’t come up yet.

Yeah, we kinda need to update this as soon as possible. I’ve had to comment in 2 plugin forums already as well, and I’m sure there are others out there that are using “live.” This is probably causing a lot of hair-pulling right now.

Hey Arne,

There is a pretty big problem with the jQuery– the current version of jQuery has dropped support for “live,” which the Colorbox uses. Using the option in the plugin fixes it, but it would be nice if it worked with the current version of jQuery as well. Think you could throw together a quick update?

Ok, fair enough.

I was just hoping that by posting this I could get the ear of whoever’s in charge of the Media Library. I have a lot of ideas for that section, and I was a little irked that it seemed like I was just being told to take a crack at it myself, so that I’d go preoccupy myself with that and quit whining about it.

I’ll take a look at it, but I honestly think that there’s somebody else who knows a lot more about it than I do that would be able to figure it out a lot faster than I could, and code it a lot better to boot.

Would that somebody please stand up?