Tips and Tricks HQ Support Portal › Forums › WP Photo Seller › WP Photo Seller – watermarks will be partially the double size as the originals
Tagged: large watermark images
- This topic has 2 replies, 2 voices, and was last updated 7 years, 10 months ago by plinden.
-
AuthorPosts
-
January 24, 2017 at 12:41 pm #13952plindenMember
Hello
it’s me again. But this time with a technical problem.
My speciality are large-format panoramas. Some panoramas have a resolution of 25000 and more pixels on the long side and a total of 200-300Mpx resolution.
I save the panoramas with a JPG compression of 70%, so that the file sizes do not exceed 20MB if it´s possible. I think the plugin gets problems with such large files. The system is extremely slow and there are always error messages until all background processes are completed.
Currently I build my shop in a local test environment. Ok, my test server is an older PC under WIN10 and the latest XAMPP version, but if it runs well on my test server, it should run well on the provider´s server.
The biggest problem are the files with watermarks. These will be partially the double size as the originals. I would like to attach you a screenshot, but this does not seem to go.
I wonder why the files with the watermark should have the full resolution. They are essentially needed for the lightbox. The current top monitors have a 4k resolution, so the files with watermark do not need to be larger. If the files are still stored with a compression of 70% or 80%, they should be very small, but the quality is still good.
In my opinion, watermarks for the zoom or magnifying function on the details page are not necessary. The plugin could there directly access to the original files. I´am think, the risk of copying pictures unauthorized, in this case it´s very unlikely. This would significantly accelerate the performance of the system, which would also be an advantage for the Google search.
I have now placed the shop via a subdomain on the Internet. The behavior is better than in my local test environment but the basic problem remains.
Do you see a possibility to adapt the plugin in this direction?
January 25, 2017 at 5:23 am #75008PeterMemberif it runs well on my test server, it should run well on the provider´s server.
The biggest problem are the files with watermarks.
This is the key point. If I understand you correctly you are saying that the photo seller runs ok on your local development environment but not on your server?
If that is the case, the issue you are seeing is server and resource-based.
Are you on a shared server or VPN or dedicated server?
Regarding the watermark files – I think you make a good point with respect to the full resolution. However I will need to look at the code to see how much work is required to make it possible to produce a lesser resolution watermark file.
January 25, 2017 at 10:15 am #75009plindenMemberHi Peter,
because I´am not expressed clearly. On my test server, I have bigger problems than on the server at the provider. The server at the provider is a shared server (50 clients per server), my test server is an old PC which I use only as a small WEB server.
On my test server values like memory_limit and max_execution_time I have already raised. Memory_limit to 1024MB and max_execution_time to 45 sec. But anyway, uploads with large files >20MB break off. Usually with an http error.
This is the one problem, but the extremely large files with watermark are even more problematic. The access to the light box becomes very slow and that frightens customers. On the very large files in a pinch, I can do without it, but the front end should have a good performance.
You can take a look at the shop here: http://test.pl-fotodesign.de/
For a gallery, the following error message is displayed:
Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 24576 bytes) in /www/htdocs/w00a0e65/nplf/wp-content/plugins/wp-photo-seller/models/WPSCommon.php on line 2894
Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 40960 bytes) in /www/htdocs/w00a0e65/nplf/wp-includes/wp-db.php on line 1171
with best regards
Paul
-
AuthorPosts
- You must be logged in to reply to this topic.