Meet QuickBox 'Smoked'!

##Feel free to discuss… :stuck_out_tongue_winking_eye:

###Want to install the QuickBox Smoked Theme?

:mega: Theme Switching is now available from your dashboard!

##Updated Theme Install Method

Thanks @Reynald for confirming this method to be working!

You can add a .smoked.lock which the updater (if it dicovers the theme lock) will port in the needed theme assets. You can add this lock by doing

printf "" > /srv/rutorrent/home/db/.smoked.lock

If you want the default theme back then do:

rm -f /srv/rutorrent/home/db/.smoked.lock

Then add the ‘defaulted’ lock file and run the update.

printf "" > /srv/rutorrent/home/db/.defaulted.lock

##The @Reynald method - simple one liner!

Select smoked:

rm -f /srv/rutorrent/home/db/.defaulted.lock && printf "" > /srv/rutorrent/home/db/.smoked.lock && box upgrade

Select defaulted:

rm -f /srv/rutorrent/home/db/.smoked.lock && printf "" > /srv/rutorrent/home/db/.defaulted.lock && box upgrade

I’ve built these in for an addition to the dashboard to swap themes… (that’s coming soon)


lush ! :smiley: good work.

Nice! How may I create a theme on my own?

Best regards

I would suggest backing up the /srv/rutorrent/home directory and then editing directly on top of the current theme. Then simply backup the theme to your local computer for safe keeping. I will be adding a new repo for this new dashboard theme. If you would like do the same, we can ensure that commits are distributed equally among the themes after the theme is approved for inclusion.

Check the /srv/rutorrent/home/inc/ directory, specifically the panel.header.php and panel.scripts.php files for the assets required. Editing the quick.css file is your option as it handles the bulk of the themes css. The quick.css file is located at /srv/rutorrent/home/skins/.

Dripping with sex appeal :+1:

1 Like

Really Nice theme!!!, I just installed:

1 Like

I think I updated at a wrong time haha.

I just updated the OP. Did you issue a restart to apache after the update?

Yeah but its okay I will do a fresh install this month anyway since Im not happy with my filestructure and Im too lazy to manually fix all of it.

You sound exactly like me… File structure sloppy? Redo!

I haven’t tested the upgrade of the theme enough to say the update is stable, however; the git commands should work to pull the update. I will run a few tests on a clean install and check this out.

Nuke it from orbit and redo is often times much better for plex since I had a lot of issues with nonexisting files (after changes) that dont get deleted ><

Also I have a lot of japanese named music which plex doesnt scan properly so I have to edit the tags in the next version… Filebot works kinda but I think I have to do them manually with beets or something similar.

1 Like

Hello there,

I get a small error when trying to get the theme.

[13:12 root@qb home] > git init
Reinitialized existing Git repository in /root/QuickBox/.git/modules/dashboard/
[13:12 root@qb home] > git remote add -t * -f origin
fatal: remote origin already exists.

Thank you for your help

Do the following as I spaced that it has already been initialized by way of the default dashboard repo.

cd /srv/rutorrent/home
rm -rf .git

Then follow the process once more.

That dit the trick thank you.

now I have the same issue as chKaze :confused: (half both themes showing)
I try updating both themes as you said but I get an error with the defaulted one:

[13:29 root@qb home] > git pull origin defaulted

  • branch defaulted -> FETCH_HEAD
    Auto-merging skins/quick.css
    CONFLICT (content): Merge conflict in skins/quick.css
    Removing skins/bootstrap.min.css
    Removing js/bootstrap.min.js
    Auto-merging index.php
    Auto-merging inc/config.php
    Removing img/switch-notinstalled.png
    Removing img/switch-installed.png
    Removing img/logo.png
    Auto-merging db/.gitignore
    CONFLICT (content): Merge conflict in db/.gitignore
    Automatic merge failed; fix conflicts and then commit the result.

Will you do git reset --hard origin/defaulted and see if that has better results? Also, service apache2 restart afterwards to clear cache on the server.

Same with chKaze and coolmansr. I tried doing the git reset and restarted apache but results were the same

Could one of you PM me so I can check this out on your server?

Did you try resetting your browser cache?
For me it did the job.
Everything is working as it should be now.

Durp, then there’s that… browser cache. Good catch there @coolmansr1 :thumbsup:

Oh derp. Yep, that did the trick!

And its B-E-A-U-tiful! :astonished: Well done!