hmm with the category mapping modification i've made. It checks whether or not the category correctly maps to a sub category.
If it doesn't map then it appends a > to the end which is can then use in another script to determine which one's haven't been mapped.
The problem i'm having is after the > has been appended, when i try re importing the feed, it's not mapping correctly because the category has a > on the end of it.
I have a separate script i use to test it, and i can't seem to find any problems with that.
{code saved}
Unsure where the > is coming from after the category should match, Think i'm overlooking a piece of the code?
Thanks for taking a look.
Steve
Yeah i think that did the trick, everything seems to be mapping correctly now, just have around 200 categories to map :P Oh well should be nice when it's working.
NO doubts i'll be hassling you again shortly, cheers :)
Hi Steve,
It's probably just down to "normalisation" (making things safe for URLs), which since you're managing your own categories can probably be removed. It's not 100% essential since the script does urlencode() where necessary but it does make for cleaner URLs.
To remove the normalisation; look for the following code in includes/admin.php (line 189 in the distribution)
$importRecord["category"] = tapestry_normalise($importRecord["category"]);...and either comment out or delete that line, and then re-import.
Hope this helps!
Cheers,
David.
--
PriceTapestry.com