Error with Events Calendar Pro when not forcing www on website

[lblnra]

In my attempt to secure my website and add it to the HSTS preload list, I kept getting an error that there were no HSTS headers in response. I worked with another plugin developer dealing with SSL. He recommended to stop forcing www to my domain. Once we did that, the site would not work. With a little help from my host, we determined it was Events Calendar Pro conflicting with the lack of www.

Two issues:
1. When removing www, it still isn’t preserving my headers.
2. Now that my site no longer forces www, Events Calendar Pro breaks my site. I have to deactivate it so I don’t get error messages: “Fatal error: Unknown: Cannot use output buffering in output buffering display handlers in Unknown on line 0”.

Any ideas?

I really need Events Calendar Pro for displaying all the programs we have…

Thanks,
Janice
landbetweenthelakes.us

[lblnra]

I solved the header issue. However, Events Calendar Pro breaks my site. This is the error code I get:

Fatal error: Unknown: Cannot use output buffering in output buffering display handlers in Unknown on line 0

I really need this to work…Any thoughts?

Thanks,
Janice

[lblnra]

Just an update…My key was still connected to http://www.landbetweenthelakes.us. I deleted it from the plugin then disconnected that domain from the key. I reconnected it with landbetweenthelakes.us. I am still getting the same error. It is definitely Events Calendar Pro that is breaking my site. I have had to deactivate the Pro plugin so my site works.

Any help is much appreciated.

Thanks!

[lblnra]

This reply is private.

[Andras]

Hello Janice,

Thanks for reaching out to us and I’m really sorry about this issue you are having!

I’m not quite sure why PRO would have an issue with not having www in the domain name. I have a test site and a local install not using www and not experiencing any issues. Also, we don’t hardcode www into the plugins for sure.

My hunch is that is has something to do with the code you implemented for the HSTS headers.

To be able to troubleshoot this issue I need a bit of help from you.

First I’d like to ask you to share your system information with me. Here’s a nice little guide on how you can do that easily.

Second, please check if you are getting the same error message if you deactivate all plugins except for The Events Calendar and Events Calendar PRO, and switch to a default theme like twentysixteen, and removing any customizations made to our plugin files if you did any. Let me know the results of that.

Looking forward to solving this issue with you!

Cheers,
Andras

[lblnra]

Andras–

Thank you for your response. When I was trying to get the HSTS thing worked out, my host did just what you asked me to do today. He had deactivated all plugins and found the culprit was EC Pro. I only get the error when EC Pro is activated.

I have not changed themes….I have done that before and lost information and format when I switched back so I’d rather not change themes at the moment (one problem at a time).

This isn’t the first time it has caused an issue. However, most issues have been resolved quickly.

I have copied the EC Pro code and pasted it in the original forum request. I do not see the link you said you provided for me to get you system info. I’m not quite sure where to go for that.

I’ll gladly send you what you need.

I appreciate any help you can give.

Thank you,
Janice

Janice R. Wilson
Public Affairs Specialist
U.S. Forest Service

[lblnra]

This reply is private.

[lblnra]

My apologies…I had replied on my email and not on the forum. That’s why I didn’t see the guide. I found it and sent it to you in a private reply.

Cheers!

[Andras]

Hello,

Thanks for your reply and your sysinfo, however I only see part of it. Please make sure that you select all of the content in the black box. Thanks!

I have not changed themes….I have done that before and lost information and format when I switched back so I’d rather not change themes at the moment (one problem at a time).

Switching to a default theme like twentysixteen would be crucial in this case as there might be something in your current theme that is causing the conflict with our plugin. In order to find that out you would need to switch.

I totally understand that you don’t want to switch themes and test things out on a live site. That is why we usually recommend to set up a staging site where you could do tests like this without disrupting your live site. Best would be setting up the test / staging site on the same server to have the same conditions, and a copy of your current site would be obviously the best. If you are not fully comfortable doing this or you don’t know how, then your hosting provider should be able to help you out.

Unfortunately without testing this we cannot really move forward with the bughunt.

The error message you get is very generic and vague, so it is impossible to draw any conclusions from that. Is there any specific action you take when you see this, or it immediately appears when you activate PRO?

Cheers,
Andras

 

[Andras]

This reply is private.

[lblnra]

This reply is private.

[lblnra]

This reply is private.

[lblnra]

This reply is private.

[Andras]

This reply is private.

[lblnra]

This reply is private.

[Author]

Posts