Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

All other Modules /

Discuss all other Modules here.

Moderators: martimiz, Sean, biapar, Willr, Ingo, swaiba, simon_w

Mollom audio CAPTCHA is missing OBJECT/EMBED fallback


Reply


5 Posts   957 Views

Avatar
sun

Community Member, 3 Posts

7 June 2011 at 6:22am

The audio CAPTCHA uses an OBJECT tag only, without EMBED fallback, which triggers a "Missing plugin" warning bar in Firefox.

To resolve this, the Mollom module should output an EMBED tag within the OBJECT tag.

See [url]http://drupalcode.org/project/mollom.git/blob/refs/heads/6.x-1.x:/mollom.module#l2268[/url] for a working example.

Avatar
Willr

Forum Moderator, 5513 Posts

7 June 2011 at 3:36pm

Good point! However the forum isn't the place for reporting obvious bugs or posts like this. You should post the message to open.silverstripe.org as a new ticket so that someone can assign the bug to the release and track the issue until it's solved.

Patches are more than welcome too :)

Avatar
sun

Community Member, 3 Posts

8 June 2011 at 2:01am

mmm, so [url]http://open.silverstripe.org[/url], it is... ok, thanks.

I'd highly recommend to put the link to trac somewhere more visible.

I carefully looked around in detail on the [url=http://www.silverstripe.org/mollom-module]module page[/url], the [url=https://github.com/silverstripe/silverstripe-mollom]github repository[/url], the forum, and the rest of the web site and could not find any link or hint about an issue tracker and/or development area anywhere.

I somewhat expected to see usage of the github issue tracker as a last resort, but that is disabled, too. The README and INSTALL files of Mollom and Spam Protection modules also do not contain any pointers as to where to report bugs, contribute patches, get support, or request new features.

In the end, I think that SilverStripe gives away a lot of unused potential. I mean, I'm a proficient developer and heavily used to contributing to FOSS projects, but due to a major lack of information and navigational pointers, the barrier for contributing even starts before the actual contribution here.

Is there any reason for why the project pages of the modules do not contain these pointers directly?

Even though this may sound like a stupid rant, I hope you can take it as an improvement suggestion. ;)

Thanks,
sun

Avatar
Willr

Forum Moderator, 5513 Posts

8 June 2011 at 11:15am

Each module page on silverstripe.org has a field for the ticket tracker which modules should fill out (i.e http://silverstripe.org/forum-module has all the links) but it looks like mollom's page hasn't been setup with all the links. Links to all the major parts of the community sites are on the help page - http://silverstripe.org/help-and-support/

Including all links in the README is a good idea (our template doesn't currently state to include it http://doc.silverstripe.org/sapphire/en/misc/module-release-process#readme-file). We'll probably see this area formally tidied up when someone gets around to implementing a proper module API.

Avatar
sun

Community Member, 3 Posts

8 June 2011 at 2:10pm

Ah-ha! :) Now it perfectly makes sense. :)

Not to side-track the issue, but that's basically one of the fundamental reasons for why the Drupal community always kept issue tracking and code repositories directly on drupal.org (even though there would've been "better" solutions in the wild).

For projects like SilverStripe or Drupal, it's the eco-system that ultimately matters. The moment you're able to "route" interests and requests into proper and appropriate channels, you'll see a significant increase of flow, love, and adoption. Regardless of whether that pertains to users, developers, or operators.

Like here, drupal.org had (and still has) a forum section. However, that is commonly considered to be dead now. Obviously, the transition started years ago and heavily advanced for Drupal already, but overall, one can say without any caveats that it's the heart of Drupal's success. In a nutshell, you add a category per module and some meta data fields to your existing forum threads (and comments), apply it consistently to all available extensions (modules/themes/etc), and profit. ;)