sova wrote:
I've tested
But on the XNews module does not work

wishcraft wrote:
The meta_description tag should be only used when the 'system' module is indexed, otherwise it only indexes the description and not the page, also the keywords should contain keywords in the URL (This is when you are using .htaccess to SEO the URL). And you need to include the apple touch icon's for iOS (iPad, iPhone etc.) when it saves a URL, instead of the desktop having the normal default icon it will have the one you specify.. The following examples should be done, in your theme's like so, this is part of the (Extreme Theme Framework).

Meta Keyword Framework Example

<!-- This is the replace for the meta keywords - Makes Unique Keyword Sentence with NO KEYPHRASES - A KEY PHRASE IS AN INCORRECT USE OF THE META TAG 'KEYWORDS' -->
<meta name="keywords" content="<{php}>
<!-- There will be errors in $search from the code display in xoops.org -->
$search = array(' with ', ' and ', ' the ', ' there ', ' their ', ' they're ', ' are ', ' to ', ' when ', ' on ', ' by ', ' you ',' ','.','<','>','"',';',':','}','{','[',']','|','\','/','=','+','-','_',')','(','*','&','^','%','$','#','@','!','~','`');
$minimumwordlen = 3;        
// Gets Meta Data
$path = str_replace($search, ',', str_replace(basename($_SERVER['REQUEST_URI']), '', $_SERVER['REQUEST_URI']));
$sitename = htmlspecialchars_decode($this->_tpl_vars['xoops_sitename']);
$slogon = htmlspecialchars_decode($this->_tpl_vars['xoops_slogan']);
$pagetitle = htmlspecialchars_decode($this->_tpl_vars['xoops_pagetitle']);
$keywords = htmlspecialchars_decode($this->_tpl_vars['xoops_meta_keywords']);
$description = htmlspecialchars_decode($this->_tpl_vars['xoops_meta_description']);
$nophrase = str_replace($search, ',', $path.str_replace($search, ',', $sitename).','.str_replace($search, ',', $slogon).','.str_replace($search, ',', $pagetitle).','.str_replace($search, ',', $keywords).','.str_replace($search, ',', $description));
$keywords = array_unique(explode(',', $nophrase));
foreach($keywords as $id => $word) {
    if (strlen($word)<$minimumwordlen||is_numeric($word)) {
        unset($keywords[$id]);
    }
}
echo implode(', ', $keywords);<{/php}>" />

Meta Descriptions Framework Example

<{if $xoops_dirname eq 'system'}>
    <meta name="description" content="<{$xoops_meta_description}>" />
<{/if}>

Favorite & Apple Touch Icons Framework Example

<link rel="shortcut icon" type="image/ico" href="<{$xoops_url}>/favicon.ico" />
<link rel="icon" type="image/png" href="<{$xoops_url}>/icon.png" />
<link rel="apple-touch-icon" href="<{$xoops_url}>/apple-touch-icon-56x56.png">
<link rel="apple-touch-icon" sizes="72x72" href="<{$xoops_url}>/apple-touch-icon-72x72.png">
<link rel="apple-touch-icon" sizes="114x114" href="<{$xoops_url}>/apple-touch-icon-114x114.png">

tatane wrote:
Quote:

redheadedrod wrote:
Personally I think REQUIRING composer to install xoops is a bad decision. It works (sort of) while under development but it will be a cause for much grief moving forward. A package that a user installs must be seamless and include everything.

I could be wrong but until composer is a default inclusion in PHP I think it is a very bad decision to force people to install composer in order to use xoops. I don't think it is a bad idea to include the code with the installation so someone could update the included packages if they want but 90% of the users that are going to want to install xoops will not want to fuss with having to have to install something else first and it will be a very big and continuous support issue.

+1