Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace intro page with core functionality #294

Closed
webbird opened this issue Mar 24, 2015 · 1 comment
Closed

Replace intro page with core functionality #294

webbird opened this issue Mar 24, 2015 · 1 comment

Comments

@webbird
Copy link
Contributor

webbird commented Mar 24, 2015

There are two main purposes for intro pages:

  • Let the visitor choose his preferred language when entering a multi lang site. (WYSIWYG-/HTML content)
  • Forward sub domain to appropriate page (Code content)

The first can be done with a "normal" CMS page, the only drawback is that one will have to tweak the page tree and the menu settings to hide that page from the menu.

The latter could be done tweaking the sub domain settings (if available in the provider's backend).

Both could be implemented into the core like so:

  • Option to forward the visitor automatically based on his browser language (Backend -> Settings -> Frontend (?))
  • Option to map sub domains to pages (Backend -> Settings -> ??? (Frontend?))

For a "manual" language selection, there's still the WYSIWYG-page way.

Benefits: The admin does not have to create or copy&paste PHP code found somewhere. Most users are no PHP developers and neither understand nor are able to tweak the code.

Forwarding by browser language:

Option (on/off) - only available if "Page language" is on (activated) under Backend -> Settings -> System settings
If on, provide mapping options like under Edit page -> Language Mappings

Forwarding by sub domain:

Option (on/off)
If on, provide extendable mapping options "Sub domain name" => "Page"

Prerequisites:

  • intro.php must be added to class_secure table
  • CAT_Helper_I18n function getBrowserLangs() must be declared as public
  • No "hard coded" server name in config.php
@webbird
Copy link
Contributor Author

webbird commented Sep 30, 2015

It works for the language, but I'm not sure if it does for the sub domains. So I leave this open for reference.

@webbird webbird closed this as completed Jun 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant