I don't think link tags cause worse havoc than any other tag where mismatched quotes are concerned.
I was thinking of that unable-to-edit, ita-had-to-get-under-the-hood thing. Has that been fixed?
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
I don't think link tags cause worse havoc than any other tag where mismatched quotes are concerned.
I was thinking of that unable-to-edit, ita-had-to-get-under-the-hood thing. Has that been fixed?
That's the same havoc -- doesn't matter which tag broke it. The key difference is if you open with a ' or a " -- affects where it gets closed.
Jon's coded the fix. I haven't implemented it yet.
Yeah, I fixed that. That happened because the t form tags got caught inside the open quoted mess. I moved the tags to points further up and down the page. Probelem Sol-ved.
Jon's coded the fix. I haven't implemented it yet.
Speaking of which (and I don't mean to sound like I'm harassing you. Really), how's the implementation going for that all all the other mods?
I'm sifting them out one by one and looking at them that way, Jon. I want to make sure there's no cross-pollination of weirdness.
Not suggesting for a moment that we don't all write perfect code the first time, or anything.
And then I have to check they don't conflict with any of the changes I implemented in the meanwhile.
Not suggesting for a moment that we don't all write perfect code the first time, or anything.
Heh. I'd be shocked if you didn't find an error somewhere.
t off to see Harry Potter with my brother
I'm no regex expert so I've no idea if this is doable, but is there a way to look inside every tag that takes parameters (like a href or font) and "close" every "open" single or double quote?
I think that's heading toward a parser again.
How about this -- we grab the contents of every tag, and count the quotes in it. If it's not an even number, throw the error. Brute force again...
I like John's idea. We can require attribute authors to use the entity forms for quotes inside of attributes, if they want to use them in odd quantities.
I was thinking about that outstanding bug/feature where, when you've quit the browser, you're unable to auto-log back in, using "remember me", directly to the message centre, you get taken to the index page.
Here's the code:
if (!$_user || (!is_array($_user->subs))) { Header("Location:" . URL_path() . "index.php"); }
and I'm hampered only by two things: not knowing where $_user comes from, and where $_user->subs comes from.
I have a copy of the board from a while ago, which predates "remember me", so I can't actually test it, but obviously it's failing one of those tests, either the user doesn't get auto-logged in on this page, or they get logged on but it can't retrieve their subscriptions.
This behaviour also happens if you have no subs and go to the message centre, is that still true now? Rather than it saying "you have no subs, can't help you" it returns the user to the front page?
[Thinks to self: you can test that you know!]
[Goes to test]
[Comes back]
If I have no subs, that's what happens, I get taken to the front page, (and the link to the message centre disappears).
Is it a fair assumption that the message centre is trying to check the subs too early or something?
If we took out that second boolean, what terrible consequences would ensue? People with no subs would get an empty message centre?
Coming back with the answer to my question -- rather than showing no threads, it shows all threads. So the tweak would be to check for subs then put "you have no subscriptions, you need the edit profile page" for these hapless users. But who are they anyway? People with no subs don't see the Message Centre link anyway, so how did they get here?
Am I being annoying? Sunday morning, nothing to do, lots of coffee, sorry.