Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 non ssl map url | Event Espresso - Staging Server
<code>The page at 'https://www.watchmanmonitoring.com/thank-you/?ee=launch_invoice&id=1-3a69e70d44e0a983e635038fdc4c8f05&html=1&receipt=true' was loaded over HTTPS, but displayed insecure content from 'http://maps.googleapis.com/maps/api/staticmap?center=225+Powell+Street%2CSa…l+Street%2CSan+Francisco%2CCalifornia%2C94102%2CUnited+States&sensor=false': this content should also be loaded over HTTPS.
</code>
There’s no telling what that’ll break/do. No I’m not interested in troubleshooting the fallout.
I just need you guys to put a S in the google maps call… kinda like that author put on the plugin’s readme?
I'll be adding other fixes as I find simple solutions for them. The better solution is to get errant plugins fixed by their authors, but until they do, let me know about them and I'll attempt to add fixes.
I have issued a ticket for the developers to look into this.
As far as I am aware google maps require a little more than just specifying HTTPS so the developers will need to investigate this to find a working solution.
I’ll add a note to the ticket to update this thread with any findings
I also realize that this is the final page in the process, a lack of ssl isn’t a huge problem.
I’ll look at it again when I upgrade to ee4 later on.
Viewing 4 reply threads
The support post ‘non ssl map url’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.