WBCE CMS Forum

WBCE CMS – Way Better Content Editing.

You are not logged in.

#1 14.02.2016 12:22:02

cwsoft
Member

Module platform and GUID

What are the thoughts on the addon variables $module_platform and $module_guid (the latter was introduced with AMASP/Lepton afaik).

Should module platform be used to identify the CMS platform (e.g. WBCE 1.x, 1.1.x etc.), or just point to the CMS used (e.g. WB, WBCE). Is this variable used anywhere in modules or core or could this be removed? Guess with WBCE_VERSION and WB_VERSION and the newly implemented WBCE hooks we can easily identify those things.

I never understood the need for the GUID, apart from the possibility offered for tracking purposes - which I don't like much by nature  smile

Any thoughts on this?


Account inactive since 2018/11/17.

Offline

#2 15.02.2016 11:02:09

webbird
Administrator

Re: Module platform and GUID

GUID: Was meant to identify modules when/after they were renamed and/or to distinguish modules with similar names. Some modules allow to be renamed, others don't. Dunno anything about tracking and never saw any code doing it.


Ich habe eine Amazon-Wishlist. wink
Ich kann, wenn ich will, aber wer will, dass ich muss, kann mich mal

Offline

#3 17.02.2016 13:40:38

norhei
Developer

Re: Module platform and GUID

Hmmm , a few thoughts...

The module folder name is basically a unique identifier. If there are Developers who do not change the name because they don't care  , they wont change the GUID either (or change it manually, so there can easily be doubles or invalid formats) .

Modul Platform may be an interesting Information to avoid confusion whith so many forks around, but how to handle modules that run on multiple platforms?

Offline

#4 18.02.2016 08:29:30

cwsoft
Member

Re: Module platform and GUID

@norhei: WBCE|WB|BC ..., WBCE>1.x ...

Something similar like Python pip or PHP Composer.


Account inactive since 2018/11/17.

Offline

Board footer

Powered by FluxBB

up