-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
react-advanced-page-properties - Script Error #4490
Comments
Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible. |
Hello! |
Hello @hugoabernier it is now more than 2 weeks ago that I have posted this issue and it is know one week ago that you have worked on it - as far as i can see. Do you have any update for me on that issue? We really like to use your webpart however we do not know how to solve this error message. Any help or hint is highly appreciated. |
No updates, because I simply review issues once in a while to make sure they are accurate and that the original author is tagged, because ultimately they are the best people to help you here. Unfortunately, all the people who participate in the repository, including v me, volunteer their time to do so. There are no SLAs around how quickly your issue will get resolved -- if it can get resolved. Our best hope is that the original author will receive the notification caused by your initial @ mention, and that they'll take time to help you Best of luck! |
I'm sorry guys, I'm woefully behind on keeping up with this web part and I'm keenly aware that it needs updating for the newest versions of SPFx and PnPjs. I'm also just very swamped right now with some important customer work within Dataverse. I have not even looked at this issue to try and diagnose what it is. I've put it on my list of to-do's and I wish I could give you a timeframe, but unfortunately, I can't right now. |
Hi @mhomol no worries at all. I was not trying to pressure you, but instead to manage expectations. We understand that you're busy and have other priorities. Thank you again for all the good work you do in this community, we're lucky to have you among us! |
@hugoabernier , thank you so much and I totally understand. I don't mind a little fire being lit. :) Still, @PretoPlasma , I can't make any promises, but it is on my radar now :) |
@hugoabernier and @mhomol : thank you very much for your kind and honest reply. I am very happy to know that you have it on your radar! :) As sw dev pro I really understand what you are talking about and I really admire what you all achieve as volunteers. So don't worry and best wishes to you. :) |
This issue has been marked as stale due to no progress in over 90 days. If you are still experiencing this issue, please provide additional information so we can help you resolve it. |
Closing this issue due to lack of activity. If you are still encountering this issue, please do not hesitate to open a new issue. Make sure to follow the guidance on how to create good issues to increase your chances of getting the help you deserve. |
Disclaimer
Yes
Sample
react-advanced-page-properties
Contributor(s)
@Abderahman88 @mhomol
What happened?
When adding the web part to a website this error occurs directly in the edit mode:
Steps to reproduce
Expected behavior
There should not be an error message.
The webpart should be available for further usage.
Target SharePoint environment
SharePoint Online
Developer environment
Windows
Browsers
What version of Node.js is currently installed on your workstation?
16.14.2
What version of Node.js is required by the sample?
v16
Paste the results of SPFx doctor
Additional environment details
No response
The text was updated successfully, but these errors were encountered: