1) To make what I just posted pics of work, it's currently necessary. It shouldn't be for (hopefully) the next release of Ubooquity. Because of this I'm holding off on releasing it until then.

2) If it isn't part of the next Ubooquity release, the necessary readme will accompany the release of this new theme version.

The default theme has a random button for comics/books that goes to /comics/?random=true and /books/?random=true respectively. I didn't have any use for this before, so I hid the control.

This is reading the random and latest pages and copying the issues from it (hence not being able to go beyond the comics-per-page setting). And yeah, when you refresh the page it re-queries the random page and gets new results.

I also added a link to the Random page under the Browse drop-down too, since there was space.

Going deeper down this rabbit hole, more and more dependent on javascript-support being added to themes stock. One of the opportunities this opened up was a more useful homepage.

You can set in the theme how many random/new comics to add to the page, it defaults to 30 (it can't be any higher than your comics-per-page setting). It'll load your bookmarks if you have any, or hide the control if you don't.

While this shows Latest Comics/Random Comics, if you have Book-sharing enabled it will also show Latest Books/Random Books.

The cookies themselves do timeout, though it's pretty long. Using the same device across multiple network connections isn't exactly as insecure as a page being wide-open.

You made it sound like you were using different devices at home/work, which would mean multiple browsers/devices are sharing a cookie, hence assuming Chrome.

Many other services that use cookie-based authentication would (and do) operate exactly the same way

Umm, authentication for both users and admin are cookie-based. Trying the direct url to the admin page from a different browser (or incognito mode, if you only have the one browser) will prompt for a password again.

Let me guess, Chrome user? Did you know if you're authenticated with your Google account, cookies can transfer from client to client? Yup, it can. And it sounds like exactly what's happening.

Is the UI rewrite more backend stuff, or should we be braced for broken themes?

After helping mediabot666 with some code to load Javascript across all of Ubooquity, I was inspired to finally fix some things that were bothering me about Ubooquity theming. The downside is, this theme needs you to use javascript injection. Because of this, I'm hesitant to release until something like this is supported by Ubooquity natively.

Just to give a good idea of what you're looking at:

• Bookmarks have been centralized. Since this applies across all of Ubooquity, you can bookmark books too.
• Home always goes to the homepage, no matter what page you're on. The page headers are better for navigation anyways.
• New and Browse adjust based on what the user has access to. If you only have comics setup, New is a button, and Browse has "Publishers" and "Story Arcs". If you have just books, New is a button and Browse lists "Authors" (just the base of books, the equivalent of Publishers. If you have both enabled, like I do, New becomes a menu and Browse shows all 3.
• If you have Files enabled, it shows as it's own button.
• This new nav bar sticks to the top of the screen if you scroll down, like on Comixology itself.

• Page controls have been redone. Rather than fighting with css, I went with jquery to move the elements, so they always line up correctly. And the page number always shows, even on searches.
• There's a persistent footer (which I haven't figured what all to put in yet). Rather than just the current one-liner.
• The search bar shows on all pages, with an option to set what it searches by default (while navigating books, it'll search books, comics while navigating comics. The setting would control while on the homepage/bookmarks/admin/etc.).

http://ubooquity.userecho.com/topics/27-comixology-theme/#comment-2382 :)

So arcBuilder is (or at least should be) using idGet to find the issues for the arc in Ubooquity, and save them into a csv file. The arc page then parses the csv to show the issues.

How are your comics setup, folderwise?

It's hardcoded looking for "Series (Year)" as the series, then looks for filenames containing "Series Issuenumber (Year)". If your comics aren't setup that way, it won't be able to find the issues and you end up with a blank csv.

You're blending what you're reading from my posts and mediabot666's. The path to your arc folder should be in arcBuilder.sh, not passed as an argument. The syntax for my arcBuilder is just:

arcBuilder.sh 'name of arc'
Pretty sure this is why his later release was named arcScanner.

If you're trying to use his instead, he'll have to assist. I never personally got it working.