horst

For me, uploading a file/image from URL works by simply copy paste the URL into the upload inputtextfield. The browser / OS does all necessary then.

You should check via phpinfo if there are more disabled functions or more restrictions on that hosting account. If yes, I would overthink to upgrade or switch to another.

That is correct. Additionally you can send the language files to the maintainers of language packs. I think that editors don‘t get the core backend untranslated, but need a single module translated. (What also can be done with one additional step, if the language files are distributed together with the module) For me it doesn‘t look that bad as described by @dragan.

Many thanks for the suggestions, @Robin S I think the main check / exception must be in the getExif method. A check during install will be useless when deploying a site folder from local to stage or live. But it is no harm to have it too. 👍

@Gadgetto You may ask the maintainer(s) of the (german) language pack to include it.

What do you think would be the best way? Returning false or throwing an exception?

@Arctic This may help you going:

There is no argument to the method page::getFields() https://processwire.com/api/ref/page/get-fields/ https://github.com/processwire/processwire/blob/3bf29d050b7f542f04628fc69c2448466e167acd/wire/core/Page.php#L1274-L1299

You can mimic a basic authentication in the file "site/templates/admin.php" Therefor you have to handle a set of valid usernames and passwords in that file too, like in the following example: <?php namespace ProcessWire; $validUsers = [ 'user1' => 'pass1', 'user2' => 'pass2', 'user3' => 'pass3' ]; $validAdminUser = false; if(isset($_SERVER['PHP_AUTH_USER']) && isset($_SERVER['PHP_AUTH_PW'])) { if(isset($validUsers[$_SERVER['PHP_AUTH_USER']])) { if($validUsers[$_SERVER['PHP_AUTH_USER']] == $_SERVER['PHP_AUTH_PW']) { $validAdminUser = true; } } } if(!$validAdminUser) { header('WWW-Authenticate: Basic realm="Adminsection"'); header('HTTP/1.0 401 Unauthorized'); echo '401 Unauthorized! Accessing this page needs a valid useraccount!'; exit(); } require($config->paths->adminTemplates . 'controller.php');

Does it all also not work when executed in the ready.php?

Kids are, - hmm, well, - mysterious. Many, many years back, when I bought my first pelican case, you could read something in the warranty description like: :-)

Yep, I think the most tips above linking to the blog are only valid for greater pw versions. (Dev-Branch)

Which pw version are you running?

Hi @alanxptm, this is already there in the edit screen for roles. See the screenshot. You need to tip the checkbox and are done.

Instead of that, you can delete the imagefile. Then the frontend page and the admin page will load again. To prevent this in the future, you may configure a setting for max filesize in those imagefields for uploads. (NOTE: not max dimensions, but max filesize and set it do be handled on clientside, not serverside) I think there is a module available for this max-filesize-setting, but can't remember it's name. (ping: @Robin S do you have created one with this feature?)