Yeah, I may have lead you down the wrong path a bit…
To be honest, I don’t think it was “index.php” sensitive until Tag 2.1.2, so it threw me off too

I’m going to see if it’s possible to have the next release not be sensitive to this, as it’s petty silly

I just upgraded from 2.1.1 to 2.1.2 and now the “suggest tags” button does nothing anymore. It worked before.

The CP path has always included index.php.

My bad. I copied jquery to the wrong place.

Not sure if this has been mentioned or not but I’ve recently noticed what appears to be a bug. That is, the tag suggestion will not suggest tags that have a space in them even if the exact word is in the text body. So if I have a preexisting tag of “sol space” and I have the two words “sol space” written just like that in the text, it doesn’t show up in the tag suggestions.

mikeyoung - 03 October 2008 11:07 AM

Not sure if this has been mentioned or not but I’ve recently noticed what appears to be a bug. That is, the tag suggestion will not suggest tags that have a space in them even if the exact word is in the text body. So if I have a preexisting tag of “sol space” and I have the two words “sol space” written just like that in the text, it doesn’t show up in the tag suggestions.

Mike,

This is a known issue for quite some time and has actually been corrected in the upcoming release of Tag 2.? (yes, 2.?)

mikeyoung - 03 October 2008 11:07 AM

Not sure if this has been mentioned or not but I’ve recently noticed what appears to be a bug. That is, the tag suggestion will not suggest tags that have a space in them even if the exact word is in the text body. So if I have a preexisting tag of “sol space” and I have the two words “sol space” written just like that in the text, it doesn’t show up in the tag suggestions.

This has been corrected with Tag 2.5