-
Notifications
You must be signed in to change notification settings - Fork 23
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
Internal Server Error on CTFd 3.7.3 #92
Comments
I will note that using the core-beta that shipped with 3.7.3 works fine -- but changing to |
@hiisukun Very recent change that has not shipped in a proper release yet CTFd/CTFd@ac8c46d We could issue a 3.7.4 release but I think it would be better for you to work off of CTFd master because this light/dark theme change has not really baked a lot. Alternatively you could remove this line: https://github.com/CTFd/core-beta/blob/main/templates/base.html#L17 and inline the code as shown here: 81c8774#diff-690b81fad8df2a1f1ce37c846641d9247e3472d244f17039d2910a5ed0c98d5e |
Excellent, thanks @ColdHeat - that worked a charm. I think it resulted in my CTFd being in dark-mode (though it's night time here..) but that's no issue. Is the And thanks for the fast reply! : ) |
I think there are some rough edges with dark mode but it works well enough. Aside from the assets.py change there's nothing in it that should cause any breakages. |
G'day mate,
We just finished running a CTF -- based on the core-beta skin on 3.7.3.
Cheers for the help getting things up and running with assets.py -- we did
end up sticking with that version.
I attached a pic of the interface after we were finished fussing with it,
which wouldn't be possible without your great work on CTFd.
Cheers,
- Heath from Australia
…On Sun, Sep 8, 2024 at 3:05 AM Kevin Chung ***@***.***> wrote:
I think there are some rough edges with dark mode but it works well
enough. Aside from the assets.py change there's nothing in it that should
cause any breakages.
—
Reply to this email directly, view it on GitHub
<#92 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC3PNH3SCAFNAF73QCUHWI3ZVM2NDAVCNFSM6AAAAABNZNIHQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZWGE3DKMRRGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hello, FYI there is nothing attached. Not sure if GitHub respects email
attachments.
…On Fri, Oct 4, 2024 at 4:06 AM heath ***@***.***> wrote:
G'day mate,
We just finished running a CTF -- based on the core-beta skin on 3.7.3.
Cheers for the help getting things up and running with assets.py -- we did
end up sticking with that version.
I attached a pic of the interface after we were finished fussing with it,
which wouldn't be possible without your great work on CTFd.
Cheers,
- Heath from Australia
On Sun, Sep 8, 2024 at 3:05 AM Kevin Chung ***@***.***> wrote:
> I think there are some rough edges with dark mode but it works well
> enough. Aside from the assets.py change there's nothing in it that
should
> cause any breakages.
>
> —
> Reply to this email directly, view it on GitHub
> <#92 (comment)>,
or
> unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AC3PNH3SCAFNAF73QCUHWI3ZVM2NDAVCNFSM6AAAAABNZNIHQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZWGE3DKMRRGU>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub
<#92 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABITPONYMBIPCPUTJFGFOLZZZEABAVCNFSM6AAAAABNZNIHQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJTGA4TGOJYGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hey team -- I cloned core-beta from
main
today, ranyarn build
without issue, but when I put the theme in a fresh CTFd:3.7.3 container I get "Internal Server Error" when loading the CTFd instance root/homepage.The container log shows
TypeError: _AssetsWrapper.js() got an unexpected keyword argument 'type'
.Any suggestions? I'd like to use a CTFd 'release' that is tagged, so if there is an older core-beta commit I need to work from that might be fine.
Here's the full log:
The text was updated successfully, but these errors were encountered: