joegomez17

I had an immediate need for a fix to this, so I hired a developer to create an additional plugin that let anchor links work behind age-gate.

Regards,

Full disclosure: I’m not a developer. But, I’ve tried something like this in a custom plugin to try and set the window location after the “Yes” click, but the same problem exists. The console echos the hash, but window location is never set.

(function($){
  $(document).on('agegatepassed', function () {
        let hashjump = location.hash;
        console.log(hashjump);
        window.location.hash = hashjump;
  });
})(jQuery);

If I run this manually from the console after the age-gate Yes button, the window is set.

(function($){
let hashjump = location.hash;
console.log(hashjump);
window.location.hash = hashjump;
})(jQuery);

Any help? Its as if the page has to be fully loaded after agegatepassed in order to run the function above.

OK, I’ve resubmitted this through the form on the nsp-code website.

Autosort: Yes
Send new items to bottom: No

Hi planettao,

I was running on a hosted environment (Linux), but I came across this for Windows when troubleshooting —

Try this solution by fredwen:
https://www.ads-software.com/support/topic/ldaps-failed?replies=6

If you are on Windows,
1. create C:\OpenLDAP\sysconf\ldap.conf (Yes, it MUST be this path because it’s hard-coded in the dll)
2. put this line at the top:
TLS_REQCERT never
3. Save, stop/start apache.

For others reading this thread in the future about shared hosting and LDAP:

I was able to work out my original issue with my shared hosting provider. The problem was two fold:

1) my host could not read my certificate chain, even though it was 100% valid on my end

This is what my host did to fix #1
-Requested my CA cert and intermediate cert.
-I provided both certificates in a single .cer file by uploading it to a /cacerts/ directory which I had access to
-Updated their config file to point to my certificates

2) My firewall was blocking secure protocols on port 636/389, even though the port was open. Deep packet inspection was turned on, and as a result, it was disallowing secure protocols over the opened port. Once we tweaked that, authentication occurred.

I’m not sure if I’m allowed to link this, but here is a link to some basic troubleshooting steps that I went through. Hopefully, they can help you: https://bit.ly/1G7vlEe

Basically, you can manually test a secure ldap lookup and get more verbose output than this plugin will show you.