VaultWiki [Paid] 4.1.7 Patch Level 1

[DaveL]

There is a different "Number of Previewed" setting for each kind of page container. For areas, "Number of Previewed Area Contents". For books, "Number of Previewed Book Contents". etc.

Thanks @pegasus

All the other settings are showing at greater then 5, however only 5 pages are currently showing within the sub area.

 

[DaveL]

Also, In regards to the edit - There are two instances of that. Ive altered both, is that correct?

 

[pegasus]

You should only change the second instance.

On a side note, I'm beginning to grow tired of Eclipse always returning 0 results for a same-file text search.

If your preview-length is only 5 even though your setting is something else, you might have VW_IS_LITE set to true in your vault/config.php file. This will make your complete version mimic the behavior of the Lite version. But it's really only a developer setting, so you should turn it off.

 

[DaveL]

Brillaint, Thanks @pegasus

Im still getting the same errors as per post 339 despite making the edit you suggested. Any other ideas?

Also, in regards to the sidebar - When I created an area, I set it to display only "Find a Wiki Page" and "Share This Page" - However for some reason all the other blocks are still showing depsite having them unticked.

 

[pegasus]

I might have a different file than you since I'm using dev versions. According to the error message, it seems like the edit I suggested should be applied to line 604 on your site.

Also, in regards to the sidebar - When I created an area, I set it to display only "Find a Wiki Page" and "Share This Page" - However for some reason all the other blocks are still showing depsite having them unticked.

Are you sure it's the same area? I made the same selection as you and there's not any issue. If you're looking at a sub-area, keep in mind that the setting isn't inherited from its parents. Also, make sure you unchecked the "Any Block" option. This acts like you checked everything.

 

[DaveL]

I might have a different file than you since I'm using dev versions. According to the error message, it seems like the edit I suggested should be applied to line 604 on your site.

The first instance is on line 611 and the second is on line 788

In the post below you said only change the code on the second instance.

You should only change the second instance.

Should I change the second instance back and just alter the code on line 611?

 

[pegasus]

Yes, but knowing your line numbers now I realize that I was misunderstanding your issue. You were not having problems with the main discussion being disabled, but rather with "Any" and "User-Created" being disabled at the same time, while "Main Discussion" was actually enabled. In this case, you are entering into a conditional branch that should be logically impossible. To repair the logic:

