Hi lukaspovilonis, in regards to the issue with lines of XML getting cut off around 6875+ , this has been logged as a known issue in our tracking system. There is not a target date for getting this issue addressed yet but our devs are aware of it. We will let you know when the fix is available.
In regards to the other errors you're experiencing, see our responses and follow up questions on the related post: https://community.skuid.com/discussion/8015362/skuid-sfdx#latest
@Jack Sanford @lukaspovilonis I've got good news here. The issue with XML lines being cut off upon pushing pages has been fixed in the latest version of skuid-sfdx (0.4.0). I've posted back in lukas's post about this (https://community.skuid.com/discussion/8015362/skuid-sfdx) as well.
In order to upgrade to the latest version of skuid-sfdx, you'll need to run sfdx plugins:update on your machine. You can then run sfdx plugins to view the list of plugins, and verify that skuid-sfdx is now on 0.4.0. If for some reason this does not work, you can also uninstall and reinstall plugins, but this is a bit more tedious (would require running sfdx plugins:uninstall, then running sfdx plugins: install for each plugin you were using).
sfdx plugins: install
If you guys have any issues with the update, please let us know!
@Jack Sanford I need to correct my last post. The issue has been fixed for skuid-sfdx only. For deploying Skuid pages between Salesforce orgs, we are now recommending the use of skuid-sfdx in place of Skuid CLI. If you're able to make the switch to skuid-sfdx, you'll be able to take advantage of fixes and new features for deploying Skuid pages on Salesforce. Let us know if you have any questions around this.
For more detail:
Apologies for the previous misinformation!
I am getting an error that I believe is the same as above.
Encountered premature end of XML: no more data available - expected end tags </rows></section></sections></skuid__form></components></division></divisions></skuid__grid></components></step></steps></skuid__wizard></components></skuid__modal></action></actions></actionsequence></actionsequences></resources></skuid__page> to close start tag <rows> from line 283 and start tag <section> from line 283 and start tag <sections> from line 283 and start tag <skuid__form> from line 283 and start tag <components> from line 283 and start tag <division> from line 283 and start tag <divisions> from line 283 and start tag <skuid__grid> from line 283 and start tag <components> from line 283 and start tag <step> from line 283 and start tag <steps> from line 283 and start tag <skuid__wizard> from line 283 and start tag <components> from line 283 and start tag <skuid__modal> from line 283 and start tag <action> from line 283 and start tag <actions> from line 283 and start tag <actionsequence> from line 283 and start tag <actionsequences> from line 283 and start tag <resources> from line 63 and start tag <skuid__page> from line 1, parser stopped on END_TAG seen ...</fields></row></r... @283:279198
This is on my public site.
Can I get around this by using page includes on the public site?
@Bill using page includes can reduce the number of lines of xml in a given page. What happened right before you got the error, were you working on the page in the page builder or did you deploy from somewhere else?
The team has made a patch for the line limitation issue in the core package, and since the CLI is a separate program, it's important to have the most up-to-date version of Skuid(Boston or higher) to be able to successfully upload large XML files.
It looks like you're new here. If you want to get involved, click one of these buttons!