Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v4_0_45 causes issue on Power Apps Portal, list are no longer rendered due to poor network connectivity #577

Open
rogercote8 opened this issue Aug 17, 2022 · 8 comments

Comments

@rogercote8
Copy link

All of our Portal used the run version at ESDC. After the release last night we ran into an issue with rendering some part of our web sites. We have determined that the issue was caused when executing wet.builder.refFooter. When this is executed, the site will not work well for Firefox and Chrome and only work for some people with Edge. It seems to be caused by a very slow load of your code. The issue goes away when we do not execute wet.builder.refFooter.

In order to solve the issue, we have reverted all of our Portals to v4_0_43 and will not be using the run version until further notice. Take note that the Microsoft Power Apps Portal only support bootstrap v3.3.6 (may be related).

The issue we are experiencing is the rendering of a list of records. Because of what appears to be the slow load of your code, the list of records does not make it into the browser and then nothing shows.

image

The second image is showing the error:

image

When we revert to v4_0_43, we do not experience problems.

@ahmad-shahid
Copy link
Contributor

Hello, as a version release, v4.0.45 has been out for about 3 months now and we haven't had any issues regarding network connectivity. I'm guessing this may be specific to Power Apps Portal.

Just for diagnosis, have you tried using v4.0.44 to see if this issue happens? It'll be easier to determine which version this issue started happening in. Thanks!

@rogercote8
Copy link
Author

rogercote8 commented Aug 18, 2022 via email

@ahmad-shahid
Copy link
Contributor

I'll investigate on my end but it looks like document.write to be the issue. Good news is that we are in the process of introducing a new way of implementing CDTS without the use of document.write. I believe this should solve this issue. We will be releasing this as part of v4.0.46.

@rogercote8
Copy link
Author

rogercote8 commented Aug 18, 2022 via email

@ahmad-shahid
Copy link
Contributor

Hello, I would like to further investigate this issue as I want to be certain whether this issue is linked with CDTS, document.write, or with WET.

Do you have a development environment of some sort that I can use to troubleshoot this problem? Or any other way of accessing Power Apps Portal? Thank you.

@ahmad-shahid ahmad-shahid modified the milestone: v4_0_46 Nov 2, 2022
@Dan-Levesque
Copy link

@ahmad-shahid I believe this issue is because Power Apps Portal (renamed by Microsoft to Power Pages now) only supports Bootstrap v3.3.x for now. They announced plans to support v5.x in the future, but if CDTS is stuck at Bootstrap v4.x we will be having the same problems again. When is the CDTS team going to support Bootstrap v5.x? Is there a timeframe?

For more info on the Microsoft official support of Bootstrap, visit this article: https://learn.microsoft.com/en-us/power-pages/configure/manage-css

@ahmad-shahid
Copy link
Contributor

Hi @Dan-Levesque, we are dependent on WET for this so as soon as WET starts supporting Bootstrap v5, we will update on our side.

@rogercote8
Copy link
Author

2 things
First: Do you have any information regarding WET moving to Bootstrap 5.0?
Second: Regarding the update to the footer applied in version v4.0.47 and must be released at the latest on March 17, 2023, as you know, for users of Power Pages, we still have the issue and we cannot use v4.0.47. We are stuck using v4.0.43. The update to the footer would not be applied for our websites. Can we get an official exception for the footer until the issue is resolved between Power Pages and WET?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants