wremmert

Hi Phil,

I seemed to have fixed it. I think what was happening was that there was another print stylesheet being loaded that I wasn’t aware of and it took over. Since I had placed the above style block in my main style.css, it never got into play.

On another note, I implemented the open Everything JavaScript and then reversed the logic to create a Close everything button. I then created a shortcode that includes both buttons, making it easier for my accordion users to add the buttons.

Cheers,
Bill

• This reply was modified 7 years, 9 months ago by wremmert.

I know the difference between Double & Single Opt In. These people never really even get to the site. The authentication plugin we’re using redirects them away from the site. However, we’re finding that for the brief second that they’re there, just before they get re-directed, a subscriber record is getting created and set to CONFIRMED. It is freaking possible, maybe not intended in the software but it is possible because it is happening.

You right after I say something is not possible in my code, someone will prove that given just the right circumstances, anything is possible.

The Email Subscribe plugin is creating subscriber records, that are marked with a status of confirmed. These subscriber records are being created for uses who did not correctly authenticate on the site. The user(s) who do not authenticate get re-directed to another site, that explains to them that they failed to gain access because they did not authenticate. However, these users, who did not gain access to the site, are then getting an email saying that they just subscribed to the site. When the ADMIN looks at the subscriber user records, we can see “Confirmed” subscriber records.

It’s as if the Email Subscribe plugin is creating a temporary subscriber record that it later deletes if a user does not really subscribe. However, since these users never really got to the site, the tmp record is not being deleted.

Thoughts?

I had that going on too. Upgrading the the current release took care of it.

Along the same lines, I was wondering if you had any plans to add label tags to the name and email input fields. My accessibility tester team dings me when fields don’t have label tags. I’ve been going to the where they’re defined in the plugin and adding them in to the input files. Could you add the labels in as a standard part of the plugin?