monk3

Thanks for the reply.

Divi2 is more like a framework than a traditional theme.
It would be helpful to have either video tuts or adequate docs to walk through use of a plugin like yours with that app.
It is common for code writers to give overviews, because they understand a plugin or app in-depth. While first-time users arrive with an entirely different schema they are working from. Thereby, it would be far more helpful if the details were covered.

Yes, of course I looked there.
There is a list of features, requirements, and available languages.
Nothing about docs or instructions.

Strefa,

Nice site!

Did you build the theme from scratch, or modify an existing one?

What does the website theteenageprepper.com have to do with a ‘Quick Adsense’ plugin???

Sounds very bizarre.

Not yet, given that the only time we experience the issue is in WP and with the plugin. If it was the hosting service, odds are our logs (the site is on its own VPS) would coincide with the time stamps of the plugin events.

Where can we find the content of the shortcode: [wysija_page] ?

On your page, https://support.mailpoet.com/knowledgebase/customize-your-confirmation-pages/,

You state:

There is a parameter allowing us to determine which page is being called. The snippet below should be placed in the file single-wysijap.php.

if($_REQUEST[‘action’] == ‘subscribe’){ //subscribe page
// Design for subscribe goes here
} elseif($_REQUEST[‘action’] == ‘unsubscribe’){ // unsubscribe page
// Design for unsubscribe goes here
} elseif ($_REQUEST[‘action’] == ‘subscriptions’){ // edit profile
// Design for edit profile goes here
}

Question: Where in that file should the snippet be placed? In the loop? Before the loop? After the loop?

You have to understand, you are intimately involved with the code of your plugin. Those of us attempting to understand it and use it for the first time, do not have the benefit of your presumptions and insights. So when you write your ‘fixes’ in your support site, it serves no purpose to write answers that assume the new users can read your mind. So please, take a few moments and write out answers which are understandable to those of us who do not participate in the writing of your plugin.

Thank you.

Yes, that was what we did. A little low-tech, but what can you do.

The URL to the site is: https://pickleballminnesota.com/pickleball-location-questionnaire/

Understand, I did NOT indicate that I believe that the WP 3.6 upgrade was at fault. Rather, it was a variable and needed to be included in any considerations.

Not able to: this is a working site that we needed to have online.
We did a work around by replacing the date-type fields with text fields. This way it doesn’t matter what they put in the box.
It’s a terrible work around, but expeditious.

I started this thread so that the plugin authors are aware of the problem. They (or others) will need to recreate it. The date fields they are using are relatively new, and in our opinion, not working well in all browsers. I’m not sure what the code is written in, but something is not right.

How is your English translation coming along?

Yes, jayredliner’s fix worked here.

Now why didn’t Yoast find this and fix it???

After installing, I discovered that the plugin is marked that it is no longer supported.

Why haven’t you stated that on the plugin page on the WP plugins directory?

Also, seems to be too much server overhead with WordPress Ultimate CMS plugin.