Solved What's up with not being able to post simple replies? (1 Viewer)

[cheekybuddha]

Remove the URI portion and it seems to work: Successful new post!

 

[The_Doc_Man]

@Doc, are you sure?

When I did the test it did nothing unusual. Not even a flicker - unless it lets me do that as a moderator. I don't have a "normal" account but Dave, I saw you asked for a test account to be created. With my number of posts, I surely have outgrown the post-count link filter, so I guess it is possible that I can't actually test it.

 

[cheekybuddha]

I surely have outgrown the post-count link filter, so I guess it is possible that I can't actually test it.

You and me both! That's why thought I'd try with a test account!
You can delete it if you want to.

 

[Uncle Gizmo]

with no one here willing/able to tell me the precise reason for the block, I guess my tenure here is involuntarily and preemptively terminated...

Well it's difficult to understand why you are the only one having these problems!

In my own experience, when I have a problem with MS Access and I am absolutely convinced there's a bug in it, and it won't work as I expect and it's infuriatingly annoying.... 99 x out of 100 it turns out to be user error,...

 

[sonic8]

Probably:
Code: "LDAP://dc=yourdomain, dc=com"looks like a URL to the crude regex parser

And the regex would be correct because it actually *is* an URL.

 

[The_Doc_Man]

I return to the issue that it is textual content.

@HavingDatabaseRelations - as an experiment, can you try to post the exact message AS TEXT that you previously screen-captured, but just before posting find every instance of LDAP in that text and make that L_D_A_P just to verify that - per Dave's suggestion - it is pre-screening your input. This is a problem with XenForo software that is our site's page engine. Most of us don't have any viewpoint into the actual code so can't tell what it is doing unless the vendor publishes something.

EDITED BY THE_DOC_MAN: Instead of LDAP to L_D_A_P, make it "L<space>D<space>A<space>P<space>:" Sonic8 is correct that syntactically it DOES appear as a URL, but the spaces would break up the continuity. Underscores would not.

 

[Gasman]

Wouldn't it be more the :// ?

 

[The_Doc_Man]

Possibly. But now we have reached the stage of second-guessing at what point XenForo says "IS/IS NOT" a URL.

 

[HavingDatabaseRelations]

Thanks for the help, everyone. I'm gobsmacked at the amount of resources you all have had to devote to this issue instead of my error when trying to pull an email address out of AD for a logged in user. Can anyone tell me what thread count I need to have to get past this level of scrutiny?

 

[Gasman]

You will need to be VERY patient, which I do not think is your strong suit.
I also responded to your crosspost.

 

[cheekybuddha]

Can anyone tell me what thread count I need to have to get past this level of scrutiny?

I think it sits at 100 currently

 

[cheekybuddha]

because it actually *is* an URL.

Is it not actually a URI ? (see post #41)

Joking aside, my guess is with @Gasman, that the pattern just matches on the '://'.

I'll test again when i get back to computer.

 

[cheekybuddha]

OK, so it seems as if it is purely dependent on finding ://

Trying explicitly:

results in:

Whereas simply doing:

is OK:

Using a resource but without completing the double forward slash is also OK:

The post goes through:

Curiously, getting the colon and slashes back to front also triggers the blocker:

like so:

So, @HavingDatabaseRelations, it really isn't anything personal against you - it's a PITA for everyone!