In vault/core/controller/ui/discussion/vw.php, find:

            foreach ($this->area['topiclist'] AS $topicid)
            {

After it, add:

if ($topicid == -2) continue;

 

[DaveL]

Thanks @pegasus , i'll give that edit a go.

Shall I leave the initial edit I made in the other file or change it back?

 

[pegasus]

You should change the initial edit to the instance around line 611 as you suggested in your earlier post.

 

[DaveL]

I did post this in the Datatables thread by Jon W, however I thought it would only be right to post it in the VaultWiki thread as well.

For some reason, Auto linking isnt working within the table. Ive cleared the cache and also rebuilt URLs, however still to no joy. The term "Powerful Delta" auto links on all other pages, except within the table. This is the code im using with the Datatables mod.

[container][table=head]Destination|Plane|Fuel|Passengers|Speed Up|Stars|Item
[div][img]http://www.airportcitygame.com/images/Ancient_Egypt/Flights/Excavations_Ancient_Egypt-Stamp.png[/img][/div]Excavations: Ancient Egypt|Powerful Delta|row 2 column 3|4|5|6|7
row 3 column1|row 3 column2|row 3 column 3|4|5|6|7
row 2 column1|row 2 column2|row 2 column 3|4|5|6|7
row 3 column1|row 3 column2|row 3 column 3|4|5|6|7
row 2 column1|row 2 column2|row 2 column 3|4|5|6|7
row 3 column1|row 3 column2|row 3 column 3|4|5|6|7
row 2 column1|row 2 column2|row 2 column 3|4|5|6|7
[/table][/container]

As you can see, it auto links when not in the table, but dosent when it is inside.



If I can get this sorted, then im good to go!

 

[pegasus]

IIRC, Waindigo's TABLE BB-Code sets a plainChildren flag internally on its contents. I have no idea why the BB-Code does that, but it makes Auto-Links think that BB-Codes (such as AUTOLINK) won't work there. There's nothing really that we can do about this from our end without adding a specific rule for Waindigo's add-on. But it's better if Waindigo uses the API we have provided for this, since it's the add-on using an unusual behavior (defining itself as plain-text, but not actually being plain-text).

Waindigo's add-on can workaround this issue by removing itself from the AutoLink skip-list, which is defined in vault/core/model/parser/handle/autolink/vw.php. By creating a Code-Event Listener for event 'vw_autolinks_create', with listener code:

public function vw_autolinks_create($autolinker)
{
$key = array_search('table', $autolinker->skip_tags);
if ($key !== false)
unset($autolinker->skip_tags["$key"]);
}

 

[DaveL]

@Jon W - Is the above post something you would consider?

 

[DaveL]

@pegasus

Just a quick question - Is there a way to stop the titles of Areas from Auto-linking?

I have two areas called "Items" and "Buildings."

When I created pages I need to use these in the text such as :

Items Required:
Buildings Required:

However I dont want them to autolink to the actual "Items" or "Buildings" area. Hope that makes sense!

 

[pegasus]

There is a stop-word list for autolinks in Options > VaultWiki: Wiki Links > Auto-Link Ignore List, but there is a bug in the current version where it only accepts one entry.

 

[DaveL]

There is a stop-word list for autolinks in Options > VaultWiki: Wiki Links > Auto-Link Ignore List, but there is a bug in the current version where it only accepts one entry.

Ah cool, will have look at that.
Don't suppose you have any sort of eta for this part to work fully?

 

[DaveL]

Hi @pegasus

Sorry to bother you again, but im having a couple of issues with the autolinking.

You can see where it has autolinked here



However it hasnt autolinked below



Theres about 4 URLs im having the issue with - all similar to the above with "Excavations". They link on one page, but not another.

 

[pegasus]

You might have still have the default setting to only auto-link each word one time within a post. Also, I think if you manually link a word in a wiki page, it disables auto-links for the same word within the same wiki page.

The setting for this behavior is on the same VaultWiki: Wiki Links page. If you change this setting, it won't clear the post cache automatically. You have to do that yourself in Maintenance > Rebuild Counters / Caches > Cache Parsed Content.

 

[DaveL]

Hi @pegasus ,

Sorry, should have mentioned but these are on different pages.

 

[pegasus]

Have you checked the Source Code view of the page? If the RTE has inserted garbage into a word, the auto-linker won't be able to see it. Example:

Exca[b][/b]vations: Scandinavia

This example might happen if you are using bold-face on a word, then go to add/remove the markup using the toolbar button, but accidentally only select part of the word, then try again. Such an action has the potential to leave empty tags behind.

Without being able to visit the page that's not working, I can only give you guesses. In general, you should not rely on auto-links to create desired links. They are a convenience feature for other users to discover new content, not to encourage laziness when writing articles.

According to the official documentation on this feature, there are many reasons why auto-links won't appear, but the most important reason for NOT relying on them is that users have the option to disable whether they can see them: https://www.vaultwiki.org/pages/Help/VaultWiki-4-Manual/VW4:Auto-Links

 

[Jon W]

IIRC, Waindigo's TABLE BB-Code sets a plainChildren flag internally on its contents. I have no idea why the BB-Code does that, but it makes Auto-Links think that BB-Codes (such as AUTOLINK) won't work there. There's nothing really that we can do about this from our end without adding a specific rule for Waindigo's add-on. But it's better if Waindigo uses the API we have provided for this, since it's the add-on using an unusual behavior (defining itself as plain-text, but not actually being plain-text).

Waindigo's add-on can workaround this issue by removing itself from the AutoLink skip-list, which is defined in vault/core/model/parser/handle/autolink/vw.php. By creating a Code-Event Listener for event 'vw_autolinks_create', with listener code:

public function vw_autolinks_create($autolinker)
{
$key = array_search('table', $autolinker->skip_tags);
if ($key !== false)
unset($autolinker->skip_tags["$key"]);
}

Done. Since VaultWiki is a paid add-on and since I've not charged to add this, I've made this a premium feature so you will need to purchase a subscription from us. Hope this is acceptable.

https://xenforo.com/community/resources/datatables-bb-code-by-waindigo.2375/update?update=13976