Eric Kuznacic

Thank you so much @whitsey for the simple solution!

@wpcal Just circling back around on this. Do you still want me to help troubleshoot? Have you had a chance to access the test site via sFTP to view the logs?

I plan to delete the test site as soon as it is no longer needed, so please let me know if you no longer need access to it.

@wpcal Thanks for the reply. My issue was indeed related to the calendar’s notification settings. I have turned those on and all works as expected.

I imagine that others might have this issue as well, depending on how they have set up their calendar notifications, so it might be something to highlight in the documentation.

I think it would be a good idea to send an email from the plugin to the person requesting the meeting, notifying them that the request was confirmed and including the details like the date, time, etc.

Thanks for all the assistance. I am really liking the plugin so far – it is very nice to have Calendly-like functionality in my WP site!

I’m going to close this, because I identified the issue. I don’t think it was caused by a bug per se, but seems to be related to how I configured my calendar accounts.

I have a G Suite calendar and a personal Google Calendar and they both have access to an appointment calendar for my business. I had WPCal configured to add events via my personal calendar, but once I switched it to the G Suite one the notifications arrived as expected.

@wpcal I looked through the logs of the test site (no traffic other than us) and the only WPCal related items have to do with admin-ajax.php.

I will send SFTP credentials for the test site to your support email so that you can go in and take a look for yourself.

You can reply to that message to arrange a screen share meeting. For time coordination, I am in Central Daylight Time USA (same as Chicago).

@wpcal Unfortunately I still have the same issue in a Chrome incognito window with all extensions disabled. I am out of ideas.

Any other suggestions? If we can’t get it figured out I can always work off of Firefox but I imagine this issue might also arise for others so I am willing to keep going to help figure it out.

@wpcal Thanks for the reply. I have found that the issue seems to only occur when using the Chrome browser (latest version). I was able to get the WPCal.io admin settings section to work properly in the latest version of Firefox.

My PC uses Windows 10 but I also had this issue on my Chromebook (which, of course, runs Chrome).

My site uses PHP version 7.2.30.

I will email you login credentials for the test site, but I believe the issue lies within Chrome.

Any help you can provide is much appreciated.

@krittika If you haven’t received it by now and it’s not in your spam, your hosting server may not be properly configured to receive the notification emails.

Do you have FTP/SFTP access to your site? Or access through a hosting dashboard like cPanel? If so you can go in and manually deactivate the Orbit Fox plugin by temporarily renaming its folder.

@krittika

1) Always start a new thread, even if you are experiencing the same exact issue. This helps show other users and the developers that it is a wider problem.

2) If you are the site admin and are using WP 5.2 or above, you should have received an email with a “magic link” that will allow you to log into your site and deactivate the Orbit Fox plugin to get the site up and running again.

Once you’ve done that, you can use the WP Rollback plugin to go back to Orbit Fox 2.8.13 or whatever version you were using previously.

Well, 8 weeks after the initial reply from @themeisle and 5 weeks since I reached out asking for an update, I finally grew tired of having to “fix” (rollback the plugin) on my client’s site every time they try to update Orbit Fox. I found a fix on my own but it is very hacky and I would not recommend what I did because it is not a fix in any sense of the word.

I realize this site is using an old version of Hestia Pro and that they should keep a current license, but the error is not being caused by the theme; it occurs when updating the **free** plugin that ThemeIsle uses to extend its themes. My client’s site makes use of Orbit Fox features so it is not as simple as just deactivating the plugin; that would cause other issues because functionality would be removed.

It is frustrating that ThemeIsle has ignored this issue, despite releasing 5 minor updates to Orbit Fox since I alerted them to the error. I will remember this poor support if/when ever considering a future purchase from them.

For those like @grossmann who also experienced this error with Hestia Pro 2.0.4, my “fix” was to comment out everything from line 10 to the end of the file in hestia-pro/inc/admin/onboarding/class-themeisle-onboarding.php

I am not concerned this “fix” will break with future Orbit Fox updates, since class-themeisle-onboarding.php appears to be used only for initial setup and importing of a site library. Because the client site does not have an active license, there will not be any theme updates to break anything.

Again, I wouldn’t recommend this fix to anyone, especially if not using Hetia Pro 2.0.4, as I have no idea if this file has changed in recent versions. But, wanted to share my experience so that any others can at least see what worked in my situation.

@themeisle Do you have an update on this?

Just adding a +1 to this request. As of today this plugin has the “This plugin hasn’t been tested with the latest 3 major releases of WordPress” flag on the homepage.

While I am using this plugin on 50+ sites with no issues, it would be nice for the developers to at least give an update to bump the compatible version to current and in the process remove the “hasn’t been tested” warning.

Thanks, I have rolled back and appreciate you looking into this.

This is a great plugin to handle WP.org plugin and theme rollbacks:

WP Rollback

Sorry David, I did not see your post until now. I am happy to report that the issue has been solved as of an update to the latest version (1.6.11).

The site is being built locally on my PC until it is ready to launch so I can’t provide a link at this time. It was being viewed in Chrome and Firefox when this issue occurred. I did not test it in IE, Edge, Safari, etc.

Thanks for responding and for creating/supporting this theme!