Issue: the wiki code doesn't automaticaly link anymore

Yeah, if the post is cached an autolink won't be created if the article is created later, because there is no record of that post trying to link to it, as there was no link. The link will only update if a BB-Code created the link, but even then the only difference will be the color. If this did not occur, tell me about the article that was created. Did you use any BB-Codes in it or no?

For example, I have the post index I created manually.

As you can see, I have few red links in it. When I click on one of them, I can write and save but after that when I go back to the post index, the link is still red even though the post exists.
Do you know what I mean?
2 days ago it worked perfectly and I don't know why it's no longer working.

Thank you for your help!

Was it working fine before for titles with spaces or accents?
Have you installed any new modifications?
Have you changed Settings > Options > VaultWiki: Server Settings > Replace Spaces in URLs?
Have you updated VaultWiki > Wiki URL Manager > Edit URL Replacements?

If you changed either of the last two, then the internal encoding of wiki pages was probably changed since the post was cached, so articles created with the new encoding won't match and the red links won't update. The only way to fix this behavior would be to clear the cache as you have done. However, you wouldn't continue to have problems since clearing the cache unless you made more changes after you cleared it. Does the problem still persist, or does it seem to have gone away?

Also, if Settings > Options > VaultWiki: Server Settings > Enable Link Caching is disabled, then the wiki doesn't store information about red links, so they can't be updated later through automation. If you changed this setting, that might be your problem.

Was it working fine before for titles with spaces or accents? Yes
Have you installed any new modifications? no
Have you changed Settings > Options > VaultWiki: Server Settings > Replace Spaces in URLs? no
Have you updated VaultWiki > Wiki URL Manager > Edit URL Replacements? no

If you changed either of the last two, then the internal encoding of wiki pages was probably changed since the post was cached, so articles created with the new encoding won't match and the red links won't update. The only way to fix this behavior would be to clear the cache as you have done. However, you wouldn't continue to have problems since clearing the cache unless you made more changes after you cleared it. Does the problem still persist, or does it seem to have gone away?

I didn't modify this option.

I forgot to tell you, I changed some settings in order to improve the forum speed :
All threads use now the caching, css style as well I don't know if this is the origin of the problem...

Please specify which settings exactly you modified. I don't think I'm familiar with the thread caching one.

Enable Post Cache & Cut Loading Time

The upside to enabling this option is that vBulletin will cache each post for a set amount of days, of which you can define in the Admin CP. Enabling this option will allow up to a 200% speed increase when displaying threads & posts. The downside, for those with limited disk space, is that enabling this option will take almost double the disk space compared to that of normal post made without this option enabled. If you have the disk space available, it is suggested you enable this option. The extra disk space used is valid for aiding in the optimization of your community and cutting down on the server load. How does this cut down on the load? Simply put, the less the server has to search for when pulling the data from the MySQL database, the less the load.

To enable this option, while in the Admin CP, follow the below. We suggest setting this option to increments of 30, 60 or 90:

vBulletin Options > Server Settings and Optimization Options > Cached Posts Lifespan

Source : http://www.vbulletin.com/forum/showt...s!-vBulletin-4!

Okay, if the Cached Post Lifespan was set to 0 before, when you weren't having problems, but now that you changed it to a higher number you are having problems, this is why:

VaultWiki didn't need to update the links before because the post always updated the link on every page load. Now, the link is saved with a cached version of the post and needs to be updated. While VaultWiki is programmed to do this, something is preventing this from occurring.

The only thing I can think of is that another modification is interfering with the process by setting the pagetext field to null when VaultWiki tries to read it, is destroying the $vault object, or preventing it from initializing.

Please post or PM a list of your currently installed modifications.

Thanks and it works when I desable the Cached Post Lifespan.

Ok I ll send you

It would appear that a required field was missing from an UPDATE query whenever an article is created. In vault/functions/data.php, find:
Add after:
This won't fix current links, but it should make sure new links are updated in the future.

It works!! Thanks