RC5.2 and link IDs

[vkaryl]

I thought I remembered that RC5+ was going to allow the disabling of link IDs. I'm still having the validation problem, though, so I must have misunderstood?

Here's one of the relevant pieces of parsed link code from the Links page:

Content visible to registered users only.

[Ap0s7le]

Completely different ID, the one that is optional is for the recip ID, so a partner doesn't require using an ID to link back.

Would the space be causing the problem?

-Casey

[kickass]

Casey, in xhtml 1.0 either transitional or strict the id in ANY tag is not allowed to start with an integer. So id="31" is a nonvalid construct and will not validate to xhtml standards. I posted this on the bugsheet awhile ago. I thought this was fixed in the new version, though I haven't gotten to the upgrade to check.

[Nobody]

So how can we come around this?

[Ap0s7le]

Here's what's going on.

When you click on a link, a piece of JS uses the ID to call a page which increments your hits for that link.

If you do not want to count hits, then we can remove that for your installation. IF you do want to count links, we would have to change direct linking, and use a redirect to get the same results.

Your choice, you let me know.

later

-Casey

[Nobody]

Sorry, my English is perhaps a bit lacking. About ten years ago now since I went to school in South Africa, and I usually don't speak English here in Sweden.

I realize ID inside the <a> tag according to the rec links, is for hits in counting purposes. If that's the case, I'd like to have the ID enabled.

[Ap0s7le]

It is enabled by default.

[Nobody]

Yeah, I noticed that. Thank you for your assistance!

[kickass]

I don't give a rat's fart about "hits" - I can just look in my stats prog for that. I want pages that validate. Tell me the fix please.

Going into the future, shouldn't the next release do this in a different way? So EVERYONE'S page can validate? It looks really really sloppy when a script produces code that doesn't validate.

[Ap0s7le]

I wasn't the one who initially started this project, so I'm not to blame in the matter. Typically if I create something, it'll validate.

Right now part of my personal site is messed up, and doesn't validate but I am all for web standards. It's going to be the only way that we'll be able to progress as a whole for the better of everyone. IMHO...

Anyhow, open up link.tpl and search for and remove
Content visible to registered users only.

Thanks

-Casey

[vkaryl]

Casey luv, that's not going to break anything else is it? I thought about just commenting that out several days ago, but you know me, I was pretty sure that (non-programmer that I am!), if I did something so seemingly simple, I'd trash EVERYTHING else....

[Ap0s7le]

*grin* Well dahling... it doesn't on my local...

Try it out and see, eh?

:twisted:

[vkaryl]

Heehee.... *laughing* Okay, I'll pick one of my dozen or so and take a flyer on it....

And I'll report back as soon as I see what gives.... by tomorrow evening at least, we'll be gone for a few days for Labor Day (can't stand it here with the idiots and the ATVs in droves.... *rolls eyes*)

[vkaryl]

Reporting back.... it validates just fine, and so far hasn't caused any problems that I can see. Next time I'll just tweak the thing that makes sense to begin with, and holler if there ARE problems....

Thanks Casey.

[kickass]

Yes. Thanks Casey. And if you can work on getting the REST of the issues re validation fixed, like maybe unencoded characters, all of us validation nazis would finally shut up about it . . . :wink:

BTW, didn't someone near and dear to us have a problem in an xml feed recently due to an unencoded character??? :o