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.

Error 500 if a ' is in the text of a Wiki page description.
This video doesn’t show the ' because it took me a few tried to understand why it failed but it is there (doesn't) . ?
Once removed (rewriting the sentence without) I could save the page description.

https://share.vidyard.com/watch/uYuxbDN2r4qEzzivSmoecy?

They may be other "forbidden" characters.

On Tiki22 the page won’t save (Error 500) if you enter more than 200 characters (white space included).

That wasn’t the case previously (19, 20... 21) can’t tell for sure but I use a lot Description of Wiki page as Meta Tags for SEO so I never seen it before.

Related to https://dev.tiki.org/item276-Multilingual-Meta-Keywords-and-Meta-Description-and-increase-255-characters-limit

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.

{syntax type="tiki" editor="plain"}
We have now a new option to set the "Content of the tag title" on the properties of a Wiki page.

We had a previous metatags field, "Page Description (used for metatags)" that can be enabled at tiki-admin.php?page=metatags

Enabling it add a field "Description (used for metatags)" to the properties of a Wiki page.

We have also "Will be added to the sitemap".

While these fields are related they are not grouped in the wiki page properties and all options seems mixed without any consideration as you can see in this example.

{img fileId="3139" thumb="box"}

Note: This is just an example other option, preferences and parameters based on admin settings should checked.

Anyway, these should be grouped in a more logical way having in mind the user experience.

{syntax type="tiki" editor="plain"}
I'm on Tiki Wiki 29 I enabled the Tiki Tags feature.
I'm using some tags on wiki page and I have set some tags.
But the keyword tags are not displayed in the head.

I went at tiki-admin.php?page=metatags (admin metatags).
I checked that "Include tags" is enabled. But I have also noticed I no Keywords set in the field Keywords.

As result I have no keyword on the page.
If I add just one keyword in the field, on the page i see this keyword but also all other missing keywords.

The condition for the elseif branch only triggers if either metatag_keywords or metatag_local_keywords is non-empty.

NOTE: I don't use forum so I didn't touch anything related to the way the forum fill its keywords. It may worth to have a look at it.

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

This tracker is made to help filtering and sorting the features vs categories vs options we need to tag a bug/regression/wish with.

There is no visible limit about the length of the description field in Tiki for the user.
However this field is limited and if you go over the limit you will have a white page when saving your work potentially losing your last edit.

{CODE()}
[Mon Jun 14 09:11:25.437718 2021] [proxy_fcgi:error] [pid 46913:tid 140057356769024] [client 10.0.0.138:52983] AH01071: Got error 'PHP message: PHP Fatal error: Uncaught TikiDb_Exception: Data too long for column 'description' at row 1 in /home/bernardsfez/public_html/lib/core/TikiDb/Exception.php:20\nStack trace:\n#0 /home/bernardsfez/public_html/lib/core/TikiDb.php(193): TikiDb_Exception::classify()\n#1 /home/bernardsfez/public_html/lib/core/TikiDb/Pdo.php(145): TikiDb->handleQueryError()\n#2 /home/bernardsfez/public_html/lib/core/TikiDb.php(101): TikiDb_Pdo->query()\n#3 /home/bernardsfez/public_html/lib/core/TikiDb/Table.php(130): TikiDb->queryException()\n#4 /home/bernardsfez/public_html/lib/core/TikiDb/Table.php(112): TikiDb_Table->updateMultiple()\n#5 /home/bernardsfez/public_html/lib/tikilib.php(5368): TikiDb_Table->update()\n#6 /home/bernardsfez/public_html/tiki-editpage.php(1227): TikiLib->update_page()\n#7 {main}\n thrown in /home/bernardsfez/public_html/lib/core/TikiDb/Exception.php on line 20', referer: https://bernardsfez.com/tiki-editpage.php?page=Comp%C3%A9tences+cl%C3%A9s+et+portefeuille+clients
{CODE}

