Last modified: 2012-03-30 12:25:56 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T37604, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 35604 - Undefined variable: cols
Undefined variable: cols
Status: RESOLVED INVALID
Product: MediaWiki extensions
Classification: Unclassified
SemanticForms (Other open bugs)
unspecified
All All
: Unprioritized minor (vote)
: ---
Assigned To: Yaron Koren
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-03-30 10:39 UTC by Ad Strack van Schijndel
Modified: 2012-03-30 12:25 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Ad Strack van Schijndel 2012-03-30 10:39:37 UTC
When using textarea with autocomplete in a form I get the notice: Undefined variable: cols in .../includes/forminputs/SF_TextAreaWithAutocompleteInput.php on line 96.
Comment 1 Nischay Nahata 2012-03-30 10:49:00 UTC
(In reply to comment #0)
> When using textarea with autocomplete in a form I get the notice: Undefined
> variable: cols in .../includes/forminputs/SF_TextAreaWithAutocompleteInput.php
> on line 96.

It would be helpful if you could give a screenshot of the page with the error displayed
Comment 2 Ad Strack van Schijndel 2012-03-30 11:11:42 UTC
(In reply to comment #1)
> (In reply to comment #0)
> > When using textarea with autocomplete in a form I get the notice: Undefined
> > variable: cols in .../includes/forminputs/SF_TextAreaWithAutocompleteInput.php
> > on line 96.
> 
> It would be helpful if you could give a screenshot of the page with the error
> displayed

Why would that be helpful? What additional information is needed to know what is wrong?
By the way, it is only a notice, so it doesn't do any functional harm as far as I can see.
Comment 3 Yaron Koren 2012-03-30 12:04:49 UTC
Yes, please disregard the screenshot thing - I don't know why Nischay wrote that.

Anyway, it looks like you're using an older version of SF. If you upgrade to the latest version, 2.4.2, hopefully the problem will go away.
Comment 4 Nischay Nahata 2012-03-30 12:10:47 UTC
Sorry, I misunderstood something here
Comment 5 Ad Strack van Schijndel 2012-03-30 12:18:40 UTC
(In reply to comment #3)
> Yes, please disregard the screenshot thing - I don't know why Nischay wrote
> that.
> 
> Anyway, it looks like you're using an older version of SF. If you upgrade to
> the latest version, 2.4.2, hopefully the problem will go away.

You're right I was (2.3.2) and it has gone away. Sorry to have bothered you.
Comment 6 Yaron Koren 2012-03-30 12:25:56 UTC
No problem - marking this as "invalid".

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links