Method Community

I added next /previous buttons to some screens in the portal. I placed them at the bottom of the screen to move through the different tabs I created. These worked great.

I then added some new buttons that I placed at the top of the screen that are calling the same action step as the bottom buttons to move through the screens and they dont work.

Quite strange. The really odd thing is they work fine if I am looking at the screen logged in as me as the user. Its just the portal they dont work in.

thanks

Ben

Hi Ben,

I haven't been able to replicate this.  I put buttons on the bottom to move through the tab links in the portal.  I then created buttons at the top and used the copy action to copy the actions of the bottom buttons.  On your screen, are you getting an error of some kind?  Or is nothing happening?

Can you double check the actions on the top button?

- Adam

No error, the buttons dont register any kind of click.

Very Odd. Like I said the buttons work fine logged in as user, just dont work in portals.

Ben,

Yes, that seems very odd.  So the top buttons don't work when in the portal, but the bottom buttons always work?  I still can't replicate this, so could you enable Method Support on your account and email me the company acount and the screens?

- Adam

Were you able to reproduce this error? Need to go live soon, so wondering if I should just remove buttons for now?

Ben,

Still haven't been able to reproduce it.  I've reached out via email with a couple of questions.

- Adam

Ben,

Just a thought... Could there be permissions issue with your screens. Are portal users allowed to see them vs you when you are logged in?

Fran

Nope, doesnt work whether I am logged in to portal or another use, but does work when I am testing it inside of method.

I have created a work around for this bug by putting a banner (picture) at the top of our portal. It seems like there is an area at the top of portals inside of frames that is not receving mouse input. Fortunately the client likes the banner but I am working on other portals where I cannot use this work around so keep trying to fix 

Ben,

We'll certainly continue to work on this.  I'll be sure to keep you posted.

- Adam