David Karich
Members-
Posts
191 -
Joined
-
Last visited
-
Days Won
4
David Karich last won the day on March 13 2023
David Karich had the most liked content!
About David Karich
- Birthday 06/19/1986
Contact Methods
-
Website URL
https://www.flipzoom.de
Profile Information
-
Gender
Male
-
Location
Bad Breisig, Germany
Recent Profile Visitors
11,108 profile views
David Karich's Achievements
Sr. Member (5/6)
352
Reputation
-
The link to the beta download unfortunately ends in a 404 error. 🫠
-
Thanks a lot for this amazing feature! 🙏🏻
-
Well, I’d let the user decide whether to use Option A or B. Although I don’t really see any practical use for use case A. Why would the image need to be displayed distorted? In principle, I’d change the new dimensions and warn the user if they differ from the original, then list all the places where changes have been made.
-
To be honest, I wouldn’t do that. Sometimes, for example when replacing a logo, the graphic simply has different dimensions (because it’s a different logo or partner, for instance, but is to be placed in the same spot). The same applies, for example, when the styles of images change as part of a design overhaul. For instance, square images used to be used for contact persons, but now the client wants portrait format. In that case, a simple swap wouldn’t be possible if there’s a restriction on dimensions.
-
I think you’ve identified all the pitfalls quite well. To me, it reads like a well-thought-out plan. One pitfall in my use cases would be ProCache: if ProCache is in use, the pages that reference the modified asset should be removed from the cache. Otherwise, on-the-fly regeneration won’t be triggered the next time the page is loaded, and the page will refer to the old, deleted file – which may even have had a different filename – resulting in a 404 error. As this replacement process can trigger many background processes, depending on the amount (e.g. clearing ProCache pages for hundreds of items), an informative loading indicator in the UI should be used to show users what is happening at any given moment. In principle, it’s also worth considering whether, when uploading the asset to be replaced, you should ask whether the filename should be retained from the original or renamed to the new one.
-
David Karich started following MediaHub
-
MediaHub 1.19.51 - available + offer
David Karich replied to Peter Knight's topic in Modules/Plugins
Must have Module! 🚀 -
@Roych It looks promising so far. Thanks for the module. Custom event tracking and goal tracking are features I personally would still like to see. Plus conversion rates based on that data. Have you already run a performance test using long-term data and a large number of visitors? How does this scale over the long term? For example: I have sites with 6 million unique visitors per year and a tracking history spanning 15 years. Does the module still run stably with such large data volumes?
-
It's not possible to upload a profile picture in the forum
David Karich replied to David Karich's topic in General Support
Hmm, not the best solution. 😅 I've tried it about 30 times already today. -
A quick note about the new documentation: the table layouts in the accordion sections don't work on mobile devices. They aren't scrollable. 😊
-
Fantastic. You've already won my heart. 🤩 P.S.: @Peter Knight, this raises another question for me: have you also planned a ‘delete protection’ feature? When an image is deleted from the Media Hub, is it first checked to see whether the image is used on any pages? If so, deletion is not possible and there is an option to list all the pages where the image is used?
- 37 replies
-
- 1
-
-
- media upload
- media
-
(and 3 more)
Tagged with:
-
Hi @Peter Knight Thank you very much for the pre-analysis. 😊 It is correct that the sheer number of pages is not the problem. I have already achieved good performance in tests with half a million pages. The real problem occurs more during output: the limit here is often the RAM limit of the PHP process. Example: You have an image field for a gallery. In this gallery (here as an example from one of my customers, an event), there are easily between 100 and 200 images per input field. When outputting to the front end – and also in the back end when editing – you run into a MAX RAM problem and very long loading times, as each image object is loaded into the RAM. Here, I now see an additional problem with the ‘1 asset per page’ approach: not only is the image object loaded, but also the complete page object where the asset is stored. And if I understand your concept correctly, the master page object of the asset is also loaded. This means, to stick with the example, that with 100 images, around 300 objects are loaded into RAM just to output them. This is overkill for most servers (especially shared hosting). One possible solution here would be to implement a kind of ‘getRaw()’ method, similar to ‘findRaw()’, which returns all asset paths (including variation paths) and descriptions as a simple array – without the complete object. This would make it easy to iterate over the array and output the images directly. I am aware that this would then make it impossible to use ‘size()’, ‘width()’ etc. and all the image methods. What do you think of this option for special use cases with many assets that need to be loaded at once? And thank you again for your truly great work and your ambition to develop such a complex module!
- 37 replies
-
- media upload
- media
-
(and 3 more)
Tagged with: