mirror of
https://github.com/simonmicro/Pritunl-Fake-API.git
synced 2026-04-26 07:36:00 +03:00
[GH-ISSUE #19] Update for Pritunl v1.30.3112.0 #16
Labels
No labels
bug
bug
enhancement
help wanted
invalid
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Pritunl-Fake-API#16
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @MANKUD on GitHub (Mar 21, 2022).
Original GitHub issue: https://github.com/simonmicro/Pritunl-Fake-API/issues/19
Hello,
The updated script does not seem to be working on the latest release pritunl v1.30.3112.0. There are changes made in the subscription.py file.
github.com/pritunl/pritunl@97f08a9ad6@simonmicro commented on GitHub (Mar 21, 2022):
-> for more context: https://github.com/simonmicro/Pritunl-Fake-API/issues/18#issuecomment-1074505700 (and following)
@MANKUD commented on GitHub (Mar 21, 2022):
why do you think he deleted them here?
github.com/pritunl/pritunl@cc02ed7ab0@simonmicro commented on GitHub (Mar 21, 2022):
Performance? Complexity on his side? Idk. To fix this I have to dive deeper into the inner workings of Pritunl anyways, so I can't say if this patch was even the real reason...
@MANKUD commented on GitHub (Mar 21, 2022):
"Performance? Complexity on his side?" Makes sense and I hope for the best 😄
@MANKUD commented on GitHub (Mar 21, 2022):
Hi did you notice the path?
github.com/pritunl/pritunl@cc02ed7ab0pritunl/handlers/subscription.py kind of weird
@simonmicro commented on GitHub (Mar 28, 2022):
Hehe - found something... The file
/www/vendor/dist/js/main.***.jschanged:to
..which seems to break
enterprise-plus/ultimate(seewindow.subPlan). To unbrick the subscription dialog you could execute this in the console:Otherwise everything seems to work fine...
@simonmicro commented on GitHub (Mar 28, 2022):
Well, the previous changes were reverted and the JS changed a bit. We are up and running again...