Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
I've just installed this package on a site as a potential replacement for the default tag datatype. However, I have a problem where it's not suggesting any tags at all.
My page is fairly complex, with several tabs, each containing various controls. If I add the datatype to a simpoler site, and paste in the same content as in the site that isn't working, it DOES suggest tags correctly, which suggests an issue with my other site, but I can't work out what.
Is there a way to get the datatype to log somewhere so I can see what (if anything) its passing to Calais?
We are currently logging the data requests using log4net. The config files for the logging can be found:
By default they're saving to c:\windows\autoTags.log, and you will also have to change the root/level value (to DEBUG I believe although not 100%) in order to get the general debugging/info messages to appear.
That said, have you tried running the requests using firebug or Fiddler to see if either one of those sheds any light on the error?
I've tried firebug, and it looks like it's posting the form values to the /base method, but the method's just returning an empty array. I'll see if I can get the logging running and see if I can see what the issue is.......
Still no joy getting to the bottom of this... any idea why it might return nothing? The same content in a simpler document returns about a dozen tags.
Yeah, this is a strange one.
If you can paste the form values (taken from the firebug request would be best/easiest) I can run them through the project to see whats happening. If you could also paste the contents of your autotags config file that would be useful.
Have you had any joy with determining the problem?
Sorry, been away on holiday! Will have a further look at this over the weekend and post the form values etc!
Any news on this?
Gah, sorry, been really busy and had forgotten to post this, the post details (from Firebug) are as follows (appologies for the abysmal formatting, copied straight from Firebug):
The response that's reveived is:
Config file contains the following:
<?xml version="1.0" encoding="utf-16"?><Config xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <GenerateTagsAutomatically>false</GenerateTagsAutomatically> <SelectTagsAutomatically>false</SelectTagsAutomatically> <AllowManualTags>true</AllowManualTags> <AllowTagSuggestion>true</AllowTagSuggestion> <ShowHelp>false</ShowHelp> <TagGroup>content</TagGroup> <OpenCalaisApiKey>[key here]</OpenCalaisApiKey> <ProxyUsername /> <ProxyPassword /> <ProxyDomain /> <Provider>GrailTechnology.AutoTags.Providers.OpenCalaisService, GrailTechnology.AutoTags.Providers</Provider></Config>
Just for my own sanity, you've removed your OpenCalais key from your post right?
LOL, yes! I took that out.
GRRR how annoying! I've just logged in to see whether you'd replied and it looks like my previous comment didn't go through?!?!
Ok so in summary (as my last one was a bit long) I tested with your data and it seemed to work fine, it came back with various suggestions; involving waste management i believe, so I don't believe it to be the package/service itself.
Looking through your comments I'm under the impression that this doctype is fairly large and complex? Is that right?
Also, if you look through the data you submitted theres a comment in there "Firebug request size limit has been reached by Firebug". I'm just wondering if the request size is too much? Perhaps it might be worth increasing the request size limit in your web.config to see if that starts playing ball?
Failing that I might have to try rewriting how the UI submits the data
Yep, it looks like its the size of the DocType. If I put the same content in one of the starter kits, it suggests stuff correctly.
Would the request size affect posts to remote services? I thought that was just for incoming requests? We've got it set to 40Mb, which should be plenty.
Is there a way of getting it to only use one or a few fields for the suggestions rather than the whole document?
Sorry for the lack of reply, I've been pretty busy of recent. Yeah, 40MB is enough for any web request I'd think....
I've got a week off starting Monday so I can put something together whereby it will only send across specified fields, providing this will still be of benefit and you havn't sacked this off?
That'd be awesome! I've basically hidden away the suggestions button for now, but it would be great to have the feature if you don't mind sorting it out?
We're using this tags control because its much better than the built in one, which has all sorts of issues when you tag and save or save and then edit tags. Plus the client loves the UI!
Great to hear positive feedback even in the face of a potential issue.
So what I'm thinking of is added a couple of fields to the config, a "Use only these properties" option and a "All except theses" option, would you say this would suffice or would you be after something slightly different/extra?
That would be spot on! Basically the doctypes are large because they have a lot of SEO/PPC settings, and widgets etc on the page, probably only two to five of the fields are actually "proper" content that needs to be looked at for suggesting tags.
I've uploaded v2.2.0 which includes the extra configuration values mentioned previously. Let me know how you get on :)
Have you had any joy with this?
I'm having the same problem with the latest version, tried both providers.At least one of the problems is, the package isn't sending content to the provides.
f4<?xml version="1.0" encoding="UTF-8"?><memes> <meme source="urn:memanage:E6063857C71351A393B6DBD74ABB5DB0" updated="Mon Sep 26 10:07:53 CEST 2011"> <dim type="language"> <item>unknown</item> </dim> </meme></memes>0
http://api.opencalais.com/enlighten/calais.asmx/EnlightenlicenseID=*******************&content=¶msXML=<c:params xmlns:c="http://s.opencalais.com/1/pred/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"><c:processingDirectives c:allowDistribution="true" c:enableMetaDataType="GenericRelations,SocialTags" c:allowSearch="true" c:contentType="text/txt" c:outputFormat="Text/Simple"></c:processingDirectives><c:externalMetadata></c:externalMetadata></c:params>
<?xml version="1.0" encoding="utf-8"?><string xmlns="http://clearforest.com/"><Error Method="ProcessText" calaisRequestID="cbb35521-3328-9053-132a-4ceb7ff4b31b" CreationDate="2011-09-26 03:16:43" CalaisVersion="R4.3_7.1.1103.5"><Exception>content is invalid: 'Empty' .</Exception></Error></string>
Strange, I'll check this out tonight and get back to you. Can I assume that you're not filtering on properties, you want them all to be included?
I've downloaded the package into a vanilla install of 4.7 and although there does appear to be a bug with the TagTheNetService not stripping out HTML, the OpenCalais service works fine.
Can you supply your autotags.config file please?
<?xml version="1.0" encoding="utf-16"?>
<Config xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
I've made a couple of tweaks to the code and uploaded a new release (v2.2.1). I've tested it on v4.7 of umbraco and it works fine, hopefully it should behave for you now kipusoep :)
Well, it's still not working for me, besides I found out your package is conflicting with the MultiNode Tree Picker from uComponents, because you're using a very greedy jQuery selector.
So I decided to stop using this package because it gives me too much trouble. Thanks anyways!
hmm, its a shame its come down to that. But in order to improve the package, can you give me any more detail into what you mean by greedy jQuery selector?
Well, just try it yourself; add a OpenCalaisAutoTag property and a Multi-Node Tree Picker property.Then select an item in the MNTP and save. Now try to delete the item and you'll get a JS error in the script from your package.
Had something to do with $("a") if I remember correctly...
It looks like its MNTP thats actually breaking this datatype. I added a mntp to a page with the autotag property on and the data isn't getting submitted to the rest service which is why you're not getting any results back. As soon as I removed the MNTP it worked first time.
So its looks like we've finally found the issue (its a pity its taken so long), and although I could argue that uComponents break my package as it came out first ;) uComponents is by far a superior and more widely used package so I'll look at getting a fix together.
Thanks for your assistance kipusoep
Hi - just about to install when i noticed the compatibility issue - any idea on when a fix might be implemented??
I'm aiming to get a fix released this week. Will post any updates in this thread :)
Ok, well after a lot of testing it appears that something with the MNTP is causing problems with ANY ajax post from data types. I've created a simple usercontrol datatype which simply posts to the handler nothing fancy the and Posted data is still empty. I've created a work item on Codeplex so if you could vote it up I'd be grateful: http://ucomponents.codeplex.com/workitem/14401
In the mean time I've discovered that if I change it to use a GET request everything seems to work ok. I'll get the updated version uploaded by monday
Both issues have been retified in v2.2.2. The fix for the tag suggestion isn't ideal but until uComponents fix the issue with the MNTP theres not a whole lot I can do. I hope this fixes the problems for everyone.
is working on a reply...
Write your reply to:
Image will be uploaded when post is submitted