Skip to main content
Nintex Community Menu Bar
Question

Unable to package pages into Static Resource (Release 10.0.1)

  • July 10, 2024
  • 13 replies
  • 1 view
  • Translate

Forum|alt.badge.img+4

Upgraded to 10.0.1 - Can no longer package pages into Static Resources.  The page hangs and just says “Packaging Pages into StaticResources…”

Did this topic help you find an answer to your question?

13 replies

Forum|alt.badge.img+10

Are you trying to bring in an old Page Pack or are you trying to bring in a new one you’ve made while in 10.0.1?

Translate

Forum|alt.badge.img+4

Not trying to bring one in.  Just trying to create the Page Pack. 

Translate

Forum|alt.badge.img+4

This is the screen that it hangs up on. 

Translate

Forum|alt.badge.img+3

also running 10.0.1 and not having the issue reported
(mac 10.2.5 skuid 10.0.1 chrome 59.0.3071.115)

Translate

Forum|alt.badge.img+10

I can get mine to hang like that when I try and package the “Skuid” module. However, I can still create page packs in other ways. Can you give more specific detail to clarify what you’re doing? The more detail, the better. 

Which module are you trying to page pack? 
How many pages are in that module?

Translate

Forum|alt.badge.img+4

Custom module - not Skuid trying to pakage the Skuid module.  This custom module has been packaged before successfully.  There are 25 pages in the module.

Translate

Forum|alt.badge.img+4

I have split into 3 separate modules to reduce the number in each, and trying to package one at a time, still same issue. 

Translate

Forum|alt.badge.img+13

Any Javascript errors in the console?

Translate

Forum|alt.badge.img+10

Zach, we have another customer claiming the same issue saying no errors in the console.

Translate

Forum|alt.badge.img+9

I had the same issue with trying to package pages in a custom module from the global action. I was able to get it to work using the mass action after multi-selecting the pages I wanted to package and selecting ‘Existing Page Pack’

Translate

Forum|alt.badge.img+4

I have nothing in the console.  

Translate

Forum|alt.badge.img+4

Thank you Craig.  This method worked for me as well.  I was able to create the page packs successfully this way.  Having said that, I did get one error in the console that may / may not shed light on the issue affecting the global action???

Translate

Forum|alt.badge.img+6
  • 62 replies
  • July 10, 2024

This helped me a lot, though may have a question for Skuid. As we were putting this into a managed packaged and had not yet created a page pack, I had to make up my own name for one since no “Existing”. I used our namespace. Hoping there were no naming requirements for it.

Translate

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings