Welcome, Guest. Please login or register.
Did you miss your activation email?
May 26, 2012, 07:05:47 AM

Login with username, password and session length
Search:     Advanced search
Wollen Sie dem WebsiteBaker Team beitreten?
Nähere Informationen finden Sie unter hier und auf unserer neuen Webseite.
155534 Posts in 21713 Topics by 7737 Members
Latest Member: chris85
* Home Help Search Login Register
Pages: [1]   Go Down
Print
Author Topic: WebsiteBaker - Media - Management  (Read 1110 times)
DarkViper
Development Team
*****
Offline Offline

Posts: 1252


« on: June 25, 2010, 11:34:18 AM »

I guess, it's the time now,  to say a few words about the Media-Management by WB (WB-MM).

I read the online help for WB-MM. I found that there are described a couple of misunderstandings and never existing functionality.
It's not our goal to make the WB-MM compatible to the online-help.. But it is necessary to make the online-help compatible to to the real existing WB-MM!


WB - Media-Management never is...

  • ... a new kind of One-Click-Hosting
  • ... a new kind of 'YouTube' or 'Flicker'
  • ... any kind of personal storage 'Cloud'
  • ... any kind of download service

What WB - Media-Management really is:

WB-MM is an easy possibility for authors to store their mediafiles, which are needed for build the content, on the webspace.
Nothing more nothing less.
The design with 'home-folders' is been made to give more overview about all the stored files, if more then one authors are working on the site.
All files must be accessible by http-requests to everybody, otherwise they can not properly included (as i.e. images) in wysiwyg-sections.

That's all what the WB-MM wants and also does.


If somebody needs an extensible functionality...
Where is the Problem?? Don't hesitate to write your own module, providing exactly this functions you need. Feel free and let your module create a new, hidden subdirectory like /wb/media/.mymodulename/. Your module can act as ever it want inside that directory. WB-MM ignores hidden directories inside of '/media/' and does not change anything at.

But: Never modify the existing WB-MM and it's directory structure! It will disturb the basic functionality of WB-MM and in the worst case WB will stop working.

WebsiteBaker is per definition a modular system which can be expanded for a lot of posibilities.
It makes absolutely no sense inflating some built-in functions in a endless way.
Why a user a outsized module must load... if he only wants to manage a handful files?

The general direction of WebsiteBaker is:
  • Make the code as secure as possible!
  • Do it easy as possible!
  • Do it as fast as possible!
  • Never do load or execute a line of code which is not needed for the current job!


Remember:
WebsiteBaker is a pure ContentManagemantSystem. It is never a Community-System, never any kind of Social-Networking-System or something else.


« Last Edit: June 30, 2010, 06:49:29 PM by DarkViper » Logged

Anleitungen lesen und selber nachdenken ist anstrengend...  Da lass ich doch lieber andere für mich denken...

In 1984:  Nineteen Eighty-Four is a unrealistic utopia!!
In 2012:  Nineteen Eighty-Four is a little piece only of our reality!!
Pages: [1]   Go Up
Print
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.16 | SMF © 2011, Simple Machines Valid XHTML 1.0! Valid CSS!