MadCap Software Forums

I have been trying to publish some WebHelp output to SharePoint. (I would rather publish directly to a secure ftp location, but SharePoint is currently my only option).

Nearly all files upload correctly, but a handful do not. These all have as a common factor a size over 200kb. (They are not huge files; just larger than than 200kb.)

I can upload these files directly within SharePoint, so the issue (as far as SharePoint is concerned) is not the size. Uploading the files that way doesn't update them in Madcap's output log, though. Each time I try to upload any new Webhelp content, the upload gets stuck on those files until a time-out is hit, then Madcap moves to the next.

As SharePoint is okay with the files when uploaded directly, I'm thinking the cap likely resides within Madcap. Some of these are image files that should be reduced anyway, but the key (and largest) one is

/Content/SkinSupport/MadCapAll.js (414kb)

I don't have the option of lowering the resolution on that, and it's a required file. So ... where is the 200kb limitation coming from, and how can I modify it?

Thanks for any insights you may have.

I thought I replied to this one, but perhaps I dreamed it. So forgive me if this is a repeat . . .

200kb seems very low for an upload limit. Could it be a timeout? Perhaps Flare accessing SharePoint is far slower than a direct access to SharePoint, so perhaps SharePoint times out before the upload has completed?

Just an idea.

I considered that as a possibility, Msquared, but I don't think the timeout itself is the problem. Files of <= 199KB -- a few seconds at most. File of 201KB -- The "publish" process sits on the "Uploading content ... " point, then after 100 seconds, instead of "Succeeded," the file is flagged as "The operation has timed out," and Flare moves on to the next.

Even the option of bypassing the one remaining problem file (\Content\SkinSupport\MadcapAll.js, 414 KB) would help, as I wouldn't have to wait that 100 seconds every time I upload the balance -- but, as it is, I have to wait each time. As I noted earlier, the file can be uploaded from the SharePoint side but that doesn't serve to update Flare's logs, so Flare doesn't know it is present on the SharePoint site and keeps trying (and failing) to upload it.

Uploading everything from the SharePoint side is not an option because that presents its own problems. SharePoint (at least the configuration I am dealing with) has a 100-file limit; doesn't do well with subfolders; and wouldn't recognize the "new or changed" indexes. Uploading from Flare is definitely the better option. If I could find what is imposing the size/time limitation on 200 KB and up, that would make everything work as intended.

I appreciate the thought, though.