Family Historian User Group

I am trying to edit the KB without much success today.
The majority of attempts to Save an edit result in a 403 Forbidden message as below.
Attempts to workaround that often produce a firewall blocking message and all attempts to use the reCAPTCH to Unblock get nowhere.
Thereafter, even access to the Forums is blocked for a while. HELP!

On further trial and error it seems a particular table structure is the cause.
I am investigating exactly what part of the structure is to blame.
I have found the two lines but cannot post them here as it produces the 403 error message.
See contributeyourknowledge:edit_links_and_media#namespace_conventions|> Namespace Conventions that contains those two lines, which if removed allow page to be Saved, but otherwise produces the 403 error message.
They are the second set of rows referring to page1 and page2 in the table.
It appears to be the double primes '' in the last column of the page1 row that is the culprit.
i.e. '':wiki:ns1:page1''

This is a problem "above my pay grade", my guess is that particular pattern is matching a virus signature of some sort. Krystal have some very advanced tools which check and try and prevent attacks at source.

I have just edited the Namespace section with out errors. It's possible the problem has been corrected. Can you check it again please.

Thanks for the feedback Jane.
I removed the offending double primes not only on that page but also in another copy of same table at contributeyourknowledge:edit_links_and_media#namespace_conventions|> Namespace Conventions.
That is why you were able to edit the page.

I've checked by re-inserting the double primes, and it is still a 403 problem.

I don't know what you mean by a double prime. If we can live with out them I suggest just leaving the page as it is.

I am using the terminology from https://en.wikipedia.org/wiki/Prime_(symbol) but otherwise described as double single quotes and illustrated in my earlier posting as '':wiki:ns1:page1'' and composed from the Wiki TT button to produce ''Monospaced Text''.

I have tried using various alternatives such as ''home:ns1:page1'' and ''home:name1:page1'' but all produce the same 403 error, so I have had to forgo the monospaced text in that position.
The problem only arises in that position within the table, and the same structure outside the table is OK.
So will just have to live with it.