Squid

https://www.php.net/manual/en/migration70.php

If you go to the project page, there's a complete forum for support there.

@Djoss has a filebot app in the Apps Tab which is supported if your issues don't get resolved here.

post /config/plugins/dockerMan/templates-user/fogproject.xml from the flash drive

You could always remove the container, then Apps, Previous Apps, Reinstall it and enter in the UI before hitting apply.

Just tried on fresh installs on Chrome, Firefox, Edge, and Brave. No problems populating the autocomplete

Execution Errors when Starting an app means that there is a problem with the docker "run" command for whatever reason (probably conflicting port or something). Post the docker run command as per https://forums.unraid.net/topic/57181-real-docker-faq/#comment-564345

Best place to start would be to post and ask a specific question in it's support thread

You can change the name all day long to suit.

You can edit the template, switch to advanced mode and change the webUI entry accordingly (if the field doesn't appear then you will also have to enable template authoring mode in settings - docker)

Is it on a particular screen, or always? Sent via telekinesis

I *believe* that my PR #473 somehow went into RC6 without my adjustment #477, even though 477 was accepted prior to RC6 being released. Either way, there's no problem with RC7+

Can you post a screen shot of htop after doing this: Launch htop from the command line. Press <F2> key, go to "Columns", and add PROCESSOR under "Available Columns". The currently used CPU ID of each process will appear under "CPU" column. And for sake of completeness, you haven't by chance pinned any containers to those isolated threads?

That looks like an error in the script Sent via telekinesis

The output is actually HTML with some common formatting converted (ie: \n to <br>)

No idea I deprecated it IIRC 2 years ago. tbh I suggest either running corz on another computer against your shares or switch to dynamix file integrity Sent via telekinesis

Now you should check for OS updates and get up to RC7, which doesn't have the problem.

It's because of the word "Share" An ad-blocker seems to think that the whole page is nothing but a link to share something via FaceBook. As an aside, the settings page for Fix Common Problems includes a test that *should* pop up a warning if an ad-blocker is interfering with the UI as a whole (and at least one user had an ad-blocker screwing with the Apps Tab because it had an element called "templates_content" and "MainArea" -> don't those just scream "this is an ad to you?") All in all, everytime an ad-blocker blocks an ad, any given website will change the element's name so that it gets through, and the ad-blocker then has to issue an update to compensate which results in more and more false positives, not just with unRaid, but with any given random website available.

Clicking Help should tell you, but Public - All users have RW access Secure - All users have R access, selected users have W access Private - only selected users have either R, W, or RW access And then you add in "hidden" which means that the user has to know the share name in order to access it as it won't show up in any list

If updating through auto update, update auto update (say that 10 times fast )

Incidentally, still no update showing on the container, the last update on dockerHub shows something like 4 months ago, and the dockerFile listed there doesn't have the quoting. Another thing also if it's possible. Currently the script is storing the intermediate file within the docker.img. Not a problem when I'm doing source files of 1-4Gig, but I will eventually start on doing source files of 50Gig+, and then it will become an issue.

Various coding improvements and minor changes across the board Renamed Trending Apps to be Top Performing Apps, and added in Trending Apps (which is the largest delta of trends) Support appfeed caching of icons * * You'd be surprised at just how many of the templates reference as their icons HTTP instead of HTTPS. CA has handled that for quite a while now, by automatically requesting HTTPS for icons instead of HTTP (it does this so as to not "break the lock" on the browsers by displaying mixed content). But, even with CA doing that, there were still a number of icons which were only available via HTTP and not HTTPS, and a few which in some webmaster's ultimate "I don't know what I'm doing, but they hired me anyways" moment that automatically redirect from HTTPS to HTTP which no matter what I did would break the lock again. Since this really annoyed me, all icons are now cached by the appfeed server and are always HTTPS, so you will always see the icons no matter what, and the lock will never break. The one gotcha though is that should the primary server ever go down, then CA's backup server will feed the original icon URLs which may or may not break the lock depending upon what you're dong.

To each their own. I'll never convince you, and you'll never convince me. But, I am convinced that I'm right

Gamble with what?

ok. How about my philosophy: I would always rather lose some than all in the case of exceeding the redundancy of my parity drives. If I have 3 drives die simultaneously, I figure that Murphy would say that one of those would be the one that has all of my wife's pictures on it, so I always keep data scattered over all drives. I could never understand why anyone would want say all episodes of a TV show stored on a single drive instead of being scattered throughout various drives. Or alternatively, with 2 simultaneous streams happening, with the files balanced out, the odds are reasonably decent that the streams will come from different drives instead of the same drive, reducing thrashing. Hence why I use Most Free as the allocation method, and whenever I increase the size of a particular drive I manually move the files around. To each their own