Does not work on HTTPS sites

  • Resolved Mangesh

    (@gmangesh)


    7 years, 12 months ago

    I recently upgraded a site from HTTP to HTTPS.

    After the upgrade to HTTPS:

    1. The contact form created by the [vCitaMeetingScheduler] appeared blank due to “mixed-content”.
    2. The vCita settings pages within wp-admin (Edit Contact For, Edit Scheduling Calendar Widget, etc) appear blank (tested in Chrome).

    This is because Chrome blocks “mixed content” by default. This can be seen in the Console in Chrome Developer Tools.
    Screenshot of Mixed Content blocked by Chrome

    Workarounds:

    1. User-facing forms: I’ve “fixed” the contact form issue by doing a search-replace in the wordpress database and changed https://wwww.vcita.com to https://www.vcita.com. (Hopefully, this will not revert back in 24-hours as reported by jeremybooze)

    2. wp-admin screens: Since these screens are only accessed by admins, we are asking the admin to override Chrome’s default behavior and allow mixed-content when visiting the admin screens.

    Issue:

    Upon digging through the vCita plugin code, we can see https:// being hard-coded in the plugin. Here is a sampling:

    ./vcita-active-engage-edit.php:23: <iframe src=”https://&lt;?php echo VCITA_SERVER_BASE ?>/widget_implementations?platform=wordpress&widget=active_engage&key=<?php echo $key ?>” width=”100%” height=”100%”/>
    ./vcita-calendar-edit.php:22: <iframe src=”https://&lt;?php echo VCITA_SERVER_BASE ?>/widget_implementations?platform=wordpress&widget=scheduler&key=<?php echo $key ?>” width=”100%” height=”100%”/>
    ./vcita-contact-form-edit.php:22: <iframe src=”https://&lt;?php echo VCITA_SERVER_BASE ?>/widget_implementations?platform=wordpress&widget=contact_form&key=<?php echo $key ?>” width=”100%” height=”100%”/>
    ./vcita-sidebar-edit.php:22: <iframe src=”https://&lt;?php echo VCITA_SERVER_BASE ?>/widget_implementations?platform=wordpress&widget=sidebar&key=<?php echo $key ?>” width=”100%” height=”100%”/>

    Suggested Solution:

    Please consider using protocol-relative urls, or, since your URLs appear to be available over HTTPS, just use https:// everywhere.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author vcita

    (@vcita)

    Hello,

    Thank you for detailing the scenario and apologies for the delay.
    Indeed the simplest way to cope with this is to change the URL and add the “s”.
    We will be mentioning your suggestion internally.

    Thank you,

    Thread Starter Mangesh

    (@gmangesh)

    FYI for those encountering the same problem – even though this thread is marked as “Resolved”, the issue is not yet fixed as of version 3.14.0

    Plugin Author vcita

    (@vcita)

    Hi. Thanks for letting us know.
    We will be checking this further and update you.

    Kind regards,

    Plugin Author vcita

    (@vcita)

    Hi,

    We would like to diagnose this further.
    Can you please email [email protected] with this query and let me know here when you have done so?
    This will allow us to help fully resolve this.

    Thank you,

    Thread Starter Mangesh

    (@gmangesh)

    Hi,

    I have sent you an email at [email protected]

    The fix is really quite simple – you can simply do a global search/replace and change the 37 occurrences of “http:” to “https:” in the plugin’s code.

    Regards

    Plugin Author vcita

    (@vcita)

    Thank you.
    We are reviewing this and will keep you posted.

    Kind regards

    Plugin Author vcita

    (@vcita)

    Hello,

    We have now released a new version of this plugin to wordpress that has resolved this.

    Kind regards

    In version 3.14.2 if the website is configured for use SSL then iframe for contact form is not displayed because mixed content, this is configured for use https://.

    (<iframe src=”https://www.vcita.com/widgets/contact_form/XXXXXXXX?ver=2)

    If in DB is changed the option_value for option_name “_transient_embed_codecontactoXXXXX500450” with https, this is reverted after some changes made in WP admin.

    Please take a look at this issue.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Does not work on HTTPS sites’ is closed to new replies.

Tags