It is an important bug (edit may be lost) on a popular feature (wiki page) and require an easy fix (real limit of text + small warning".
it should be fixed asap.

UPDATE:The value of the length accepted by the field in the database is 200 characters.
{img fileId="1608" thumb="box"}

This should be migrated to the community site, and handled with ((doc:Organic groups)) and ((doc:User Trackers))

Create ((PluginMeta)) as described in the subject.

You can use the plugin meta tag (https://doc.tiki.org/PluginMetaTag) to set a content for a meta tag on a Tiki object.
However this will be added as a new metatag in the -+head+- keeping any other value you may have set (admin, control panel same meta tag or automatic feature).

For exemple:
#I have at tiki-admin.php?page=metatags in the field description : "My very general description".
#In a wiki page about Tiki and I would like to have specific description for this page.
I set the following plugin
{CODE()}
{metatag name="description" content="Tiki is the best"}
{CODE}

After saving, if I check the page -+head+- the description "My very general description" is still there and I can see a second metatag for description with "Tiki is the best".

Results of having meta tag duplication (twice description meta tag) are unclear.
From page validation point of view it seems to be forbidden and bad.
From SEO (Google) point of view it is unclear if the second tag will ignored, will replace the first one or will be considered as an extension of the first one. This because it seems it depends of the meta tag (robot = extension, keywords = not used anymore, description = unsure ?, etc).

Each meta tag nature is different and Google may change its rules at any time.

So, to use the plugin meta tag, it should be advised to remove the "global" values for a meta tag which leave ALL the pages (object) without this meta tag.
Thus I have now to set the meta tag plugin on every pages (or objects). ?

It would make much better sense in real life to have the "admin" meta tags used by default and have the "plugin" meta tags used if they exist.

Also, as side effect it forbid from using the multi-lingual admin feature for meta tags (you can't use any)

On a Tiki22 I have multilingual, restricted language, page and site synchronised.

From Google I land on the English page.
I switch to Hebrew and then paste the french url on the browser bar.

The page language is French
The Tiki language is French
The keyword and description tags are Hebrew
{img fileId="1476" thumb="box"}
This will stay even after a refresh. Only if I click on the French language (language selector) even if it is already displayed as selected the tags will synchronise (all in French).

Now if from an external tools to check what my meta tags are I select the French version of the page (french name) It show me the right page in french, the right text in french but the meta tags, Keywords and Description are still in English.
{img fileId="1475" thumb="box"}

Somethings is not synchronised...
---
~~#F00:UPDATE~~: And this is messing with search engine and social network.
---
~~#F00:UPDATE~~: This happen when using SEFurl.
If you use domain.com/tiki-index.php?page=nameofyourpagenotinenglish it will work (site language will switch)
If you use domain.com/nameofyourpagenotinenglish the page will display but the site language won’t change. I can’t use SEFurl on show2 to demonstrate.

On a Tiki23 when checking tiki-admin.php?page=metatags I see the following error:

"Preference metatag_imagetitle is not defined" and "Error" in the value field.

Visible also on dev: https://dev.tiki.org/tiki-admin.php?page=metatags

I was doing a little testing with https://github.com/ffoodd/a11y.css. One of the errors it flags is -+ <head> must start with [charset] +- . Tiki doesn't have that exact meta tag, like -+ <meta charset="utf-8"> +- but it has -+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> +- .

A search turned up this information:
{QUOTE()}
Both <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> and <meta charset="utf-8"> serve the same purpose of declaring the character encoding for the HTML document. However, <meta charset="utf-8"> is the preferred method in HTML5 because it is more concise and easier to read.

The http-equiv="Content-Type" version was used in older HTML specifications like HTML 4.01, while the charset attribute is the standard in HTML5. Although both are still supported by browsers for backward compatibility, the simpler <meta charset="utf-8"> is recommended for modern web development.
{QUOTE}

I checked a dozen or so tech and popular websites and found only one - drupal.org - using the -+ http-equiv="Content-Type" +- version. Functionally, it apparently doesn't make a difference, but just to be up to date and use the modern syntax it seems like a good idea to update that (assuming there are no downsides to this change).

!!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))]

{syntax type="tiki" editor="plain"}
When you enable SEFurl you want to redirect all traffic to the SEF counterpart.

To have them also correctly out of reach of robots you have to uncomment the following elements in the robots.txt file.

{CODE()}
# == Begin SEF URL Section ==
# Remove pages in favor of the SEF counterpart (Enable only after SEF URL’s are enabled in tiki will otherwise prevent indexing.)
# Disallow: /tiki-forums.php
# Disallow: /tiki-view_forum.php
# Disallow: /tiki-index.php
# Disallow: /tiki-read_article.php
# Disallow: /tiki-view_blog.php
# Disallow: /tiki-list_file_gallery.php
# == End SEF URL Section ==
{CODE}

It was working till Tiki28.
But if you do it in Tiki29, a <meta name="robots" content="index, follow, NOINDEX, NOFOLLOW"> will be added to all the pages.

May come after this : https://gitlab.com/tikiwiki/tiki/-/merge_requests/6653

On a Tiki23 I use description for meta tag (may be unrelated) and if I insert a description that is more than 200 char (more than 199 I think) on save I have a white screen.