Skip to content

Added support for SI Schedule+Register form (StudioIntern)#167

Open
RealZendor wants to merge 2 commits intoFriendlyCaptcha:mainfrom
RealZendor:main
Open

Added support for SI Schedule+Register form (StudioIntern)#167
RealZendor wants to merge 2 commits intoFriendlyCaptcha:mainfrom
RealZendor:main

Conversation

@RealZendor
Copy link
Copy Markdown

What is SI Schedule+Register?

SI Schedule+Register is a Wordpress PlugIn which can fetch dance class schedules from a StudioIntern SaaS instance and display it inside a Wordpress page. Further, it can display a registration form / trial lesson appointment form which then will be sent to the StudioIntern instance.

What is the change intended for?

The changes I made is simply adding a module to support the StudioIntern SI Schedule+Register form.

Where can I get more information on StudioIntern and this special form?

For information on StudioIntern in general, visit https://www.ballettschul-software.de/ .
For information about the SI Schedule+Register WP Plugin, see https://www.ballettschul-software.de/zusatzmodule.php#sischedreg
Send support requests to support@studiointern.de .

@RealZendor
Copy link
Copy Markdown
Author

Don't know if I am allowed to change the plugin's version number. That's why I didn't. Please change version number before committing the merged repo.

@merlinfuchs merlinfuchs self-requested a review April 14, 2026 07:17
LU-386 added a commit to LU-386/friendly-captcha-wordpress that referenced this pull request Apr 14, 2026

if (empty($solution)) {
/* translators: Error message when captcha was not completed */
return __("Bitte lösen Sie das Anti-Spam-Rätsel.", "frcaptcha");
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this integration only relevant to german speaking users? All our other error messages are in english, I think it would be best to keep it that way.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, most StudioIntern users (and their customers) speak German.

Comment thread friendly-captcha/includes/core.php Outdated
"slug" => 'tws_siwp',
"entry" => "tws-siwp/tws-siwp.php",
"plugins" => array("tws-siwp/tws-siwp.php"),
"settings_description" => "Enable Friendly Captcha for the SI Schedule+Registration trial lesson signup form.",
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be best to link to the relevant website here, so users understand what this integration is for :)

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done with new commit.

@merlinfuchs
Copy link
Copy Markdown
Member

Hey, thanks for the PR!

If I see it correctly you are part of the StudioIntern team, so I wonder if it wouldn't be best to integrate Friendly Captcha into the StudioIntern Wordpress plugin and not the other way around? We have a PHP SDK which should make it fairly easy to integrate it into your plugin.

This way you have better control over how Friendly Captcha is integrated and users don't have to install the separate Friendly Captcha Wordpress plugin. What do you think?

@RealZendor
Copy link
Copy Markdown
Author

Yes, you are right. I am the author and provider of StudioIntern. In fact, trying to integrate FC directly into my plugin was my very first idea. It first seemed to work. But it didn't. There were some strange phenomenas. On my lokal dev machine, it worked perfectly. On production, FC provided a different "version". Look at these screenshots:
Bildschirmfoto vom 2026-04-07 20-56-10
and this:
Bildschirmfoto vom 2026-04-07 21-03-52
The first one is from my local env, while the second ist taken from production. Both of them have identical code (the difference in font an button design come from different WP themes)!
The production widget showed up in English, but the HTML lang attribute was set to 'de':
Bildschirmfoto vom 2026-04-07 21-07-16
Then, the transmisson of the solution didn't work; the FC class received an empty value. All this only when running on a live server. This live server is not under my control (it's a customer's server) so debugging was a nightmare and I finally gave up.

@merlinfuchs
Copy link
Copy Markdown
Member

This looks like to be mix of Friendly Captcha v1 and v2. The first screenshot shows Friendly Captcha v2 but the second one shows Friendly Captcha v1. This is probably because the wrong scripts are included on the live site.

You most definitely want Friendly Captcha v2 and I would guess the integration of v1 on the live site was done by mistake. This would also explain why the form field was empty, v1 uses a different form field name than v2.

You can find more information on v1 and v2 here:
https://developer.friendlycaptcha.com/docs/v2/versions

And the integration guide for v2:
https://developer.friendlycaptcha.com/docs/v2/getting-started/install

Let me know if you have any more questions or need further help with the integration :)

@RealZendor
Copy link
Copy Markdown
Author

It's impossible being a wrong script included only on the live site. As I mentioned before, the whole plugin code was identical on dev and live.

@merlinfuchs
Copy link
Copy Markdown
Member

What I see on the screenshot is definitely a mix up between v1 and v2. The two versions work completely different, so it's impossible that they are shown with the script.
Maybe you have the Friendly Captcha Wordpress plugin installed and enabled on the live site as well? In that case it could take precedence over your custom scripts. Or you have included both scripts for v1 and v2 and sometimes v1 takes precedence over v2?

@merlinfuchs merlinfuchs self-assigned this Apr 16, 2026
@RealZendor
Copy link
Copy Markdown
Author

Oh yes! This seems to explain what happened. My customer does have the public FC plugin installed because he uses it elsewhere on the site. I didn't know about that.
And that’s another reason why I’m NOT integrating the FC features into my plugin. Other users of my plugin may also have “FC official” installed. That could lead to similar issues to the ones I’ve experienced. Therefore, using this seems to be the cleanest solution. If they haven’t installed FC, I’ll advise them to do so.

LU-386 added a commit to LU-386/friendly-captcha-wordpress that referenced this pull request Apr 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants