LSP Enigma2 RC1 Integration

[Zarsky]

With the first Release Candidate of the Enigma 2 portal (based on SMF 1.0.7)....the fine developers of Enigma 2 have also released an excellent seamless integration with Coppermine v 1.4.4.

Details and files are available here:

http://www.lunabyte.net/index.php?topic=4082.0


For those of you unaware of the Enigma Portal CMS....it is an excellent portal, very easy to use for a novice and infinitely expandable and adaptable for an expert.

I hope this integration drives more interest over to Enigma.

You can see Enigma2 in action here:                    www.lunabyte.net
And you can see E2 with Coppermine 1.4.4 here:  www.lunabyte.net/gallery

[Joachim Müller]

Hey Mark,

this looks great. The readme that comes with it is very well written. However, the suggestion to replace the existing smf bridge is not a good idea imo. Instead I suggest using the custom bridge option and naming the bridge file something like enigma_smf.php or similar.
Imo this bridge could be integrated into future releases of coppermine with slight modifications. What license does it come with?

[Zarsky]

GauGau,

I let the devs over at Enigma know about your question about the license and suggestions for improving the integration so that it can be added to future releases of Coppermine.  As far as I know the license is essentially the same (if not identical) to SMF's license.

I am not entirely sure if the integration/bridge code is released under the same license....but I would presume so, since the devs of Enigma2 essentially created the integration/bridge code as well.  I would expect them to comment over here, letting you know.

UPDATE:  After looking at the bridge file...it makes it clear the bridge code is released under same license as Enigma2 which is the license I quoted below

You are of course welcome to post over on their site as well.  I am sure they would appreciate any suggestions for improving the integration.

Here is the Enigma2 License:

Notes:
     - License modeled after SMF, c/o Lewis Media, all rights reserved.


Definitions
-----------------------------------------------------------------------------
i. This Package is defined as all of the files within any archive file or any
group of files released in conjunction by Lunabyte Systems.

ii. This Package does NOT include any SMF files, which are fully protected
under the SMF License as currently posted by Lewis Media.

iii. A Modification, or a Mod, is defined as instructions, to be performed
manually or in an automated manner, that alter any part of this Package.

iv. A Modified Package is defined as this Package or a derivative of it with
one or more Modification applied to it.

v. Distribution is defined as allowing one or more other people to in any
way download or receive a copy of this Package, a Modified Package, or a
derivative of this Package.

vi. The Software is defined as an installed copy of this Package, a Modified
Package, or a derivative of this Package, not to include SMF files.

vii. The Lunabyte Systems Website is defined as http://www.lunabyte.net/.

viii. Any and all SMF files are copyright Lewis Media, and subject to their terms
and agreement. All SMF agreements must be honored in regards to the SMF files

Agreement
-----------------------------------------------------------------------------
1. Permission is hereby granted to use, copy, modify and/or distribute this
Package, provided that:
   a. All copyright notices within source files and as generated by the
      Software as output are retained, unchanged.
   b. Any Distribution of this Package, whether as a Modified Package or
      not, includes this file and is released under the terms of this Agreement.
      This clause is not dependent upon any measure of changes made to this
      Package.
   c. This Package, Modified Packages, and derivative works may not be
      sold or released under any paid license. Copying fees for the transport of
      this Package, support fees for installation or other services, and hosting
      fees for hosting the Software may, however, be imposed.
   d. Any Distribution of this Package, whether as a Modified Package
      or not, requires express written consent from Lunabyte Systems.

2. You may make Modifications to this Package or a derivative of it, and
distribute your Modifications in a form that is separate from the Package,
such as patches. The following restrictions apply to Modifications:
   a. A Modification must not alter or remove any copyright notices in
      the Software or Package, generated or otherwise.
   b. When a Modification to the Package is released, a non-exclusive
      royalty-free right is granted to Lunabyte Systems to distribute
      the Modification in future versions of the Package provided such
      versions remain available under the terms of this Agreement in
      addition to any other license(s) of the initial developer.
   c. Any Distribution of a Modified Package or derivative requires
      express written consent from Lunabyte Systems.

3. Permission is hereby also granted to distribute programs which depend on
this Package, provided that you do not distribute any Modified Package
without express written consent from Lunabyte Systems.

4. Lunabyte Systems reserves the right to change the terms of this Agreement at
any time, although those changes are not retroactive to past releases.
Changes to this document will be announced via email using the Lunabyte Systems
email notification list. Failure to receive notification of a change does not make those
changes invalid. A current copy of this Agreement can be found on the
Lunabyte Systems Website.

5. This Agreement will terminate automatically if you fail to comply with the
limitations described herein. Upon termination, you must destroy all copies
of this Package, the Software, and any derivatives within 48 hours.

-----------------------------------------------------------------------------
THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY WARRANTY. ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
EVENT SHALL THE AUTHORS BE LIABLE TO ANY PARTY FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES ARISING IN ANY WAY
OUT OF THE USE OR MISUSE OF THIS PACKAGE.

[Zarsky]

GauGau,

Luke responded at Lunabyte.net

Basically they are fine with having it added in future Coppermine releases.  I guess they had some trouble with the custom bridge option, so they took the easy route and just added the E2 specific functions to the SMF bridge file.  Anyways....Luke says to have at it...I am sure they would be willing to have anyone take the necessary steps to create a seperate bridge file along with the requisite radio button.

Luke @ Lunabyte.net:  http://www.lunabyte.net/index.php?topic=4082.msg32465#msg32465

That's cool mark. Wink

It's no different than the SMF bridge, really, other than it comes with a couple extra functions in addition to the SMF bridge.
We did try their custom bridge option, but couldn't ever get it to load right. So, we just modify the SMF bridge to simply add a couple custom functions in there. The SMF portion is the same, and unmodified.

We might play with it a little more in the future though.


It would be fine if they built it in as a predefined bridge. It's no different that the SMF one on their end, and basically it would only require a radio button for selection.


As far as the license, it's no different than the SMF file.
Tell them to have at it.

[Luke (LSP Dev)]

Mark is right, GauGau.

I'd be happy to work with y'all on it.

We (for some reason) had some issues with the database settings running it through the
custom bridge area of the bridge manager. So, since it's the SMF bridge that comes
with Coppermine, with a couple additional functions added, and Enigma 2 is already
integrated with SMF, we thought it would be easier for the time being from a users
perspective to just upload a new version of the file. Plus, if they already have an SMF
bridge, and then add E2, they can just replace the file and be done.


The additional functions were addded mainly to let E2/SMF control certain aspects in
regards to spitting out the source code to the browser, so that it would be W3C compliant.

What we ran into was being integrated with E2, the closing of the head, and opening of
the body, and the closing of the body and html tags. It would actually end up putting
things that should be in the head, just inside the body tag, which the validator at W3C
didn't like. As well as the closing tags having an issue as well.

So we add a custom header function and footer function, which are the same as the
coppermine functions without killing the tags mentioned previously, as well as we
also added the custom header and footer functions with the paths already coded to
save users having to go in and add each file inside the config section of Coppermine.


For E2 to be added in the bridge manager, it would be as simple as copying the existing
bridge manager stuff for the SMF area, generating another radio button, and then
renaming the bridge file included in our bridge package to Enimga vice SMF.


If it's something that you all would like done, that's fine.
Technically we could have went ahead and done it, but with all our bridges we
are trying to not impact any of the original application files if we don't have to.
So, we went the easy route. But like I said,  if it's something y'all would like done,
we don't have any problems with it. In fact, I would even be willing to make the
changes needed and submit them back to you if you would like.

We've done a similar bridge with WordPress (it's my baby, lol), and the more I play with
it the more I'm amazed that I can do with it. This being the case, I think there is the possibility
of even more users finding the power of Coppermine as well as E2.

[Luke (LSP Dev)]

Oh, we've also got some screenshots in our gallery of the bridges.

http://www.lunabyte.net/gallery/

[Zarsky]

Just wanted to let everyone know....I tested the Enigma2 RC1 integration with Coppermine v 1.4.5 and it works perfectly.  I followed the standard Coppermine 1.4.5 upgrade instructions with one minor addition:

Remember not to overwrite the SMF bridge file: "smf10.inc.php", otherwise you will break your E2 integration.