If you can’t install the update because your support license doesn’t permit you to, then just go into XML Source view and delete all of the occurrences of the processing instruction, as I described in this post…

I have a similar issue but not with XDP’s. This is a PDF. My base file was 35kb. After adding numerous fillable fields and testing it many times the size grew to 13MB. If I open it in Livecycle and save it, it grows and grows.
I’m on 8.2.1.4029.

Any ideas?

Pieter

Thanks for posting that script! I’m sure it’ll help a lot of people.

As for the other XDP bloating issue, I’ve never heard of this outside of the processing instruction bug. If it’s not that, then large, embedded images and/or schemas could be the cause, but you say you removed all images and data connections…

Looking inside the XDP using Notepad (or some other text editor), can you see any repeating nodes? Perhaps many processing instructions that look like “renderCache” (seeing some is normal but perhaps these are being repeated like the StyleID processing instructions)?

Otherwise, I would encourage you to provide Adobe with these XDPs so they can be further investigated.

We are not seeing any extra tags – in fact the XML Source looks identical to our other forms which only expand to about 2.5MB in XDP format (which is what we expect).

This occurs on very limited forms. Deleting Data Connections and removing images does not help.

Same symptoms – poor performance in Designer (sometimes it can’t even be opened on some machines), takes a long time to view XML Source, crashes Designer.

Just wondering if anyone has experienced this, and might have ideas as to what other areas we should investigate as a possible cause.

Thanks
- Duane

This bug has been around for quite a while – I remember it from the Designer 7 days. It had a patched version of Designer that fixed it, but seemed to re-emerge in 8. (And naturally Adobe only released the patched version to customers who complained about this exact behavior and had a support agreement)

For the benefit of any reading the blog, I’ll post here a perl script that we use to clean our XDP files (since in some cases we’ve found hundreds of thousands of lines of code that need to be stripped out). This leaves one instance of the tag and removes all repeated instances.

Download perl (I use strawberry perl). Then from command line run perl <yourperlfile.pl> <yourxdpname.xdp> It will create a new xdp file with a “new” prefix.

The actual templateDesigner tags can vary (ex. “aped3″ or “apcb1″) so you can just add extra if clauses for any specific tags affecting your xdp file.

#!/usr/bin/perl

#use strict;

use DirHandle;

my $sourcefile = shift;
my $outputfile = “new” . $sourcefile;

open SOURCEFILE, “$sourcefile” or die;
open OUTPUTFILE, “>$outputfile” or die;

$flag = 0;
foreach $line (<SOURCEFILE>) {
if($line=~ /<\?templateDesigner StyleID aped2\?>\n/) {
if($flag == 1) {
$line=~ s/[\t]*<\?templateDesigner StyleID aped2\?>\n//gi;
}
$flag=1;
}
elsif($line=~ /<\?templateDesigner StyleID aped3\?>\n/) {
if($flag == 1) {
$line=~ s/[\t]*<\?templateDesigner StyleID aped3\?>\n//gi;
}
$flag=1;
}
elsif($line=~ /<\?templateDesigner StyleID apcb1\?>\n/) {
if($flag == 1) {
$line=~ s/[\t]*<\?templateDesigner StyleID apcb1\?>\n//gi;
}
$flag=1;
}
else {
$flag=0;
}
print OUTPUTFILE $line;
}

close SOURCEFILE;
close OUTPUTFILE;

Hope that helps
- Duane

What I tried, with success, is this: Submit XDP data from a PDF that I was previewing in Designer, save the XDP file to a folder on my web server, move the PDF to some folder on my web server, change @href in the <pdf href=”…” …/> node in the XDP to be an absolue URL to the location of the PDF on my web server and hit the XDP in my browser. What happens for me is the referenced PDF is loaded with XDP data merged-in.

The only difference I can think of between my situation and yours is that when you view a PDF from the web (i.e. using the PDF plug-in), you’re using Reader to view that PDF and Reader cannot import data unless the PDF is enabled to do so using LiveCycle Reader Extensions.

If line in XDP is <pdf href=”./rozhodnuti1.pdf” xmlns=”http://ns.adobe.com/xdp/pdf/”/> then file is open and populated with data correctly.

if I copy the file rozhodnuti1.pdf to we server and change line in XDP to <pdf href=”http://server.com/rozhodnuti1.pdf” xmlns=”http://ns.adobe.com/xdp/pdf/”/> then file is open but NO populated with data.

Do you have some ideas ot recommendation?
I use Acrobat Reader 9.1.3

Best Regards, Vlada

If line in XDP is then file is open and populated with data correctly.

if I copy the file rozhodnuti1.pdf to we server and change line in XDP to then file is open but NO populated with data.

Do you have some ideas ot recommendation?
I use Acrobat Reader 9.1.3

Best Regards, Vlada

If your form file becomes very large at design-time and you see many duplicated lines that look like

<?templateDesigner StyleID apcb2?>

in the XML Source view, then you should delete all the duplicates except one.

When saving the form at runtime (in PDF format) after filling it, it’s normal for the PDF to grow slightly in size because it stores lots of information (state deltas and data) related to what the user has done to/with the form.

Single line: “?templateDesigner StyleID apcb2?”

Long code:
“ui”
“checkButton”
“border”
“edge stroke=”lowered”/”
“fill”
“color value=”255, 255, 255″/”
“/fill”
“?templateDesigner StyleID apcb2?””/border”
“margin/”
“/checkButton”
“/ui”