On Page Load not executing

I have a very complex prototype that I have been updating with design changes for a couple of years now. Just recently a bunch of stuff stopped working on it. Some buttons don’t execute their click actions, but most perplexing is that on Page Load, I have a bunch of widgets hiding, but they don’t hide. During troubleshooting I deleted all my pageload cases, and just added two Hide commands. They don’t work. On another page in the same prototype, similar page load cases work just fine, so there is something in this page that is interfering with the page load cases. Any thoughts as to what might be causing this?




Without seeing your .rp file it is hard to say. The fact that it is “very complex” and “a couple years old” are two big hints, though :slight_smile: --also reasons I probably would not want to look at it. But you can always send the file to support@axure.com --they are usually pretty good at figuring out things.

Most browsers have “recently” (in the last year or so) changed the way they handle “automatic actions” such as you might have in your OnPageLoad event. For instance, i have older RP8 files with video links that used to autoplay but now do not, or chains of actions such as checking a global variable and firing an OnClick for some widget–used to work fine, but now works only after a user “touches” a page by clicking anything, scrolling, etc. If a widget is hidden or in a dynamic panel that is hidden, its interaction code cannot be called from an OnPageLoad action, etc.

When running your prototype, you can look at the Console panel to determine what gets called by OnPageLoad and if any subsequent or corresponding actions actually take place. If you have conditions, double-check that they are still valid and all local variables are still pointing to the correct widgets.

in general, my workarounds have been something along the lines of placing my “deprecated page load” interactions on a visible widget in a visible dynamic panel, then shrinking that dynamic panel until nothing inside it is visible in its viewport area (making it effectively invisible to the user), then calling “Fire OnClick” for that widget.

I also experience that issue in RP 9 and my prototype is not that old, but also complex.

@GregoryOR I figured it out: had a looped animation in my prototype which somehow blocked the on-load function. (I fired the same action at the end of the action) Maybe you have also something like that in your prototype.

I’ve sometimes used the console feature in the generated prototype to debug stuff, but it’s pretty primitive really. Often wished it would be a bit more helpful somehow by maybe visually classifying actions to be a bit clearer about what might be stopping something happening, or what actions aren’t being triggered (if that’s a thing?).

1 Like