"Show Links" not working in metaProfile

dschmidt · Post by **dschmidt** » Thu Feb 23, 2006 2:29 pm

When clicking on "Show Links" in a result set from a metaProfile, I get a message "No such document id". This works fine in a regular profile...

URL:
http://innovateforum.com/innovate/searc ... temization

Post by **mark** » Thu Feb 23, 2006 4:53 pm

I see that. A workaround is to turn on allow xml in the search settings for the member profiles. A fix is in the works.

dschmidt · Post by **dschmidt** » Thu Feb 23, 2006 5:40 pm

Thanks... Would turning on allowXML have any potential to negatively affect the member profiles as long as they are not used individually outside the metaProfile...

Post by **mark** » Thu Feb 23, 2006 5:50 pm

No, it's just a perm flag. Turning it on just makes things less restrictive. So someone could request results in xml format instead of html if they knew the appliance url syntax. There's no real danger in allowing xml except to make it slightly easier for others to fetch and republish your results with their style or name.

dschmidt · Post by **dschmidt** » Fri Feb 24, 2006 8:20 am

Hmm, i turned on allowXML in all the member profiles and still getting the same error... Is there anything else I might have to change?

Post by **mark** » Fri Feb 24, 2006 12:47 pm

Did you "Apply Appearance" to all of the member profiles?

What happens when you access the test search directly from the appliance instead of via your proxy script?

dschmidt · Post by **dschmidt** » Fri Feb 24, 2006 1:53 pm

Hmm, no, it doesn't. Are there any parameters added to the query that are exclusive to the meta search? I never had a problem with that before...

Post by **mark** » Fri Feb 24, 2006 3:02 pm

Not sure what you're answering here. There were 2 questions above. "no it doesn't" doesn't sound like an answer to either of those.

Yes, there is extra info in urls from meta searches. And when trying to debug odd behavior it's best to eliminate as many unknown variables as possible. People's proxy scripts have been known to mess up plenty of applications for various reasons. We can only support direct usage of the appliance, not people's own proxy scripts.