Hi @carolyntband,
Indeed, that message in the plugin’s settings is likely related to this behavior. If the connection with SimplyBook was lost, the plugin would be unable to load the settings.
Could you try logging out from the plugin’s dashboard (SimplyBook -> Settings -> General -> Authentication -> “Log Out”) and then re-authenticate; and check if this allows the plugin to load the data correctly once more?
Kind regards, Jarno
Thread Starter
CT
(@carolyntband)
Unfortunately this did not work.
Hi @carolyntband,
Sorry to hear that didn’t help yet. Could you navigate to the affected “Theme Settings” page in SimplyBook once more?
Once you’re on the page, please open the “Developer Tools” in your browser (CTRL/CMD + Shift + C) and navigate to the “Console” tab in the window that appears. I would expect to see some errors related to the issue here.
Could you copy and paste any errors from the “Console” window and share them here, so we can have a closer look at those?
Kind regards, Jarno
Thread Starter
CT
(@carolyntband)
I’m not able to find this. Is that for PC? I am on a Mac using Safari.
Hi @carolyntband,
You can see this information in Safari as well. After navigating to the design settings page in the plugin in Safari, look in the ‘top menu bar’ of your Mac for a tab called “Develop”, and then select “Show JavaScript Console”.
This will open a new window on the bottom of your screen. Please copy all of the errors/messages as displayed in the “Console” window that appeared, and share them in this thread. Please find a screenshot below.
Kind regards, Jarno
Thread Starter
CT
(@carolyntband)
Hi @carolyntband,
Thank you for sharing the screenshot!
There is a “404 Not Found” on the /simplybook/v1/theme_list/ endpoint which is used to load the Theme Settings page, which explains why the plugin can not load this data.
However, other endpoints from the plugin (like simplybook/v1/subscription_data/) do respond as expected; as your screenshot does display data like “Premium – 4 days left” correctly.
To rule out the possibility that your browser (Safari) might be related to this (possibly due to a strict cross‑site cookies/privacy setting): could you verify whether this issue also persists when using another browser, such as Google Chrome or Firefox?
If using another browser does work as expected, it confirms that a setting in Safari is preventing the Theme Settings from being loaded.
Kind regards, Jarno
Thread Starter
CT
(@carolyntband)
Hi @carolyntband,
I see, in that case; this makes it unlikely that this concerns a browser-related problem.
Could you navigate to the SimplyBook Dashboard once more in your WordPress Admin, and then visit the following URL by manually entering it in your browser’s address bar?
https://vocaleuphoria.com/wp-json/simplybook/v1/theme_list
Please share the full output of that page in your reply here.
Kind regards, Jarno
Hi @carolyntband,
Thank you very much, this unexpectedly empty response does explain why the Theme Settings data can’t load correctly on your site. The plugin receives different data than it expected and this causes the issue.
Admittedly: I haven’t encountered this specific response before, so I’ll have to discuss with the team as to the likely culprit, e.g., whether the message originates from the SimplyBook API or if it is likely to be caused by something else entirely.
Will get back to you as soon as I have more information, but I hope this short clarification helps in the meantime.
Kind regards, Jarno
Hi @carolyntband,
I’ve discovered the most likely cause of this issue in the meantime: if the allow_url_fopen setting is disabled on your webserver, this will block the theme_list request, and this causes the exact error message that you shared previously.
Enabling allow_url_fopen on the server should fix this issue. That might have to be done by your hosting provider though, so I’d recommend reaching out to them for assistance with this.
In some cases, your host may allow you manually change this setting directly in your hosting control panel. But as this varies per host, reaching out to your hosting provider is often the easiest approach.
In any case, we hope to remove this requirement in a future release of the plugin, so that enabling allow_url_fopen would no longer be needed for the theme_data request to succeed.
Hope this helps!
Kind regards, Jarno
-
This reply was modified 5 months, 2 weeks ago by
Jarno Vos.
Thread Starter
CT
(@carolyntband)
Hi @carolyntband,
It’s unlikely to be a PHP version issue, but PHP 8.2 would indeed be perfectly fine.
While allow_url_fopen is enabled, the most-likely explanation is still that there is some setting on your server (e.g., a security restriction) that causes PHP HTTPS streams to user-api.simplybook.it/public to get blocked; which leads to this exact error message.
You could ask the host to verify that outbound POSTs to user-api.simplybook.it over port 443 are not blocked on the server, perhaps there’s a WAF/Firewall blocking the requests.
In any case. We will create a patch on our end, to make this request work like the other ones which do behave as expected on your server. I’ll provide such a version once it becomes available, but that may take some time as it still has to be developed.
In the meantime, contacting the host for assistance with determining the cause of this failing request may be your best bet.
They can check the server configuration more closely (e.g., checking for potential firewall restrictions that could block the HTTPS POST request to user-api-v2.simplybook.it, confirming that the OpenSSL library on your server is enabled and up to date, and whether PHP can fetch HTTPS via streams).
Kind regards, Jarno
Thread Starter
CT
(@carolyntband)
Its fixed!
https://drive.google.com/file/d/11PiFFwfGqu3rI-zJEhE5sRaTCqvjyc3k/view?usp=share_link
https://drive.google.com/file/d/17BEyr9VV8ijZlNSVjgemd9cqUQv-ZbAC/view?usp=share_link
https://drive.google.com/file/d/16e0aq6YnYGrTmxbomu0x1imzRjJZlooA/view?usp=share_link
This is what my host said
“Hello there! From what I can see, the domain is currently running on 8.1 You may verify this from here: > https://prnt.sc/gjKXNkwvf371 So I went ahead and created an info.php file for you. > https://vocaleuphoria.com/info.php From what I can see, the requested allow_url_fopen if enabled on it as well. https://prnt.sc/B_lg-joPB1Us So went ahead and change it to 8.2 under your .htaccess file. > https://prnt.sc/oQU6M0P3gxM2 Please check now and let me know if the issue continues so we can investigate further.”
