horst

Look / debug what you get from ->images->getRandom(), maybe via die(var_dump($randomImage)); Then you will know what to do, or you come back with the new information and ask how to proceed further.

Hey @teppo, the user 8-bit-guy is one of my sons favourites. My 12 years old son loves to work and hack retro hardware, like commodore 64 and a whole bunch of gaming handhelds or consoles, (besides others). Every third or second time, when he get something to work, and I ask him how he got it to work, he answers: "I found some useful information from the 8-bit-guy."

Cool specs!

Yep, it then definetly removes all variations. But in some cases it may become handy to use a scalpell instead of a hammer. For example, if you use the same images in different locations, as with centralized image pages, you may have a total of 100 variations but only 7 do belong to your current template. Just a thought: Maybe a programmatically created suffix, based on the (page | template | imagefield), can be embedded into the variation names? This way, you only need a delete-function that gets passed that suffix, to remove only variations containing it in their names.

Yep, I know. My comment was addressed to Bernhard and his main question in this thread. Sorry for being unclear.

This will not work well together with a centralized (and included) version number. There are multiple possibilities to mix wrong files together. My personal conclusion is to keep the version number hard written in each class file, ( the old schooled way).

You need wireHTTP to send a GET or HEAD request to get back the status code.

What about a proxy script on site B that gets invoked via htaccess for all images coming from site A. This script determines which variation is desired and redirect to it on site B. If the desired variations are yet not pre created, the script from site B must talk to a script on site A that is possible to create a variation before finally redirecting to it.

Hi, thank you for the write up. For me it looks you found the right balance for beginners and experienced users. A following second part would be very nice and useful. Additionally to that, if you don't mind, I would be interested in a third part too. This one should cover how the function(s) recognize or act upon changes of a focus point or zoom value, if used. Does it recognize it, and recreate all variations? Do you also include / provide or already use a function to remove exactly the previously created variations? Maybe useful during developing a side, when my first used sizes need to be adjusted. (Otherwise I would have a lot unused variations). If you don't use this already, I think it could be done very easy by using a suffix for the variations.

Hi Bernhard, Q: .. and when the changelog.md has gone, (by accident of corse)? The modules are PHP, why not using a PHP file and including this? I think with a PHP file, people will be more careful then with a readme, or changelog file. public static function getModuleInfo() { include(__DIR__ . "/version.inc.php"); // the inc.php contains a var $moduleVersionNumRockGrid, which holds the current version return array( 'title' => 'RockGrid', 'author' => 'Bernhard Baumrock, baumrock.com', 'version' => $moduleVersionNumRockGrid, 'summary' => 'RockGrid Main Module', 'requires' => ['RockFinder'], 'installs' => ['InputfieldRockGrid'], 'icon' => 'table', 'autoload' => true, ); } This way, you can style your changelog file to match @netcarver desired formats for programatically read those in.

upload_max_filesize & post_max_size have nothing to do with memory_limit! try: php_value memory_limit 256M // or 512M Also, post_max_size has to be 20 or 30 percent greater then upload_max_filesize!

@iNoize, I cannot get the context between your question and this more then six years old thread. (?) If you have posted here by accident, please tell us and I/we can move your post to the right direction.

or if even needed more early, but thats not very common, add it into your site/config.php.

Definetly, the quality of DeepL is double, triple or quadruple the quality of g**gle translate. Regarding the API usage, what is a pro or paid feature, I understand it as a monthly price of 20 €, (but only up to 1.000.000 words), what results in a yearly cost of 240 € per user, regardless if you translate 12.000.000 or 0 words.

Congrats for the new site! ... and, as always, the good write up! --- --- --- I never forgot your first case study here back in 2014. Especially one post a bit down in the thread: --- --- --- There is only one question I have: Why you’re called Pigtail Pundits?