Extension talk:SemanticSignup

nice extension. But how do you create bots?

Also, it seems that one can't use this extension in conjunction with confirmEdit an a captcha. The captcha section seems not to be part of the <signupfields/>

Setup error?

I am getting a warning message after I install the extension, create the bot and a user form.

Warning: call_user_func_array() [function.call-user-func-array]: 
Unable to call SES_SignupFields::render() in .../wiki/includes/parser/Parser.php on line 3243

Any ideas for me? Thanks much.

-- this problem, along with others, happens when the <signupfields/> tag is not at the top of the form.

SOLUTION: The callback for setting the parser hook needs to be modified. Replace line 194 with the following: $wgParser->setHook( 'signupfields', array( 'SES_SignupFields', 'render' ) ); --Mtyeh411 16:15, 10 September 2010 (UTC)

Bug: FCKEditor not working

In SemanticSignup 0.2.0 in file SES_Special.php line 301 $wgScriptPath is unknown. This prevents the loading of the FCKEditor.

Fix: Add $wgScriptPath to the list of global variables at the top of the printForm-Function.

Note: Also, make sure you include Semantic Signup after Semantic Forms in your LocalSettings.php, as the one uses variables defined in the other. Inserted a note in the installation instructions. --F.trott 14:14, 3 November 2009 (UTC)

Captcha

If there was a workaround for Captcha I'd be thrilled and already using this extension. I run a role playing game based in Wiki software and this would be a brilliant streamlining tool. Is there a workaround patch sort of thing available, seeing as the folks at SMW encourage captcha it seems like a workaround should be available. Does anyone have a solution they're willing to share? Kitsufox 14:34, 13 November 2009 (UTC)

Warning using Semantic Forms version 1.8.8

SF 1.9.x fixes this problem.

The SemanticSignup 0.2.0 worked fine till Yaron Koren came out with a new Semantic Forms (SF) version (1.8.8). Suddenly some added fields I created for the Signup process were given values from fields above and the extension generates the following warning when I went to the 'create account' page:

Warning: Missing argument 4 for SFFormPrinter::formHTML() in <directory to extension>/SemanticForms/includes/SF_FormPrinter.inc on line 127

I'm not a php programmer but compared line 127 of SF_FormPrinter.inc (SF 1.8.7 versus SF 1.8.8). Turns out that Yaron and others changed a SF function that is called by:

Old line 127:

  function formHTML($form_def, $form_id, $form_submitted, $source_is_page, $existing_page_content = null, $page_title = null, $page_name_formula = null, $is_query = false, $embedded = false) {

New line 127:

  function formHTML($form_def, $form_submitted, $source_is_page, $existing_page_content = null, $page_title = null, $page_name_formula = null, $is_query = false, $embedded = false) {

The variable "$form_id" is missing in the new SF_FormPrinter.inc and apparently SemanticSignup 0.2.0 calls that function and passes on the function with the "$form_id" still in it.

Does anybody had the same experience and figured a work around this? It would be great if I can still use the SemanticSignup extension in the future! so please share your work around it. Thanks, --Albert Ke 17:46, 5 February 2010 (UTC)

Special:SemanticSignup does not load

after i include this line in the LocalSettings.php

require_once('extensions/SemanticSignup/includes/SES_Main.php');

something goes wrong and new a new account cannot be created. also the page Special:SemanticSignup is just blank...

i ve created a template but m unable to use it.please provide me a detail procedure on using this extension. ne help ll be appreciated

Credits URL is incorrect

Credit URL points to Semantic Watchlist in 0.3. C+P error. --Olivier Beaton 15:46, 21 November 2011 (UTC)

Real name not mandatory

HI,

I set

$egSemanticSignupSettings['requireName'] = true;

but the user can still be created altough the field "real name" was not filled out. Also if you make other custom fields mandatory through the form they can also be left blank. What can I do to make those fields truly mandatory? Thanks for your help, Markus 109.193.12.254 06:38, 7 December 2011 (UTC)