Category: Meta Tag

Please increase the limit and make it multilingual

When adding a folksonomy freetag to a page, it would be nice if Tiki automatically added the tags to the META KEYWORD tag for the page.

When you view an article, the URL simply includes the id# of the article. On wiki pages, however, the URL lists the article title.

You cannot assign meta tags to individual pages. If you use the universal meta tags, that is not the best way to optimize for search engines.

This is still a problem in 3.0rc1


Sorry - just spotted that this bug ===has already been reported as #2141=== but hopefully the additional information provided here will help resolve this more quickly.

You can no longer set/change the meta robots setting in Meta Tags Admin ie the NOROBOTS, NOFOLLOW settings

When you fill in the form field and click the Change Settings button the field blanks and viewing the HTML page source code shows that nothing has happened. The "revisit after" field works fine however.

Old 1.9 sites work fine and sites that have migrated through to 2.2 from 1.9 have their old values preserved but they cannot be changed. New 2.2 sites cannot have the setting established.

Examining the database for a new site shows that the metatag_robots row in the tiki_preferences table is missing. Hacking the table to add the row with appropriate values allows the appropriate HTML code to be generated in the head section of each page BUT the admin form still does not work.

Have also now spotted that ticking any of the Meta keywords options e.g the "Insert freetags in keyword list" and changing the settings does seem to set that option BUT the tick box is then blanked and then there is no way to 'untick' the option or you are not sure if it has been set or not.

very old bug - now fixed/not relevant

I'm using TikiWiki 2.2. and tried to enter the following in the "meta robots" field of the Meta Tags admin panel:

-index
-follow
-index, follow

As per http://doc.tikiwiki.org/tiki-index.php?page=Meta%20Tags&redirectpage=Meta%20Tag these seem to be valid values.

Once I pressed "change settings" the parameters I entered were gone. When checking the source code of index.php I found out that no robot instructions have been included.

Looks like saving those data doesn't work.

The implementation of favicons is incorrect for types other than .png.

Tiki currently renders the favicon as:
{CODE(caption="Current rendering",ishtml="0")}<link rel="icon" href="favicon.png" />
{CODE}

Notice that there is no declaration of MIME type (very bad). If you goto Administration | Look & feel | Other, there is a pull-down box to select the favicon icon MIME type, which gives choices:
* image/png
* image/bmp (wrong!)
* image/x-icon (wrong!)

None of these selections actually effect the LINK tag! In other words, someone forgot to implement the MIME attribute of the link tag. Even if it was implemented, these choices would be wrong (see solution).

Also on the Look & feel | Other page, there is a 32 character limit on the favicon icon file name. This limit is too small and is problematic for sites where the favicon is not located in the tiki root directory.

For future versions 11 ? 12 ?

Hi,

There are several main marked up languages that we know well.

I think that it will be useful to be able to exchange (import, export) documents with other selected marked up languages.

!!I particularly think to two categories :

!!!1- The task and documents managers used by development tools : Eclipse-Mylin Aptana environment and Bugzilla

Remark :
About this category, I redact documents using textile to describe the developments integrated into projects and bugzilla.
This because I have near fifty elementary project developed since 4.0, stabilized at 8.3 and that I am preparing for 10.x. (They remain for most of them available and someones must be adapted - galleries particularly)

!!!2- The wikies
The problem is to exchange data with users of main wiki.

The need is to use the large capabilities of tikiwiki to hold projects management and documentation. But as it is not specialized it cannot be directly used.

!!There are several ways, this is completely opened :
1- Be compatible i/O with textile which is very closed from basic tiki marked up language. This for basic articles.
2- Develop a plugin using tikiwiki as marked up language for Mylin
3- Look farther with a full XSL XSL-Fo (note that with eclipse all marked up supported languages can be exported as XSL-

!!On the way, proposal
1- First : list of major marked up languages for wiki and task managers
2- Links import export existing from one to another
3- Choose the optimum
!!
Aim :
- Prepare use of tikiwiki in project management
- Be compatible with environments as Eclipse to with other project management tools

!!Reason(s)
- Tiki provides a lot of coherent and very useful tools to manage the content of projects (documents and detailed task management, studies) and groupware life and management which is the core of project management (the classical tools for planning are only in my mind a little part). __But it cannot be connected with specialized existing tools and information systems in various businesses. The problem and aim is to prune efficiently tikiwiki into these organizations.
__
Trebly

Features Classification

Contributors

Contributors

!!Problems

__Pretty Much Resolved by the wiki ALIAS function__ - so closed.

Redirect plugin
*is not included by default in TikiWiki because it could be used for bad things
*creates redundancy (in search results, page listings, etc) - maybe redirected pages should not appear in list?

Renamed pages
*do not automatically redirect - creates broken links.


!!Proposed solution:

!!!renamed pages
*When a page is renamed the user must choose "hard or soft redirect" perhaps better known as "redirect or refer from old page?"
**hard redirect places redirect plugin on pagename-old to pagename-new.
**soft redirect puts something at top of page like
^This page has been renamed: pagename^


!!!Add synonyms/aliases to a page

suggestion (mlp): adding aliases to a page should automatically create pages with hard or soft redirects to pagename. Note that the adding of alias pages must not destroy data if page already exists.

Ex.:
dev.tikiwiki.org/Tracker
dev.tikiwiki.org/Trackers
dev.tikiwiki.org/Bug tracker

would be aliases. It would avoid the pollution we have here: http://dev.tikiwiki.org/tiki-orphan_pages.php


doc.tikiwiki.org/Install
doc.tikiwiki.org/Installation
doc.tikiwiki.org/Installer

Each wiki page should be able to put one or many aliases. These aliases would work in search. All the aliases should have an important weight in the internal search engine.

We could use this instead of renaming pages. Also, when we do rename a page, we could have an option to have the old page name to be an alias of the new one. Thus, better for external search engines.

Theses aliases could even be used as meta tag for this page.

Putting aliases to non wiki pages (ex.: tiki-forums.php) would make ((doc:structures)) more useful. Now, using structures for site navigation only makes sense if you only have wiki pages. And who ''only'' wants to have wiki pages with all the great features offered by TikiWiki? :-)

It also help to use cleaner page links in sentences. If my Wiki page is called Install, I have to do the following now:

{img src=images/code.png}%%% {CODE()}
For more information about ((Install|Installation))
{CODE}

With aliases, I could do:
{img src=images/code.png}%%% {CODE()}
For more information about ((Installation))
{CODE}

Page aliases - and hard redirects - should permit to set status "Moved Permanently" for robots to send traffic to main page.

What would we do with page renames? (which correct links in wiki pages). Needs some thought. We don't want some unwanted changing of text in existing wiki pages.


Do we need?
Redirect to internal or external http is ok because a special permission is needed to use. -> tiki_p_wiki_alias . In security admin, warm that giving tiki_p_wiki_alias to untrusted people is a security risk.


Related:
[wish1119|Better handling of page renaming]
[wish1610|Redirect plugin : should permit to set status "Moved Permanently"]
[wish1292|Plural WikiWords when using ((WikiWord))]