BackpackersUnion

Hi @vibethemes

Thanks for your offer to help! I’m currently utilizing another option, so no need to debug further. I’ll remove my review so it doesn’t discourage others from testing out your plugin.

Thanks again!
Carl

I just shot you an email.

Thanks Shane!

2. Exactly. I like the Identicon idea, but it’s just not right for my site and it seems with the current setting you can’t get one functionality without the other.

I’m currently trying to troubleshoot a problem with the way Social Login profile pictures are handled and it seems as though the way BP Local Avatars handles Gravatars may solve it.

Would you be willing to modify BP Local Avatars to work with a Social Media Login plugin? And How much would you roughly charge for customization?

We may have to take the conversation over to Philopress but thanks for you help as always!

-Carl

Hi Scott, same issue here. The error is along the lines of:

[Sat Jan 21 23:36:01.256961 2017] [:error] [pid 897] [client IP-ADDRESS] PHP Fatal error: Class ‘WPSS_Utils’ not found in /nas/content/stage/account/wp-content/plugins/wp-spamshield/wp-spamshield.php on line 7323, referer: https://websitename.com/../../network/update-core.php

It happened in the staging area, so I pushed a new copy to the staging. Then once I updated Spam Shield, the site crashed again with the same 500 error.

Let me know if any another information is helpful. Thanks!

-Carl

Hi @waltmesser and @danieliser

Thanks for your response!

I did test the CSS class with a period (i.e. ‘.permclose’), but didn’t have any luck. This 20 year cookie is behaving like a Session Cookie that resets when the browers is closed (‘Use session cookie?’ NOT checked in options).

I did look at the advanced targeting controls, but aside from finding something that Popup Maker can target during account activation (Some unique Query String, A Referrer URL unique to activation?) I’m unsure how to trigger the popup early then prevent it from opening again once the user permanently dismiss it.

I suspect the solution may require writing something to the database that indicates the popup has been permanently dismissed on a per user basis (Outside my expertise).

I know this isn’t currently a feature of popup maker, but does it sound possible? There are no other popup plugins that do this, and because most BuddyPress users have registered accounts, it would make popup maker incredibly flexible.

Thanks again!
Carl

Just an idea:

Would it be possible to hook into some action that occurs at account activation (to open the popup)? I figure there must be some condition that could trigger the popup window when a new user first logs into their account using something like bp_core_activated_user (Guessing)?

If a condition could be set that only happens when a user first registers, then setting a cookie to prevent it from opening again could be avoided.

I’m speculating quite a bit, but let me know if there is anything that could be tested. Thanks!

Hi @waltmesser

Thanks for the detailed response!

For #2, the permanent close button, I wasn’t able to get it working.

The CSS Class I created for the close button is: permclose
Cookie Name: pum-598

So, the code I added to my child theme function.php looks like:

add_action( 'wp_footer', 'my_custom_popup_scripts', 500 );
function my_custom_popup_scripts() { ?>
<script type="text/javascript">
	(function ($, document, undefined) {
		$('permclose').click(function (e) { $('#popmake-598').trigger('pumSetCookie'); });
	}(jQuery, document))
</script><?php
}

*I also tried ‘pum-598’ in place of ‘#popmake-598’, with no luck.

Settings:
Manual JavaScript Settings: name= pum-598, Use Session Cookie= No, Cookie Time= 20 years, Site Wide Cookie= Yes.

Button Short Code= [popup_close tag="span" classes="permclose"]No Thanks[/popup_close]

Trigger= Auto Open, Cookies= pum-599, pum-598, Delay= 0

When “No Thanks”, the permanent button is pushed, it’s behaving like a Session cookie, so closing the browsers and logging back in reopens the popup.

Are there any other combinations I could test?

Also, is the Manual JavaScript Cookie unique to the BuddyPress User (So, logging in on a different computer won’t trigger the popup once the permanent close has been pushed on another device?) or is the cookie device/browser specific?

Thanks again for your help on this! Let me know if any addition information is needed.

Carl

PS: I just noticed a second <?php at the very end as well as a ?>. I’m not sure if they were intentionally added so I tried removing them with no luck (White screen of Death). The function.php does already have the <?php , ?> Thanks again!

Hi @lukecavanagh

For #2, I’m looking for the ‘dismiss’ to last forever (i.e. the life of the users account). So, the dismiss could be years.

The idea is to create a “Welcome / Getting Started” popup message. Once the user reads and ‘permanently dismisses’ the message, the user shouldn’t see the message again.

Any ideas on how this might work?

Thanks Luke!

Hi Libin, looks like the update worked great! Thanks for your help and support!

Good point! It could take me a few days to make the changes and watch the logs for the error, so I’ll mark this resolved for now. If it ends up not solving the Error I’ll just open a new thread.

Thanks again for everything, Jeff!

All the best,
Carl

Sorry, I hadn’t refreshed the page to read your last comment. I will do!

Thanks for sticking with me on this one ?? !

I just checked the client IP Address associate with the Error and it looks like it came from China, possibly a Baidu search engine spider: 180.76.15.145 (The Chinese search engine I believe).

Is it possible the crawler was trying to extract data from the GA code and asked for an incorrect option? I’m 90% guessing, but figured it was worth an ask.

You are correct, it is a Multisite install with “GA Google Analytics” Network Activated. Should I deactivate network-wide and then activate individually?

It looks like gap_options is present in the wp_options table.

The search populated 1 gap_options result within the wp_options table, followed by the GA tracking code and other "gap_ " related code.

Does this sound about right?

Thanks for the quick response!

I’m not very well versed when it comes to working with the DB, so I did a search through the DB for gap_options and returned 4 results referencing it.

Is there a better way to properly confirm gap_options is where it needs to be?

Sorry for the learning curve on this one.