You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using Pyrevit 5.0.0.24227 WIP.
urlbutton doesn't work with Revit 2025, However, It works fine inside Revit 2023, 2024
⌨ Error/Debug Message
An error occurred trying to start process
' https://status.bluebeam.com/' with working directory
2025'. The system cannotfind the file specified.atSystem. Diagnostics. ProcessStartWithCreateP rocess(ProcessS..startlnfo)at System. Diagnostics. ProcessStart(ProcessStartlnfostartlnfo)atPyRevitLabs.PyRevit.Runtime.HyperlinkEngine.Execute(Script..runtime)
♻️ To Reproduce
Install WIP 5.0.0.24227
Start Revit 2025
click on a ulrbutton (like the Regex tool)
⏲️ Expected behavior
Clicking a urlbutton show open a url using the webbrowser.
🖥️ Hardware and Software Setup (please complete the following information)
Windows 11 + Windows Defender + Crowdstrike Falcon
Revit 2025
Pyrevit 5 WIP
Intel Processor + Nvidia GPU
The text was updated successfully, but these errors were encountered:
tay0thman
added
the
Bug
Bug that stops user from using the tool or a major portion of pyRevit functionality [class]
label
Aug 14, 2024
tay0thman
changed the title
[Bug]: Broken .urlbutton / HyperlinkEngine in 2015 #Pyrevit5 #Revit2015
[Bug]: Broken .urlbutton / HyperlinkEngine in 2025 #Pyrevit5 #Revit2025
Aug 14, 2024
tay0thman
changed the title
[Bug]: Broken .urlbutton / HyperlinkEngine in 2025 #Pyrevit5 #Revit2025
[Bug]: Broken .urlbutton / HyperlinkEngine in 2025 [Pyrevit5] [Revit2025]
Aug 14, 2024
✈ Pre-Flight checks
🐞 Describe the bug
Using Pyrevit 5.0.0.24227 WIP.
urlbutton doesn't work with Revit 2025, However, It works fine inside Revit 2023, 2024
⌨ Error/Debug Message
♻️ To Reproduce
⏲️ Expected behavior
Clicking a urlbutton show open a url using the webbrowser.
🖥️ Hardware and Software Setup (please complete the following information)
Additional context
@dosymep @sanzoghenzo
No response
The text was updated successfully, but these errors were encountered: