[development] 3rd party sites/all/plugins

[Simon Hobbs]

sun

FWIW, I felt that SWF Tools, which has heaps of plugins, also suffered
from this (swfobject, flash players, etc). Thanks for the thread link.

Simon


On Wed, May 13, 2009 at 4:28 PM, Daniel F. Kudwien
<news at unleashedmind.com> wrote:
> Hi Simon,
>
> Separate location for editor libraries
> http://drupal.org/node/320562
>
> investigates exactly this issue.  Of course, that is closely tied to Wysiwyg
> API - but from all contrib modules out there, I assume that Wysiwyg API is
> the one that needs this most.
>
> Let's discuss on-issue.
>
> sun
>
>> -----Original Message-----
>> From: development-bounces at drupal.org
>> [mailto:development-bounces at drupal.org] On Behalf Of Simon Hobbs
>> Sent: Wednesday, May 13, 2009 2:24 AM
>> To: development at drupal.org
>> Subject: [development] 3rd party sites/all/plugins
>>
>> Hiya
>>
>> Is there best practice for 3rd party plugins?
>>
>> Recently a tiny site was upgraded, the fckeditor module was
>> updated but the dev didn't re-add fckeditor. The owner didn't
>> notice for ages and eventually I have to work backwards
>> through backups to make sure I get the right (possibly
>> customized) package.
>>
>> So I've started creating a sites/all/plugins folder for all
>> the fckeditors / swfobject / jqueryplugins / pdfwriters / etc
>> that I need for a job. I then use symlinks, so in the
>> scramble the fix is simple.
>>
>> It's nice too I can put different versions of tools side by
>> side, and the symlink just points to the desired one.
>>
>> In theory it would be great if modules expected a plugin folder.
>>
>> For non-professionals we put them under duress with install
>> instructions that tell them to clutter their modules with
>> plugins, making upgrades harder for them, and I think we send
>> the message that altering modules is ok.
>>
>> Thoughts or guidance?
>>
>> Thanks
>> Simon Hobbs / sime
>>
>
>