|  WBCE CMS Home | Imprint | Privacy | Sitemap | 

General Settings

Website Title

The title of your website which is displayed in the default BE theme top left, is also used for the <title>-Tag in the template and, depending on your template, may appear in the header of your pages too. Technically, you can change it any time and use all and as much characters as you want (but there are SEO restrictions you should keep in mind).

Website Description

The value entered here will be used for <meta name="description" content="your text here"/>. Many search enginges display this text under the title of the page in their search results.

You can (and should) set individual descriptions for every single page. That means, if you give a description at the page settings, that text will be used; if the description field in the page settings is blank, the value you've entered here at general settings will be applied.

Furthermore, if you include simplepagehead in your template, Topics, Bakery and News items will use the descriptions you give them.

Website Keywords

You can enter general keywords here, but regarding search enginge optimization this is quite useless.

You can define individual keywords for each page at the page settings. The value you enter here at general settings is only used if the keywords field at page settings is empty.

Website Header

If the template supports the output of WEBSITE_HEADER, the code (HTML is allowed in this field) you enter here will be appear at the given position.

Website Footer

If your template supports the output of <?php page_footer(); ?>, the code you enter here (HTML is allowed), will appear at the given position.

Page Level Limit*

You can limit the value how deep your website can be structured. Setting a limit can be useful if your template's navigation supports only a limited amount of levels.

Please do not lower the value if there are already pages on deeper levels!

Page Trash

When activated (by default), pages you delete from the page tree are not quashed immediately but stored in a virtual wastebin. They are neither accessable from the backend nor from the frontend, but can still be restored. To quash them, you have to delete them one more time.

If you switch off the page trash, deleted pages are inreversible quashed at once.

Please notice that if a page is deleted, this is always applied to its child pages too, so be extremely careful when switching of the page trash!

The quashing of pages is irreversible!

Please notice that if you deactivate the page trash, pages which were trashed before are deleted finally; they do NOT appear if you re-activate the trashbin!

Page Languages*

If you build multilangual pages and you activate this option, WBCE CMS decides depending on the default language of a visitor's browser or the language selection in a user's profile which pages are displayed to a certain visitor/user.

That means, a user which has selected "English" as language in his profile, will see only links to english pages in the website's menu (if the page language is set accordingly).

If this option is deactivated, all users see all pages.

Multiple Menus*

If your template supports multiple menus (e.g. main navigation, meta navigation, footer links), this option has to be actvated (what is the case by default).

The assignment of a page to a certain menu is made at the page settings.

If you have already assigned pages to other menus than the main menu (ID=1), you should not switch off this option, because in that case the pages which were assigned to the other menues are not reachable from the navigation and have to be assigned to the main menu manually one by one.

Personal Folders

If you maintain a site with several users and switch on this option, you can assign a sub directory of the media directory to a given user at the user settings. In the backend, the user directories can only be accessed by the corresponding user(s).

But!

  • This setting has NO impact for the frontend view, that means, any content of the user folders are accessable for visitors and other users.
  • Users without an assigned folder have backend access to all media directorys, not only the root but the other user folders too.

So in fact this is all a quite useless.

Manage Sections*

Here you can disable placing more than one section in a block. That means, if your template consists of one block, you can put there only a single section, and if you have more than one block in your template, each block can contain only one section.

If you disable section management and there is already more than one section in a given block, this section is still accessable via backend and frontend, but you cannot alter the ordering of the sections any longer and you can't assign any sections to other blocks neither.

So just leave this setting enabled.

Section Blocks*

If a template supports more than one block (most timely templates do), this setting has to be set to its default value, e.g. "Activated". Otherwise, all sections are assigned to the main block.

You can switch off this option if your template has only one block, but this has no advantages. Just leave it activated.

Intro Page

If you switch on this value, you will see an additional link "Edit intro page" where you can alter the contents of the page.

The intro page will be displayed when a visitor accesses the main URL of your site, (e.g. http://yourdomain.tld/). You can put there a language selection or something else, but please consider, that most visitors are annoyed of intro pages and these pages usually have negative impact on the search engine optimization efforts.

The intro page is placed out of the usual structure, that means, you can't use there any template functions, and the template of your site is not assigned to this page. So if you want to use the stylesheet of your template, you have to set the link to it manually and build the complete HTML structure which should be applied to the intro page by yourself.

The intro page's content is stored if you disable it, so if you need it lateron again, you do not have to start at zero.

Homepage Redirection*
  • If a visitor points his browser to http://yourdomain.tld and the homepage redirection is enabled, the visitor will be redirected to the first page of your site. If your first site is named "home", in the address bar of your visitor's browser will appear "http://yourdomain.tld/pages/home.php".
  • If this option is disabled, the visitor sees just http://yourdomain.tld until he navigates to another page of your site.
  • If you have built a multilingual site, or the first page of your site is a menu link for any other reason, the enabling/disabling of this option makes no difference, since in this case the visitors are always redirected to the first "real" page of your site, e.g. http://yourdomain.tld/pages/en/home.php.
Smart Login*

Has no impact. In former versions the login data was stored in a cookie so that the fields on the login dialogue were pre-filled. Has been deactivated for security reasons.

Login

You can switch on/off the possibility for users to login from the frontend.

  • If this option is activated, and this feature is supported by the frontend template, the visitors will see a login form on your page. Furthermore it depends on this setting if the "loginbox" droplet generates any output.
  • Pages with the visibility "private" or "registered" appear in the navigation only if frontend login is activated.

So if you wonder why certain pages are missing in the navigation or the "loginbox" droplet seems not to work, you will probably just have to enable frontend login.

 

Redirect after*

Setting how long error and success messages are displayed in the backend. The default value of 1500 means one and a half second. Setting this to -1 means that every message has to be confirmed manually.

Sign-up

If you have created a user group before, you can select it here to allow visitors of your site to register themselves as a member of this group.

You should be very, very careful with this option! The group to which users can register for should have only reading access. In worst case, users could damage your whole site or place malicious code on it if they were granted to much access rights.

Also, you do not get any notice if a new user is registered, and there is no way to accept/decline registrations by an administrator.

So you'd better use this option only in protected environments, i.e. Intranets, where you can trust all visitors.

PHP Error Reporting Level*

If you are a developer and/or are asked to switch on error reporting by a community member in a support forum thread, you can switch this setting to "Show all errors and warnings (development)". This is useful if you encounter any issues while developing a template or working on/with modules.

The default setting is "Use system default (php.ini)", because the PHP error messages can contain confidentional information, which better should not be presented to the public (and they don't look very nice neither). So just alter this setting if necessary and don't forget to switch it to this setting again, or, if there are still errors/warnings appearing, to "Hide all errors and notices (WWW)".

Please notice, that on some shared hosting environements this setting has no impact, and the provider has deactivated PHP error messages for security reasons permanently. In this case, you might have to put some code in a .htaccess file or you can access PHP error logfiles on your server - please contact your webspace provider for more information.

WYSIWYG Editor*

You can choose which WYSIWYG editor (which is installed as a module) you'd like to use for WYSIWYG sections and other input filelds where a WYSIWYG editor is supported.

The default setting is CKEditor. Setting this to none will force you to enter plain HTML without syntax highlighting. Brrrr....

* displayed only in "advanced" view.